Database Users

help! Defy wont boot, white light at top, rsdlite doesnt recognise

Deleted by user

I suggest you to completely charge your phone for half a day and then try to power it on. It should at least get stuck in the M logo.
Sent from my MB525 using XDA App

Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.

Was your battery low when you tried flashing? It will not charge in bootloader mode so if you're battery is low you will have issues. If you boot with volume up pressed does it give you a message?
Try the Mcgyver battery fix found in this forum.
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
gookia2000 said:
Hi all, I am a proud owner of a t-mobile defy (for about 2 months now!) and my hands got itchy today and went ahead to "debrand" it following the guide by Higgsy.
I was trying to flash a uk 2.21 rom onto my t-mobile defy (rooted with z4root).
Well, I managed to do all the steps of the guide. my phone was recognised by rsdlite, i selected the uk 2.21 sbf file, i clicked start, and it started flashing the different code groups. Finally, it said "finished" and "PASS". Here is when the problem started. The phone did not reboot into android. It was just a blank screen with a white light on the top (where the green led is to inform you about new messages.)
i panicked and disconnected the phone (the white light turns off after disconnecting), took out the battery, tried rebooting, tried rebooting into recovery (power + vol down), tried rebooting into bootloader (power + vol up). Nothing worked. it just stayed dead.
I then plugged it back into the computer. immediately the white light came back on and rsdlite recognised my phone. i tried flashing again - same result. I then tried flashing the 2.52 uk rom - same result.
even more panicky now, i unplugged everything and decided to take a nap and hopefully think of some ingenious solution to the problem. now, after a 3 hour rest, i tried plugging the phone back into the computer. the white light comes on, but now rsdlite doesnt even recognise the phone.
In essence, is my phone bricked? I cannot:
1) load into recovery to do a nandroid restore (yes, i have a nandroid backup copy)
2) load sbf files from rsdlite. every sbf file i tried doesnt seem to work. now its worse as rsdlite doesnt even recognise my phone.
i have even tried doing a nandroid restore via adb. but i get the error message that no phone was detected in the command prompt. perhaps its because the phone was not started in recovery mode.
The only explanation i can think of is that i have recently updated to the t-mobile 3.6.360 update and that might be the reason why so many people before me were able to flash their defy's roms successfully while i got stuck.
Can anyone please help? I LOVED my defy more than any other phone, and 2 months was too shortlived!
Click to expand...
Click to collapse
skateguitar00 said:
Mine has done the same thing, i left it connected to rsd lite to flash, went to bed, and now its stuck at a black screen and won't boot up at all. Same white light when plugged in to the pc, but rsd doesn't recognize. please help.
Click to expand...
Click to collapse

Deleted by user

Actually, all you have to do is press the power button while the LED is on and RSDLite is running. You will hear the USB detection sound and your phone will appear on the list. It won't appear as it normally would but it will be listed.
Then just choose the Froyo ROM and then click start to flash it. It'll take less than 10 minutes...
There's no other way that I know of to get it working. Even in the link that I posted, you can check and see that no one even bothered to give me an idea of what to do. I had to figure this out myself.
I figured it was the bootloader protection that was causing the problem so the logical choice was to flash the only T-Mo ROM available which happens to be the leaked Froyo.
It's been almost 24 hours and I've had no problems with FroYo so as far as I'm concerned, I'm good.
gookia2000 said:
Beach Head, thanks for your reply. you have provided me with a glimmer of hope!!! the leaked tmobile froyo sbf is one i have not tried. I will certainly try to flash my defy with that once i have gotten it recognised by rsdlite.
I believe my phone is currently not being recognised by rsdlite due to insufficient battery. (cant confirm this, as all i see when i plug in the usb is a white light on my phone. but ever since i started this entire nightmare, i think i have attempted flashing at least 5 different sbf files and considerable battery has been drained.) I will try the Mcgyver battery fix next.
skateguitar, THERE IS HOPE!!! i havent confirmed it yet but i think we all got stuck cos we were trying to flash from a "non-downgradeable" 3.6.360 firmware. and rsdlite does not recognise our phones due to low battery (your phone was left with a white light on after flashing for 1 whole night.) SO... i propose this course of action: 1) perform the Mcgyver battery fix and try to get our phones recognised by rsdlite first. 2) once recognised, flash with the leaked tmobile froyo sbf.
Does anyone have any better suggestions before i plunge head first to save my phone?
Click to expand...
Click to collapse

Yes all i wanted to say was that you might have lost your downgradability and thats why phone does not boot. Simple thing is to flash the original sbf like what beachhead suggested. It definitely should work.
Sent from my MB525 using XDA App

Guess what, it works!!!
Deleted by user

Glad I could help you out!
Enjoy Froyo!
gookia2000 said:
OHMYGOODNESS!!! I LOVE YOU GUYS!!!
My Defy has been flashed with the t-mobile froyo leaked rom and IT WORKS!!! I was so mentally set with the idea that my defy has been bricked and I just threw $400 down the drain... NOW I AM SO HAPPY!!!
Anyway, just for your information, here is what I did:
- I first tried to get my defy recognised by rsdlite. I tried Beach Head's suggestion of pressing the power button while the led is on to no effect. I reckon that the battery has just been drained too low. So, i went ahead with the McGuyver battery fix.
- Alas, with the wires protruding precariously from my phone, rsdlite finally recognised my phone. I went to load the leaked t-mobile froyo rom and went ahead flashing it.
- And, guess what, IT WORKS!!!
Thank you all so much, especially beach head, for your help in this forum! I would have gone to the mobile store to get another phone if not for you guys!!!
Click to expand...
Click to collapse

I have the same problem, and will probably end up trying to flash the leaked Tmobile Rom.
Can you point me to where you downloaded this file? I think I found the thread, but I want to be sure

Deleted by user

got it! Thanks!
Now to ultimately decide if I want to flash this, since it's non-downgradeable

To update, flashing this rom has fixed my phone. Yay! Thanks!
I wonder if it was the 3.66x update that Moto pushed out - this phone was brand new, bought in Dec 2010, no other hacking done on it...

Beach_Head said:
I had that problem while trying the "Flash FroYo without losing downgradeability" solution: SBF Problem
After downloading, flashing every other available official ROM, and failing with each one, and seeing that no other SBF fro T-Mo exists anywhere, I bit the bullet and flashed the T-Mo signed FroYo ROM. And it worked!
So now I may have screwed myself over by flashing the leaked ROM but hey, it works well and is fast. Plus, it's FroYo so I now have A2SD and built-in Tethering...
Click to expand...
Click to collapse
How did you get it to show up in rsd

I'm not working on my phone because i think i messed it up enough, so i took it to a store that fixes phones. The guy told me that he had my battery on a universal charger and he still cant get rsd lite to recognize it... What can i do

Another Happy Defy User
Just to confirm, I was seeing the same thing gookia2000 was seeing. Here was my resolution in case it helps anyone:
I was able to get mine working by flashing the US Stock Froyo build as explained in this thread: http://forum.xda-developers.com/showthread.php?t=938708&highlight=bricked&page=2
I found this thread to be super helpful as it helped me confirm my suspicion that the battery being low was the issue: http://forum.xda-developers.com/wik...#Recover_Nearly_Bricked_Phone_.28hopefully.29
Thankfully my wife has the same phone so I borrowed her battery, otherwise I would have been going McGyver style per Sorensiim (da' man) as seen here:
http://forum.xda-developers.com/showthread.php?t=892026
So happy this nightmare is over - running Froyo is a little bonus love!
Thanks to all @ XDA!!!
-Dave

Defy wont come on get a white light!
im having the same prob i did the the steps but its not working is there anything else i can do or is there a video of the proceeder

I have the same issue with a Telstra defy. I can get RSD to recognise something is connected but it isnt listed as MB525 like before but as "S Flash OMAP3630" I have flashed various SBF files but nothing is changing.

[Q] HELP! Stuck at splash Screen

I rooted my phone with z4 root. Got Koush's bootstrapper was granted superuser permissions created nandroid backup downloaded liberty 1.5 flashed it without any problems, used it decided I wanted to check out Rubix Focused 1.9 same procedure had no problems flashing it over with bootstrap recovery mode. Decided I wanted to try the Watermarkd theme for it downloaded it transfered to phone no problem followed step by step instructions for this theme and when the phone rebooted BAM stuck at splash screen ( battery is now at about 40% life)
Realized I was going to have to SBF Flash phone downloaded all required tools drivers, the_gift, RSD 4.9 Went to turn phone on it wouldnt turn on. Hook it up to the wall I get the splash screen nothing else. Tried using the home power button search button to factory reset. After doing so same thing even after wiped partition. I can get into the bootloader screen also but it says low batter cannot program. Is the only way to charge my battery enough to SBF Flash it is by using an external charger or cutting the usb and manually charging the battery through the computer? How can I access my nandroid backup? I know there is something that can be done Im just a little to new to know what that is Please Help
Any help is certainly appreciated!

I do believe that there is a way to charge your battery by cutting the USB cord and I'm going to get back to you on that but one thing you really want to watch out for is that from my experiences, the_gift is for system version 2.3.315 (aka bootloader version 30.03) and since you were running liberty 1.5 I'd assume you're on version 2.3.320/2.3.340 (aka bootloader version 30.04). If this is true and you try to flash it you will brick your phone. Make sure you check you're bootloader version and if it is the newer one look for happy_holidays_from_tbh or something similar. Just make sure its for the right bootloader version

He is correct, you need to pay attention to that.
But you could also just charge the battery in a buddys phone and try again. But if you are like me with no friends ( , lol) you could stop by a store somewhere and ask if they could charge your battery for you in a phone for a bit. Usually they are pretty cool about it. Then that way you can try reflash to stock.
If you still had access to CWM, I would have recommended wipe, wipe dalvik, and reflash of liberty. But that is a nogo at this point.

Thanks for the heads up about the SBF file. I will delete the gift since it never registered on my pc when I loaded up rsd 4.9. ( might be the reason why haha)
Charging the battery is where I am at right now, I need to either wait for the external charger i bought off ebay to come in or use my buddys phone. I feel I am going to want to make sure when I do the battery charged I have detailed instructions in order to FLASH my phone. Im hoping when the battery charges I will be okay but as I stated I am new to this rooting thing and am learning everything super fast. Any and all help is truely appreciated.

How can I go from Unlocked bootloader/B20_Boot back to locked bootloader/B20?

Looks like I have to return my phone to ZTE because a hardware issue has appeared. It doesn't always charge when I plug it in and it never does quick charge 3.0 (Always says to connect original charger to charge faster even with the original charger). Never deep sleeps either.
I used B20_Boot method to unlock bootloader and am I little nervous about sending it back to them in this state. Any ideas guys?
Thanks.

runderekrun said:
Looks like I have to return my phone to ZTE because a hardware issue has appeared. It doesn't always charge when I plug it in and it never does quick charge 3.0 (Always says to connect original charger to charge faster even with the original charger). Never deep sleeps either.
I used B20_Boot method to unlock bootloader and am I little nervous about sending it back to them in this state. Any ideas guys?
Thanks.
Click to expand...
Click to collapse
Wait for the update , if what been saying is true , they'll release factory images and you can flash those images get back to normal state but we don't know yet till they release the images.

DrakenFX said:
Wait for the update , if what been saying is true , they'll release factory images and you can flash those images get back to normal state but we don't know yet till they release the images.
Click to expand...
Click to collapse
Thanks for the response man, I really appreciate it.
I am pretty paranoid that eventually I won't be able to charge my phone as it seems to be getting worse. If there isn't a way to do it now I guess I'll just send it back in this state. Not like I opted out of any warranty.

runderekrun said:
Thanks for the response man, I really appreciate it.
I am pretty paranoid that eventually I won't be able to charge my phone as it seems to be getting worse. If there isn't a way to do it now I guess I'll just send it back in this state. Not like I opted out of any warranty.
Click to expand...
Click to collapse
Have you try Factory Reset or Wipe Data-Cache-Dalvik from TWRP?
The update will be ready this week , I hope so you can just little longer but try the above.

DrakenFX said:
Have you try Factory Reset or Wipe Data-Cache-Dalvik from TWRP?
The update will be ready this week , I hope so you can just little longer but try the above.
Click to expand...
Click to collapse
I should have said yeah I did try factory reset. I think physically something with the charger port went bad. I was in recovery and the charger wasn't working. So weird.

DrakenFX said:
Have you try Factory Reset or Wipe Data-Cache-Dalvik from TWRP?
The update will be ready this week , I hope so you can just little longer but try the above.
Click to expand...
Click to collapse
Hey man I am quoting you so maybe you will notice. You seem pretty knowledgeable about this. Is there a img (twrp backup maybe?) of a working system partition for B20_boot? The final thing I can check is to reflash that and take out all the stuff that root and xposed did.

runderekrun said:
Hey man I am quoting you so maybe you will notice. You seem pretty knowledgeable about this. Is there a img (twrp backup maybe?) of a working system partition for B20_boot? The final thing I can check is to reflash that and take out all the stuff that root and xposed did.
Click to expand...
Click to collapse
The one I uploaded and is located in my thread (guide/info) have Xposed install ... But I have no issues ...just make sure to BACKUP YOUR SETUP before doing anything else and read that post

runderekrun said:
Hey man I am quoting you so maybe you will notice. You seem pretty knowledgeable about this. Is there a img (twrp backup maybe?) of a working system partition for B20_boot? The final thing I can check is to reflash that and take out all the stuff that root and xposed did.
Click to expand...
Click to collapse
You should be able to find it in this post, it's a full system image, so unzip and flash with TWRP
http://forum.xda-developers.com/showpost.php?p=68248798&postcount=53
There is also a possibility that the charger or cable went bad, only way to know for sure would be with another pair. BTW there is a way to go back to stock to the point that old OTA will flash, see
http://forum.xda-developers.com/axon-7/how-to/request-unmodified-byte-byte-dd-b20-t3459107

Intermittent charge(Help!!)

Hello, I'm so sorry for annoying you, but I'm having an intermittent charge when charging the phone, I don't understand why, I haven't dropped the phone or something related with poor care. I plug the charger to the phone, it appears charging but suddenly it stops charging, it happens with all the Roms, even with the stock. I have to disconnect and reconnect the charger to continue, it's randomly. Thanks in advance.

Maybe the cable or the charger have some issues? Try another one.

Bender1987 said:
Maybe the cable or the charger have some issues? Try another one.
Click to expand...
Click to collapse
Oh sorry but I didn't specify, I have tried with a Samsung charger, LG charger and others, even with the USB port from PC.

I had this issue. Also had a weird issue if unusual battery drain. I had to send it back to Motorola to get a battery replacement. Just came back yesterday and has been fine. I do not recommend the turbo charger in my opinion. Moto support told me not to use it...

daverobinson88 said:
I had this issue. Also had a weird issue if unusual battery drain. I had to send it back to Motorola to get a battery replacement. Just came back yesterday and has been fine. I do not recommend the turbo charger in my opinion. Moto support told me not to use it...
Click to expand...
Click to collapse
Okey thanks, I have cm14.1 and TWRP, I have a TWRP backup, it's necessary to return to stock? Like flash stock recovery and restore the stock rom with the backup? Also I flashed ElementalX kernel, then I returned to stock kernel but now on the bootloader says "firmware status: modified", obviously I don't have warranty, the question is, Would Motorola repair the cellphone?

D4N6L4CK said:
Okey thanks, what I have cm14.1 and TWRP, I have a TWRP backup, it's necessary to return to stock? Like flash stock backup and restore the stock rom with the backup? Also I flashed ElementalX kernel, then I returned to stock kernel but now on the bootloader says "firmware status: modified", obviously I don't have warranty, the question is, Would Motorola repair the cellphone?
Click to expand...
Click to collapse
I do not recommend this but this is what I did. I did a restore using fastboot. I also did the overwrite of the boot logo using fastboot. I did the online warranty thing about unusual battery drain. They gave me an email with a prepaid FedEx label to send it to them. Once it was received I did online chat daily and nagged about what's the status of it. All I know is I got it back and it was still unlocked and appears to have been reset because it was back to the black screen. So far I haven't had any problems the last couple days.

daverobinson88 said:
I do not recommend this but this is what I did. I did a restore using fastboot. I also did the overwrite of the boot logo using fastboot. I did the online warranty thing about unusual battery drain. They gave me an email with a prepaid FedEx label to send it to them. Once it was received I did online chat daily and nagged about what's the status of it. All I know is I got it back and it was still unlocked and appears to have been reset because it was back to the black screen. So far I haven't had any problems the last couple days.
Click to expand...
Click to collapse
I was thinking to do the same but I'm afraid of brick my phone, could you please tell me what guide you use to flash the stock?

D4N6L4CK said:
I was thinking to do the same but I'm afraid of brick my phone, could you please tell me what guide you use to flash the stock?
Click to expand...
Click to collapse
I used this thread and YouTube video. http://forum.xda-developers.com/moto-g4/how-to/how-to-unroot-moto-g4-return-to-stock-t3417386. Hopefully the link copied. It's in the Moto G4 forums. Make sure you have the correct firmware downloaded and adb tool.

daverobinson88 said:
I used this thread and YouTube video. http://forum.xda-developers.com/moto-g4/how-to/how-to-unroot-moto-g4-return-to-stock-t3417386. Hopefully the link copied. It's in the Moto G4 forums. Make sure you have the correct firmware downloaded and adb tool.
Click to expand...
Click to collapse
Thanks for your help!

Bricked, low battery, can't enter recovery mode.

So I bricked my phone
And now I can't enter recovery mode apparently because the baterry is low (red lightning bolt and red led flash). The phone won't charge, it boots up into error mode when I plug it into the charger but it never takes in any charge as far as I can tell. Left it hooked to the charger all night but low battery warning persists. Any ideas? please!

Have you tried switching it off then on again? :laugh::laugh::laugh:

osscar said:
So I bricked my phone
And now I can't enter recovery mode apparently because the baterry is low (red lightning bolt and red led flash). The phone won't charge, it boots up into error mode when I plug it into the charger but it never takes in any charge as far as I can tell. Left it hooked to the charger all night but low battery warning persists. Any ideas? please!
Click to expand...
Click to collapse
I have the same problem as you, I've been finding ways on how to unbrick my phone. As far as I can tell though, using fastboot and flashing some .img files won't work. If you haven't tried it yet I suggest you do it and try it yourself and see if it will work or not.

LioN-HearT said:
I have the same problem as you, I've been finding ways on how to unbrick my phone. As far as I can tell though, using fastboot and flashing some .img files won't work. If you haven't tried it yet I suggest you do it and try it yourself and see if it will work or not.
Click to expand...
Click to collapse
Yeah, I tried all the unbricking methods I could find. Extracted UPDATE.APP, flashed the typical .img files, but no shebang. Bricked as bricked can be so far. I will post if I can figure something out. Not looking pretty thus far. Thanks for the reply!

osscar said:
Yeah, I tried all the unbricking methods I could find. Extracted UPDATE.APP, flashed the typical .img files, but no shebang. Bricked as bricked can be so far. I will post if I can figure something out. Not looking pretty thus far. Thanks for the reply!
Click to expand...
Click to collapse
So, after some more head banging against the wall, some more crying, and some more moaning -my phone remained bricked. Finally, I reached out to the FunkyHuawei Club fellas, who very kindly and patiently replied to all of my doubts and helped me prep up the needed files to run the unbrick process. I borrowed some dough from a friend, bumped credits and used the tool, which in a matter of about an hour or so unbricked my phone (it flashes the entire contents of UPDATE.APP (~4.31GB) twice through, which takes some time).
Now all is well and swell. I feel a little dissapointed with myself for bricking my phone and not being able to unbrick it myself, but I can't complain one bit about the FHUbnrickTool. It works like a charm!

osscar said:
So, after some more head banging against the wall, some more crying, and some more moaning -my phone remained bricked. Finally, I reached out to the FunkyHuawei Club fellas, who very kindly and patiently replied to all of my doubts and helped me prep up the needed files to run the unbrick process. I borrowed some dough from a friend, bumped credits and used the tool, which in a matter of about an hour or so unbricked my phone (it flashes the entire contents of UPDATE.APP (~4.31GB) twice through, which takes some time).
Now all is well and swell. I feel a little dissapointed with myself for bricking my phone and not being able to unbrick it myself, but I can't complain one bit about the FHUbnrickTool. It works like a charm!
Click to expand...
Click to collapse
Looking back. It might have been possible to unbrick it without the tool if I could have gotten access to TWRP, which, long story short, was not possible at first because I had the wrong kernel, but then flashed the correct one, but then found myself in the low battery situation.
I found a script somewhere in these forums to be able to charge the battery bootlooping into fastboot, but I did not have the patience to try the script, as it takes a very long time to charge using the script (2% per hour if i remember correctly). But maybe it will come in handy to someone so I am attaching the script here.

scook94 said:
Have you tried switching it off then on again? :laugh::laugh::laugh:
Click to expand...
Click to collapse
hahahha.. yeah, that should work most of the time, right?