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!!
hey guys,
the original thread is located here: http://forum.xda-developers.com/showthread.php?t=940647
i did everything according to the description...
directly after flashing chineese stock rom^^ .... came back to the pc (wasnt there during flashing, but nothing could have happened, only rsdlite running, phone wasnt recognized, phone was off, white led on)
(battery has been fully charged, so battery is okay)
i tried everything, volume up + power, didnt work, rsd lite cant recognize. nothing here...
maybe someone can give me advices? no chance here so far to get it recognized in rsd lite.
thanks - appreciate any help,
but i got the really bad feeling that i've bricked my phone - OMFG guys.
edit: omfg, now there is a warning. it wasnt there when i flashed it, on the links stands, u can flash some leak, BUT - no rsdlite, no fllashing^^ ? right?
edit2: read some more posts, will try mcgyver hack 2morrow, invited to a party right now^^ so without a phone meeting some people always a litte bit more complicated :====P ***so thumbs Up *** for my little person for tomorrow. cant explain why the battery should be completely empty? but hope, that white led just means that. - will report 2morrow -
edit3-solution?
my defy is already on the way to service, BUT
someone told me: ! --> HOLD THE POWER UP KEY - BEFORE u PUT THE BATTERY IN ...
this worked for him.. maybe this could help anyone else! good luck to everyone!!
this work for me
http://forum.xda-developers.com/showthread.php?t=892026
just flashed the chinese 2.2 with RSD lite, all went well, RSD gave a "pass" result to the flash And now the phone will not turn on, no lights or anything. Charge light doesn't even come on when plugged in, if i press power when it is connected to charger, the led flashed white once and nothing else. I had 3/4 full charge when I began, don't see how the battery could have drained out, but I will try charging externally
Also I was coming from T-mobile Eclair 2.1
ok, so my first flash I used a flie I downloaded labled 2.2CN_SBF.sbf
So I reconnected the phone to RSDlite, and it showed the device was connected, I downloaded the Chinese.SBF from Higgsy's page and still nothing but a dead phone, its definetaly not the battery if its connecting to RSDlite and letting my flash, and reflash. Maybe I will try going back to stock 2.1 sbf
make sure your set to first-Come-first serve Deviceid mode in rsd lite config
I've tried flashing the orignal offical UK SBF, and a Lite Chinese 2.2, nothing screen is black, can not get into recovery, phone stays in bootloader but has black screen although says SW upate when flashing
crazyVII said:
hey guys,
the original thread is located here: http://forum.xda-developers.com/showthread.php?t=940647
i did everything according to the description...
directly after flashing chineese stock rom^^ .... came back to the pc (wasnt there during flashing, but nothing could have happened, only rsdlite running, phone wasnt recognized, phone was off, white led on)
(battery has been fully charged, so battery is okay)
i tried everything, volume up + power, didnt work, rsd lite cant recognize. nothing here...
maybe someone can give me advices? no chance here so far to get it recognized in rsd lite.
thanks - appreciate any help,
but i got the really bad feeling that i've bricked my phone - OMFG guys.
edit: omfg, now there is a warning. it wasnt there when i flashed it, on the links stands, u can flash some leak, BUT - no rsdlite, no fllashing^^ ? right?
edit2: read some more posts, will try mcgyver hack 2morrow, invited to a party right now^^ so without a phone meeting some people always a litte bit more complicated :====P ***so thumbs Up *** for my little person for tomorrow. cant explain why the battery should be completely empty? but hope, that white led just means that. - will report 2morrow -
Click to expand...
Click to collapse
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
nitski said:
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
Click to expand...
Click to collapse
Was forced to flash the leaked froyo tmobile signed SBF. Forgot that this Defy wasn't the orignal, my wife had it replaced due to Earpiece failure, so the replacement must have had the OTA already, cause i never installed it. Oh well its her damn phone anyways LOL
Just curious how would you check next time to see if its 2.51
So to sum up CrazyVII, You have to flash the Froyo Leaked SBF with the signed keys, otherwise you will never finish the bootloader flash.
Just connected to RSD and make sure its set to First cum first serve, and hit the power button on the phone, screen won't light, and my led didn't either, but it should safe connected in slot one of devices.
Start Flash, and wait to see the "M" , RSD will let you know when to restart the phone.
Hopefully they figure out how to make this downgradeable, I perseonally Have a G2, but I really enjoyed Rooting, and deblurring my wifes phone, its a nice device
nitski said:
I already experienced this. It's a big no-no to flash the Chinese SBF if you're coming from 2.51. After flashing the SBF through RSD, the phone won't boot up. It's a good thing that my phone is under warranty and so i got a new replacement
Click to expand...
Click to collapse
seriouus answer? dont want to wait until a new one arrives..
Dalamak said:
So to sum up CrazyVII, You have to flash the Froyo Leaked SBF with the signed keys, otherwise you will never finish the bootloader flash.
Just connected to RSD and make sure its set to First cum first serve, and hit the power button on the phone, screen won't light, and my led didn't either, but it should safe connected in slot one of devices.
Start Flash, and wait to see the "M" , RSD will let you know when to restart the phone.
Hopefully they figure out how to make this downgradeable, I perseonally Have a G2, but I really enjoyed Rooting, and deblurring my wifes phone, its a nice device
Click to expand...
Click to collapse
thanks for summing up,
u mean the chineese froyo release is something like the 3.4.?.? version? im going to search for it right now
maybe anyone can supply a link?
the problem is, i tried nearly evey combination, the phone doesnt recognized by rsd lite.best proposal would be - battery out - in - vol up + power - wait .... rsd lite doesnt do anything.
so very hard to flash.
do i need to apply the mcgyver trick, or is it useless....?
edit: why can't the phone load while off? i just understand the logic behind this behaviour...
best reagrsds thx,
cV
phone really dead.
guys, tried mcgyver trick....
white light goes on on usb connect directly... dont know why, but nothing worked. first come first served mode enabled in rsd lite.
rsdlite running the whole time. nothing connects, nothing realized.
direct boot (only power button), power + volup button, everything. no result.
the strange thing, in the meantime i saw someone posting, he flashed the whole thing(as in the description, 1st post) on 2.51 and on his phone everything worked fine.
no idea. but i think mine is really gone now. i think ill send it to my reseller tomorrow. im not quite sure if i can stay with such a situation (not loading in boot loader mode? WTF? no real recovery image? F*CK? bad hacks? no useful backup situation.. why do i need a recovery, when i cant access it when i screwed up? -> useless to me.
im really thinking of switching back to htc, although the DHD is too big, i think ill gonna take it
guys, any tipps? suggestions? id really appreaciate it. :=)
thanks for all the responses so far.
current situation
- mcgyver trick tried for 45 mins,
- rsd lite in first come first served mode
- white led goes on on usb connect immediately
- screen is black the whole time
- no results - no recognization...
- flashed chineese 2.2 on 2.51 firmware
Did the same goof up....got greedy for froyo and couldn't resist f&(*ing my defy........was cribbing for 8 hours while figuring out the solution.... escaped office for this.....but finally finally .......i saved it.......man.....if blood is the answer for blooood....then it has to be 2.51 for 2.51....
please click the link below for the only feasible 2.51 sbf....flash your defy in a standard manner and kabbooooom........defy reincarnated...
:
hope it works for all the good people in need....it worked for me (Atleast my defy turned on still observing how it works)..
Defy 2.51 sbf
Theres more....though i sacrificed one of my data cable for mcgyver jugulary...but got a wonderful outcome of my 12 hours wait..........my earlier (india) rom was not full blur...never realized it...facebuk never synced......but this uk rom is FULL BLUR..and its awesome......alll my accounts are intact......everthing works just fine....in face some of the the apps which never used to work earlier work flawlessly now........
ACCIDENTS ARE NOT ALWAYS BAD
All those greedy people wanting to flash froyo from 2.51 and wanting to keep their downgradability, you will need to search for tutorial from Bihariel where he put up froyo rom only for 2.51 base.
All the best.
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 guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
simon211175 said:
Hi guys.
Last night has been a nightmare for me, I have to say. My Defy has been suffering recently from battery fatigue - the battery holds charge for about ½ an hour before I need to plug it in again. At the time, I was running CM9 (Epsylon's) so I thought I'd try downgrading to CM7 to see if it was software or hardware.
This is where the trouble began.
I faactory reset the phone and flashed the CM7 ROM I was going to use (http://forum.xda-developers.com/showthread.php?t=1604501) then hit reboot.
My phone got stuck on the M boot logo. Great. Back to recovery, I wiped all cache etc and rebooted. Still the same. Back to recovery and I tried the whole process again. Still the same.
By this point, my phone was losing charge, so I left it to charge a bit (plugging it in from 2% charge takes it instantly to 60%).
Then I retried the whole process again - still the same.
Okay, it's getting late now and I'm starting to panic. So I download a stock ROM (T-Mobile 2.2.2) and flash it using RSD Lite. Looks like it's going well, until it tries to reboot me - stuck at M Boot logo.
Now, I can't even switch my phone on to get it to the bootloader. I've tried a different battery too, and no joy.So now I have a well and truly broken phone.
From my knowledge, I have two options here:
1. Try the Macgyver fix method. I'm not confident doing this, and don't even know if it will work.
2. Take my phone back to T-Mobile and hope they don't notice what I've done.
I'd appreciate some help please if any one is able.
thanks.
Click to expand...
Click to collapse
ok mate
right the mcgyver trick works a treat and is surprisingly easy. i wasnt keen on it but it works and is not hard although it is fiddly and if you are anything like me it will take a few attempts to peel back the shielding and expose the wires and then get them in place.
i found the best way to get the wires in place was not put them under the battery as the guide suggests but instead just put the battery in as normal and have the wires in at the very end. you will understand what i mean when you start but i have decided to take a photo and you can see what i mean here
http://sdrv.ms/OPDczX
everything you need for that this section of the recovery is here.
http://forum.xda-developers.com/showthread.php?t=892026
then you need to flash the sbf again. the one you have already flashed is fine and is the one you need so use that. (if for some reason it doesnt work after what i am going to tell you then ask again on here before you choose another).
next follow the guide to un-bricking your phone (linked below). if the phone wont boot and gets stuck after you have flashed the sbf you need to boot into recovery and wipe the data/ cache. reboot and all should be ok.
so follow the guide to the letter but when/ if (the phone wont boot past the moto logo) follow step 8. however you will find that when you press power on/ volume down that instead of motorola recovery you get a droid with an exclamation mark (this is ok so dont panic). to get into stock recovery from this position you need to press and hold down both up and down volume buttons at the same time for about three seconds and viola. then you can wipe and you should (fingers crossed) be good to go. if you dont understand anything then ask but it is relatively straightforward and if you do what i suggest above then you should have a working phone in next to no time.
http://forum.xda-developers.com/showthread.php?t=1828639
good luck
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
simon211175 said:
Thanks for the prompt reply, I feel more confident doing this after reading that. Unfortunately I've no spare USB cable to try this with at the moment, but having looked further I've noticed my battery has a bulge in it, so I doubt there's much point in trying this with this battery.
I did however successfully manage to flash the sbf file (according to RSD Lite) using my friend's battery - but the phone still doesn't boot. Given that my phone isn't going to be right with the current battery - I think my best option now is to take it back to T-Mobile, tell them the battery has done some damage.
Click to expand...
Click to collapse
did you wipe the cache/ data after you flashed the sbf? if you didnt you may want to give it a go before you send it off. it may spring to life once you have done that.
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
simon211175 said:
I don't get that option - the phone doesn't reboot. RSD Lite said it did, but all I actually got was a blank screen.
Click to expand...
Click to collapse
It looks real bad. You sure the battery didn't die in the flashing process.?
Also try booting into recovery and do a wipe.
It's entirely possible that the battery died during the flash.
I cannot boot in to recovery - the phone doesn't get that far!
I've sent it back to be repaired. hopefully they'll do it under warranty, but if not it's only going to cost around £60 to buy out the remainder of my contract so if the repair costs more I've got that as a backup option.
Thanks for all your help guys.
You can cut an old wall charger but if you can't measure the voltage to know what wire have 5 volts and 0 Volts , and you can hold the wires 5V to plus on akku and 0 to minus and the supply would load..... you can left the batt out of the device...
Wait 10 till 15 min ,for save check if batt getting hot, boot into stock recovery and factory reset your phone
If you can't enter recovery you should be able to enter boatloader
If there is battery low can not program ..load akku.. or ready to program which means .... flash rom with rsd, factory reset , reboot, have fun
i did this two times, flash with low batt one of with not loading batt in dev - i charged with Nokia wall charger cable
If only battery is too empt and briked batt loader.......
If boot loader is briked by bad flashing search Google......
But i mean ciao loved defy
And don't forget : factory reset is always after you changed your rom....
Wiping cache/dalvik cache in only installing new nightly
Sent from my MB526 using xda app-developers app
so, here's my update.
You will recall (see two posts up) that I gave my phone back to T-Mobile on 20th August for a repair. I got my phone back today (+18 days). Here's how it went:
Day 1
Took phone to T-Mobile store. Informed them my battery had a strange lump, which I suspect had fried my phone somewhere. They advised they would send it to the repair centre the following day. No courtesy phones available so I'd be living in the 1980s for a while.
Day 10.
Phone actually arrives a the repair centre. I have no idea where the repair centre is, but I'm guessing really really far away.
Day 15.
Repair centre advise my battery is faulty and to replace would cost me £26.40 for a genuine Motorola battery. Advised repair centre that I told them my battery was broken, and asked why it took them 15 days to repeat that back to me. Also advised them I would rather by my genuine Motorola battery from Amazon for £11.95. Gave them a link in case they want to update their price lists.
Day 17.
Repair started on actual phone.
Repair finished. Yep - the repair took less than 24 hours.
Day 18.
Phone returned to store. it took 24 hours to get there, so I'm assuming the post travels down hill only on the way back.
Picked up phone from store, all set to complain about poor service etc. Noticed brand new battery I hadn't paid for sitting in the returns package. Kept quiet. Left store promptly.
So now I have a working Defy once more (Hurrah).
Obviously I've rooted it already in order to get Titanium Backup to restore all my apps.
Now I have stock 2.2 Blur running on my phone (Boo!), and with only a few months remaining on my contract, I'm not sure if I want to risk loading a new ROM again (I'll reread this once I've loaded a new ROM next week, for sure).
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!