Related
I have tried to flash my phone but have had no success due to the problems with Windows 7. While going through the flashing process, the battery died. Unlike the Samsung Captivate, the phone will not charge (not as a fact, only as I have noticed) unless it is "on". Therefore I am unable to continue the flashing process since I get the message: "Failed to boot 4
Starting RSD mode
Battery is too low to flash"
So my first question is: How do I charge the battery if I can't get the phone to boot?
My second question is: Can anybody help me unbrick the Atrix using Windows 7 IF I can get the battery charged?
Any help at all would be greatly appreciated. I would rather send a donation to an xda helper than have to pay Motorola to get this phone working again.
androidrookie said:
I have tried to flash my phone but have had no success due to the problems with Windows 7. While going through the flashing process, the battery died. Unlike the Samsung Captivate, the phone will not charge (not as a fact, only as I have noticed) unless it is "on". Therefore I am unable to continue the flashing process since I get the message: "Failed to boot 4
Starting RSD mode
Battery is too low to flash"
So my first question is: How do I charge the battery if I can't get the phone to boot?
My second question is: Can anybody help me unbrick the Atrix using Windows 7 IF I can get the battery charged?
Any help at all would be greatly appreciated. I would rather send a donation to an xda helper than have to pay Motorola to get this phone working again.
Click to expand...
Click to collapse
Is it an actual brick or soft brick? What is the win7 problem your referring to? Please explain and maybe I could help?
I think you may have to get a development USB cable that actually powers the unit while flashing, I may be wrong but you can make the cable. I stand to be corrected.
I don't get it could't they just pull the battery to stop the boot loop then plug it into a wall charger? shouldnt that charge it?!
androidrookie said:
I have tried to flash my phone but have had no success due to the problems with Windows 7. While going through the flashing process, the battery died. Unlike the Samsung Captivate, the phone will not charge (not as a fact, only as I have noticed) unless it is "on". Therefore I am unable to continue the flashing process since I get the message: "Failed to boot 4
Starting RSD mode
Battery is too low to flash"
So my first question is: How do I charge the battery if I can't get the phone to boot?
My second question is: Can anybody help me unbrick the Atrix using Windows 7 IF I can get the battery charged?
Any help at all would be greatly appreciated. I would rather send a donation to an xda helper than have to pay Motorola to get this phone working again.
Click to expand...
Click to collapse
Just plug the phone to the charger,that's how u charge a battery.Phone does not need to boot up in order to charge.
Sent from my MB860 using Tapatalk
Did this on my phone once, I just took my battery down to best buy and asked one of the guys to charge it in the demo unit. Went and got lunch and came back.
As stated the only way to charge it at this point is with a Dev cable
Sent from my MB860 using XDA App
If you connect directly the red wire of an usb cable where the battery connects to phone, phone will think is fully charged.off course the battery must be in its place correctly inserted.
Worked with milestone and atrix, did it myself
I exchanged batteries at the at&t store. I downloaded the latest version of rsd lite and this time it it ran through the flashing process and PASSED. However, when the Atrix tries to reboot, the same thing happens:
Failed to boot 4
starting RSD mode
If I am having successful flashing, what do I do now? PLEASE HELP!!
Thanks for your replies.
Your problems aren't with Windows 7.
Was your battery charged fully when you flashed?
What sbf are you trying to flash?
Your symptoms sound like those of a flash with the wrong sbf for your phone model.
Yea if you have a buddy or go to the store you could swap them batteries if they go for it.
CaelanT said:
Your problems aren't with Windows 7.
Was your battery charged fully when you flashed?
What sbf are you trying to flash?
Your symptoms sound like those of a flash with the wrong sbf for your phone model.
Click to expand...
Click to collapse
I flashed this sbf,
OLYFR_U4_1.2.6_SIGNED_OLPSATTSPE_P012_HWolympus_1g_1FF.sbf
and this one.
OLYFR_U4_1.8.3_SIGNED_OLPSATTSPE_P013_HWolympus_1g_Service1FF.sbf
Both had the same results, both flashed successfully, both stated that they passed the flashing process, and both times I still get the "failed to boot 4" error message.
4.1.26 should flash fine. The 4.1.83 you have there is a service sbf. Need to get 4.1.57 on there before flashing that. When you are able to I would flash the 4.1.57 sbf, then OTA to 4.1.83. No need to do 4.1.26.
Beamed in from WinBorg 4G via XDA Premium app
Just flash the 1.5.7 sbf and bring the phone to att for warranty.
CaelanT said:
4.1.26 should flash fine. The 4.1.83 you have there is a service sbf. Need to get 4.1.57 on there before flashing that. When you are able to I would flash the 4.1.57 sbf, then OTA to 4.1.83. No need to do 4.1.26.
Beamed in from WinBorg 4G via XDA Premium app
Click to expand...
Click to collapse
I've flashed from 1.26 to 1.83 with no issues several times with the service SBF. The "service" part just means it's not wiping /data.
The 1.26 SBF is a good starting point. The error you're getting is because the signature check is failing on the device. Where did you get the phone from?
I bought the phone from the at&t store. The problem started when my son pulled the usb cable from the computer while it was in the flashing process! (a serious no no). The good news is that I called Motorola about the issue and explained that the phone is rooted. I told them that I read in numerous forums (including Motorola's forums) that rooted phones would not be covered by the warranty. He put me on hold and checked with his supervisor then told me that they would not charge me for the repair! (thank GOD!) So my Atrix is on its way back to Motorola as I type.
Thanks to everyone who tried to help, these forums are great!
Also, I think Caelan T is right, the problem is not with Windows 7. A lot of people complained about the "grayed out" start button. None of this was a problem with the latest version of the RSDlite program from Motorola. It loaded the sbf file from the directory just fine. I did not need to change the file name, move it to the C: drive, or use the drag and drop method to make it start. So anyone with the grayed out start button problem, you need to search for the latest version. The "check for update" did not detect the newest version for me, I had to search elsewhere.
Ririal said:
I've flashed from 1.26 to 1.83 with no issues several times with the service SBF. The "service" part just means it's not wiping /data.
The 1.26 SBF is a good starting point. The error you're getting is because the signature check is failing on the device. Where did you get the phone from?
Click to expand...
Click to collapse
When I get the phone back, I figured I would have the latest version without root. Won't I need to flash 1.26 to start the Gladroot process all over again?
JayRolla said:
I think you may have to get a development USB cable that actually powers the unit while flashing, I may be wrong but you can make the cable. I stand to be corrected.
Click to expand...
Click to collapse
Where can I pick up a developer cable?
I Googled it but nothing in particular came up...
Same problem here.
If i left the atrix plugged to the charger wont charge the battery?
Thanks
the cable that comes with the atrix supplies power as it is used to charge the phone. i just soft bricked my phone and it eventually gave me the low battery message can't flash i began to panic and jumped on xda to look for help and i read that it doesn't charge while it is in this state, i pulled out the battery to turn it off since the computer was keeping it on. then put the battery back in i and plugged it in to the computer and it started to charge but didn't turn on its acting like its charging the green light is on but the phone isn't turning on I'm guessing its because i am running vmware and i set it to ask what os to use when i plug it in i didn't pick an option just left the window open and it looks like its charging... I'm praying that it really is charging ill keep you guys posted it if works
Qster626 said:
the cable that comes with the atrix supplies power as it is used to charge the phone. i just soft bricked my phone and it eventually gave me the low battery message can't flash i began to panic and jumped on xda to look for help and i read that it doesn't charge while it is in this state, i pulled out the battery to turn it off since the computer was keeping it on. then put the battery back in i and plugged it in to the computer and it started to charge but didn't turn on its acting like its charging the green light is on but the phone isn't turning on I'm guessing its because i am running vmware and i set it to ask what os to use when i plug it in i didn't pick an option just left the window open and it looks like its charging... I'm praying that it really is charging ill keep you guys posted it if works
Click to expand...
Click to collapse
Google how to charge any phone with no charger. You will have to take apart a spare usb cable but it works.
Sent from my MB860 using xda premium
Ok so I have a rooted droid x2 with bloatware frozen, well my battery puked, went to Verizon and got a new one, but I made the mistake of letting one of the guys put it in well he decided to do a factory reset and it is now stuck at the setup screen and its blank. What do I do? It got reset with bloatware froze and rooted. Any help would be great cause even after I let loose on them and had to be escorted out by security officers my phone will not be replaced.
And I know I am an idiot for letting him touch it!
Rule 0: Don't do anything requiring security to escort you out.
Rule 1: Don't let people touch your phone.
Have you tried using the SBF to flash it back to factory state? For me, that'd be step one.
Actually, step one would be pulling the battery, but I'm assuming you've tried that.
Yes tried both, and unfortunately didn't work.
Is there anyway to apply through sd card? Or an easy rsd way?
The SBF isn't an update.zip file, so no SDCard method.
nene95 said:
Is there anyway to apply through sd card? Or an easy rsd way?
Click to expand...
Click to collapse
Have you tried going into recovery and wiping your data and cache? This would of course be a factory reset.
Sent from my Droid X² using XDA App
Yes it still went back to blank setup screen, would the frozen bloatware cause this?
I'm not sure. Have you tried posting this problem over at the Droid X Forum?
Sent from my Droid X² using XDA App
If you aren't sure if you flashed it correctly with RSD, try following this post.
When you say the startup screen is blank, what is it doing? Like, if you were describing it, you hold the button to power it on, then...?
It powers up goes through the droid eye, then gets to the blue screen where your supposed to call to activate your phone but the top part is normal and the lower part is dark blue.
Does it respond when you touch it, or is the screen frozen? Is the entire screen fine when the droid eye is on it, or is the lower part messed up then as well?
My thoughts on the subject are this; A) You froze something that's needed to go through start-up, or B) The phone got physically damaged somehow. If the screen is responsive while the bottom part is messed up, I'd lean more towards something physically went bad.
Assuming you still have service with Verizon, have you thought of taking it to a different store? Or even sending it in for repair?
Sounds like something else went wrong, as far as I know any frozen apps simply get defrosted with a factory reset.
If it is a software problem then a successful sbf will clear it up. If you are getting a PASS after sbf and it's still not working then your battery "puking" was just a symptom of a larger hardware problem.
Sent from my DROID X2
I can use the pull down notifications so its not froze up.
Sent from my DROID X2 using XDA Premium App
Sounds like a bad screen.
Sent from my DROID X2 using XDA App
Hi.
I was flashing my phone back to stock gingerbread and after doing some verification and stuff my phone just went crazy.
The touchscreen clicks on everything by itself, sometimes it's so hard to unlock the pattern.
The screen is clean, nothing on it, nothing went inside the phone.
flashing back to any other ROMs wont work so im assuming that it's the hardware problem.
I was going to go to the verizon retail center and ask for the exchange but I already made an exchange from tbolt to x2, and now I'm wondering if I can get my phone exchanged for the malfunctioning.
Or any way that I can get this thing back to normal.
Thank you.
I'm sure that as long as you can reproduce the issue they won't have a problem replacing it with another X2. Just make sure you SBF before you make the exchange.
Well that's the thing.
It wont show up on rsd lite 5.3.1 with PC mode and USB debugging on.
------------------------------------------------------------------------------------
i factory reseted by using the recovery mode. This is really annoying and driving me nuts.
As long as it's on stock firmware and SU isn't there or anything that requires root you should be okay.
Alright. Thanks for the comment!
stevebizkit said:
Well that's the thing.
It wont show up on rsd lite 5.3.1 with PC mode and USB debugging on.
------------------------------------------------------------------------------------
i factory reseted by using the recovery mode. This is really annoying and driving me nuts.
Click to expand...
Click to collapse
if youre trying to sbf you have to put it on rsd mode...power off the phone hold power and volume up till it flashes and it should say ready for rsd protocol or whatever, from there plug it in to the computer and it should recognize it.
Mine was doing the same thing,only it was a random ocurrence throughout the day for like two weeks and it only happened in the middle left of the screen,flashed back to stock still happened then it just stopped doing it,weird
Sent from my DROID X2 using XDA App
mine does this on the atrix rom but once I sbf back to GB it works fine.
Had this happen to me one time. I accidentally flash back a nandroid of a froyo backup. I was running P3's Pre-GB at the time, phone went crazy. SBF fixed everything, I was S***ing bricks when it happened though... lol
It also happened to me too. Bit it went away after I started to mess with flashing stuff to the phone like themes. It sucked, I thought I messed something up bad haha.
Sent from my DROID X2 using XDA App
Mr_GreenJeans said:
Had this happen to me one time. I accidentally flash back a nandroid of a froyo backup. I was running P3's Pre-GB at the time, phone went crazy. SBF fixed everything, I was S***ing bricks when it happened though... lol
Click to expand...
Click to collapse
BEST description for what was happening lol. Bricks are hard coming out lol
btw..
any new news on ya nandroid problem greenjeans? I mean MR greenjeans ..r u from the same area as me? Near claymont boothwyn Philadelphia etc....sorry for off subject...looking for the small world lol
I have had this happen several times when flashing. Just SBF back, wipe all data and cache and start over. It will go away! It seems it happened more when I took short cuts or flat out forgot a step, but it always went away after a clean instal. Hope that helps...
same here.... i do the sbf and a wipe (3X) and it always comes back for me
Sounds like you need an exorcism!
My wife's DInc had was also possessed. With her's it was a faulty digitizer and is a problem with many DInc.
More directly related, my DX2 does this about every day at some point. I'm running Eclipse v.6 FWIW. It seems to be a software problem as I can just turn off the screen and it goes away.
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
It works fine after SBFing to stock GB.
lol i thought i f***ed up something bad haha
I might just keep using this GB until the eclipse .6 gets fixed up or something
Well I'm currently on .7 rc1 eclipse and its the best rom I've tried yet... And I've tried a lot lol
Sent from my DROID X2 using xda premium
DAG425 said:
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
Click to expand...
Click to collapse
mine was still acting weird after restoring with the backup i made with stock froyo.
It's fine after deleting all the data/cache in the device and flashing stock GB.
you should just give it a try. This problem just seems so random
DAG425 said:
This happens to me on my DX2 with some ROMs but only when the phone is plugged in to the charger or the USB cable... Unplug it and it goes away... Really random... I have thought about taking it in but cant remember if it does it on stock unrooted or not... Might give it a try this weekend and if it does I may just get it replaced.....
Click to expand...
Click to collapse
I have heard that if the wrong voltage is coming through the charger it can make it go nuts like that which can be pretty bad for ur phone.
Are u using the stock x2 charger or a replacement of some kind?
Mine says output 5.1Volts (850mA)
ashclepdia said:
I have heard that if the wrong voltage is coming through the charger it can make it go nuts like that which can be pretty bad for ur phone.
Are u using the stock x2 charger or a replacement of some kind?
Mine says output 5.1Volts (850mA)
Click to expand...
Click to collapse
Im using the rocketfish wall charger for the DroidX so I would assume it should be fine... But the voltage is interesting because it happens when the phone is plugged into my pc or my lappy also..... and that is using the stock USB cable... If it were more frequent and on all ROMs including stock I would have had it replaced already... I'll check the voltage on that rocketfish wall charger with the stock moto one and see when I get off work later....
So I went to bed last night after putting my phone on the charger. Woke up this morning and my phone was off with a white notification light, I tried to turn it on and nothing happened, I've tried different outlets, different cables, I've tried USB charging and using a car charger, each time it shows a white notification light and nothing else. No matter what I do the phone won't turn on. A hard reset did nothing. can someone please help? the phone is a gsm RAZR running 2.3.5. It's rooted but no other mods..
Sent from my A500 using xda premium
Just look @ here, seems you have to flash a new stock rom:
http://forum.xda-developers.com/showthread.php?p=23453478
Sliced by my Razr on Tapatalk
Edit : nevermind. I didn't read your entire post.
Sent from my DROID RAZR using XDA
zeidof said:
Just look @ here, seems you have to flash a new stock rom:
http://forum.xda-developers.com/showthread.php?p=23453478
Sliced by my Razr on Tapatalk
Click to expand...
Click to collapse
the problem with doing this is i cant get the phone into fastboot. The phone will literally do NOTHING except for the white light that comes on when i plug it in. RSD will not recognize that my phone is plugged in.
Any other suggestions? someone please help
Did you mean that the screen display nothing and the led light the color white? That always means that the screen is broken or something control the display was broken, try to contact the one who sell it to you.
If it was the screen wouldn't I still be able to force it into Fastboot using RAZR utility? Me and the seller have been in constant contact. He's been great!! I'll be sending the phone to Motorola tmw I guess. I hope that I don't have any problems with moto. I'm praying they fix it!!
Sent from my A500 using xda premium
I know , sorry I cant be of more help. I had something similar happen the other day while flashing a new Rom. Took me forever to get Rsd to recognize my phone. I eventually got back up. Some days suck lol. Just when you think you know what you are doing.
blueis300 said:
I know , sorry I cant be of more help. I had something similar happen the other day while flashing a new Rom. Took me forever to get Rsd to recognize my phone. I eventually got back up. Some days suck lol. Just when you think you know what you are doing.
Click to expand...
Click to collapse
If I was flashing a ROM I would be much happier because atleast I would have a clue about what happened. I was sleeping and the phone was on the wall charger. I've got the phone all packaged up for shipment to Motorola tmw. I really hope they fix it.
Not trying to start a war but that's what I loved about apple, as long as it was within 1 year of purchase, you could go to apple and get it fixed/replaced. Even if you bought it off someone else and not apple or a carrier. I didn't have any luck with HTC and my desire z.. Hopefully moto is more like Apple in the warranty dept. lol
Sent from my A500 using xda premium
Just thinking a tad (sad I know). I think what I did and dont know if it had any effect was uninstalled rsd,drivers etc.. I re installed and Rsd recognized. Think it was my usb drivers that got screwed somehow. I even went as far as too go into control panel of my computer which is win 7 and delete usb drivers and reinstall. Needless to say I went through alot and tried alot but got back up.
Hello,
I recently bought a droid x2 to use on straight talk. The stock system was fairly laggy so I rooted it and installed eclipse 2.3. That was better but still unacceptably laggy. From there I thought I would give cm10 a shot. Based on what I read I figured it would be faster. I sbf'd my 2.3.5 x2 to 2.3.4. Rooted it and installed cm10. No problems. CM10 is actually the best I have tried thus far, however I could not get certain apps to run (I know this is known with cm10) and the alternatives to the app I want do not run either. So I thought I would give cm7 a shot. I started rsd lite picked the correct sbf, turned off my phone; held the power button while holding up to get into rsd mode on the phone. Then connected it to the computer. RSD saw it and I pressed start. The program went through the first phase fine; rebooted then only made it to 30% of the second phase and failed. I've tried rebooting computer, taking the battery out and letting it sit and now I fear the phone is bricked. Also I cannot seem to get it to charge; now when the phone boots up it says boot up failed (or something like that) then underneath that text will say rsd mode then underneath that it says not enough power to flash. Besides getting an external charger, is there a way around this?
Any help would be much appreciated.
Thank you
Phone will not charge without firmware, need a charged battery or fastboot cable
Links in my list under low battery options
sd_shadow's (themib) [Collection] of Links for Droid X2
Sent from my DROIDX using Tapatalk
sd_shadow said:
Phone will not charge without firmware, need a charged battery or fastboot cable
Links in my list under low battery options
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Thank you for the fast response man. I just ordered a cable off ebay. You wouldn't happen to have an idea as to what (if anything) I did wrong? I sbf'd the device twice now with no issues and then this happened.
Thank you again for the fast response..
endlessnameless2013 said:
Thank you for the fast response man. I just ordered a cable off ebay. You wouldn't happen to have an idea as to what (if anything) I did wrong? I sbf'd the device twice now with no issues and then this happened.
Thank you again for the fast response..
Click to expand...
Click to collapse
bad usb cable, drivers issue, bad usb port (PC or DX2), bad sbf download, battery was too low but didn't get the warning right away, battery is old and not reliable...
verify md5 checksum for sbf https://sites.google.com/site/sdshadowscollection/home/hash-checksums
verify drivers
use rear usb ports on desktop pc, often front usb ports are not good for flashing
try a different usb cable
fully charge battery before flashing, if battery is more than 2 years old, it should be replaced
use a different RSD Lite version
use DX2 ezSBF it runs from a bootable cd/usb drive using a linux version called Slitaz (so no driver issues)
edit:
Flashing Stock 2.3.5 Firmware with moto-fastboot.exe
Hey Thanks again. I know you probably get tired of answering questions like mine, but your knowledge is greatly appreciated.