Database Develop

Update.zip for . 340 Kernel, Radio Image, Bootloader, and System!

Hey all, Team Black Hat have released a series of update.zip’s that will allow you to easily flash the newest kernel, radio, system, and bootloader. Thought some might wanna download ASAP in case they get pulled.
Article About it here:
http://www.gizmoninja.com/2010/12/1...date-your-kernel-system-radio-and-bootloader/
Direct link To Team Black Hat Thread and Downloads:
http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html
Cheers! And all credit and thanks foes to Team Black Hat!

If I flash the system.zip from recovery will it take me from Tranquility 3.6 back to stock? What's the best way to go from Tranq back to stock? Thanks.

Flashing the kernel and radio as I type.

aaaaand SBF time lol.

Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.

romanvail said:
Sorry.. just trying to understand...
I have downloaded these 4 files. Now I go to Bootstrap/Recovery and use the Update.zip option for these files one at a time? (in a particular order?) OR do I re-name them update.zip one at a time?
Secondly, I have ApeX 1.2.1 installed... it's working with .320 and I wonder if it will work with the new files?
Any advice on these 2 things. (please)
Thanks.
Click to expand...
Click to collapse
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....

zeavott said:
To answer your first question, we don't need to rename them. We can got o bootstrap and update them one by one. I don't think there's a particular order, however, I do think that we can only do one at a time (install one and then reboot)
I'm not sure about coming from Apex, i'm personally coming from Fission 2.3.1, and I am a little scared to do these....
Click to expand...
Click to collapse
Yeah no renaming is needed.
I am on fission 2.3.1 as well, flashed the Kernel, Bootloader, and Radio Image all one after another while in clockworkmod recovery, and had 0 issues.
U will have to *228 again after radio, but other than that u its fine.

So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing

Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?

mdhaliwal said:
So I just got a question..is this the file that is downloaded ota or put together by these guys? I only ask cause trying to understand why we can't just throw in our own stuff in this update.zip and resign it..but I am sure there is some kind of keys we will be missing
Click to expand...
Click to collapse
Lol, if only it were that simple, unfortunately we can't because of the bootloader being locked, it wont pass security, so we can only modify or use their kernels.
Sunblood said:
Did the 2.3.340 SBF also update the radio or should I use the .zip to update that?
Click to expand...
Click to collapse
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.

ive recently upgraded from my Eris to an X so im having a hard time understanding all of what i need to do, ive downloaded these files and saved them cuz im sure ill need them as soon as i learn everything can anyone point me to a cut and dry tutorial or some kind of explanation? thanks!!!!! loving the x already
edit: i am searching while im waiting for an answer, my bootloader says 30.04 but i dont understand the whole sbf stuff and i can get into clockworkmod recovery im not completely helpless just a little lost after playing with my eris so much.

Confused
I downloaded each file then rebooted into recovery. I installed each file one by one. I reboot system out of recovery and I get a black screen that says:
Bootloader
30.04
Err: A5, 70, 39, 00, 27
Battery OK
OK to Program
Transfer Mode:
USB

btw as far as i can see by the numbers my version is the .340 and the 1.09.07P baseband....i updated mine yesterday

acidbath5546 said:
If u did the .340 sbf u should be all up to date, this is more for .320 users and such. U can double check ur kernel, radio version in about phone though as well.
Click to expand...
Click to collapse
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.

mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
k thanks guys updating now

mob87 said:
The .340 sbf is system only so no he wouldn't be up to date. His system would but not anything else. Still have to apply the patches if you want to be 100% up to date with everything.
Click to expand...
Click to collapse
Oh yeah ur right...forgot .340 is system only...haven't had to SBF in a long time...lol
Thanks for catching that.

I am on Fission 2.2.2 (FRG83), would these updates work for me?

So I am somewhat familiar and want to make sure. I can not get my 2.3. 340 update to go will these files let me do this
Sent from my DROIDX

im at the same screen what to do??

[DUMP] Bootloader (from devkit atrix)

So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?d13i7uxrhw38y7o
SHA: FDA1FDBFD70628CBF1C79361525168847A00830B (motoboot.bin)
DO NOT FLASH THIS!
jimmydafish said:
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.
Click to expand...
Click to collapse

designgears said:
So I haven't tried to use this yet, but it was dumped from a devkit atrix that supposedly has a bootloader that doesn't blow
http://www.mediafire.com/?q053u356h5u52zd
It can be flashed with Qualcomm QPST
http://www.filecrop.com/QPST.html
Click to expand...
Click to collapse
the link is dead

Does "doesn't blow" mean unlocked/non-encrypted?

t0dbld said:
the link is dead
Click to expand...
Click to collapse
Which? I was able to get a copy of motoboot.bin (I think, anyway. designgears, could you post a md5/sha hash of the bin file for us?)
FYI, here's what I have for the file I was able to download:
Code:
$ shasum motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b motoboot.bin

really i cant tells me file has been removed can you mirror or send ?

"Doesn't blow" should mean "lets us load our own kernels" in this context I think
now to figure out how to get the dev bootloader onto our phones..

sorry, was uploading a compressed version

designgears said:
sorry, was uploading a compressed version
Click to expand...
Click to collapse
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader

t0dbld said:
ok now to test... this would be great esp considering they jsut anounced on twitter that zoom comes with locked/unlockable bootloader
Click to expand...
Click to collapse
damn, wish we would have gotten that.

designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
already did

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type

Slow Down Everyone...
this is P3Droid again,
I have all Dev phones with matching consumer phones, granted these are on VZW, but in the past placing a Dev phone bootloader on a consumer phone would result in a system that is inoperable (basically a soft bricked device). I would strongly urge you to not modify this file until you have a way to backup and restore this file.
This is just a word of caution from someone and a group that actually possesses both dev and consumer model phones and have already attempted what you are proposing here.
either way good luck, but do not return the device to ATT if you break it.

Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App

t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.

perdurabo2 said:
designgears? post the SHA or MD5 checksum of the bin file please? I want to get cracking but want to ensure my downloaded file is intact first.
Click to expand...
Click to collapse
smiths-MacBook-Pro:~ smith$ shasum /Users/smith/Downloads/motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b
smiths-MacBook-Pro:~ smith$ md5 /Users/smith/Downloads/motoboot.bin
MD5 (/Users/smith/Downloads/motoboot.bin) = f3cb372a7498f175b53dc7881e4bd3c2
​
P3Droid, you have past experience with Dev phones and retail phones, what does this mean to the hacking efforts? Does an unsigned bootloader move us past any of the previous obstacles or is this just something to study?

t0dbld said:
LOOKS PROMISING!!! so far went through with hex editor and i see no signatures etc !!!
lol so excited cant spell or type
Click to expand...
Click to collapse
humancyborg said:
Not to be too dense here, but how would we make use of this? Wouldn't we still be at square one regaring not being able to get this onto the device?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you would like to brick your device I can teach you how to get it on, but it will require you to be rooted and running a custom recovery, the other method requires a fully released sbf file.

jimmydafish said:
You are not listening and I'm trying to help you not brick your device. DO NOT FLASH THAT BOOTLOADER or you phone will not work...there are a lot more signatures than just the bootloader, in fact if you don't hack/crack the mbr or change the signing keys and verification in the NVRAM you will just sit there with a brand new paperweight.
Click to expand...
Click to collapse
i am listening and i am not flashing anything yet .. .i heard ya before and i hear ya now

Could this bootloader work on Defy also?

I do have to say though with this Xoom news... gives us hope that maybe with GB release for atrix that was promised soon and to include 1080p it might also come with unlock/lock

[Q] wrong sbf? need proper one for (RTGB)

first post, yes, i'm new to this... (forum, not flashing, not entirely anyway, i did fiddle with Sony Ericssons and stuff, kindergarden compared to androids)... but not an idiot, to the point:
firmware config. version seems to be RTGB, great britain, right? wrong, a RTUK is not it. I am sort of lost, i bought the phone with 2.1-update1, the 2.2.1 update has not yet been rolled out in my backwards country, so i did an official update over the internet with motorola app etc etc. I have no idea what was the 2.1 fw config. ver., but it strikes me as weird that i have a RTGB one now, the packaging/box/manuals all were German or something that looks like German. And now, i got myself RTUK sbf file, and RDS lite fails to do anything. I require assistance, and an explanation if possible as to why this didnt work? if i chose the wrong sbf, why does it show me having RTGB? and finally which sbf to take and from where (two german one's are available on this forum), but i've seen only one RTGB and it was only 2.1. For comparison, the friend bought the same phone on the same day, but she got one with a qwertz keyboard, mine is normal qwerty, fw config. ver. shows VFDE, did not update hers, it's still 2.1-update1. I can only assume that VF is german for RT and that her phone did not come from an unknows source. The phone company selling these obviously imports them, possibly even from random countries or EU countries at least...
however something did happen, my battery in the notification seems to be not present, there's just a question mark inside what appears to be an empty battery... apps that show battery levels work fine... although, scratch this last one, a reboot fixed it, even though i have not seen it before.
also, help me rack up some posts ^^ ask for info or whatever, i'd like to give a shot at improving my android...

Check the link below. You will get both service and non-service versions of 2.2.1 sbf's.
http://and-developers.com/sbf:milestone221
VF would be vodafone ( service version) while RT would be retail version.
Sent from my Milestone using Tapatalk

Thanks, gonna try asap, will come crying if it explodes in my face...

SuicideTree said:
Thanks, gonna try asap, will come crying if it explodes in my face...
Click to expand...
Click to collapse
It wont. I have done it many times and my face is still intact, as you can see from my avatar.
Sent from my Milestone using Tapatalk

now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]

SuicideTree said:
now add a laptop that sometimes, actually recently starts bsoding not when you're gaming but when you're picking your nose... and now a serious question, how screwed am i if the laptop crashes WHILE doing something with RDS Lite or something similar ;]]
Click to expand...
Click to collapse
which version of rsdlite and what OS? rsdlite should not cause your OS to crash.

oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.

SuicideTree said:
oh no, it's not rsd lite related, it's just laptop hardware being faulty, that's my assumption anyway, this laptop is going to the warranty next monday, it bsods randomly and i mean really randomly... atm i have win7ult x64 and rsd is 4.9... however this is unrelated, i had a linux here and on it was screwing me over from day one.
Click to expand...
Click to collapse
Try it and see if it works.

Just finished. Seems to be good. Gonna Continue with the guide then ^^ Many thanks.

instead starting a new topic IDIOT QUESTION but... can someone give me a detailed dumbed down version of this instruction bellow:
If you applied an OTA update before, there is a script run at every system boot that checks and re-flashes the recovery when its checksum doesn't match. In such case, you have to avoid booting to android after the vulnerable recovery flash. Boot directly to recovery when RSD Lite restarts the phone (hold camera button) and from there remove the /system/etc/install-recovery.sh file.
rm -f /system/etc/install-recovery.sh
i am getting this
E:Cant open /cache/recovery/command
just upon entering AOR (power+x)
trying to apply the update regardless i get this
- install from sdcard
finding update package
opening update package
verifying update package
E:EOCD marker occurs after start of EOCD
E:signature verification failed
Instalation aborted
what is the meaning of this?
possible solutions:
"It seems that the key to successful recovery flash in some cases is to not let the phone to boot to android or recovery until the RSD Lite will signal PASS. When the RSD Lite is restarting the phone during flash, hold the D-Pad Up, so the phone enters the bootloader again immediately."
does this work? DIDNT WORK, so i still need help
i'm still combing through many threads mentioning this... either please tell me this works or point me in the right direction -_- thanks

Once you flash the official sbf, you need to flash the vulnerable recovery to enable you to run openrecovery which is used to flash custom roms and much more.
There is a script which checks your recovery image everytime it boots and replaces it with the original if it finds any changes. So you need to remove that script.
Procedure would be as follows.
1. Download and extract androidiani openrecovery to the root if your sdcard. You should have a update.zip file and openrecovery folder.
2. Flash official sbf.
3. Flash vulnerable recovery sbf. When the phone restarts and before it displays Moto logo, press and hold the 'x' key on your keyboard. You should see a triangle with exclamation mark. Press volume up + camera button and choose apply update menu option.
AOR should load up. Choose console option and type the following commands.
rm - rf /system/etc/install-recovery.sh
reboot
That's all.
Sent from my Milestone using Tapatalk

okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?

SuicideTree said:
okay, so it seems i did all the steps EXCEPT flashing the original sbf... wait, the first link you provided was to a an official sbf - correct? then where do i get the vulnerability? or vulnerable_recovery_only_RAMDLD90_78.sbf is it? so, i have original flashed, when trying the vulnerability now it says failed, 0x7100, phone connected. what does that mean?
Click to expand...
Click to collapse
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.

I suppose there's no harm in trying that, i already had to rename it to something shorter, cause it wouldnt even give me the Start button.... brb

skadude66 said:
The RAMDLD90_78 is the Vulnerable Recovery.
RSD Lite is a buggy program sometimes. What you need to do is put the sbf you want to flash on the ROOT of your C:/ drive and try it again.
Click to expand...
Click to collapse
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.

sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
You helped me out with that sileshn!
Yeah, I'll keep this thread up and I'll see what issues he's got.

sileshn said:
Buddy, please help him out with the rsdlite problem. I presume you had the same problem and someone helped you out, especially with the Windows 7 x64 error.
@SuicideTree : What is your ultimate goal? You want to have a Official ROM on your phone or you want to flash custom roms.
Click to expand...
Click to collapse
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moved files around, renamed and stuff... weird
EDIT2: by the way, is it normal for the vulnerability file not to show any file properties in RSD Lite?

SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
EDIT: it also appears that once again it wont give me the START button, cant press it, moves files around, renamed and stuff... weird
Click to expand...
Click to collapse
Once you get VR, rooting and flashing a custom ROM is a piece of cake, so it shouldn't be that bad once you get there.

SuicideTree said:
oh well, i was going for cyanogenmod, but for starters i'd like root to have some more control over my phone
Click to expand...
Click to collapse
If you want to flash CM, just install GOT 2.2.1 from here and forget about VR. GOT has VR injected into it. Use the Retail UK sbf.
Once you have CM, you have root.
@skadude : Didn't know it was me.

is cm7 much better over cm6? cause i was looking into that ^^ however if the end goal can be achieved easier with got cm6 i should give that a try, but, what if i wanna play around with this stuff later or something? i'd like to understand what's happening at the moment... anyway, if i go with got solution what are the steps? flash uk sbf, then got or... then cm?
also, got or is better than aor? except apparently having vulnerability alreay in it... anything else?
thanks for all the help, sorry for being not too enlightened, i'll get there ;]]]

[Q] How to start over?

I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.

atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv

Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.

Redownload?

Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?

I would redownload everything and try agian

littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?

atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?

I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App

http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium

wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.

Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.

i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721

I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!

i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.

How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).

i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop

Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.

re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used

[Q]Any details on at&t OTA update?

Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app

not sure but...
jonslice said:
Subject says it all. No luck with Google. Don't want to update until I know what's being updated.
Sent from my HTC first using xda app-developers app
Click to expand...
Click to collapse
I installed the update last night. I honestly don't know what all the changes are, but I'm pretty sure it is a bugfix release. Still android 4.1.2. The only thing that I have noticed is that after the update my led will actually flash green for a text message or email. Before the update, my led only worked for charging, so I would have no idea whether I had email or messages without turning my screen on.
I have not noticed any other changes. No noticable speedups or slowdowns. Haven't discovered any issues. None of my apps have ever forced closed on this phone, and that has not changed after the update.
So...not a bad upgrade, although it might be pointless if you don't have any issues.

19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...

The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip

nuclear_eclipse said:
The OTA zip is on my dropbox in case anyone is curious to look at it. [1] Looks to me like it's updating a handful of system files, as well as the boot and recovery images. With clockworkmod installed, I was prompted to confirm installing the update because its signature wasn't verified, but I haven't yet attempted to let it install it. This should definitely give us an "official" image for the boot and recovery partitions though, which never hurts.
1: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/OTAPkg.zip
Click to expand...
Click to collapse
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!

chrisliphart said:
It'll fail if you try to install it. I'm thinking it needs the official bootloader to work. Someone will need to make this flashable. I was trying to extract it from my phone, but you beat me to it. Thanks!
Click to expand...
Click to collapse
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.

nuclear_eclipse said:
I pulled this recovery.img from the firmware.zip that's included inside OTAPkg.zip: https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.img
I would assume that a simple `fastboot flash recovery recovery.img` should suffice.
Click to expand...
Click to collapse
Huh. I couldn't get the Firmware.zip to open on my system. Thanks for doing that. Now I'm gonna go be an idiot and possibly brick my device by pushing this recovery to my phone to try and install the OTA. lol

I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log

nuclear_eclipse said:
I did also manage to snag the recovery.log from clockwork recovery when the update first tried to run, just in case that actually proves useful to anyone... https://dl.dropboxusercontent.com/u/7859496/Android/mystul/recovery.log
Click to expand...
Click to collapse
Thanks. I posted both the update and your log to the development forum to see if someone with more knowledge can do anything with them.
For the record, pushing that recovery doesn't work. Well, pushing it works, but you can't get into it on the phone. I repushed TWRP to my phone in the interim.

chrisliphart said:
19.8MB update. Can't be too much going on in there, but I'd also think it's more than a few lines of code being updated...
Ooh, fun. Looks like I can't install the OTA with CWM or TWRP. Jonslice, are you rooted?
EDIT:
Weird. Now my phone says the software is up to date. What's the Build info under About Phone for you guys? Wondering if it did actually update even though it said it failed...
Click to expand...
Click to collapse
I got failed update with CWM also. I'll try to post a build info screen shot once I'm on my desktop when my work week is over. Manual check for update says I still need update.
Note: unlocked boot loader, CWM and rooted.
Sent from my HTC first using xda app-developers app

As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?

Daman09 said:
As long as this doesn't remove the ability to disable Facebook Home, I'll probably update it. Can anyone confirm that this is the case?
Click to expand...
Click to collapse
That's a feature of Home, not the firmware. So yeah, you can still disable it. I don't ever see even Facebook changing that.