[Q] Brick Help - Droid RAZR M Q&A, Help & Troubleshooting

I've done my best, and now I must reach out. I got an M from my friend that is completely locked up at the initial red "M" logo. The only thing I can do is get into fastboot, and I can communicate with the computer from there. I can flash the fastboot files (I've tried both Jellybean and ICS), however even when it goes through a successful flash, the phone acts no differently; will not boot. I've tried editing the xml a few times with no luck. Now, when I try to flash, it hangs up at random stages (first it hung up at 16/19 cdrom, now it's hung up at 7/19 flash modem). My only thought other than being hardware issues is that the batter isn't full enough to sbf. If this is the case, how can I know that it's charging, since it won't charge in fastboot? When I plug it in to the wall charger, it turns the phone on to the M logo, but hangs there. Does that mean it's chaging? Thanks in advance.

It should charge the second you plug the lead in whether it boots or not
Sent from my GT-I9300 using Xparent Skyblue Tapatalk 2

Alright, it just went through another "successful" JellyBean sbf. Still no boot, so I turned it off from fastboot and then plugged it into the wall to let it (hopefully) charge.

It doesn't appear to be charging. Now when I boot into fastboot, it says "Battery Low". Any more suggestions?

razgriz8426 said:
It doesn't appear to be charging. Now when I boot into fastboot, it says "Battery Low". Any more suggestions?
Click to expand...
Click to collapse
Call Motorola I had the same problem and couldn't fix my phone, had to return it for a new one. Luckily I was within my return dates

Related

Bricked phone!? Please help me!

Hello! I think i bricked my phone. (MB525). With the latest Quarx CM10 everything is fine, the phone charge, etc... But randomly the phone dont charge anymore with wall charger or usb.
Now, i cant boot, the phone dont charge. When i connect to pc i see white led. With battery and wall charger i can access to bootmenu, recovery. But if i disconnect from wall charger the phone shutdown immediatly. So i cant flash any sbf via rsd lite. I try to restore an older nandroid, but nothing changed.
What can i do? Please help.....
Brother just flash or phones sbf Frm rsd lite u will search tutorial here
Sent from my MB526 using xda premium
illumanati22 said:
Brother just flash or phones sbf Frm rsd lite u will search tutorial here
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I cant flash it. Bootmenu or recovery only work with power cord on the wall. If i disconnect and try to attach the phone to pc (to flash) its shut down
XianHuen said:
Hello! I think i bricked my phone. (MB525). With the latest Quarx CM10 everything is fine, the phone charge, etc... But randomly the phone dont charge anymore with wall charger or usb.
Now, i cant boot, the phone dont charge. When i connect to pc i see white led. With battery and wall charger i can access to bootmenu, recovery. But if i disconnect from wall charger the phone shutdown immediatly. So i cant flash any sbf via rsd lite. I try to restore an older nandroid, but nothing changed.
What can i do? Please help.....
Click to expand...
Click to collapse
Hi, there!
I'm not an expert, but maybe I can give you a direction as a starting point.
Either your battery is empty and only needs to be reloaded or it is to old, so you have to get a new one.
A third posibility is, that the battery is empty and had not always contact to get loaded, but that I can't say from here and it's up to you, to check over.
And also your cable and your plug could be damaged.
Your options:
1. Reload your battery (and test its health) in another device or an external loader. You could put it in another Defy of a friend. Or bring it to a service center for cell phones for reloading.
2. You could otherwise buy an new (loaded) battery. Service center again?
3. Finally you could try the following method with the risk of a final damage to your battery:
http://forum.xda-developers.com/showthread.php?t=892026
Tell us, how it has been going for you.
Good luck!
:fingers-crossed:
XianHuen said:
Hello! I think i bricked my phone. (MB525). With the latest Quarx CM10 everything is fine, the phone charge, etc... But randomly the phone dont charge anymore with wall charger or usb.
Now, i cant boot, the phone dont charge. When i connect to pc i see white led. With battery and wall charger i can access to bootmenu, recovery. But if i disconnect from wall charger the phone shutdown immediatly. So i cant flash any sbf via rsd lite. I try to restore an older nandroid, but nothing changed.
What can i do? Please help.....
Click to expand...
Click to collapse
As long as the white LED is there, you are fine. Just charge that thing for some hours.
If you have a nandroid backup you can restore that without the battery but with the wall charger connected.
Swift2603 said:
As long as the white LED is there, you are fine. Just charge that thing for some hours.
If you have a nandroid backup you can restore that without the battery but with the wall charger connected.
Click to expand...
Click to collapse
Thank you guys! I try to charge it via usb, but the phone always started automatically after 5 minutes
That happened to me while ago, I just plug my phone to the wall charger and left it for like two hours and the battery charged quite fine.
XianHuen said:
Hello! I think i bricked my phone. (MB525). With the latest Quarx CM10 everything is fine, the phone charge, etc... But randomly the phone dont charge anymore with wall charger or usb.
Click to expand...
Click to collapse
I don't have any advice really, but just wanted to note that I've experienced something similar. I'm on the Nov 2 CMX build from Quarx.
Every couple of days, my phone won't charge when connected to wall charger or USB, signal bars never change, wifi is dead, and clock is dead. My phone basically stops functioning altogether until I reboot. Rebooting always seems to fix it for me though.
If you need advice on which SBF to flash send me a PM or something. I had to flash an SBF for the first time a month or two ago, and finding the proper SBF was the most difficult part of it all.
Thanks for the help guys, i can flash the sbf, but now i get "code corrupt" and "battery low" errors. I can charge the phone via pc, but its restart in 5 minute. I keep charging it, but after 3 hour its still "low battery" message. With wall charger, the phone enter to bootlader and 1-2 minutes later the "battery low" error disappear but no charging led. After this the phone dont have enough battery life (i keep doing this charging method for 2 hours)
Charge your battery longer.
Check the MD5SUM of your SBF
This post has been beamed to this area by quantum teleportation.
Coodarah said:
Charge your battery longer.
Check the MD5SUM of your SBF
This post has been beamed to this area by quantum teleportation.
Click to expand...
Click to collapse
I tried everything. When usb-pc in, i see the white led. 5 minutes later the phone enter to bootloader mode. Low Battery, Cant program error messages flashing. After 2 minutes the phones say "OK" and RSD lite recognize the phone! BUT! I cant do the whole flashing process, because 3 minutes later the phone shut down. If i wait to charge more in the bootloader more, its still shut down in 3 minutes.
I try to shut down the device everytime if its enter to bootloader, to charge more, but after 8 hours doing this, its still "low battery".
XianHuen said:
I tried everything. When usb-pc in, i see the white led.
[...]
I try to shut down the device everytime if its enter to bootloader, to charge more, but after 8 hours doing this, its still "low battery".
Click to expand...
Click to collapse
I think, we are at a point at which we are running in circles, my friend.
You tried just everything to reanimate your phone.
You must check your battery in ANOTHER device or load it in ANOTHER external charger to be sure that it's okay. Not in your phone and not in your PC.
If the battery charges well, then your phone is either physically damaged or bricked.
(Service Center needed)
Otherwise, if it's (battery) just charging fine and your phone boots up, first flash stock SBF and then flash what you want to.
If the battery isn't charging in that OTHER charger, then you know, you have to buy a new one.
Another thought, not very likely, but maybe your phone is damaged by overclocking/heat and suffers due to this under those permanent blackouts?
Bottom line is: you need another Defy with another battery to find out for yourself to solve your problem.
Unfortunately there is no wizardry
Question:
Is it necessary to go to boot loader for charging?
(I'm not sure about that.)
As a try, just let the phone off connected to power for a couple of hours.
__________
This post has been beamed to this area by quantum teleportation.
Thank you!
I flashed 4.5.3-109-fixed.sbf and i GOT MOTOROLA BOOT LOGO! but always bootloop.
Now, if i flash DEFYPLUS_U3_4.5.1-134_DFP-231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf.gz
its okay? And i get fully working rom? (i know its defy+ but with the fixed sbf its partially working)
Glad to read that. This is good news :highfive:
Nope, unfortunately you won't get it running with a Defy+ SBF without having trouble/more work on your side.
Better download a MB525 SBF playing the game save. But it's your very own decision.
First see here (Maybe you already know all this stuff):
http://forum.xda-developers.com/showthread.php?t=1216982
Then, after lots of reading, swearing and understanding read on here:
http://forum.xda-developers.com/showthread.php?t=966537
_________________________________
Okay, I would take one of the MB525 SBFs from the "Android 2.2.2 "Froyo" section (3.4.2... or 3.4.3...)
NOT any Chinese SBF = no go!
But watch out for your Bootloader version (BL5, BL6) and your type of camera (red or green lense).
After flashing your stock ROM/SBF and the initial rooting, I would first make a NANDROID backup (CWM Custom Recovery) to have a clean ground.
Then I would first flash the stable CM7.2.0 and also do a NANDROID backup (CWM Custom Recovery) to have a solid home base for playing around.
Finally I would flash the latest Nightly of CM10 02.11. + Update from 07.11. completed with gapps minimal or gapps signed from 2012.10.11 (Google apps Android 4.1.2)
Much work to do for you, but remember: Even the longest way starts with only one little first step.
:fingers-crossed:

Blinking Red Light - I Might Be Different

Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)
Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.
Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.
I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.
Yeah, I saw that, too. But I don't have the equipments for it, unfortunately
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though
I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.
Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4
Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel:

[Q] Defy not booting/blank screen

(Motorola defy MB525) Well, deciding to upgrade from quarx's android 4.2 to 4.4 I went and gave the whole flashing method a try again but I made a mistake on a couple areas and I was stuck in bootloader or the motorola logo appearing on and off over and over. That was because my battery was near death or pretty much dead, so I used the mcgyver method to flash it while it was being charged which 'worked'. It did the usual 'SW update in progress' and the sbf flashed, but after the phone just went to a blank screen (as if it were off) and no longer turns on or goes anywhere. Holding the power button and/or pressing the volume buttons does nothing. I cannot access bootloader or recovery or even get the phone to display. If I connect my defy to my computer, the white led charge light comes on briefly then goes away when the cable is fully connected. Thats the only thing that makes me think my phone isn't totally broke but, I cannot flash anything with RSD Lite again, it does not detect my phone as pressing the 'start' button does nothing.
I even went and bought one of the universal battle chargers thinking my battery just needed to be charged, but even after a full charge the phone has been no different. I'm at a loss, Is my cable the issue? Is my defy just busted? I really need some advice...
Anyone have any ideas? I uploaded a video to youtube showing the problem I have a bit better.
https://www.youtube.com/watch?v=Q25klbN9kWE
The same thing happens whether I have the battery inserted or no. Its very confusing.
Try to charge the battery with another defy or with an adapter, I think that has no charge
I already charged it with a universal charger (http://www.amazon.com/gp/product/B002XY5F6A/ref=oh_details_o00_s00_i00?ie=UTF8&psc=1) But was no different. Wouldn't this have worked? It gave me the green LED (full charge) after I left it connected for a while
If mcgyver cable is made properly, and you can't enter bl, you may have bricked your device
Sent from my MB526 using Tapatalk
thekguy said:
If mcgyver cable is made properly, and you can't enter bl, you may have bricked your device
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
I thought even if a defy is bricked you can at least get into bootloader. Can I unbrick it then?
You should be able to get into bl even then, but since you cannot, for some odd reason, there is no alternate method left
The brief white led glow seems to indicate a damaged bl, as when the internal eMMC is wiped completely
Sent from my MB526 using Tapatalk
Motorola defy is not booting
Hi can any one help me on this.
I rooted my defy and upgraded to jelly bean. It was working fine for a year and after that I found issue. So I tried to upgrade to kitkat cwm11, however it didnt work. So, did a factory reset and when i tried upgrading again, it threw an error saying, unable to mount sd card and unable to clear cache and data. After this I couldnt clear any settings or upgrade anything. Tried with different SD card and it didnt work as well. Finally, phone is not booting and when I tried to go to recovery option it doesnt work, even default motorola recovery doesnt work. My phone is not detecting in computer as well. Phone stays dead on moto logo. Please tell me how to upgrade the phone.
thekguy said:
You should be able to get into bl even then, but since you cannot, for some odd reason, there is no alternate method left
The brief white led glow seems to indicate a damaged bl, as when the internal eMMC is wiped completely
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
Alright, I guess my defy is toasted :/ Thank you for the information.
gokul_eee09 said:
Hi can any one help me on this.
I rooted my defy and upgraded to jelly bean. It was working fine for a year and after that I found issue. So I tried to upgrade to kitkat cwm11, however it didnt work. So, did a factory reset and when i tried upgrading again, it threw an error saying, unable to mount sd card and unable to clear cache and data. After this I couldnt clear any settings or upgrade anything. Tried with different SD card and it didnt work as well. Finally, phone is not booting and when I tried to go to recovery option it doesnt work, even default motorola recovery doesnt work. My phone is not detecting in computer as well. Phone stays dead on moto logo. Please tell me how to upgrade the phone.
Click to expand...
Click to collapse
Open a new thread
(Sorry double post) Wow, progress!!!
I tried the mcgyver method one last time and upon connecting the second usb cable I heard the windows chime that tells a new device has connected, but still nothing on screen. On a whim I launched RSD lite and tried flashing an SBF which did work! Halfway through the flashing process the screen came on giving me the 'SW Update in progress', though after the flash I'm back at bootloader, Did the flash work? I tried flashing another sbf but same deal, just back at bootloader. Is there a certain sbf I should use?? Please help if you can I'm getting there!
Dfp 231
Sent from my MB526 using Tapatalk

nexus player bricked

hi all,
i had the nexus player with me and installed cm12.1, everything was working fine, i had it at the hotel i was staying at. no issues whatsoever. but after i unplugged it and brought it back home, i plugged it back in and it just bootloops on the google logo. the bootloader is unlocked.
i tried pressing the reset button while powering it on, but no luck, the leds dont flash quickly to enter fastboot.
ive tried also keeping the reset button pressed again while powering it on, and eventually the led will blink slowly. i then let go, but then it just brings up the google logo again and will bootloop. tried plugging it into the pc while doing this as well, but adb doesnt detect it either.
pretty cant get into fastboot mode or even the recovery mode. any hints or tips i should try? i dont want it to be dead after just 4 months of usage.
Lol I did the exact same thing in pretty good at getting out of a brick but the nexus player is pretty low on my list its actually been like this for about two months now and I haven't touched it
While the LED is blinking slowly have you checked to see if the device is enumerating over USB at all. I believe slow flash indicates recovery mode. Do you ever see Andy with an exclamation mark?
Sent from my D6503 using Tapatalk
well I was able to get it back up and running by plugging it into my pc and messing with the drivers a little bit, then I used fastboot to flash the stock firmware again and now im putting a custom recovery back on it, all in all its pretty easy to fix so its definitely not dead for good. Sorry im not great with tutorials
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
kewvention said:
howd you end up recovering. i want to get it back up and running. perhaps i can try another pc.
when the led flashes slowly, i have the hdmi cable plugged in, but it just bootloops, never gets to to the android recovery mode. first time ive had a bricked android device.
Click to expand...
Click to collapse
Boot into the bootloader by unplugging the nexus player and then hold the button on the bottom and plug it in. Let the button go when you see the google logo. Then just use fastboot to flash the stock firmware.

Hard Brick Recovery - What are my options?

While returning my phone to stock for an RMA (bad microphone), I have encountered a hard brick.
I was using Wugfresh's tool to return stock. The device rebooted to recovery, and when the "flashstock.bat" file took over it hung on "waiting on device".
I left it sit overnight, but now I am left with a phone that just has a black screen, and a red blinking led.
Cannot boot to recover, or get anything to happen other than the blinking red led.
Do I have any options?
try plugging it into the wall to power up, maybe the battery died flat out... then try booting into recovery
second, learn to use fastboot... this is the no1 reason not to ever use these toolkits... not that you cant hardbrick using fastboot, but at least YOU are in control, and can get out of jams much easier.
good luck
yeah, do you have ADB setup? If not, now would be a good time look into it :cyclops:
You might have discharged the battery and need to wait for several hours until it´s charged again. I had something similar with my old Nexus 7 ( 2013 ) Never use any toolkits, learn to use ADB and FASTBOOT instead

Categories

Resources