Develop Bugs

[Q] Yet another bricked Defy: no response at all

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..

[Q] Xperia Bricked after update-Already flashed. Help!

Hello there. I recently bought an unlocked Xperia Play from Ebuyer. I then rooted it successfully. But the problem is, my phone automatically updated itself one morning, causing it to be bricked. As I have already flashed the phone before I knew how to do it, but this time when I press the power button, my phone only vibrates once and nothing else happens, and only when I keep pressing the power button it just keeps vibrating.
When the USB cable is connected to my laptop, the phone has a Green light if that is of any help to you.
Thank you in advance. Any help would be greatly appreciated!
---Another problem I seem to be experiencing is the main drivers for the phone appearing as "Flash Device" but on my main computer it was seen as Android. Sadly, my power supply for my main PC failed (Not having much luck, am I?) and I can only use this laptop. Do you possibly have drivers for my XPeria Play for Windows 7 64 bit that would see my phone as Android? Or, could it be because my phone is bricked that it's only being seen as a Flash Device.

Ah... don't worry, it happened to me too not so long ago, it can be fixed. What you gotta do is relock your bootloader so it unbricks itself, while loosing root. Search here in the forums for something called Blagus Relock Bootloader Script. That green light you see there, that indicates your device is either fully charged, or it is in flash/recovery mode. Make sure to enter that mode before doing anything with it by holding the BACK buttoj (NOT the search button) while plugging in the USB cable to the phone. Search for the script I said before using fastboot or flashtool, I don't remember quite well. I'm new here so I can't give you the link, but good luck anyways! This will fix the problem, just re-unlock the bootloader again and you'll be fine. BEWARE, though, if you flash a new custom ROM after that, you will break the baseband/radio. You MUST re-flash a new, updated 2.3.4 firmware for you R800i/a/x/etc, DON'T use a generic from UK if your phone isn't from UK, and use US version if yours actually from America. I believe there's a difference but I did use first "generic" UK 2.3.3, then it bricked, relocked the bootloader, and flashed an updates firmware, totally generic, 2.3.4 that was made specifically for R800i and showed up differently than the other in flashtool. It has a new screenshot function which was pretty awesome, which wasn't my case since I was flashing CM7. Good luck!
EDIT: I usually hate doing this on forums, but since I'm new and my post does actually help I must say FIRST! I'm so happy right now

I have the same problem with my daughter's Play.
However it is originally an unlocked phone bought in Singapore. No rooting, no custom kernals, no nothing. It is original.
After installing the Firmware through PC Companion, she got the instruction to unplug the phone, remove and reinsert the battery and power up.
The Play vibrated once when the power button was pressed and then nothing....
I subsequently tried reflashing again with Flashtool but no difference. I see the .sin being flashed in but the same thing happened on power up... vibrate once and then nothing...
Any suggestions? Help?

How do you check if the phone is set to receive over the air updates automatically?
Sent from my R800i using Tapatalk

Black screen, no fastboot

I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..

If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59

Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.

The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/

freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...

Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.

freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...

familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone

freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^

familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.

freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^

[Q] Phone won't power on. Bricked?

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!

[Q] HELP! My Xperia Play Died!

Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.

You have a hardware failure, I see that right now is very common, you will need to replace the automatic light sensor, to get it working, or if you don't want replace it, you will have to switch onto JB, because it has ALS disabled by default.

Windshade said:
Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.
Click to expand...
Click to collapse
You could try using this app, https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=en , but i don't think thats the issue personally.

gangstermartorell said:
You have a hardware failure, I see that right now is very common, you will need to replace the automatic light sensor, to get it working, or if you don't want replace it, you will have to switch onto JB, because it has ALS disabled by default.
Click to expand...
Click to collapse
Okay I will try that later. Thanks!
fma965 said:
You could try using this app, https://play.google.com/store/apps/details?id=com.hatcyl.android.Disable_Auto_Brightness&hl=en , but i don't think thats the issue personally.
Click to expand...
Click to collapse
But I can't use it because there's no display on my phone.

Windshade said:
Okay I will try that later. Thanks!
But I can't use it because there's no display on my phone.
Click to expand...
Click to collapse
Flash a stock FTF again and see what happens.
try
fastboot erase system
and
fastboot erase userdata

fma965 said:
Flash a stock FTF again and see what happens.
try
fastboot erase system
and
fastboot erase userdata
Click to expand...
Click to collapse
I already tried it but it says permission denied because the device must be rooted. >.<
Sent from my GT-I9505 using xda app-developers app

Windshade said:
I already tried it but it says permission denied because the device must be rooted. >.<
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
actually no, it needs a unlocked bootloader to use those commands.

fma965 said:
actually no, it needs a unlocked bootloader to use those commands.
Click to expand...
Click to collapse
Yeah, tried it for the 2nd time.. I was able to erase system but I can't erase data because it says partition not found or permission denied.

Windshade said:
because it says partition not found or permission denied.
Click to expand...
Click to collapse
Which 1 is it?

fma965 said:
Which 1 is it?
Click to expand...
Click to collapse
That was the error message. It says "failed: partition not found or permission denied."

Windshade said:
That was the error message. It says "failed: partition not found or permission denied."
Click to expand...
Click to collapse
hmm i dunno then, wait for some one else to assist

Windshade said:
Help! I think My Xperia Play died on me! Here's what happened. It may be a long post but PLEASE bear with me. I really need your help guys! My phone was just lying around on my desk and I decided to use it and was surprised because it won't unlock. So i thought that my home button was just malfunctioning and tried to slide it's game pad as it unlocks the phone by itself but still no respond. So I thought it turned off by itself and when I tried to turn it on, it won't turn on at all because there's no short vibration. Usually when we turn on our device, there's a short vibration right? So I removed the battery, placed it back again and turned on my phone and at last there's the short vibration. But after a while I noticed that the boot splash hadn't appeared yet. I waited for a couple of minutes but still nothing happens. When I turned it on again there's the short vibration and that's it. So I searched for solutions here on XDA and on the web and I tried almost all of it. I flashed it back to it's stock firmware using Flashtool and still the same. I tried using PC Companion and Sony Ericsson Update Service but still to no avail. I also relocked it's bootloader and reflashed everything again but nothing works. So I gave up because I thought it might be a hardware issue but I didn't drop my phone or anything so i don't know what went wrong.
Then the following day I decided to check on my phone again and to my surprise it's back to normal and I was really glad about it. So I didn't flash any custom ROM and Kernels because I'm afraid that it might screw everything again. I just rooted it and completely debloated it and installed init.d support for stock kernel. I flashed CrossBreeder and RTMixManager and modified it's systemui for quick panel and battery % mod. I also flashed custom boot animation and that's it. I was happy about my phone because it seems all is well.
But yesterday when I was about to use my phone, the same thing happened again! I tried to redo everything I did all over again but still nothing! I can still use it in flashmode and fastboot though. I also tried entering CWM Recovery. After I turned on my phone I spam pressed volume down and blue LED showed up with the vibration if you enter recovery mode but there's no display. Can anyone tell me what's the problem? It might be the flex cable or the digitizer but I don't know. Has anyone encountered the same situation as mine? Please help me! I don't know what's wrong with my phone!
P.S. I can't send it to Sony Centre as my warranty is already expired. My only option is buying a new Xperia Play. Because I browsed for replacement parts on the web and they don't ship it directly to my country and it costs too much if I have it ship to me indirectly.
Click to expand...
Click to collapse
This happened to me and i had the phone checked and it was the flex cable that needed replacement

Did you find any solution or are blocked in recovery or flash mode?