Related
I flashed my Defy with froyo, then installed CM7, i charged it to 20% battery and turned it on. All worked fine for a couple of minutes, but afterwards it started restarting every 30 secs, So i tried flashing it again with the Chinese froyo (I'm from Israel, if it matters), but without charging the battery back to full, Which means I started flashing with about 15% battery.
I finished flashing rsdlite wrote "pass" and everything but the defy wouldn't power up, it just shows white led whenever i plug it to my PC. rsdlite recognized it in the first couple of hours and i tried flashing froyo again and again, but after a while even rsdlite didn't recognize it anymore.
I read a thread here that said that the phone doesn't charge in boot mode, and i thought that might be the problem, so i took out the battery and charged it at a phone store for about 15 minutes, then tried to turn it on but still no powering up. So now I have a defy that doesn't power up and isn't even recognized by rsdlite.
I'm hopeless, I loved my defy very much, and I really need an clue.
I'll do anything!
Thanks for reading this far, I hope you can help me
http://forum.xda-developers.com/showthread.php?t=892026 maybe this will help
Tried it, didn't work, I also tried to charge the battery already so I think its not just a dead battery problem, its probably more than that.
Hi there and welcome to the forums. You didn't mentioned which was the base OS you've had on your Defy before installing CM7, but I'll assume you have had a Froyo version, maybe the stock one (please provide more details).
If you flashed nordic SBF before installing CM7 or if you had official Froyo on your phone then you won't be able to Flash the leaked Chinese Froyo. It has some partitions with version code -2- like Eclair, whereas the nordic ROM has the code -4- and therefore it's not possible to directly downgrade by applying the Chinese SBF.
To revive your Defy you must charge your battery (at least 50% to be sure it will have enough juice and will last the whole process), then start it in stock recovery (Vold Down+ Power and then by pressing both volume buttons when the android with exclamation mark appears) and wipe data+cache. After this step you can start your phone in bootloader mode (Vol Up + Power) and flash again the initial ROM you had right before installing CM7.
you are from israel right?
why you choose chinese froyo for god sake?
some chinese froyo sbf is intended only for different DEFY (ME525) / Chinese Defy, and normal Defy is MB525.
it could damage your flashlight and phone.
use sbf from central europe froyo for best result installing CM7.
thanks guys, I charged the battery, got rsdlite to recognize the phone, and flashed a UK sbf, now its back on, working, and showing that motoblur animation.
I guess now all that's left is to install a 2.1 OS and everything should work.
(Please correct if I got this wrong, since I AM a noob and i really don't want to make another mistake)
THANKS ALOT!
If you flashed a full Froyo SBF then you cannot install Eclair SBF. It's not possible to directly downgrade after you have flashed Froyo using a full SBF. However you can easily flash a Froyo official ROM or... why not CM7 or MIUI.
Thing is... I already flashed 2.1, and got it to the point where it shows me the M logo. but it didn't go any further than that. i tried flashing a 2.3.3 ROM, same thing happens, M logo but nothing more. right now im back to this version of 2.2:
p3_jordan_umts_jordan-user-2.2.1-3.4.2-107_JDN-4-000000-release-keys-signed-T-Mobile-US.sbf
and I'm getting an animation of Motoblur with nothing else.
flaah nordic sbf then go to cm7. Follow the guide read first cm7 faq before proceeding
Sent from my MB525 using XDA App
All you do is flashing.. Have you actually do total wipe in recovery? Since you're having the motoblur animation splash screen, it is obviously your previous data is conflicting while the phone is trying to boot normally..
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium
farsight73 said:
All you do is flashing.. Have you actually do total wipe in recovery? Since you're having the motoblur animation splash screen, it is obviously your previous data is conflicting while the phone is trying to boot normally..
Sent from my awesome Moto Defy: Stock Rooted Gingerbread 2.3.3 - XDA Premium
Click to expand...
Click to collapse
I believe you are right about wiping, I've bricked my phone to the point i couldn't turn the phone on. So all you usually have to do is flash the full sbf, when it tries to boot it gets stuck on the m logo, just pull the battery, power it up holding volume down wait for the the triangle and press the middle of the volume rocker and it will take you to the stock recovery. Wipe and factory rest, flash the sbf again.
wipe/factory reset didn't fix it, though I noticed nordic sbf got it to show the android animation.
is it possible that I need to install a rom after I flash an sbf? and if so, how can I install a rom (custom recovery doesn't give me an option to install a zip, only "update.zip").
do I install some sort of 2ndinit?
do I install a rom through "update.zip"?
sorry once again for another (hopefully last ) noobish questions.
The SBF is a full ROM so atfer flashing a SBF there is no need to put another ROM via recovery, unless you want to do so (let's say you'd like to install CM7 or MIUI). If you haven't flashed a 2.3.4 full SBF you should be able to revive your Defy using the nordic SBF. Try to download it again or try a different one (one of those official SBF's released this summer).
I did install a 2.3.4 full sbf, but it too didnt work, tried a factory reset + cache wipe, and reflashing the 2.3.4 and it's still stuck on the M logo
Ive done something stupidly wrong.. Help me please..
Ok Ive a me525 and I tried to flash my phone with JRDNEM_U3_2.51.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTINT_P029_A018_HWp3_Service1FF
Was not sure what I was doing at that moment(just following a guide/tutorial on YouTube)After the whole progress with RSD lite, my device turned black as the title says with only showing a white led light. Was getting pretty deperate thinking about I had broken the phone.. :crying:
I have searched for a solution on the forums saw some people did get their device repeared, but everything they had done didnt worked for me..
So please help this boy in need.. We dont have lots of money to spare so buying a new phone isnt really a fast option..
p.s. Not sure though but would a chinese sbf work and where would I find one?
Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading
The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.
I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk
I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.
what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium
When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.
Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk
I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate
Is the general consensus that this is an unfixable hardware issue, then?
Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow
Hey guys. I'm trying to fix my friends Defy for him. I've rooted my old Evo 4g, my wifes samsung transform, and her motorola Photon Q so I'm pretty familiar with rooting. But I'm having a problem with his Defy. Here's the skinny:
So his phone froze up on him. And after pulling the battery, it now won't boot. So I booted into recovery, and tried a factory reset. The factory reset won't complete. The little loading bars that go across the screen just keep going forever (I let them go for 3 hours straight one day). And I still can't get the phone to boot. So I figure, no big deal, i'll just root and install custom recovery. So I looked into rooting methods for the Defy, and they all seem to involve booting the phone. Does anyone have any ideas? Or know of a way to reflash the original recovery? I'm assuming the problem is the recovery. Thanks in advance for any help. And my buddy thanks you too.
You can use RSD to flash it with stock rom of your region. Do not flash any gingerbread rom if the phone never had gingerbread(you will have downgrade issues).
I don't want a Tapatalk sig!
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Any Luck M8
dhughes214 said:
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Click to expand...
Click to collapse
was just reading your post and was wondering if you have had any luck with your buddy's Defy ???
Flashing a fresh .sbf using RSDlite should fix the recovery problems, as it will overwrite it with a fresh one. The /system partition will be rewritten, also. After flashing, the phone might boot to the system already, but if not, just enter recovery and do a factory reset, now it should finish fine and boot fine, as well. (it doesn't matter if you do a factory reset before or after the flash)
Latest RSD Lite I've found is v6.1.4. You will also possibly need drivers, google for - "Motorola_End_User_Driver_Installation_5.9.0"
Keep us posted! Good luck
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Battery
Williamharv said:
Hi all,
Recently I've had a few troubles with flashing ROMS, to the point where I cant start my phone without it rebooting. I've been using CWM PhilZ 6.0.4.4, GT-I9505 and I did a full wipe everytime.
Originally I was on Omega 10 and decided to try out a new ROM (phone kept dying at 15% for some reason as well). Flashed PACman ROMs latest nightly and had some troubles getting past the set up as it froze every time, and when I tried rebooting it, it would simply not start. It was suggested to upgrade my recovery, so I did so from PhilZ CWM 3.0.3.3 to 3.0.4.4. Tried it again and it worked fine, but due to my own clumsiness I accidentally restored system data from Omega to PACman. Obviously it wouldn't start properly after that, reflashed again and was very careful to only restore apps (restored SMS as well as .xml). Everything was fine except a few bugs here and there, but then I rebooted it and it just wouldn't start.
After that I tried cyanogenmod, as I thought it would be more stable. Pretty much same thing happened, less bugs but when I tried rebooting it just wouldn't start.
Given up by this point, I tried reflashing Omega v10. It worked perfectly for a few hours, flashed the latest 3minit framework and ausdim kernel. The next day, my phone suddenly died at 42% and when I try to start it up it gets stuck at the Omega logo. Went into recovery, tried doing full wipe again and cant get past setup without it turning off. Furthermore, when I try to reflash, it just unpacks the zip but turns off randomly.
I'm not quite sure what to do next, I'm thinking it's my recovery not doing wipes properly since when I try to wipe dalvik it says "path not found", and if I try to reboot with recovery it says "root may have been lost, would you like to root?"
Sorry for the whole wall of text, just thought all the information would be better than not enough! If anyone could help it would be greatly appreciated as I cant even access my phone currently
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
I also think there's a problem with your battery, it might need to be replaced.
ebahena said:
Seems to me that you are having battery issues. You might need to get a replacement. If that doesn't work you could try flashing a pre-knox ROM though ODIN 3.04. This would mean starting from scratch, but it could be your solution.
Quick question. Are you downloading the ROMs with your phone or downloading them with your computer then moving them to your phone via usb? because it might be your pc's/usb fault.
Click to expand...
Click to collapse
Thanks for the quick reply! Would the battery explain why my ROMS wouldn't start though? Such as how Omega got stuck at the logo. I will try using my friend's battery, or just keeping the phone on charge whilst doing it and see how that works.
Im sending them through Usb currently, is there any other way to get it on my phone as I can't turn it on to send it over wifi :/
Sent from my GT-N5110 using Tapatalk
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
norml said:
Whenever you flash stock tar through Odin, the phone will restart by itself and wipe cache. After it does this, you should factory wipe and no more bootloop, or soft bricks. I would start from scratch if i were you. If you have working custom recovery installed., I would go in and do a format, not a wipe, but format the sdcard and restart into download mode and flash stock tar, cf auto root, and then flash a custom recovery. And then decide what rom to flash.
Click to expand...
Click to collapse
Thank you for the reply i just got home so I'll try this soon, would it be risky though since my battery and/or cable may be damaged, meaning if it turns off during flashing stock, I'll get a hard brick?
Update: just reflashed Omega whilst it was on a charger and it actually worked.
Does this suggest that the battery is damaged?
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Sounds to me like a definite battery problem.
Samsung recalled batteries with a serial number starting with BD. have a look and check your battery mate.
Also check it's not swollen
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I just checked my battery, it does start with BD, and it does appear to be somewhat swollen.. I haven't noticed it before :l Could I just return it to Samsung for a replacement, without going back to stock ROM? I'm currently in Australia, haven't really seen a Samsung support center anywhere nearby.
Update: got my hands on a new battery, everything seems to be working great now. Flashed paranoid android, no reboots or any other problems.
Thank you so much to everyone who helped
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
tmcookies said:
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
Click to expand...
Click to collapse
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Click to expand...
Click to collapse
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
tmcookies said:
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
Click to expand...
Click to collapse
Is RSD recognizing it?
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Is RSD recognizing it?
Click to expand...
Click to collapse
Who would have thunk? RSD Lite did recognize the phone and when it started flashing, the phone showed
"SW Update
In Progress.."
So, now what? Which sfb file should i flash?
Anyway, thank you so very much!
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Yes, root again if needed.
I saw your other post in the cm11 thread about how your phone died.
I remember reading somewhere in the forums that you should go to cm10.2 before installing the updated recovery, and then install cm11.
I'm not sure if that's 100% accurate, and I couldn't find the link (sorry).
Couldn't hurt, though, seeing as you'd just have to do a few extra ROM flashes.
Good luck!
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
after some effort - great on CM11!
leandrolutz said:
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
Click to expand...
Click to collapse
I had a simiilar problem - somehow after a similar failed CM11 install, I pressed that "reboot" button and my mb525 was dead. I did as suggested here, Except I happened to have CM10.1 not CM10 on the SD.
However I had a lot of trouble getting a successful boot after installing update-recovery.zip, and then also after installing CM11 with the updated recovery.
Now I have a great well-running defy on CM11. I don't exactly why it succeeded when it did - just repeatedly wipe and install and wipe until it worked.
The defy really runs well on CM11 - very responsive - it is robust both in HW and SW! - maybe I'll myke it my main phone again! (before the S3 or the xperia V) - Samy just ain't interested in my S3 - the community provides the same Android version for my defy as I have on my nexus 7 2013!!!
Many thanks to all who have contributed, especially quarx -
try this http://forum.xda-developers.com/showthread.php?p=48501247