Database Users

[Q] 2.3.15 SBF fail

Hey Guys,
I need some help! I used RSD lite 4.8 and the new sbf (2.3.15) and I get all the way to the end and then it fails....Here is the error log:
Failed flashing process. Interface BP: Error sending RAM download for bootloader. Device API Error: 0xE0030009 Address: 0x18F000 Command ADDR (0xE0231009); phone connected.
Any ideas?
I am using the OTA 2.2 update and was rooted using BigDX theme.
I have tried the sbf 2x, and both times, would up in the same spot...
When the phone reboots, I have all my contacts and apps...
The reason I wanted to use the sbf is gmail keeps force closing so I'm not getting my emails over push...

So you didnt do a nandroid backup before you installed themes/roms?

I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY

thepolishguy said:
I know this is a stupid question so sorry in advance- did you enable USB debugging on your phone? If so- have you tried it in different modes? Media Sync or USB mass storage?
I have heard reports of having to be in a different mode.
And you are sure it was the new sbf...
VRZ_MB810_2.3.15_1FF_01
Not the system sbf...
SHADO_X6_2.3.13_SYSTEM-ONLY
Click to expand...
Click to collapse
To SysadmNJ,
Yes I did a nandroid backup, so I have a place to go back to...but gmail was still force closed... So that is why I wanted to do the SBF.
Polishguy,
yes I have USB debugging enabled, and had thrown the phone in PC mode so it was detected. I'm stumped as to why it is failing at the end. Yes, I grabbed the SBF from rootz wiki. Would like to have a full SBF work so I can get the gmail service working again.

did you place the patch in rsd lite folder?

mob87 said:
did you place the patch in rsd lite folder?
Click to expand...
Click to collapse
Yes, the patched pst_flash.ini file?
Is there a new one for RSD 4.8?
Just trying to figure out what else might be going wrong...

there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.

mob87 said:
there isnt a new one just wanted to make sure. maybe you got a bad download of the sbf.
Click to expand...
Click to collapse
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks

SysAdmin-X said:
Tried the original that was hosted here before it got pulled by the mods, and also grabbed the one from rootz wiki as well. Got the same result with both. I will try putting the phone in charge only mode as well as media sync mode later and retry the sbf.
If anyone has done this successfully, can you please list the steps you took?
Thanks
Click to expand...
Click to collapse
You are suppose to be in bootloader when you flash the sbf.

mob87 said:
You are suppose to be in bootloader when you flash the sbf.
Click to expand...
Click to collapse
Ok. Will give this a try. I read you could do it with the phone on or off.... That it would put the phone into bootloader...which it looks like it did.
I will try putting it into bootloader prior to running the sbf.
EDIT:
I put the phone into bootloader mode, and have run the sbf 2 more times...still with the same error. Just wind up with different values on the error codes....

Yes holding the volume down, camera, and power button for a few seconds will make the screen flash then release the buttons and you will be in bootloader mode.
Sent from my DROIDX using XDA App

Try a different USB port or even a different PC.

Have tried the above suggestions.... I noticced each time it would make it slightly farther (or so it seemed) that there were device druvers being installed along the way.
Anyone have the driver p package they used if they got the sbf to work?
I'm using the 4.7 drivers
Sent from my DROIDX using XDA App

I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.

FSRBIKER said:
I recently got the same error message, I asked a few developers and P3 told me its the radio that is not being changed. he said it is not a problem unless you are not happy with the radio. This was about a week agao and i have been flashing Rom's/Themes all week and my phone is running great. I wouldn't worry much about it.
Just an FYI I am on the leak and used the first sbf.
Click to expand...
Click to collapse
Hm...interesting. So the radio doesn't really matter unless its already messed up... I guess I should have thought of that...
ON ur x, it does look like everything else is back to stock tho?

did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread

chiaroscuro7 said:
did you do a battery pull ; and/or clear data/cache and do a factory reset after the process seemingly completes (never mind the error) - coz I got some error when I tried flashing using sbf - but I was on the 1st leak - and used the original (2.1) sbf - rsdlite said 100% - but error - mentioned somethin abt bootloader - I did a battery pull - phone went into loop of death - I cleared data/cache and also did a factory reset by going into recovery - and my phone was as good as new... just a thought..
EDIT: Actually, all your questions seem to be answered in the other thread in this very forum by name " Droid X Full SBF Release" posted by catalystsupreme2 - read through all the posts - esp. abt the radio etc which someone here also mentioned in this thread
Click to expand...
Click to collapse
I read through this, and I haven't done the battery pull, or clear..... trying to avoid it if possible...but will if needed.
As for the answer about the BP, it didn't seem like the post really answered the question per say...just gave an explanation about it overall
thank you for the help

Stuck in Bootloader.

I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?

silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.

Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch

This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.

Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.

I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse

http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!

bricked, verizon is overnighting one, should have a good clean one tomorrow.

SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?

edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!

SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.

[Q] I've Bricked another one!

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

Bricked my phone trying to root-Need help getting it back to stock

Hey guys, let me just preface this by saying that this was my first time trying to root, and that I am still very unfamiliar with many of the things involved in rooting. That said, here is my problem and almost exactly what I did to get there.
Alright, so I chose last night to be the night when I finally rooted my Droid 2. I had android 2.3.4 gingerbread .621 version when I started. I ran through the easy windows install instructions first on this page: well, since I can't post links, the page is http: //rootzwiki . com/topic/29930-new-root-method-for-stock-234-621622-found-droid2-r2d2/ (just remove the spaces in the web address). This didn't work because being the noob that I am, I didn't realize how to flash the .sbf file using rsd lite (now I know how to do that I guess, just a little too late).
So I said screw that, I will just run the cd. I downloaded the .iso, burned it to cd, booted to cd, and ran the program. The first time, I tried using the "Root Only" option. This ran, but didn't seem to work. So once that didn't work, I ran the first option that let you have the option to root (I have forgotten the exact wording). This worked and I got to the screen where I had to factory reset the phone. However, instead of being able to do this, I was stuck in bootloader with the error message "Err: A5,70,70,00,1F." So at this point I kind of realized that I was screwed so I tried to flash stock android 2.3.4 back to my phone using RSD Lite. I did this, and ended up changing the error message from the previously mentioned one to "Err:A5,70,70,00,00." So at this point I figured that I had a bad .sbf file and downloaded a new one and used RSD Lite to flash it. After I did this and it failed, I now am stuck in bootloader with a "Code Corrupt" message.
So basically, rooted or not, I would like to be able to use my phone again. I have seen in a couple places that the problem could be due to low battery, but I have switched to a fully charged one with no luck still.
This was my first attempt at rooting, and I am fully hating my first experience, but I'm already this far so I am willing to do the work to learn and get my phone back. If anyone can provide me with some pretty detailed instructions (remember, I'm a total noob and bricked my phone on something everyone else seems to have had no trouble with), that would be incredible.
Thank you in advance!

Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http://droid.koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid. koumakan.jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Yes, it is the droid 2.

bhigham said:
Sounds like your problem with rsdlite might be related to drivers. Here is a page written for the Droid 2 Global, you can read it for information and drivers.
The instructions and drivers would be the same, but the SBF file would be the one for the Droid 2
http ://droid.koumakan. jp/wiki/SBF
Also, just to verify that your phone is the Droid 2, not the Droid 2 Global, correct?
Click to expand...
Click to collapse
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?

xwsxlogan said:
Quick question though, when I am looking for an SBF to flash, do I want to flash on 2.3.4 like I had on, or a previous version, or does it matter?
Click to expand...
Click to collapse
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?

bhigham said:
Problem with Droid 2 on 2.3.4, is that once on that version, you can never go back to an earlier one.
That error message you mentioned first, sounds like the error message you get when trying to flash an older SBF.
Incidentally, where did you download the CD that you tried to flash from? Was it the one linked in the first post of the thread?
Click to expand...
Click to collapse
Yes, it was in the link listed before. The method had been cross posted on this site and on their site.

Ok, above the err message, what does the top line say?

bhigham said:
Ok, above the err message, what does the top line say?
Click to expand...
Click to collapse
The only screen that I can get reads as follows:
Bootloader
D2.37
Code Corrupt
Battery OK
OK to Program
Connect USB
Data Cable
Someone suggested that by holding up and power would bypass the "code corrupt" message, but that does not work. Also, the X+Power to try and wipe the phone clean doesn't work either.

When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,

bhigham said:
When you flash stock 2.3.4 with rsdlite, does rsdlite give you any error messages?
One of the most common errors with rsdlite is when it has the drivers for the regular bootloader mode, but not the drivers for the radio flash mode.
If this happens, you will get that code corrupt error message.
Also, what OS are you using? XP, Vista, 7, 64bit,
Click to expand...
Click to collapse
I did get an error message when trying to flash the stock 2.3.4 and it was something to do with RAM, but unfortunately this was 5AM this morning and I was beyond exhausted so I don't remember exactly.
I am using Windows 8 x64, but have access to XP, Vista, 7, and server if I need to.

I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP

bhigham said:
I would definitely try XP if I were you, and if you have access to another USB cable, I would try that.
To use XP, install the motorola drivers first, then use rsdlite.
I have used RSDlite 5.6 and 5.7 on my D2G, and both have worked fine with XP
Click to expand...
Click to collapse
Alright, I will go ahead and get XP installed along with the drivers. Do you think that I should use a version previous to 2.3.4 then so that I have a better chance to root?
I am charging up my battery now using another phone, so I will start on it in a bit. Thank you again for answering all of my stupid questions and helping me out, I really appreciate you taking the time to do it.

It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.

bhigham said:
It would be nice if you were able to go back to an earlier version, but that isn't an option. Once on 2.3.4, no going back.
Click to expand...
Click to collapse
So you're saying that the only thing I will be able to flash is the 2.3.4?

xwsxlogan said:
So you're saying that the only thing I will be able to flash is the 2.3.4?
Click to expand...
Click to collapse
exactly

bhigham said:
exactly
Click to expand...
Click to collapse
Alright, I will try again tonight with a charged battery and XP and let you know how it goes.

This link here http://www.google.com/url?sa=t&sour...rICoBg&usg=AFQjCNHht4SU69VoDkBnMBCA_0uf9WYpyw. Will take you to the download for the correct sbf.
Correct sbf should read: 1ff-p2a_droid2_cdma_droid2-user-2.3.4-4.5.1_57_dr4-51-120117-release-keys-signed-Verizon-US.sbf.gz
Sent from my DROID2 using Tapatalk 2

Alright Update after flashing the .sbf file that was given in the previous post.
I used XP, running RSD Lite 5.6, with Motorola drivers installed. I charged a second battery up to around 70% or so to use during the process. I also changed USB cords from the previous one that I was using. I loaded the .sbf into RSD Lite, started it, and it ran flawlessly, skipping right over the RAM step in which it failed last night. Had to remove the battery and reinstall to do the manual reboot, and all of my phone settings were exactly as I had left them when I started. I had to dial *228 +1 to get the phone back on the network, but that was no problem.
So after all of this, I'm back to where I started last night haha. Special thanks to bhigham for all of the support and walking me through this today and also slogar25 for confirming that I had downloaded the right .sbf file.
So I guess my problem is solved...until I try and root it again!

glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.

bhigham said:
glad your phone is working again.
If you want to try to root again, you might have better luck with a freshly wiped phone, but if you prefer not to risk it, I don't blame you.
It is possible a cord issue, but just guessing here.
Click to expand...
Click to collapse
Yep, I've noticed you have been following the cross post on this site for the methods that I tried last night when I really didn't have a clue what I was doing. Do you think that I should just try the CD method again? I mean worst case I would do the same thing I did last night, but now I know how to flash it back to the stock 2.3.4. I don't mind wiping my phone, but after it survived everything I did last night, I feel more attached to my data haha.
Also, how do I mark this post as solved?

[Q] So, I think I completely broke my phone

I hate to use the term "brick" because people here sometimes get their panties in a twist when that term is used, but that's kind of how it seems to me. Currently all I can get to is fastboot. It says the device is locked and then says:
Downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load gpt
CID read failure
Invalid CID status 0x69
I've tried holding vol up, vol down and power, then releasing power while holding vol up and vol down. It got me right back to where I am.
If it helps, I got here by messing with some settings on the phone and somehow disabling all voice functionality on my phone. Data still worked, but not voice. I figured since I had messed it up, I would factory reset. This fixed that problem. Then I went into TB and restored my system data and apps. The phone then got stuck at the boot screen. I figured I'd go into recovery, wipe again and restore just the apps this time. When I did that, the phone got stuck in it's current status. I fired up the Razr M utility that's out there (w/the Batman logo) and tried to re-flash stock recovery and the stock rom. Both failed claiming my partition is bad. I'm not sure where to go here or I've permanently broken the device. The bootloader is unlocked if that helps at all.

try this? or House of Moto utility at droidrzr.com
A. Nonymous said:
I hate to use the term "brick" because people here sometimes get their panties in a twist when that term is used, but that's kind of how it seems to me. Currently all I can get to is fastboot. It says the device is locked and then says:
Downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup: 0x35
failed to load gpt
CID read failure
Invalid CID status 0x69
I've tried holding vol up, vol down and power, then releasing power while holding vol up and vol down. It got me right back to where I am.
If it helps, I got here by messing with some settings on the phone and somehow disabling all voice functionality on my phone. Data still worked, but not voice. I figured since I had messed it up, I would factory reset. This fixed that problem. Then I went into TB and restored my system data and apps. The phone then got stuck at the boot screen. I figured I'd go into recovery, wipe again and restore just the apps this time. When I did that, the phone got stuck in it's current status. I fired up the Razr M utility that's out there (w/the Batman logo) and tried to re-flash stock recovery and the stock rom. Both failed claiming my partition is bad. I'm not sure where to go here or I've permanently broken the device. The bootloader is unlocked if that helps at all.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2526311 same as this?

jimyv said:
http://forum.xda-developers.com/showthread.php?t=2526311 same as this?
Click to expand...
Click to collapse
Same thing. Getting the "failed no such partition" errors as well.

try
A. Nonymous said:
Same thing. Getting the "failed no such partition" errors as well.
Click to expand...
Click to collapse
grab this VRZ_XT907_9.8.1Q-94-1_CFC.xml at http://sbf.droid-developers.org/ exract it. grab this http://www.mediafire.com/download/tq09cpqupvo4fdq/HouseOfMoto-xt907.zip . extract all. grab this only FULL_xt907..out of/ rsd_scripts / folder drop in ur extracted sbf file open RSD lit v 6.1.5 . navigate to the script u dropped inside ur extracted sbf file add select the FULL_xt907 script udropped and run..fixed mine not my work just made a luck guess combination that worked for me...thank House of Moto guy for script over at droidrzr.com

jimyv said:
grab this VRZ_XT907_9.8.1Q-94-1_CFC.xml at http://sbf.droid-developers.org/ exract it. grab this http://www.mediafire.com/download/tq09cpqupvo4fdq/HouseOfMoto-xt907.zip . extract all. grab this only FULL_xt907..out of/ rsd_scripts / folder drop in ur extracted sbf file open RSD lit v 6.1.5 . navigate to the script u dropped inside ur extracted sbf file add select the FULL_xt907 script udropped and run..fixed mine not my work just made a luck guess combination that worked for me...thank House of Moto guy for script over at droidrzr.com
Click to expand...
Click to collapse
I'm at work and don't have adb setup on my computer here so I'll do that when I get home. I'll let you know if it works. I've been rocking my original DInc (which has some sort of usb bug that I need to fix in it) all day and having just 3g is kind of killing me. Not gonna lie.

I'll add
A. Nonymous said:
I'm at work and don't have adb setup on my computer here so I'll do that when I get home. I'll let you know if it works. I've been rocking my original DInc (which has some sort of usb bug that I need to fix in it) all day and having just 3g is kind of killing me. Not gonna lie.
Click to expand...
Click to collapse
I used the RSD lite that is in the Houseof Moto http://www.droidrzr.com/index.php/topic/28162-house-of-moto/ All thanks it his WORK/ extract it all and go to HouseOfMoto_1.4/HouseOfMoto/rsd/SDL/ run that one I don't know if theres goodies in threr that help or what but it worked for me that way only...of course have drivers installed / I didn't need adb setup just make sure ur run as administrater

Many thanks. That totally worked. Was easier than I thought it would be too. Had a hard time finding the gui for rsd and couldn't find a way to point the cli at the right file, but that was probably user error. Once I found the GUI, it worked just fine. Kudos to you. I'm impressed.

Deperation
A. Nonymous said:
Many thanks. That totally worked. Was easier than I thought it would be too. Had a hard time finding the gui for rsd and couldn't find a way to point the cli at the right file, but that was probably user error. Once I found the GUI, it worked just fine. Kudos to you. I'm impressed.
Click to expand...
Click to collapse
No problem glad it worked for u also.. I just got lucky after few days sweating the battery count down before I had to buy adapter it was stuck in ap boot only stating locked device pus same errors as urs no recovery no nothing no flashy nothing even my phone guy gave up after 3 hrs. five xt912s later and one blue wifey razr M you would think I would have one but sadly no. I moved on to sch1545 ver. s4 and rusty at the moto work ,but I refuse to ins.claim on an oops I fd up . I was bout to send her phone shopping went something worked . did a lil dance and handed her phone back ..with 4 present battery.she perfered it that way cuz new moto products ,,,GOOGLE [products] don't support sd cards anymore so was going ti Sammy it up ..but she loves her freaking blue razr. thanks for the thanks happy to assist u with my dumb luck lol...like I said I hit right combo of someone elses work..SamuriHL over at droidrzr.com thank him over there.. for work on HouseOfMoto.
---------- Post added at 08:31 AM ---------- Previous post was at 08:05 AM ----------
jimyv said:
No problem glad it worked for u also.. I just got lucky after few days sweating the battery count down before I had to buy adapter it was stuck in ap boot only stating locked device pus same errors as urs no recovery no nothing no flashy nothing even my phone guy gave up after 3 hrs. five xt912s later and one blue wifey razr M you would think I would have one but sadly no. I moved on to sch1545 ver. s4 and rusty at the moto work ,but I refuse to ins.claim on an oops I fd up . I was bout to send her phone shopping went something worked . did a lil dance and handed her phone back ..with 4 present battery.she perfered it that way cuz new moto products ,,,GOOGLE [products] don't support sd cards anymore so was going ti Sammy it up ..but she loves her freaking blue razr. thanks for the thanks happy to assist u with my dumb luck lol...like I said I hit right combo of someone elses work..SamuriHL over at droidrzr.com thank him over there.. for work on HouseOfMoto.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2526311 should help him aslo

Only problem I've got now is that I lost root in the process and got upgraded to 4.1.2 so the Motochopper root exploit doesn't seem to work. The bootloader is still unlocked so I'm guessing I might be able to flash something. I tried flashing the stock recovery and stock image from the Razr M utility, but that didn't seem to allow me to root. Any ideas?

A. Nonymous said:
Only problem I've got now is that I lost root in the process and got upgraded to 4.1.2 so the Motochopper root exploit doesn't seem to work. The bootloader is still unlocked so I'm guessing I might be able to flash something. I tried flashing the stock recovery and stock image from the Razr M utility, but that didn't seem to allow me to root. Any ideas?
Click to expand...
Click to collapse
just use matts 1.20 .root it and ota on up to current useing voodoo ota root keeper each step and restoring root and rebooting each step worked for me
---------- Post added at 11:58 AM ---------- Previous post was at 11:44 AM ----------
http://forum.xda-developers.com/showthread.php?t=2249773
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
http://forum.xda-developers.com/showthread.php?t=2249773

That's what I've been using. The text based app w/the batman logo. I tried the motochopper exploit (option 5). It failed. I tried option 2, then option 1. It bricked the phone. Had to boot into the recovery partition to fix it and let stock recovery run which gave me a phone I couldn't root. I'll try it again though.

Never mind. Second try worked.

jimyv said:
just use matts 1.20 .root it and ota on up to current useing voodoo ota root keeper each step and restoring root and rebooting each step worked for me
---------- Post added at 11:58 AM ---------- Previous post was at 11:44 AM ----------
http://forum.xda-developers.com/showthread.php?t=2249773
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
http://forum.xda-developers.com/showthread.php?t=2249773
Click to expand...
Click to collapse
I can verify this, it does work.
Matts 1.20 utility works 100%!
Sent from my Nexus 7 using XDA Premium 4 mobile app