This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App
Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.
what rom was the phone running when you had the original issue?
Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.
I have the same Problem with my Defy+ what can i do?
I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.
Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!
Related
Managed to get my Droid 2 to a point where it will not go beyond the M screen on boot. I've tried pulling the battery over and over again and cannot get to the Clockwork bootstrap. I've also tried plugging it in and pulling the battery many, many times.
So I figure the next best step is to .sbf this mofo.
I've downloaded & installed rdslite, the USB drivers. Also have the Droid 2 .sbf files. Droid.Co_Downloader.exe pulled down RSD Lite v4.8 though rather than 4.7. And the link to 4.7 is now showing as invalid. Will 4.8 work for what I'm trying to do?
Also, when I plug in my phone RSD Lite never shows anything in the devices table. What are the steps to get my phone to show up? Plug in phone, power on, turn on RDS Lite? The tutorial seemed to be aimed at people who still have working phones in that it has you adjusting setting on the phone i.e. enable debug mode.
Sidenote, I know debug mode is disabled on my phone. Does that mean RSD Lite isn't going to work?
Help!
I think if you pull and replace the battery at the M it should reboot into recovery, and if it won't do that you can always try sliding out the keyboard and booting the phone while holding the X key to see if it will dump you into the stock recovery
Ok, some more reading uncovered hitting the physical keyboard's Up arrow and powering on will take the phone to the Bootloader and once in the bootloader my pc recognized it.
And then RSD Lite showed my device in the table but it didn't show up as the A955 it was Model "S Flash OMAP3630 MI".
Currently flashing DROID2_X6_2.2.20 .sbf, hopefully that pans out.
Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.
Ok, disaster averted.
Looks like rebooting into the bootloader was the secret. Hope that is helpful to someone else who's bricked their phone.
BTW, used RSD Lite version 4.8 and that worked with my Droid 2.
aplus01 said:
Thanks, I tried the battery pull thing A LOT of times. Never went into bootstrap. Not sure what's going on there.
I tried the stock recovery but got the Android-exclaimation mark icon which I presume means the stock recovery was F-ed up.
Really hope this sbf recovery works.
Click to expand...
Click to collapse
Glad you got it working! For future reference if you want the stock recovery, after you hold x and get to the exlamation point, press the search key on the keyboard. (The little magnifying glass) and it should take right Into it.
Sent from my DROID2 using XDA App
Me too!
Search key? Good to know. Man, that could have saved me quite a bit of time I think.
So now that I've restored everyting I'm going to risk it all and install the fission rom again.
It's less intimidating now that I know how to sbf restore. Hopefully I won't need to this go round.
Just follow the instructions as they are laid out and you shouldn't run into much trouble. Also, be sure to let the device sit for a bit after you reboot from clockwork, as it could take a good 15 minutes before it fully boots up the first time, and interrupting that could put you back at square one
Could you add [SOLVED] to your thread title please. Thanks
I installed Gingerbread that was recently released by team black hat, it was working perfectly for a few days, then all of a sudden.....im stuck at M logo. So i followed P3Droid's instructions , down loaded all the necessary files and tried to flash the 2.3.20 sbf file and nothing happens. When i connect my phone to RSD Lite (tried 4.7, 4.9) it does not recognize my phone, it says my phone model is sflash, not droid 2 or a955. I went ahead and tried to flash but when it hits 100% it says please manually power up phone and i do....still stuck at M logo. Im ****ed, my phone is a brick, this suck! Everyone elses phone I root works perfect, except mine.....please help me if u can!!
make sure you have the correct moto drivers on your computer and make sure they are for the correct bit of your OS also. whenever i sbf the phone reboots itself.
I got all the updated files...i found it weird that my phone dosnt power up on its own. In rsd lite does it show ur phone model or show it as sflash? Mine shows as sflash, thats what i think the prob is.
evilteam00 said:
I got all the updated files...i found it weird that my phone dosnt power up on its own. In rsd lite does it show ur phone model or show it as sflash? Mine shows as sflash, thats what i think the prob is.
Click to expand...
Click to collapse
Mine shows up as sflash, but the SBF has always worked correctly, even when flashing back from 2.3
Have you ever SBF'd before, and if so, has it worked?
Also, have to tried getting into the stock recovery? Try to, and wipe data and cache and see if that helps any.
Also, you may try uninstalling the moto drivers, rsd, redownload and reinstall them, and also try redownloading the SBF file.
orkillakilla said:
Mine shows up as sflash, but the SBF has always worked correctly, even when flashing back from 2.3
Have you ever SBF'd before, and if so, has it worked?
Also, have to tried getting into the stock recovery? Try to, and wipe data and cache and see if that helps any.
Also, you may try uninstalling the moto drivers, rsd, redownload and reinstall them, and also try redownloading the SBF file.
Click to expand...
Click to collapse
Ive flashed SBF'd SPrecovery a long time ago with my droid 1, it worked fine. Tried uninstalling the drivers sbf file and rsd, then reinsalled them. When I hold X and power my phone just stays stuck on the M logo. Im not sure what im dokng wrong...i followed the steps from here...http://forum.xda-developers.com/showthread.php?t=770224
What sbf are you using? I use the full system sbf from here:
h t t p://www.mydroidworld.com/forums/droid-2-discussion/5323-tbh-mydroidworld-present-droid-2-2-3-20-triple-threat.html
Try that if you aren't using that one.
Also, what bootloader version do you have? Mine is 2.37
Sent from my Liberated DROID 2
This happened to me, and I almost **** a brick. You need to hold down the power, and X buttons simultaneously, until the exclimation point in the triangle comes up. Then hit the Search button on the keyboard, which is directly below the X. If it's not working flash And again, and make sure you have the correect drivers from Motorola on your PC.
Sent from my LiberatedDROID2 using Tapatalk
AKSurprise said:
This happened to me, and I almost **** a brick. You need to hold down the power, and X buttons simultaneously, until the exclimation point in the triangle comes up. Then hit the Search button on the keyboard, which is directly below the X. If it's not working flash And again, and make sure you have the correect drivers from Motorola on your PC.
Sent from my LiberatedDROID2 using Tapatalk
Click to expand...
Click to collapse
He already said that he cannot get into stock recovery.
Besides, GB stock recovery is different from froyo. Instead of hitting the search button, you have to hit vol up and vol down at the same time. Then use the volume keys to go up and down, and the power button to select.
I think i may need a working droid 2 to make sure the drivers all installed correctly.....a guy was helping me out and he thinks thats the prob. I had 2.37 bootloader and the full system sbf file, that didnt work so I went to bootloader 2.35 with full sbf, and still stuck at M logo. I hope its the drivers cuz before my phone bricked i diddnt have the latest drivers...Gotta wait a few hours till i get another droid 2 to see if that was the prob. Thanks for the suggestions.
good night friends!
I'm here asking for this help not for lack of looking for the solution, sorry my bad english, I'm from Brazil and I
defy caught in a bootloader, I tried almost everything I found here in the forum, but most of the problems is
reset solved by making the recovery, but in my defy the recovery does not open, the flash works only power + vol up, already
I spent several roms to no avail, could someone help me run my recovery? grateful heart
list of roms flashead
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FFJORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbfz
JORLA_U3_3.4.2_107-7_R02_SIGNED_USAJORDMR1B15CLABRLA019.0R_JORLAFROCLABRLA_P009_A008_M002_HWp3_Service1FF.sbf
JRDNEM_U3_2.34.1_DEBLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA02B.0R_USAJORDANRTCEE_P029_A019_HWp3_Service1FF.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA035.0R_USAJORDANRTHKTW_P021_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_3.4.2_164-003_VFBLUR_SIGN_SIGNED_USAJRDNEMARAB1B8VFFR03A.0R_PDS03C_USAJRDNFRYOVFFR_P028_A014_M004_HWp3_Service1FF.sbf
Motorola_Defy_Nu___Android_2.2_FroYo
shadow_defy_2.3.3_85_Orange
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
mmec2 said:
If you turn it on while holding "dolume down" do you get the android+! screen? Some go into recovery if you touch the bottom right corner of the screen, but on some you have to hold volume up + down together. I had this problem today!
If you actually can't get to the screen with the android+! then I don't know what else you could do :-(
Click to expand...
Click to collapse
I really can not, no way to go to the screen with the robot android! he goes right on the logo motorola M!
can it be hardware problem?
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
farsight73 said:
1) Did you use the correct flasher? rsd4.9 with motorola driver installed properly.
2) If (1) not working, you could use motorola own service update from their site.
Click to expand...
Click to collapse
I'm using motorola rsd 4.9 with updated drivers, what happens is install the rom normal after reboot gets stuck in the Motorola M logo, the software update site does not recognize my phone, do all these roms that I would be no my phone?
im tried this roms now
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANRTFR_P043_A010_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_117-002_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB035.0R_USAJRDNFRYORTGB_P003_A002_HWp3_Service1FF
JRDNEM_U3_2.21.0_SIGNED_UCAJRDNEMARAB1B80AA028.0R_USAJORDANRTGB_P026_A007_HWp3_Service1FF
3.4.3_11-Stock.UKTmobile_BLUR
but no results!
don't worry about it, dude.
maybe you can try the way followed:
1.power off your defy;
2.remove the battery from the phone;
3.plug the usb cable into the phone without battery;
4.open RSD and chose one of the roms your listed, but 3.4.2-177-005 NORDIC prefered,
5.take the battery into your phone, now your can see the "connected" on RSD;
6.click the "start" button to flash;
7.wait the phone reboot completely, usually it'll reboot.
if not reboot, remove and on your battery, power on your phone, then press the "volume - and power" botton together, you can enter the robot screen, press volume up and down botton together, usually you can enter the recovery, then chose wipe 3 and 4, totally you can save your defy~~
Be sure to have enough battery while flashing..
Get the phone into bootloader (hold volume down when switch on) and flash an SBF like one from the list you've attached using RSD lite. Surely you have used RSD Lite before?
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
jdearauj said:
It seems you have the same issue I have on my Defy as per this thread: http://forum.xda-developers.com/showthread.php?t=1095444
I’m also unable to get into recovery or get to the Android Robot screen using “Power + Volume Down”. Hopefully we will be able to figure it out and get this issue fixed.
Click to expand...
Click to collapse
This same friend, I have the same problem, is this a hardware problem? I move the roms but not normal
Vol I login recovery - + Power key
http://forum.xda-developers.com/showthread.php?t=966537
Try flashing nordic, if fails arabic, if fails, 2.3.3, if fails probably corrupt nand broken hardware.
Before and after every flash always try to access recovery (volume down) and WIPE. reboot and wait crossing fingers, if it fails to boot flash next sbf, try to go recovery + wipe; reboot, cross more fingers; if fails to boot try next sbf and repeat.
The reason for this is that you can flash a lower version but it wont boot, so you have to flash a higher and higher version until you get one that works.
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
zyxwvut said:
I tried to help someone with this problem before to no avail!
Everyone who is saying just wipe in recovery, or just flash with RSD blah blah blah, need to understand that he CAN NOT access recovery and HE HAS flashed multiple roms using RSD 4.9, read the OP. Im convinced this is physical hardware failure or similar. We all know the drill to recover our precious defy's in the event of semi-brick ie: bootloop or corrupt code. However this is more than a semi-brick. We are talking about successful flashing and still no access to recovery and infinite M logo!
I walked more than one person with this problem through every known procedure to bring these phones back. Even using sbf_flash for linux doesn't work as this is the only way I flash anymore I don't bother with RSD anymore. The thing is it DOES FLASH SUCCESSFULLY just no recovery or boot!
Click to expand...
Click to collapse
OMG Exactly!!!! i have same problem and nobody seems to be able to tell me what to do, they keep saying same thing about trying various SBF's and Vol down + power method. No matter what SBF file I successfully flash with, i cannot get into boot recovery mode.
I have heard before from desperate users that they were able to revive their phone by flashing a full 2.3.4 sbf. This however comes with downsides of not being able to downgrade to froyo by flashing ANY froyo sbf's. There is a way to downgrade back to froyo but its a dirty method. Even after downgrade you can't just flash a sbf, you will always need to restore nandroid and flash fixed sbf
Hello. Well to start off I had recently rooted my Droid2 which was running the OTA GB. So I started looking for roms like I use to with froyo and the leaked GB. Was looking for something to change the battery life frame poor to great. Anyway I came upon Cyanogenmod's Rom for Droid 2 For the ota gb. I made a nandroid back up, downloaded it and was ready to flash. Seconds away in boot recovery and while i was looking for the file before I think I hit "apply update" instead of "search for zip file on scdard(or what ever sentence it says) and i got it but it started loading an update. I was like wtf kinda freaked out and I did a battery pull . Now my phone stays at the M boot logo and i have no way to go back. I heard the SBF for GB ota isnt her yet . if anyone can help I would be grateful. Plz Help
Things I've tried/
1.Battery Pull.
2.Hold power button + hold X(doesnt work like froyo Poo)
3.Tried going back with rsdlite 5.3.1 with moto drivers(it won't show my device ;'( )
4.Left this message on xdadev / please help
SOLVEd
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
T3viin said:
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
Click to expand...
Click to collapse
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Charge your battery in another phone like yours. Borrow someones spare battery. Take battery to verizon store and see if they can charge it somehow. There is a thread on here somewhere on how to do a hack job on your cable and hook the wires directly to your battery and charge it independent of the phone. I can't post a link so I hope you can find it by searching.
Sent from my DROID2 using XDA App
dmeadows013 said:
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Click to expand...
Click to collapse
I've had this problem 4 times in the last week. I used a terminal based OS to SBF using ADB.
And in the same step I re rooted my phone. Whole thing takes about 15-20 minutes.
The steps are on the CMWiki.
I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse