Database Users

[Q] Updated MIUI, now Defy is dead

Hi everyone!
Today the new weekly release of MIUI was released. I downloaded it to my phone, and chose to install it. The phone rebooted and was stuck on the M-logo. I could only get into the stock Android recovery.
After some googling I found a site that told me to flash the phone with RDS Lite.
After having flashed my phone with RSD Lite the phone is simply dead.
The LED light turns white when I connect it to a computer, but nothing happens when I push the power-button.
I excperienced this also when I tried to root my phone, back then the issue was low battery. This time the battery was at 100 % when i updated MIUI, so i doubt this is the problem. The phone has been connected to AC charger for 30 minutes now, and there's still no reaction.
Anybody got a solution for this?

Holding volume-up and push power button. If you can get into bootloader, connect the phone to computer and get RSD lite working.

yuffany said:
Holding volume-up and push power button. If you can get into bootloader, connect the phone to computer and get RSD lite working.
Click to expand...
Click to collapse
whit this will not boot...
Jallenbo said:
Hi everyone!
Today the new weekly release of MIUI was released. I downloaded it to my phone, and chose to install it. The phone rebooted and was stuck on the M-logo. I could only get into the stock Android recovery.
After some googling I found a site that told me to flash the phone with RDS Lite.
After having flashed my phone with RSD Lite the phone is simply dead.
The LED light turns white when I connect it to a computer, but nothing happens when I push the power-button.
I excperienced this also when I tried to root my phone, back then the issue was low battery. This time the battery was at 100 % when i updated MIUI, so i doubt this is the problem. The phone has been connected to AC charger for 30 minutes now, and there's still no reaction.
Anybody got a solution for this?
Click to expand...
Click to collapse
you should make a flactory reset in stock recovery
it will boot whit MIUI

I didn't try the factory reset, but I think I got the wrong ROM. When I downloaded the Nordic Edition of Motorola SBF, and flashed it, the phone booted normally.

Defy can not boot - M logo flashes
It seems that our problems are similar and your Defy works again - what did you do to bring it back again?

[Q] Milestone 2 BRICKED, do not know what else to do. Help.

Hello Guys,
I bricked my Milestone 2 when trying to install the update for version Android 2.3.
It appers the Google logo when the phone starts, but it shuts off by it self.
When I try the recovery mode:
I get to it, but when I select the option of wipe data and reset to factory, does it start, but shuts off in the middle of the progress.
(When does it shut, I can turn back on easy)
When I try the bootloader:
Stuck saying that battery is low Can't program.
(I left the phone charging all day and I get the same message)
I do not know what to do anymore, some of the users here, says that is the battery.
But, the battery is bad or the phone is not charging?
When I plug the charger, the light turns on.
What do you guys think?
I already see the option in use the Nandroid Recovery, but I'm nor sure how to do it...
I do not have any friend with the same phone, so I will have to buy another battery or a universal charger, that I can charge the battery with out the phone.
Thanks in advance for your help.
Jeferson.

Wow, that was there so many times. For instance:
http://forum.xda-developers.com/showthread.php?t=1344740
or http://forum.xda-developers.com/showthread.php?t=1363918
in the sum some facts:
- you can't charge battery in bricked milestone 2
- you MUST have some charge in battery for SBF flashing via bootloader
1) you have to charge battery
2) you have to flash SBF via RSDLite

Milestone 2 hardbrick
First I upgraded the milestone 2 kitkat then disappeared until it was trying to downgrade and there it all began. No button works x vol + vol - @ all possible combinations already tried the rsd lite does not recognize the phone, adb and fastboot also not the phone, but makes up the sbf_flash is waiting for the phone in the end, the only thing q works is the LED side of the micro usb is solid and sometimes q could use rsd she appeared sw update in progress so but after that it also could not switch on the phone. I read a lot and could not find any case equal to staff]
Please help me
God bless us all ..
Thanks Hemerson
sorry about my english
google tradutor

[Q] Defy can't boot!!

Hi, when I tried to flash this rom: http://forum.xda-developers.com/showthread.php?t=1768702 it gave me an error("the process can't be done" or something like that) and after that I pulled out the battery and when I put it back, I turn on the phone and it gave me bootloop, and I can reach the bootmenu but only if the phone is "charging". And one more thing, I can't boot into custom recovery because it give me the error: "E:Error in /system/bootmenu/script/recovery.sh (Result: no such file or directory)", however I can boot to stock recovery but, I tried to wipe data/factory reset and then reboot, but nothing happened, it gives me bootloop.
PS: My pc and RSD Lite doesn't recognize the phone, and I can't charge the my defy because when I try to charge it, it shows me the battery with a question mark inside it.
So, what should I do in this case?

out and in battery untill success i had the same i coulden't switch on the phone ,there was only red led and write google ,i put out and put in battery several times and it worked after.

slon11 said:
out and in battery untill success i had the same i coulden't switch on the phone ,there was only red led and write google ,i put out and put in battery several times and it worked after.
Click to expand...
Click to collapse
I tried that already and it didn't work. And one more thing, my defy doesn't get stuck at google logo, it gets stuck at motorola logo and no led is on(first at motorola logo I have the blue led turn on, and after 1-2 sec it turns off and then it gets stuck at motorola logo, and nothing happens).

what happand when you push vol- when this blue led lights ? try, if nothing happand try push power and vol- in the same time and keep until sth happand ,if this not works hm.....
one thing ,you have defy plus or defy ?, becouse defy plus prabobly works with vol+ or both ,try every option

slon11 said:
what happand when you push vol- when this blue led lights ? try, if nothing happand try push power and vol- in the same time and keep until sth happand ,if this not works hm.....
one thing ,you have defy plus or defy ?, becouse defy plus prabobly works with vol+ or both ,try every option
Click to expand...
Click to collapse
I have defy, and I can turn my defy on only if it is conected to the charger, and when it shows the blue led if I push on the vol+ It goes in bootloader and there it says: "battery low cannot program", and if I push on the vol- it goes in the bootmenu, and from there I can go only in the stock recovery.

Are you sure the battery was charged before flashing CM10?

nastys said:
Are you sure the battery was charged before flashing CM10?
Click to expand...
Click to collapse
No, my battery was low( maybe 15-25%) before flash-ing CM10.

mih406 said:
No, my battery was low( maybe 15-25%) before flash-ing CM10.
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=1828639
See How to fix empty battery. Then try again.

nastys said:
Try this:
http://forum.xda-developers.com/showthread.php?t=1828639
See How to fix empty battery. Then try again.
Click to expand...
Click to collapse
Before you post, I tried the mcgyver method, and it worked! Now, I am charging my defy, but it doesn't charge normal, like other phones, it jump from 50% to 70% and so on, and I don't think that this in normal, otherwise, this is the only issue that I've encountered so far.

[Help!] Bootloop.

So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.

Charge battery with mcgyver metod or with other defy & reflash it with 231 sbf. For more info read: http://forum.xda-developers.com/showthread.php?t=966537

So, there's no other option out there?...

Deformat said:
So, there's no other option out there?...
Click to expand...
Click to collapse
Recharge battery with mcgayver metod and reflash sbf, you'll need start from scratch, because your bootmenu was corrupted and you can't restore nandroid or reinstall zip

Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...

Can't acsess anything
locn said:
Once you have flashed the sbf and back on stock you need to go into the moto recovery and do a restore to default / format system. that should get around the boot loop issue... at least it did for me...
Click to expand...
Click to collapse
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi

Heddi72 said:
Hi together, well I hope this is the right place.... I'm owner of a motorola Defy MB 525 that ran without any problems on cm9 nightly for last 6 month. Now suddenly it doesn't start any moer andIi can't access recovery setup nor anything else so it's impossible to wipe anything, too. When connected to my notebook only the white LED is shining but nothing happens. The typical "hardware-found-ping" appears and several seconds later the " hardware was removed ping." The right drivers are installed on my notebook, but even RSD Lite doesn't found my Defy so I can't flash enything. Anyone has any Idea what to to?
Thank's in advance for any help!
Heddi
Click to expand...
Click to collapse
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
Deformat said:
So, I had some issues with my Defy+...
I tested the latest 4.1.2 nightly and seemed like my backup was corrupted (?!) and I had to flash a 2.3.6 BL-6 .SBF since the backup would make me enter a bootloop.
Well, I tried with different .SBFs and sadly all of them have the same effect: the flashing process moves smooth, except that in the moment when I'm asked to power it up it's entering a bootloop.
Now, my battery STILL has some inside, but trying to charge it won't work(gives me the "?" sign). Don't know what should I do. Should I leave the phone in the bootloop until the battery goes away and then to re-flash a .SBF?...
Or my flashing process wasn't good enough and there's a workaround I don't know?... I don't want to brick my phone forever.
Click to expand...
Click to collapse
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.

bootloader
corrinti said:
Do you connect it to RSD in bootloader mode? Volume + when powering on. What is on the screen then?
If you haven't flashed yet try to keep with BL6 sbfs, and not BL7 like 231.
After battery charge try to get to stock recover (volume down when powering on) and wipe data/factory reset before flashing.
Click to expand...
Click to collapse
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris

Heddi72 said:
Hi, I can't enter bootloader mode, nor anything else. The screen stays dark and the phone doesn'treact. Only mi notebook pings when i press the startbutton one phone. Once for Hardware detected and seconds later for hardware removed. from time to time the notebook tries to find drivers, but couldn't and abort searching.
Chris
Click to expand...
Click to collapse
And your battery? Is it charged?

[Q] Defy bricked. Wont turn on, only white led on pc

I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?

Niko. said:
I had cm11 (or 10, not sure) installed for about a month now (back in december) .... Went on a trip, and when coming back my phone battery ran out at the airport somehow, but i had fully charged it and i was not out all day enough for it to run out fully... I take my phone home, not really giving it much importance, and i noticed it was stuck on the bootlogo.. so i went into recovery and tried to re-flash the rom and fix it, but when i was installing the ROM again, the phone shut off randomly (i heard that happened with a certain recovery menu software sometimes, i cant remember the name)... then the phone wouldn't charge and/or turn on, and when I connect it to the pc, nothing happens other than the white led coming on.. RSD won't recognize it...
So i found out i had to charge the battery manually, and used a Universal Charger... Still, no recognition by RSD Lite...
Finally, i found a way:
1. Open RSDLite
2. Connect phone (no battery on it)
3. While holding Power + Vol Up, put the battery in
4. RSD will recognize your phone!
Problem is, it recognizes my MB525 as "S Flash OMAP0360"
And when i try to flash a .sbf i used previously to recover my phone (had bricked it before by trying to change ROMs in a sloppy manner), it seems to flash smoothly, but when it's going to reboot the phone, the progress goes up to 100% and then asks me to reboot it manually.. I read somewhere that to fix that i should take the battery out, disconnect the phone, put it back in, and make RSD recognize it like i mentioned before...... and after RSDLite says flashing is PASSED, the phone still won't turn on... I have tried at least three times and gotten the same result... Help?
The SBF i am using (because it helped me save my phone before) is:
JORLA_U3_3.4.2_107-9_SIGNED_USAJORDMR1B25TIGCOLA01E.0R_JORLAFROTIGCOL A_P009_A002_M010_HWp3_WIG146037_Service1FF.sbf
EDIT: Also, i read somewhere that when all you get is the white led (when connecting to PC) it means that your battery is not charged enough for flashing.. ?
I don't know what to do?? I read that defy's are really hard to brick... But mine got bricked out of nowhere.. wtf?
Click to expand...
Click to collapse
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.

htto said:
Hey there. Well, if it's still flashable it ain't bricked. I've got my other one to not be recognized (broken bootloader), which is beyond usual repair. So, did you you flash some random SBF before the rescue one you're trying out now? There's a problem with previously flashed GingerBread or Defy+ SBF images. So it would be good to know, what was the SBF running before trying "JORLA_U3_3.4.2_107-9". Also according to http://sbf.droid-developers.org/phone.php?device=27 that is 2.2.1 and there's also a "Android 2.2.2 Blur_Version.34.4.802.MB525.Latam.en.01". Tried that as well?
Anyhow, if the phone is seen by RSDlite it actually powers on and is recoverable. If the screen is just staying black, then you probably tried a downgrade from a Gingerbread SBF and didn't watch out for the BL-version.
If it's a BL-version problem then this might help. Also there is a guide to unbrick. And yes, keep an eye out for the battery level. Best would be an external charger, as the phone does not charge. McGyver way should still work though.
If it shows a LED and is seen over USb, it's not dead (yet)
Also look out for section "Common Problems/Questions" here.
Click to expand...
Click to collapse
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing

Niko. said:
No, i have not flashed other SBF's ever... only CM roms but i did it through the phone itself, in recovery mode.. I'll try the 2.2.2 one you told me about and see how that works out!
EDIT: No luck, the phone stays at a black screen.. it wont even reboot when RSD is done flashing.. i have to take the battery out and put it in bootloader again for RSD to say it PASSED the flashing
Click to expand...
Click to collapse
Too bad Anyway, did you try 8. from here, that is
"
If you get " Please manually power up this phone " in RSD Lite pull battery out > put your battery back > reboot into stock recovery by holding Power button and Vol- button > Choose Wipe data/cache > Choose Reboot system now
"? Also holding Power and Vol-Down while inserting battery is said to work.
I wonder if there is an SBF that also flashes cache and userdata partitions...

Nope, it just stays black-screened.... It only works if i do VOL-UP for bootloader mode, but that doesnt help

Umm, as a shot into the blue: Did you try to reinstall the Defy drivers from Motorola? It seems that missing those hinder RSD lite from detecting the Phone as MB52x and instead just show the Processor identification, i.e. "S Flash OMAP3630"

Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Sent from my MB526 using Tapatalk

thekguy said:
Try dfp 231. The processor identification is correct( rsdlite has been set up properly).
Click to expand...
Click to collapse
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.

htto said:
Yeah, it worked also for the defy in this thread.
And just for reference the original thread with the hinted SBF:in post #4
"
WIIII i have successfull unbriked my defy with this rom
defyplus_u3_4.5.1-134_dfp-231_cn_sign_ucadefyemarab1b50aa009.0r_pds03c_usajr dngibrird15_p015_a030_service1ff.sbf.gz
"
Basically had the same BL7-problem.
Click to expand...
Click to collapse
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...

Niko. said:
wtf, the phone flashed correctly and everything but the screen won't turn on.... The computer recognizes it as MB526 now, and i can touch the home button and stuff and it will vibrate like it used to when it worked... i can also make the ringtones play using the moto portal page... Everything works (except for calls) other than the fact that i still have a black screen... the screen just wont turn on... Also it said it had very little internal memory compared to what it had before (had at least 2 gb i think.. now not even one)
I had sent the phone over to fix, and they told me it was unfixable... Is it possible that the guy (it wasnt an official company) who "tried to fix it" simply took parts out of it ? -_- (if he had taken parts out of it im guessing the phone wouldnt turn on at all..?)
What can i do to turn the screen on??
EDIT: i flashed DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf
I couldnt find the one you posted there so i did the central europe one...
Click to expand...
Click to collapse
Umm, according to this thread it is supposed to be this one.
The GR vs CN maybe doesn't make a difference, but maybe the P022_A022 vs. P015_A030?
Doesn't a working phone portal allow for somehow to get logs/adb etc?