Related
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
AMcKeeCT said:
Hello Everyone,
First off, I will apologize for posting this in either the wrong section, doubling up, or both. If I did, feel free to post a RIGHT HERE n00b message.
Anyways, there will be a long and short version.
--------------------------
THE LONG VERSION:
--------------------------
Recently, I tried to .SBF back to Froyo. I really wanted to root it to get rooted gingerbread, but I'm going to probs tell verizon that I didn't like the UI of 2.3
I used RSD lite, current version, and flashed the stock image SBF for Froyo.
However, it failed. I tried to boot it up, and it goes straight to Bootloader.
I can't boot into anything else (including recovery).
On the top of my screen it says Err: A5,70,39,00,27
Full output as follows:
Bootloader
30.04
Err:a5,70,39,00,27
[Empty Lines]
Battery OK
OK to program
Transfer mode
USB
I was reading up on articles about this, and I found pretty much nothing, except for someone who said their phone was bricked past the point of SBF fixing.
--------------------------
THE SHORT VERSION:
--------------------------
Tried to flash SBF of Froyo (stock) from Gingerbread OTA
Got output Err: A5,70,39,00,27 using the latest version of RSD Lite and bootloader 30.04
Can't load into any other form
Totally screwed.
--------------------------
THE QUESTION:
--------------------------
What do I do?
Have I voided my warranty (never rooted before, no physical damage)?
Am I ok for a return, and if not, can they tell I have been SBF-ing, or is it possible for this to occur doing something else that doesn't void the warranty?
Is this fixable?
What do the codes mean?
Am I just a complete moron?
Click to expand...
Click to collapse
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
bigshotrob22 said:
I would flash the "full" SBF and when that one fails flash the "SYSTEM" only Sbf. I have done this many times before so hopefully it works for you.
Click to expand...
Click to collapse
+1
I thought I bricked my first phone when i constantly bootlooped until I tried this combo.
From what I understand your recovery is messed up. So then loading the full sbf loads that, but fails to load the system. in which case your sbf the system only sbf and then reboot and you should be able to boot.
I have done this a few times as well. You may have to flash the full sbf a few times for it to take, but it will work
Sent from my DROIDX CM7 nightly using XDA Premium App
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
That is my vote. Worked like a charm for me and my bro. His X was very skrewed...
As the title asks...
Has anyone been able to SBF back to 2.2.2 Froyo from the OTA update? If so, please advise all details. Thanks.
Much of the software conveniences I use, are better working in 2.2.2 especially screen lockers, unlockers, blockers, and Wireless Tethering.
W/ 2.3.5, I change the hotspot info to that of Wireless-Tether's and use it, but that's annoying...
Feels like two different setups.
i tried once... didn't go so well, ended with warranty replacement.
downloaded sbf that indicated it was for cell south(cspire) from here. everything appeared to go just fine. until the phone rebooted. gave me a message that said something like MEM_BLANK or something similar. i will admit that i am not very proficient with motorola's yet, and may have done something wrong, but i followed the steps that i found posted here on xda. if you find any more information i would love to hear it.
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Rocheforte said:
I had the same issue come up with no success as well. This happened when I tried flashing Liberty3 after doing full wipes and installing the Droid 2 bootstrapper. After the flash, I kept getting stuck on the bootloader with some error codes. At that point, I tried flashing the sbf using rsd lite and sbf_flash on ubuntu, but those ended up giving me more error codes with the MEM_BLANK and SERVICE REQ'D outputs. Meh, guess I'll just have to stick with stock rooted.
Click to expand...
Click to collapse
exactly. i came to the same conclusion. makes me wonder why the motorola roms aren't more like the htc roms where they are not carrier specific.
edit: did you manage to get past the MEM_BLANK and SERVICE REQ'D errors on your own? and if so, how?
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Rocheforte said:
No success, anytime I tried to sbf it would output a slightly different error with MEM_BLANK and Service Req'd. I eventually just replaced it, but now I'm likely going to return this one because it won't update to 2.3 and wifi doesn't work.
Click to expand...
Click to collapse
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
ngholson said:
did u install the bootstrapper? it changes the logwrapper file, however changing it back and removing the bootstrapper all together still yeilds the same problem. update fails after about 1 minute.
here is a strange morsel of info, when i was trying. (before warranty replc) even tho the update would fail, it did change the system info on the phone, it would indicate that .602 was installed on the phone even tho it had failed.
Click to expand...
Click to collapse
Yeah, I had used the Droid 2 bootstrapper at that point. Has anyone tried using the Verizon Droid X sbf's since apparently they are supposed to be very similar to the Milestone X's?
Sent from my Milestone X using xda premium
Night before last my Droid X was upgraded via OTA from Froyo 2.2.1 to Gingerbread 2.3.4 , at which I lost my Root. So I started searching YouTube for videos on taking my phone back to Froyo. And I found just what I was looking for. Return your Droid back to Froyo. So I followed the instructions to the letter, I downloaded - RDS Lite 4.9 - Motorola Helper_2.1.40_5.5.0 - VRZ_M810_2.3.34_IFF_01 . According to RSD Lite the flash was successful. Droid X reboots, and this is what I was left with.
Bootloader
30.04
Err:A5,70,70,00,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program'Transfer Mode:
USB
I have tried SBFing twice and RSD Lite sees the phone, goes thru the flash, reboots the phone but I get the same responce on the phone as stated above. Although in my computer, the Droid is not detected.
In your opinions, have I done an unrecoverable bricking to my Droid?
Go ahead, I can take it.
TIA
I used 4.5.621 SBF file, and was able to bring my phone back to the way it was before I got in a bind (Droid X SBF Files - Motorola SBF Files). It is alive with all of my Apps, so I'm not sure just what happened to it. But to whoever is responsible for the web site, I think P3 Thanks
Great job on getting back to .621.
Unfortunately, being on .621 makes it impossible to flash back to Froyo.
However, you can root and install custom roms.
Sent from my DROIDX using Tapatalk 2
yeah I know, but at this point I'm just happy to have my phone back in good working order. I had just bricked my Droid X2 @ 2 weeks ago, so now I don't have to face my wife with another $200.00 paper weight.
I have the same issue. Someone pointed me to this forum so I'll just include my text.
So I just got my first droid yesterday, it's a droidx from motorola. I initially factory reset it and cache cleared and it was working like a charm. Anyways, today I got the idea after reading over cyanogenmod following these instructions. Since I didn't have much on it I didn't backup. I remember vaguely updating the system previous to this, I think I was at 2.34. Anyways, I get done with flashing it- as far as I know it was successful- rdslite said it was complete. I try to do another factory reset, can't get into it. Just the bootloader comes up saying : Bootloader30.04 Err:A5,70,70,00,1F and a few things about to plug usb in and that it needs service...
I see something on cyanogen's page that I overlooked before:
WARNING: The 2.3.4 OTA release, the bootloader was patched to version 30.04. If an attempt is made to downgrade to an earlier version through the SBF method below, the bootloader will throw an error and the phone will not boot.
FLICK.
I tried the 1kds cd and it says it installed properly, I turn it on only to see same bootloader issue. I tried another rom and same thing. The last one I used was apparantly a 2.34 one and now my phone says code corrupt on the bootloader screen.
I need to find a way to charge the battery. I feel bad because it was a present to me from my girlfriends sister, and I don't want to see her and tell her I broke it already
But, can you guys help me with this? I don't really know where to go from here.
Sbf
Sbf is the only way. And from what I understand if you did the. 621, you won't be able to do previous releases.
I could be wrong.
When it comes yo moto flashing, donkey skip reading anything lol
Sent from my DROIDX using xda premium
Has anyone figured out how to unbrick the droid 2 after that spring ota update from verizon?
I bought a few droid 2's online for almost nothing, attempting to revive them. But one was stuck in bootloop (couldn't see system properties before it rebooted) and wouldn't recover after a hard reset. I tried downgrading to 2.3.20 sbf (oops) which made me go to bootloader every time I started up. From then, I presumed that it received the new ota update already.... I tried using the new sbf's, but I still get error messages when powering up, which directs to bootloader after seeing the red m logo. The latest sbf released in may yields this:
Bootloader
D2.35
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
Maybe there is an ezsbf iso for the latest sbf? Anyways, I couldn't find it. I also tried to look for a valid bootloader sbf, but also to no avail...
Do you not know there is a search function? Look around.
Sent from my Droid Incredible using xda premium
It seems like a lot of other people are dealing with bricked droid 2's so far, no real fix yet unfortunately....
I'm 90% sure you can flash the 2.3.4 sbf
Sent from my Droid Incredible using xda premium
bobkameron said:
Has anyone figured out how to unbrick the droid 2 after that spring ota update from verizon?
I bought a few droid 2's online for almost nothing, attempting to revive them. But one was stuck in bootloop (couldn't see system properties before it rebooted) and wouldn't recover after a hard reset. I tried downgrading to 2.3.20 sbf (oops) which made me go to bootloader every time I started up. From then, I presumed that it received the new ota update already.... I tried using the new sbf's, but I still get error messages when powering up, which directs to bootloader after seeing the red m logo. The latest sbf released in may yields this:
Bootloader
D2.35
Err:A5,69,35,00,27
Battery OK
OK to Program
Transfer Mode:
USB
Maybe there is an ezsbf iso for the latest sbf? Anyways, I couldn't find it. I also tried to look for a valid bootloader sbf, but also to no avail...
Click to expand...
Click to collapse
This will unbrick it http://forum.xda-developers.com/showthread.php?t=1662091
enjoy. Also no root for 621 so enjoy stock
Still a no go unfortunately. I've been trying everything lately. I'm beginning to suspect some innate hardware fault as the cause of the bricked phone...
I was flashing ROMs and had DLed a bunch from a site exclusively for RAZR M phones and some guy had put a bunch of stuff for the XT910 and I accidentally flashed a AOKP GSM zip and now I can't flash anything or RSDLite back to stock, which was always my failsafe out of a soft brick. I still have TWRP and I was able to restore my backup but boot and system files only, data wouldn't restore. Now my phone will boot to the custom splash screen but it just loops. And I first get the red Moto M circle and do NOT get the unlocked boot loader warning. So any help? I will post the RSDLite results when I get home.
ok heres the site I got the file from, this guy should be hung...surdu_petru...http://www.androidfilehost.com/?w=developers&did=70
noone? help is needed please! OK well I restored to a TWRP recovery i had and it worked partially, as long as i unchecked the data partition, the boot and system partitions stuck, so now my unlocked bootloader warning is back as is my custom ROM splash screen, but in a bootloop. I tried RSDLite flashing it again and the 4.1.1 firmware seemed to work but still loops. 4.1.2 and 4.0.4 wont flash because of the "get var, OEM" issue. I had this happen once before aswhile back but was using CWM recovery and juyst switched to TWRP, which fixed it, but not so lucky this time around. So I am wondering if i flash some other partitions like the persist forthe radio, esp since i flashed a xt910 GSM file which is why my phone now thinks its a xt910. Any ideas? please!!!
ok PROBLEM SOLVED. aFTER LOSING THE CUSTOM RECOVERY BY TRYING TO FASTBOOT WITH RSDLITE I DID THE "delete the Getvar and OEM LINES FROM THE FACTORY FIRMWARE OF 4.1.2 (THE .78 VERSION) AND SINCE THE xt910 ROM WAS 4.2.2 AND MY RADIO HAD PREVIOUSLY BEEN UPDATED TO .78, I FIGURED THE .78 4.1.2 WOULD BE MY BEST SHOT, AND SO IT WAS. THAT "GETVAR" ISSUE IS DEFINATE PROBLEM THAT SHOULD BE RESOLVED ANYWAY. wELL ANOTHER TRAGEDY AVERTED, AND IM GETTING PRETTY GOOD AT THIS, LOL, AVOIDING MISTAKES WOULD BE BEST THO. sO BEWARE OF THE "ANDROIDFILEHOST" SITE, THEY HAVE A GUY POSTING XT910 ROMS UNDER XT907 FOLDER! almost cost me a phone Close this thread
Edit does not work on either of my razr m phones
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Here is my Feedback for you...
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
rocketrazr99 said:
one last note, I thought i was unable to get the radio/modem working again as a resullt of flashing a GSM ROM for the XT910, but that issue was fixed with a Firmware flash, or FXZ file, through RSDLite. The issue is actually the RAZR Ms US GSM unlock (NV edit using RadioComm) that is still not working. As with my other RAZR M (LOCKED, rooted, and SS installed) I can not seem to get it working by using RC or DFS, and I am really starting to think the .78 or .94 update killed this edit just as it did the bootloader unlock, even though everyone says it doesnt and that this edit can be performed on locked, unrooted and completely updated devices. If so then....
CAN SOMEONE EXPLAIN WHY BOTH MY LOCKED AND UNLOCKED RAZR M DEVICES WILL NOT ACCEPT THE US GSM EDIT???? PLEASE?
Click to expand...
Click to collapse
The phones will accept the edit and will work on GSM if you unlock with RadioComm. He ran into issues because he didn't unlock with RadioComm.
Sent from my Droid RAZR MAXX HD using xda app-developers app
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
Sorry but they both unlocked. The issue was (I think) that I was typing "01" but only needed to actually type "1" and then the window shows "01". It was something like that anyway.
soft bricked now
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
rocketrazr99 said:
Now my problem is I wiped the whole phone by mistake and cant restore since i lost CWM and cant RSDLite any firmware since the latest was already on it and some error message showed that i had flashed an earlier version or somthing, IDK. But I read that to fix it i need a newer firmware to run on RSDLite, of which none exists. So my phone is soft bricked until Kitkat gets released for the M, which is never, lol
Click to expand...
Click to collapse
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
RikRong said:
You don't need to run a newer firmware, you just need to run one that's equivalent to what you have now. You got the TZ fail because you tried to flash an older FW.
Click to expand...
Click to collapse
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
rocketrazr99 said:
It was actually more than just that. I cant remember but saw a thread about it saying that it had an old firmware and a present firmware and it needs a newer firmware, but I am onm the newest one already so I have to wait for one to get pushed out, idk. Now i can get as far as flashing process 17/21, which is the system flash, when te phone returns a fail. i will try a few tricks i learned from prior luck
Click to expand...
Click to collapse
OK, Rik was right, I didnt have to wait for a new firmware release. I kept trying to flash the most recent version of 4.1.2 and kept hitting a wall at 17/21, which is the flashing of the system image. Occasionally it would fail before that at 16/21, which is CDROM files. That always happened the first attempt after I unhooked the phone and restarted everything, so I started thinking, what is causing the flash to fail for no apparent reason. Then it finally hit me....it was as if my phone was running out of storage space. But that just isnt possible when you are flashing with RSDLite since it wipes out everything first. So I then remembered that my PC has very little room left on its hard drive. Could it be that RSDLite needed more space to work? Hmmmmm, so I deleted a few videos and moved the firmware file to that area (it may or may not help) of the drive and tried again. After the initial fail at 16/21 I was met with a successful flash, although it took a very long time to flash the system image, which I attribute to low disk space. So there you have it.... of course I had to modify the XML file and remove the "getvar" line, and realized I had forgot a golden rule.... all programs and apps need a certain amount of disk drive space in order to operate, and RSDLite is no exception! So now my locked phone will get the carrier unlock edit and Safestrap installed with an extra ROM in slot 1, then it goes on eBay, lol. I have my other RAZR M in semi retirement, it has the BL unlocked as well as the carrier, but I couldnt pass up a new Nexus 5 for $250, but I will surely be swapping the SIM card back and forth because I really miss my RAZR M already. Wish they would make a RAZR M with the processing power of the Nexus 5. Anyhow, PLEASE CLOSE THIS THREAD, TY.
Use this I used it when I bricked mine
Sent from my XT907 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2249773
Sent from my XT907 using Tapatalk
I'm having a similar problem with my xt907. The phone will boot and loop on the boot loader. I have tried to restore with rsd lite bit haven't had any luck. Any suggestions, I know it may not be enough information. If you ask I might be able to give you more details.
---------- Post added at 10:33 PM ---------- Previous post was at 10:28 PM ----------
Also I can't get into recovery.
ImDroidxpert said:
The Reason why it doesn't accept the Us GSM edit Is because the Motorola Droid Razr M is not a gsm phone it is a CDMA phone with LTE. Thus it will not work on any GSM providers unless that provider is like straight talk with multiple networks supported otherwise the phone is stuck on verizon wireless or any other carrier you bought it from. Have A Good Day. By the way my two old accounts got banned for no reason. if you want to know what experience i have look at my devices on the accounts Droidxpert and Droidxpert1. Thanks
Click to expand...
Click to collapse
I am sorry to say that you are uninformed and the XT907 CAN have van NV edit which allows it to be used on GSM networks. The phone is already setup to be comparable with GSN since Verizon made it a "global" handset, but....they also blocked any GSM capabilities in the U.S., until of course you do the NV edit. So please remove your post.