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).
Related
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..
OK, so I flahsed CM 7RC 1 and everything was fine. So then I used it and enjoyed it for an entire day. But, very soon my browser started to FC and so I just went ahead and wiped dalvik cache thinking it would solve the problem. Unfortunately for me, I accidentaly wiped the normal Cache.
Now my phone just boots and stops at the Motorola logo, I can access bootloader and stock recovery, so am thinking of flashing the full sbf - SEA version. But, my phone has no more battery charge left
I plugged in my charger and all I get is a huge "?" on my charger icon. How do I know if it is charged. I am pretty sure this can be unbricked using the Full sbf....
Please some one help me out here.
do the macgyver trick
http://forum.xda-developers.com/showthread.php?t=892026
I have done it and have seen no ill effects. Just make sure you dont leave it in for a while (more than an hour or two). After that flash to a stable build and then reload cm7. good luck!
Chem57guru
chem57guru said:
do the macgyver trick
http://forum.xda-developers.com/showthread.php?t=892026
I have done it and have seen no ill effects. Just make sure you dont leave it in for a while (more than an hour or two). After that flash to a stable build and then reload cm7. good luck!
Chem57guru
Click to expand...
Click to collapse
Thanks for your help. I have just seen this post after using macgyver trick. Couldnt wait that long as I was goig crazy thinking about my bricked Defy.
Worked like a charm! So I went ahead and posted 2 pics from modmymobile in the macgyver thread. That will give people an indication as to where to insert the red and black wires.
I connected and went straight ahead and flashed....no problem...... but after flashing however, when i disconnected the modded USB cable, the battery was empty - 0%. So I charged it for 20 mins till it reached 20% and then started it.
Lucky for me, its back to normal. Flashed SEA Full Sbf and viola! as good as new.... albeit this is more faster than the original froyo I received with the phone
Next stop WIUI... I hope the procedure is same for that too ie Nandroid + fixed sbf
i bought this Defy+ just a couple of days ago and i was trying to get CM7. I struggled to root it but i achieved it. I wiped and did all the procedure before installing it, but i didn't had enough space on my SD, so i rebooted and booted like a brand new defy, going through the Blur config and everything... So i went to Recovery again, but at this time i forgot to do the wiping - which, i guess, led to a brick.
So i managed to get a .sbf to flash it.. What i didn't realized is that the .sbf was a custom, so i guess this ****ed up my phone even more. And so i went on trying to rescue my phone but this time i couldn't complete the flashing process, i wasn't able to perform a downgrade - i guess. After this, i got a non-rootable .sbf and began the flashing. The process got stuck on some message at 0%, then i disconnected the phone.
When i was able to download a stock firmware, from the .sbf thread, the phone wouldn't reboot when RSD asked, it didn't turn on again. So i tried to re-flash it, same .sbf and now i'm stuck with this situation: the pc is not recognizing my phone, i have a black screen - not even the Bootloader error screen is appearing and i'm here, begging, for someone to help me. is it dead? can i get it back?
HELP, PLZ
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Auris 1.6 vvt-i said:
Is there any juice in the battery left? Does the phone even turn on or did you just drain all of your battery? If so, you have a couple of options - do McGyver or find somebody with the same phone and ask him to charge your battery and then start over. I would strongly recommend you take the second option.
Click to expand...
Click to collapse
it doesn't turn on, but i guess it does have battery, i can see the led on when i connect it to the pc
Led is always on when connected to the PC - it means nothing. If it doesn't turn on, then your battery's dead. Find someone who has the same phone and can charge it for you.
I think there is no problem, but you flash older firmware, which is probably due to the 7 bootloader does not go up.
try to be flash with one of these (2.3.6 GB)
http://forum.xda-developers.com/showthread.php?t=966537
begins with the 139-ended, if it is not going to work with the 188-ended
Sorry for bad English
"As of today there is no a full SBF** for the Defy+ (found here).
This full SBF is a new CG Version**, with Android 2.3.6. You wont be able to go back to your Stock Defy+ Rom, but at least you wont kill it if something goes wrong."
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
caiowatanabe said:
i successfully flashed it but still it won't turn on, i'm almost giving up on this one
Click to expand...
Click to collapse
If it gets past the red m and just keeps playing the android animation then simply pull battery hold volume - put battery in and keep volume - held when you get the android and the triangle press volume + and - and wipe all, should boot, unfortunately you've just flashed the un root able sbf and are stuck on moto standard
teamwork makes the dream work
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
caiowatanabe said:
nevermind, i flashed other sbf version and it is now working; too bad this version isn't rootable
anyway, many many thanks for all the help
Click to expand...
Click to collapse
Feel free to keep an eye on the dev section for the bl7 rooting thread you may get lucky
teamwork makes the dream work
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!
So I wanted to install a new custom ROM and I all ready had one. It wasn't the first time. So, like usual I download the files needed and put them on my phone, boot into recovery and flash them ( but I didn't factory reset or anything because with the ROM I had I didn't need to for it to work I could just fix the not responding errors) Then i go to reboot and I wait. Nothing, nothing at all. Now I try to remove the battery and try again and now none of my buttons do ANYTHING the only sign of life there is, is when I remove the battery and plug my phone to a usb cable and attempt to charge it, all that happens is a red LED comes up. It's probably due to one of the things i installed on my phone that flashes a red LED when battery is low. Please help me with this. My last resort is to give my phone to rogers for them to fix it because I still have a warranty.
Specs: S3 i1747M Rogers
I had aokp jellybean 4.3 as my ROM
I do have a nandroid but its on my phone's sd card
Thank you for your time and I hope we get this to work.
Can you get into recovery mode or download mode?
FoxTrotz said:
Can you get into recovery mode or download mode?
Click to expand...
Click to collapse
No there's litteraly nothing I can do. pressing all the buttons does absolutely nothing. Just stays black and no signs of life
bump. I need help fast with this.
Not sure exactly what you did but I hate to say its sounds hard bricked. Mine was exactly the same, with only the red light coming on for about a minute when cord was plugged in with no battery. I screwed mine up with a file I grabbed without reading properly what it was for and in my haste I installed it. After I rebooted it never came back until I got it back from warranty with a replaced control board. Im guessing they didnt even check the internal memory or they would haven known what a dumbass i was since i voided the warranty doing stuff i had done before that mistake. Glad I had made a nandroid before i pooched it so i didnt lose anything after i got it back.
Yeah after some research I found out I hardbricked it but this isn't the first time and I had a warranty for both( different phones btw )times so I guess I'll just send it out. :c
could just be out of juice, leave it on the charger for around an hour then try and go into download mode.