Disclaimer:
I have the same problem this guy have:
http://forum.xda-developers.com/showthread.php?t=1036327
But no one in the thread was able to understand him, so I'm trying to open a new thread to organize the thoughts (there are too many people with too many problems posting there).
What happened:
I have a 1-month-old Defy. On the 2nd day I already had it rooted, running froyo (with Pays ROM), overclocked, undervolted and all this stuff. Three days ago, suddenly, it started to FC apps randomly. So I wiped. Then it became stuck on M logo. No big deal.
I tried then to reflash the SBF via RSDLite, but for some reason I only had the previous SBF (3.4.2-155-2) and my phone was running on 3.4.3-11. Don't know if it has downgradeability issues, but I couldn't flash it. It threw some checksum errors in the process and wasn't able to finish the process. Then my phone became "Code Corrupt". I was still able to see it in RSDLite. No big deal.
I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal.
I read about the MacGyver method, but prefered instead to use a universal charger to charge my battery. Was charging all night, seem to work on other defy (tested it later). But, now, my phone makes no response to battery insertion. Not even power+vol up, nothing. No white led, no bootloader, no code corrupt, no nothing. Ok, that's a big deal.
If I connect it to USB, nothing happens. No driver instalation, no device recognized, no RSDLite, no bootloader, no white led. Nothing.
The only response I have from the phone is: if I pull the battery and put it again while connected to USB, the computer will make an USB connection sound, then 2 seconds later, it makes an USB disconnection sound. If I open the device manager, it shows the Motorola Device for 2 seconds (OMAP something) and then it desapears. So I'm not able to see it in RSDLite.
I tried even to power up the phone with the MacGyver-crafted USB cable (with and without battery inserted together), but the computer response is the same. That is the only thing that makes me believe that my Defy isn't entirely dead. But isn't much useful after all.
Hope I explained it well. I'm one of those guys who doesn't speak english well, so I hope you guys understand me . Thanks in advance.
I would really like to be helpful, but it looks, that you tried everything. Only one thing. Try to check the battery voltage and if you can, try another battery in your phone. The charger could broke your battery, even if it one time worked in another phone.
Try reinstall usb drivers, rsdlite, different usb port, and different pc.
@peetr_
The battery seems to still work, as putting it in the phone makes it to be recognized (for 2 seconds) on the PC. Also, the phone seems to get a little warm while with the battery.
@ABC_Universal
I tried. Installed all the drivers in another PC I have here and tried the same methods I said before. Same results.
If you're planning to dumb the phone into a dumb site.. let me know when and where...
Ok... you need to narrow down the possibility here by putting another full charged battery and see if the phone do get connected status via PC. External charger might just toast your battery if you read carefully your entire story back starting from this line "I didn't know the battery wouldn't charge in the bootloader screen, so I quickly ran into a "Battery Low / Cannot Program" state. It was written in the screen what happened. I knew what I had to do. No big deal."
External charger might giving out totally different voltage/current rating from the defy own charger.
im having the same issue, did you solve it?
im having the same issue, did you solve it?
try putting a different Defy's battery, doesn't work just give it for RMA... you'll get a replacement. looks like a hardware problem to me...
You have tried the McGyver-trick?
I tried using another battery in it and didn't work. I was far from a computer when I tried, so I didn't check if I was able to connect it to PC (even if the screen was totally black). But if it was a battery problem, I was expecting at least the bootloader to appear, but still nothing happened.
I took it to RMA two weeks ago. Here in Brazil they take too long to return it =/. Still waiting.
skattegat: I tried. With and without battery inserted together. Both cases, I was only able to listen the USB connection start and end, 2 seconds later. I know the cable was working because even without battery, when I touch the wires, I was able to listen the usb connection sound.
Ok. At least you have the time now to enjoy your sunny weather in Brazil...
RSD lite sucks... Well it doesn't suck but it refuses to work anymore no matter what I do!
Use sbf_flash in linux and it should do the trick! PM me if you need help
First flash the sbf. Then enter stock recovery and do the recovery from there. Flashing does not wipe cache. But after the flash the recovery will do the wipe automaticly.
Sent from my MB525 cm7quarx
Just a follow up:
My phone returned today from the warranty. Is fully working now, but I noticed the IMEI has changed. So I guess they changed the entire circuit.
It's not helpful for those who have the same problem, but I'm happy again
i have problem too..
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me Quarx
thanks before
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Fotogravin said:
Don't see why you should ask the same question in multiple topics. My answer still is the same:
If pushing the lower right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
it's work..!! sorry i ask same question on other thread.
i'm so confuse
makasih gan
hey omneon are you able to solve your problem..plz help me man mine defy is stuck on m logo. same problem like your..
Related
Hey guys,
I have a very annoying and reproducible problem with my Desire. Everytime I connect the phone via USB (no matter if dock, laptop, wall) it reboots ~2 seconds after removing the USB cable from the phone.
I have had this problem for about 2 weeks now, across 4 or 5 Custom Roms (Sense and Non-Sense) and right now I am on CM6.1 Nightly 214.
It just annoys the crap out of me, for example when I got the Desire in the dock next to my desk and I receive a call, I can only accept the call handsfree, because removing it from the dock would cause a reboot and I would lose the call...
Please give me some kinda advice, I just flashed the latest radio and it worked twice without rebooting and now I'm back to square 1.
All the best,
Paul
Sounds like a faulty battery or some kind of defect at the power supply.
I suggest you try this with another battery, maybe from a friend.
You should check the usb connector on the phone too for some sort of deformation or smudge.
I thought that it could be the usb cable you are using, but since it does the same with the dock, it's not it.
The easiest and the most not likely way to fix it is with the calibration of the battery, if you have luck maybe it's just the OS that errs.
Thanks for your thoughts on my problem. Right now I am waiting for an important call but I got a spare battery from a friend of mine already and will later check and see if the problem occurs with the spare battery as well.
But the other point you mentioned was a calibration of the battery: how exactly do I do that? Just AmonRA Wipe Battery Stats or are you talking about another method?
Cheers for the advice!
this is for the calibration of your battery.
http://forum.xda-developers.com/showthread.php?t=755903
Hi, hope it works with the other battery, otherwise you'll have to send it for repair.
The battery thing I mentioned, has a minimal chance of working, but at least when I am desperate I try things that have even the smallest chance of fixing it. So in essence the process is: charge untill full when powered on; disconnect charger (which will automatically reboot your phone in your case);
don't let it boot, enter hboot for example and turn it off; then charge till full again; now boot into recovery wipe stats; and finally just boot into android.
Another thing worth checking I think is the pins where the battery connects to the phone, they should look clean (I wipe pins with rubber for a pencil) and intact.
Edit:Well seems like Marios already posted a link but mine is specific for your situation
did you solve the problem?
i have the same thing... very strange.
calibrating the battery didn't help.
No, I still haven't found a solution. Strangely though, it doesn't reboot anymore if I charge it via USB on my laptop. On my desktop and via the wall charger it still reboots every time I unplug it. Sorry I can't be of more help
my phone reboots when disconnecting from my laptop too.
even when in recovery, very strange...
have you tried to try the unbricking process with the misc.img?
Actually, I haven't tried that one. Can you give me a link to what you're talking about?
IT WORKED!
http://android.modaco.com/content/h...com/309939/usb-brick-rickrolled-b0rked-fixed/
just flashed the update.zip and i can copy the files to/from my laptop using the usb cable.
and it doesn't reboot when unpluging too
Got the same issue, tried modaco´s workaround, same thing... it started happening after i flashed CWM3.0x wich reovery do u use?
gonna try flashing Ra again and see what happens....
Solved It
Like i said, happened after flashing cw3.x finnaly i got home, flashed RA-desire-v2.0.0-CM again, then flashed update.zip from modaco´s thread, and for now it stoped....
just gonna see what happens when the battery get fully charged....
EDIT: Fully charged 4192mV removed it, and.... nothing happened...
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
congrats
powlemann said:
Unfortunately it didn't work for me. Now my phone freezes every now and then when I unplug it
EDIT: IT WORKED, IT WORKED!!!
Click to expand...
Click to collapse
NICE....
How did u solved it, u never know.....
I tried all things listed in this thread and some more, too.
But, it still reboots when removing from power supply (pc connection works now).
Perhaps you tried some things not listed here?
I am not sure when the problem started for me.
I installed cm7 nightlies with no reboot-problem, also switched from alpharev1.5 to alpharev1.8 and from cwm2 to cwm3.
All in a few days.
Somewhere along these days the problem appeared.
Btw.:
I got reboots on both kinds of usb connections (PC/power supply).
Debugging connection (adb, fastboot) worked.
Accessing the phone as usb storage device worked, too.
So this may be a little bit different from the cases described in the thread.
To solve the issue, I tried several things:
First I restored older backups (versions of cm7) with no success.
Then I restored my last backup of cm6 nightly from just before cm7, and it didn't work either.
As I was 100% sure that this worked before, I now concentrated on the remaining parts, recovery and boot loader.
So I first tried downgrading to clockworkmod2.
Then I tried updating to a newer alpharev1.8 (as it was a little bit newer than my installed version).
After finding this thread, I became a little happier again...
I applied the fastboot oem ... thingy (hmm, what does it do exactly?).
Then I calibrated my battery, which seemed to work well, as it shows 99% now, which it didn't before.
And at the end I installed the fixmisc-update.zip as linked above.
Between each step I checked if the issue disappeared.
Nothing of those steps completely solved the problem.
However, when disconnecting from PC, the reboots don't appear anymore, so at least something has changed.
So, powlemann, ferreinf and others being successful with the steps above, which configurations do you use now?
Can you tell me which change solved the issue for you?
Do you use alpharev1.5 or 1.8 (and the later from which date) or none of them?
Did you install cwm3 again after solving the problem and did the problem re-appear?
Good News for you, hg42!
I am 99% sure you can fix the problem when first flashing AmonRA recovery and then do Mocados Usb Brick rickrolled.
Do you know how to flash a different recovery?
I fixed it with modaco's zip, that was very annoying!!
Hi i had just flashed my phone back to standard rom with seus, and had rooted and was removing bloatware.
i used ADB Mask Controller for removing files because it was faster, but on the list of non essential apps i chose the ones a i wanted to get rid of, and accidentally clicked "delete all", because i thought it meant the all the files on the list. after that, i rebooted and the phone was dead, seus cant find it or anything, but now a day later when i press the power button, the led on the front blinks red a couple of times...
is it completely dead or is there a chance of getting it up and running again?
try flashtools
you should try bin4ry's flash tools it works most of times, there are a few tutorials around the forum but in general you just have to turn the phone off completely start flash tools select flash, select firmware and connect your phone pressing the back button just like in seus , also try posting problems like this in the general section, i know i'm no mod, but it helps keeping th forum clean , but don't sweat it, i think we all have done this when we started (i know i did XD)
Sorry if i posted it the wrong place, didnt think of other places cuz my bookmark leads me there.
Thanks for replying, but my problem is that i cant turn it on, when i press the power button, the only thing that happens is the led flashes red a few times.
Blinking red means that battery is empty. You can to charge it a bit with AC charger and then try to boot the phone.
yeah, sorry for the scolding , and i think it flashes red a few times because the battery drained, and flashtools is a pc program like seus, you don't have to turn your phone on, you connect it turned off, it is for flashing firmware to your phone and i recommended it because i think the reason your phone died is because of the missing apps, think of flashtools as a much MUCH better program for repairing your phone than the pc companion one or seus
also, here is a link to the main post for flashtools
http://forum.xda-developers.com/showthread.php?t=825664
edit: wiilweer beat me to it , and great port by the way, haven't tried it myself because my xrecovery is not working, but it looks great, specialy the 1000 in benchmark =O, excellent work men, thanks for the froyo port and your work
Thanks ill take a look at it again, hadnt seen the thread u linked now.
its been charging for a few hours and still just blinking... and it was at 100% when i started messing it up
maybe it is a stupid thing but...
have you tried
1) center hardware button + power for a few seconds?
2) disconnecting and reconnecting battery?
in the worst case you can try charging it with an external charger
but this means disassembling your mini:
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
Gx3 said:
maybe it is a stupid thing but...
have you tried
1) center hardware button + power for a few seconds?
2) disconnecting and reconnecting battery?
in the worst case you can try charging it with an external charger
but this means disassembling your mini:
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
Click to expand...
Click to collapse
Yea i tried that, but it didnt do anything.
maybe it just cant charge the battery. i could try to connect the battery from my gf's x10 mini
PressEsc said:
Thanks ill take a look at it again, hadnt seen the thread u linked now.
its been charging for a few hours and still just blinking... and it was at 100% when i started messing it up
Click to expand...
Click to collapse
The issue is not batery, its system files.
Do you have recovery instaled?
If no, download the flash tool and e10i firmware from this thread:
http://forum.xda-developers.com/showpost.php?p=10879519&postcount=2%22SE%20Firmware%20Files[/URL][/B]%3Cbr%20/%3E[URL=%22http://forum.xda-developers.com/showpost.php?p=10879528&postcount=3
Happy flashing.
Looks like its working now.
it wouldnt charge the battery, so i took the battery from another x10 mini, and then i flashed it. pc companion could find it and flash, with power from another battery
Dunno why it wouldnt charge the battery, maybe i deleted stuff that had something to do with power management.
Thanks for helping, i was already looking to buy another phone.
Thread belongs in the general section.
i have the very same problem !! ... WHAT did u dooo 2 fix this ?? am hopeless
try charging it and not with usb, if it wont start, try an external power source.
does it blink red when u press power botton?
Just want to share this, I do not create this procedure, and I forgot where I seen this.
1. Open SEUS, one it ask you to disconnect and connect. follow the next procedure.
2. Connect your X10 mini or Pro. Disregard SEUS Procedure
3. Press the Middle+Right+Power Button at the same time.
4. Once Screen Goes Blank, release all button except the middle.
5. now you could Update using SEUS.
Hope that help.
Sira. said:
i have the very same problem !! ... WHAT did u dooo 2 fix this ?? am hopeless
Click to expand...
Click to collapse
if the procedure above is not working you should try to recharge the battery or use one from another mini charged before trying that cause if battery is drained you won't be able to repair firmware...
http://www.ifixit.com/Teardown/Sony-Ericsson-Xperia-X10-Mini-E10i-Teardown/3124/1
PressEsc said:
Looks like its working now.
it wouldnt charge the battery, so i took the battery from another x10 mini, and then i flashed it. pc companion could find it and flash, with power from another battery
Dunno why it wouldnt charge the battery, maybe i deleted stuff that had something to do with power management.
Thanks for helping, i was already looking to buy another phone.
Click to expand...
Click to collapse
would u like 2 help me then >??
what is it doing?
I spent the whole yesterday afternoon and night and this morning trying to figure out what happened to my 'dead' x10 mini.
It has been lying there for over a year since I last tried reviving it.
Long story short, I forgot that I had flashed miniCM kernel on it. For some reason it just entered boot loop with Sony Ericsson logo and restarting and refused to charge. Then tried SEUS and Sony Update supposedly 'flashed' successfully, but I still could not get it to boot nor charge. Flashtool also was used to try a couple of other ROMs, until it dawned upon me I should flash back miniCM ROM since I think I had last used it year ago.
Voila it worked and I pressed BACK several times while the nAa logo came up. CWM was back. I jumped for joy... now I'm charging it and also downloading miniCM10 with gapps.
I really hope this helps - and that it would work for some of you out there in deep frustration. All the best! :good:
mcmlxxvi said:
I spent the whole yesterday afternoon and night and this morning trying to figure out what happened to my 'dead' x10 mini.
It has been lying there for over a year since I last tried reviving it.
Long story short, I forgot that I had flashed miniCM kernel on it. For some reason it just entered boot loop with Sony Ericsson logo and restarting and refused to charge. Then tried SEUS and Sony Update supposedly 'flashed' successfully, but I still could not get it to boot nor charge. Flashtool also was used to try a couple of other ROMs, until it dawned upon me I should flash back miniCM ROM since I think I had last used it year ago.
Voila it worked and I pressed BACK several times while the nAa logo came up. CWM was back. I jumped for joy... now I'm charging it and also downloading miniCM10 with gapps.
I really hope this helps - and that it would work for some of you out there in deep frustration. All the best! :good:
Click to expand...
Click to collapse
Looks like I went ahead of myself.
It managed to stay on in CWM... and I even managed to install update.zip and gapps, but once out of it the phone simply refuses to boot.
SEUS managed to flash stock ROM on it as well. However, even after leaving it hooked to the USB overnight (it only gets warm from this, not wall plug charger), it constantly looping in a flash mode (green LED) and then low batt mode (blinking red LED), it failed to boot up successfully on its own. After flashing the sony ericsson or custom ROM logo, it would go into a boot loop until the battery drains. Upon connecting back to wall charger, the first time it actually flashes real quick split seconds battery indicator of 2 out of 3, then go into the said boot loop again.
I really dunno if the battery's fried or did I do something wrong to hard brick it.
Hi all.
I know there are many threads about this, but there was no solution for my problem anywhere out there
Yesterday I got my Defy back from repair (broken speaker) and switched it on - I wondered why there is the vodafone 360 (I'm in germany) logo coming up, because it was not there before I sent it to repair... I immediately switched it off, to flash the de-blurred version (JRDNEM_U3_2.34.1) from and-developers.com which worked on the device before, without any problems.
After flashing it with RSDlite and got a PASS, it did not reboot - but it was still recognized by the Computer (USB-connecting sound on Windows) and RSDlite! So I tried to flash it again, but the problem persists. I already tried the McGyver-USB-cable-method and various battery-out-pressing-button-battery-in-again solutions... no chance. After a few hours testing, the phone stopped being recognized by the computer, too! I did not flash again and the white LED is still lighting up, when I plug the cable into the computer.
I left the phone with the USB-cable plugged into the computer over the night (6 hours), hoping it will charge (assuming I got the battery drained by testing too much) but the situation is still the same this morning.
I think I REALLY bricked it and have to send it to the shop, which also fixed the speaker (which I did not get to test yet ) - I would like to see a different approach, because I know I will get that ****ty vodafone 360-ROM on my phone again
Any help is appreciated.
Thanks,
hitti
They have updated your software to 2.51 when they gave it back. It is foolish of you not to even check before flashing it. Flash the 2.51 or chinese froyo sbfs.
Sent from my MB525 using XDA App
Yes, that's right - I should have checked it before.
I can't flash anything, because my computer does not "see" the phone anymore
Edit:
I sent it back to that shop, which repaired it before - hoping they get it fixed.
But u cud just flash 2.51. Well, anyway.
Sent from my MB525 using XDA App
Turn off your phone (by pulling battery if necessary). Press and hold the volumn up button and turn on the phone to open the boot loader page. Then plug in the usb cable and flash the 2.51 rom.
ABC_Universal said:
Turn off your phone (by pulling battery if necessary). Press and hold the volumn up button and turn on the phone to open the boot loader page. Then plug in the usb cable and flash the 2.51 rom.
Click to expand...
Click to collapse
ABC is right..the problem is you might just get a blank screen but it gets detected by RSD. This happened to me before and thought I bricked my Defy, which almost made me shat bricks! But since you sent it in already..hopefully they fixed it if not, you can do it yourself.
http://forum.xda-developers.com/showthread.php?t=884105
download and flash....it worked for me...
I tried all kinds of combinations of pushing buttons and putting batteries in and out - it was not recognized by the computer or RSDlite at all. Thanks for helping, anyway
Maybe the battery is discharged
Do you know any person who has a Defy to let you the battery, and then reflash?
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Check battery pins
hedeon said:
Hi guys, need very quick help from you, as I think I have bricked the phone which suppose to be a Christmas gift for may son. I was trying to revert phone from root and custom rom to stock. I've downloaded older OTA update (one of very first ones with android 2.2) an installed it in bootloader. Phone booted fine, and I went for official update. It showed to me there is update available to android 2.3. I have downloaded it and phone rebooted in to update mode. After progress bar gone to the end it disappeared and phone stayed in that update mode (logo with phone and green arrows shaped it to circle) for nearly half an hour. I though, some thing had to vent wrong so I decided to turn off phone, but power button gave no effect, so I pulled battery out for few seconds. After I have putted it back phone never turned on again. I mean is completely not responding. Pressing power button for even minute doesn't wake it up, it is not possible to go to the bootloader. There is no characteristic vibration when it turns on. Basically it behaves like there is no battery in socket but there is, and it is fully loaded as I charged it before updating. When phone plugged to AC or computer LED is not lighting as well whatsoever.
Please, can any one help with this one? I in rush as phone is a Christmas present for my son who lives in Italy and I supposed to ship this today to make it arrive b4 Christmas. This is why I can not spend to much time on searching forums.
Thank you
Click to expand...
Click to collapse
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
whiperhack said:
After reading what you said i think that you placed battery wrong. Check the pins inside the phone with battery pins.
Click to expand...
Click to collapse
That was my first idea too but, no m8, battery is placed ok....
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
if4ct0r said:
Try pressing volume down+power button for a while then leave the power button while still pressing the voulme key. You should boot into the bootloader.
Click to expand...
Click to collapse
Tried that too, still dead
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
I understand I should not be worried that all of these RUU's are listed as for model: ACE?
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
if4ct0r said:
Not at all. 'Ace' is the codename HTC gave to Desire HD/Inspire. Just choose the RUU that fits your location(i.e. WWE stands for WorldWide Edition).
Click to expand...
Click to collapse
OMG! I was previously looking for stock roms and everytime I ended up on that site from your link I was annoyed that someone is giving a wrong link to roms for wrong phone. Silly me!
I am downloading right now.
if4ct0r said:
Try connecting you DHD to the PC.
Download one of these Stock RUU's : http://shipped-roms.com/index.php?category=android&model=Ace
Run the installer from PC. See if it detects the device.
Click to expand...
Click to collapse
No it says phone not connected (error[170])
hedeon said:
No it says phone not connected (error[170])
Click to expand...
Click to collapse
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
when you connected it to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then sorry to say, its bricked.
The only way to recover it now is via jtagging or replacing the mainboard (which generally is what they do when you send it in for warranty repair)
whiperhack said:
My idea is to double check again the battery position in the socket and if it is ok try to leave it 5 minutes alone on the AC adapter. If this will not give good results, go to the appropriate HTC representative.
Click to expand...
Click to collapse
Yes, I thought about it as phone behave like it has no power at all. But this is not the case, as I have been flipping that and another battery in every possible position. And I know which one is correct as I can see where pins are in battery pocket. I left it alone under charging and other time with no battery at all hoping that will hard reset phone. No effect at all .
JSLEnterprises said:
when connected to your computer... did it ask you to install qload drivers?
if not, go into device manager on your computer, then plug in your phone. If you see an unknown device that shows as qload something or other, then its bricked, sorry to say
Click to expand...
Click to collapse
I had drivers previously installed. But I am not entirely sure are we talking about same thing as I don't know what QLOAD is. Anyway comp doesn't see any recognised or unrecognised device that could be my phone...
I am not worrying about damn phone as if it is hard bricked tech guys in service will not probably spot that it was rooted. So they will replace, or if not I will go to insurance company. Problem is it takes to much time, I wont make it b4 Christmas.
Thank you guys,
anyone has some other ideas? Please...
desperation bump
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
if4ct0r said:
Sorry.. It really seems to be beyond software-repair, If it cannot boot in the bootloader or be recognized by PC there's really not much we can do. We need the device to start in some way.
Although one last thing that we haven't tried and can try is to see if it can be accessed via adb or fastboot. (Although I highly doubt it since the RUU also wasn't working).
I've attached the adb and fastboot files required to test that. Extract it, double-click on StartHere.bat and type "fastboot reboot" or "adb reboot". If it returns an error citing device not found then this too has failed.
(This probably wont work.. desperate action)
Another silly thing that might be tried is to try to put your phone on charging via a charger(not USB via PC) and then try to switch it on. Try normal switching, switching on to bootloader(volume down press)...
If these don't work then you really should give it to the repair center.. you're right that they wont probably realise that it was rooted and would probably change the main board.
Click to expand...
Click to collapse
Sigh... I got "waiting for device" forever in CMD... As you said, it's dead. Gonna send it to HTC in Monday...
Thank you all, appreciate your time
Hello hedeon,
I have the same experience today, as you state in the first post in this thread.
Did you, and how solve the problem?
Is there people with the same problem? This morning I receive notification about system update for my HTC Desire HD. The rest is exactly same problem from the top of this story = death + death + death.....
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
GuyInTheCorner said:
The problem is that you PULLED THE BATTERY WHILE UPDATING! Have some paitience. I switched on my DHD after 3 months and it needed updating. Takes around 20 mins to complete update
Sent from my HTC Desire HD A9191 using xda premium
Click to expand...
Click to collapse
May be, but updating started with downloading, then resetting, and then green line was growing up to 1/3 of total size, and at that size stay more then 20 min. Then I try to to push every button, and every combination of buttons, and after 10 minutes more I had pull battery out.
Was it too impatient ?
What was the Android version before you rooted if you can remember and which tool did you use to root?
From what you wrote earlier, it asked you for a 2.3 update which means you probably flashed a Froyo RUU as stock, to bring the phone back to stock ofc.
However, if your DHD came with stock Gingerbread, flashing a Froyo RUU will most definitely screw the phone. I'm not sure if it's beyond repair atm or not, but if that was the case, even if you didn't mess with the battery, chances are the phone would never boot anyway.
Look into AAHK thread, I think there is a good how to there.
Hi all,
I was having some random reboots on my HTC desire Z lately and decided it was time to try a custom rom. I followed the right steps to first downgrade to froyo, which was successful and next rooted the phone, which seem to have worked as well.
The next step was to get into recovery mode to install the rom, but I did not get to that. I took out the battery while it was still on to power it off, but then it did not power on anymore. Also connecting the charger has no effect at all, so it sure seems to be bricked.
Does anyone have a suggestion on what I can try, or what happened to it?
The way I downgraded and rooted was by using Strawmetals guide which can be found here:
http://minus.com/mu9vZ3P38
and was suggested in this thread:
http://forum.xda-developers.com/showthread.php?t=1178912
I carefully completed all the steps, checked the MD5's etc. and made sure the notifications/verifications I got back in the process were correct..
Also, I wonder if I would run into problems if I send it back in for warranty. If I can't get it to boot, will they? And next they will probably blame me for rooting, right?
Regards & TIA
Yes they gonna blame you for rooting. I was had a same problem, no boot to recovery. I solved the problem with install 4Ext updater and fromit install 4ext tuch,and now I can flash roms. Try to find a charged battery or put yours into another phone and charge it. If I understand right your battery died?!
Sent from my HTC Vision using xda app-developers app
Sounds like it might be bricked mate, same thing happened to me... 3 times. They probably won't be able to get the phone to boot, where did you buy the phone from? My second one was from Vodafone with a warranty, when it bricked I took it in, they plugged the phone in and left it for a few minutes and tried to power it on, tried a different battery (All things I already tried) to see if the device was showing any signs of life, it wasn't and I walked out with a new phone. I doubt they'd be able to bring it back to life to see that it's been rooted. You COULD connect your phone to a car battery and fry it, tell them you went to sleep and woke up and the phone was very very hot and it burnt your hand and melted the charger cable, not sure if I could recommend this, never done it myself... but if you have no other option.
These were also the options I considered. Got to give it a try with a different battery, if I can find one. If that doesn't make a difference, I'll just hand it in and see what they have to say, as there's nothing else I can do without being able to power on the phone..
All of a sudden the phone started working again . And afterwards I was able to complete the update to Mimicry 1.5.
Strange problem, as the phone seemed to be dead for hours.. Hope it doesn't happen again!