Database Info

Please help my nexux s

I just unrooted my nexus s (9020t) and returned it to stock. It came up with 2.3.1 originally and wanted to update it back to 2.3.3. I found the update drivers and tried to update it, and came up with the status 7 errors. If found the solutions, and tried to go from 2.3.1 to 2.3.2, than install the radio thing to 2.3.3. Up to 2.3.2, it came up with the same error and tried the last resort of updating it to the full 2.3.3 os.
After the update, the nexus s turns on to the google splash screen and hangs up there. I can still access the recovery by holding the volume up and power. I also tried to do factory reset, and wipe data. Nothing seems to help.
Any help?

I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App

I'm totally new into the android community and have no idea what Odin or jig is.
Since the fastboot is working, is there something that I'm missing with resetting orders or something else? I found that some one did a wipe dalvik (I think) with factory reset and cache, but I cannot find the dalvik.

donharden2002 said:
I'm no expert by any means but you may have to use odin to get it going again. You will probably need to make a jig or buy one to get into download mode.
I hope this helps you and your able to get up and running again.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
You dont need a jig to get into download mode
Aslong as the bootloader is unlocked
Power down phone hold volume up/down then plug in USB from computer ....in download mode
Sent from my Nexus S using XDA App

im thinking if you could still access the bootloader then you can still flash clockworkmod. when you get that running, flash any rom u want in clockwork including stock 2.3.3. no odin necessary.

As long as you can still use fastboot there's no need to use Odin or JIG to flash the ROM.
I assume that:
you already have clockworkmod recovery installed and it's working properly.
your phone model is I9020T (SAMOLED)
If those are correct, I'd suggest you to download the 2.3.3 OTA package and flash it via clockworkmod (use the menu "Install zip from sdcard")
After flashing you'll have 2.3.3 on GRI40 running. And if you want to continue updating to 2.3.4, there's a thread dedicated to the topic.

PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!

SovereigN7 said:
PROBLEM SOLVED! Big appreciation to sonnysekhon who helped me over the phone at 11 in the night!
I was guided to just unlock fastboot, load the cwr and go into usb storage, add the cyanogen mod 7 and voila, problem solved. Now my only problem is, I've got 2.3.3 and want to update it to 2.3.4. Is there any easy way to do this?
Again, I want to thank you guys for the help!
Click to expand...
Click to collapse
Are you on cm7 or stock?
Sent from my Nexus S using XDA Premium App

I'm on cm7. It shows the cyanogen mod splash screen during bootup and has rom manager, file manager preinstalled.
I'm not really savvy when it comes to android mechanics because I just moved from itouch and iphones to androids couple days ago.

First of all. Congratulations on making the best decision! Iphone sucks. Lol.
Anyway, you can't update to 2.3.4 yet since its only available on stock right now. We're gonna have to wait until devs incorporate it into their custom roms. I believe there is a nightly version of cm7 that is already 2.3.4 but its not as stable as the 2.3.3 yet. hope that helps.
Sent from my Nexus S using XDA Premium App

yea you made the right move switching
Give it time you will get use to messing with Roms ..ect

[Q] Droid 2 Global Stuck In Bootloader

Earlier today my phone was acting up, not sending messages. So i did a soft reset. Now when I turn it on, all I see is Boot loader D0.11 Battery OK Program OK connect USB cable.
I've tried to flash 2 SPF's. It was rooted recently, and had the latest updates. Everything was fine untill I did the soft reset.
What is causing it to keep returning to the boot loader screen?
Also, when I try to flash it via RSD Lite i keep getting Error switching to pass through, or something simular to that.
Ive tried 2 SPF's and factory reset, cache format, all that.
I have to have this phone for work, so any prompt help would be greatly appreciated.

Hey man that exact same thing happened to me. You are going to need to SBF to stock. 1KDS has a nice tool out there. It is a mini linux distrobution that you burn to a CD and boot up on it. Just google ezSBF by 1KDS. Hope this helped
Sent from my DROID2 GLOBAL using XDA App

skript_kidee said:
Hey man that exact same thing happened to me. You are going to need to SBF to stock. 1KDS has a nice tool out there. It is a mini linux distrobution that you burn to a CD and boot up on it. Just google ezSBF by 1KDS. Hope this helped
Sent from my DROID2 GLOBAL using XDA App
Click to expand...
Click to collapse
I tried using all 3 of his CDs and none of them would boot my D2G past the bootloader. Also tried using rsdlite with 3 different SPF and nothing came of that either. Would continue to receive MEM_MAP blank error. I'm really out of ideas now.

There was an OTA recently by Verizon/Motorola released which breaks the ability to SBF to an older software release (they simply updated the boot loader and the new one does not accept older releases).
Unfortunately the cure of this would be a new SBF to be leaked with software release same or newer than the one from the past week OTA. Until then you're stuck with soft-bricked phones.
Check this thread out: http://forum.xda-developers.com/showthread.php?t=1531341

unbrick here http://rootzwiki.com/topic/23207-how-tounbricking-downgraded-629-root-normal-function-ota-629/
Sent from my DROID X2 using xda premium

D2G bricked

I moved from latest cm9 which caused some troubles when I want to call, unknown phone call appear and was unable to cancel it, only reboot helps. Then I found another ICS rom which look attractive for me - MIU in newest version because not all roms support GSM which i'm using as a carrier (european O2). After flashing I got message phone proces fails every 5sec, so I decide to do same as by cm9 to clear both cache and than flash again rom. After clear of all cache I was unable to install any rom, because I had message, it is not signed (tryied cm7.1/2, cm9, miu, some verizon roms).
I decide to sbf this phone.I take rsd lite v5.4.4 and try to flash 2.4.33 rom, but first time, I deplete my batery, ok, I have second one, change it and try again, everything goes like a charm but after 100% of proceed I get message there is some failure, I'm asked for driver to qhsusb_dload and bootloader writes
bootlader d0.11
code corrupt
and don't recognize cable is connected.
Is there some hope?

Maybe newer rsd lite http://forum.xda-developers.com/showthread.php?t=1348587 also try newer drivers http://androidevolved.com/forums/dr...orola-droid-2-global-usb-driver-download.html

some device bricked like that for about 1 month in China , but no one solved this problem. . .
Sent from my DROID2 GLOBAL using xda premium

kew1701 said:
Maybe newer rsd lite http://forum.xda-developers.com/showthread.php?t=1348587 also try newer drivers http://androidevolved.com/forums/dr...orola-droid-2-global-usb-driver-download.html
Click to expand...
Click to collapse
guys in China that phone bricked like this tried different rsd, drivers, computer,USB cable ,sbf(.29,.33,.608,.629),no luck
Sent from my DROID2 GLOBAL using xda premium

jararak said:
After clear of all cache I was unable to install any rom, because I had message, it is not signed (tryied cm7.1/2, cm9, miu, some verizon roms).
Click to expand...
Click to collapse
Were you getting this message in ClockworkMod Recovery, or were you trying to flash custom ROMs in stock recovery?
As for the other, it sounds like you either have a corrupted SBF or your phone's internal flash memory has become damaged. If it is a problem with the internal flash, your only options are replacing the phone or trying to convince VZW or Motorola it should qualify for warranty replacement.

it looks that there is some problem with step by step from CM
http://forum.xda-developers.com/showthread.php?t=1637429 same issue
on other hand I have win xp 32b and battery was fully charged before I start with "games"
I will try those new drivers, I will see if something differs
on other hand, I bought this phone on ebay without any paper, so probably without possibility to try reclamation on verizon/motorola.
edit : to question which recovery I used, I think it was stock recovery (x+power button, than both volume button after ! showed up)

jararak said:
it looks that there is some problem with step by step from CM
http://forum.xda-developers.com/showthread.php?t=1637429 same issue
Click to expand...
Click to collapse
What step-by-step are you referring to?
jararak said:
edit : to question which recovery I used, I think it was stock recovery (x+power button, than both volume button after ! showed up)
Click to expand...
Click to collapse
You can't flash ROMs in stock recovery, only signed update.zip files from Motorola. To flash non-Motorola ROMs you need ClockworkMod Recovery.
If you manage to SBF successfully, you will need to install a root exploit first, then follow these instructions to install CWM: http://droid.koumakan.jp/wiki/ClockworkMod_Recovery

Hi
I tryied this step by step for sbf, it looks this currently is corrupted http://wiki.cyanogenmod.com/wiki/Motorola_Droid_2_Global:_Full_Update_Guide
To my current problem, it looks I have newer driver revision - 5.4.0, but this rsdlite looks like helpfull (now red icon instead of blue one before). phone was recognized. downloading sbf file from http://www.droidknows.com/showthread.php/364-Gingerbread-Full-SBF-4-5-608 , i hope it will be successfull
about original rescue mode, i don't have this knoweledge, it works only with signed rom, but it is good to know to future. I've already bid for some new d3, but some guy beat me by 1$, when I run for one shot of vodka ;D
i will update shortly if this help me or not, but it does not matter, thanks for help
edit : process failed, After 100% of flashing image to phone, it was unable to find qhsusb driver, it is possible somewhere to download it to win xp 32bit?
Failed flashing process. Phone(0000) Error switching phone to BP Pass through mode (0x70BE); phone disconnected.

http://droid.koumakan.jp/wiki/SBF
Read the How-To section.

I think is something wrong with the phone
Sent from my DROID2 GLOBAL using xda premium

zyy757 said:
I think is something wrong with the phone
Click to expand...
Click to collapse
I think you just replied without thinking.
I posted a link to a wiki article that explains what this error is, and a way to fix it.

Gasai Yuno said:
I think you just replied without thinking.
I posted a link to a wiki article that explains what this error is, and a way to fix it.
Click to expand...
Click to collapse
sorry，is the way in wiki work？
Sent from my DROID2 GLOBAL using xda premium

try search cynogen.wikipedia..
follow this instruction
Sent from my DROID2 GLOBAL using xda premium

I tried it my way
cut some mini usb cable which I have, you need red and brown wire, red is + so you need to connect it to the left pin and brown is ground to righ pin, two in a middle is just for checking state of battery - so now I have a charger for both of dead battery (facing screen to bottom and power button up)
than I created bootable usb via this instruction http://www.droidforums.net/forum/droid-2-global-hacks/170060-tool-ezsbf-d2g.html
now my jedy droid which cut apple is changed with red motorola logo, I get rid of code corrupt message and also have bootloader.
now I'm trying again rsd lite to flash 4.5.608 sbf image. I hope this will help someone in future, at least as one step or kind of fallback from state which I found.

I tried sbflite, sbf_flash but still no progress, I still have only red M logo, after that I get bootlader. as I understand, sbf phone shoul install also OS to phone, doesn't?
I also try to cler cache (/data) via recovery mode (default), but not help.
Should I try to install some rom via recovery? i asume i will need some differ rom than sbf

Gasai Yuno said:
I think you just replied without thinking.
I posted a link to a wiki article that explains what this error is, and a way to fix it.
Click to expand...
Click to collapse
The way to fix that in wiki is for windows 7 or vista, but xp?
Sent from my DROID2 GLOBAL using xda premium

I have a theory of a possible way to fix this, but don't know if it will actually work.
From the sounds of what you are describing, it sounds like everything is flashing except the radio in rsdlite, and that the radio is possibly corrupted by the process.
If this is the case, and you still have access to Motorola recovery (booting with X pressed), maybe you could put the OTA update from 2.4.33 to Gingerbread on the SD card, and try installing the update from zip. The reason for doing this would be to flash the radio without using rsdlite. EzSbf does not flash the radio, so if a corrupt radio is your problem, it will be no help. Just a thought, hope it is helpful.

meon_69 said:
try search cynogen.wikipedia..
follow this instruction
Click to expand...
Click to collapse
Do not follow any instructions for the D2G from the CyanogenMod website if you have ever had a stock Gingerbread firmware (versions 4.6.x) on your D2G. Everything on the official CM site assumes your D2G is running stock Froyo (firmware version 2.4.x) and will not work with a Gingerbread kernel.
---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------
zyy757 said:
The way to fix that in wiki is for windows 7 or vista, but xp?
Click to expand...
Click to collapse
The wiki article G.Y. linked says "Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly." This means that the problem is more likely to occur under Vista or 7, not that the fix only applies to those versions. If the same problem occurs in Windows XP, the same fix should solve it.

bhigham said:
I have a theory of a possible way to fix this, but don't know if it will actually work.
From the sounds of what you are describing, it sounds like everything is flashing except the radio in rsdlite, and that the radio is possibly corrupted by the process.
If this is the case, and you still have access to Motorola recovery (booting with X pressed), maybe you could put the OTA update from 2.4.33 to Gingerbread on the SD card, and try installing the update from zip. The reason for doing this would be to flash the radio without using rsdlite. EzSbf does not flash the radio, so if a corrupt radio is your problem, it will be no help. Just a thought, hope it is helpful.
Click to expand...
Click to collapse
Tried flash .608 sbf and ota .629,error when update bp
Sent from my DROID2 GLOBAL using xda premium

jabberwockish said:
Do not follow any instructions for the D2G from the CyanogenMod website if you have ever had a stock Gingerbread firmware (versions 4.6.x) on your D2G. Everything on the official CM site assumes your D2G is running stock Froyo (firmware version 2.4.x) and will not work with a Gingerbread kernel.
---------- Post added at 05:23 PM ---------- Previous post was at 05:21 PM ----------
The wiki article G.Y. linked says "Under certain circumstances (especially when using Windows Vista and Windows 7) there might be a problem with not all device drivers being installed correctly." This means that the problem is more likely to occur under Vista or 7, not that the fix only applies to those versions. If the same problem occurs in Windows XP, the same fix should solve it.
Click to expand...
Click to collapse
Tried, no luck.I'll try again later
Sent from my DROID2 GLOBAL using xda premium

RDS Lite Phone return FAIL

RDS lite used stock rom install Error:
falied flashing process.3/20 flash mbmloader ''mbmloader.bin''.Phone return FAIL
Help Please
Thanks

tr.sertac said:
RDS lite used stock rom install Error:
falied flashing process.3/20 flash mbmloader ''mbmloader.bin''.Phone return FAIL
Help Please
Thanks
Click to expand...
Click to collapse
Too little information and rds lite does not exist.

Post the full details here including your base firmware version which rom you tried to flash etc etc
Sent from my MB865 using xda app-developers app

Mui ICS rom install after reboot fail.
RSD tlie used stock rom,error Phone Return Fail
My Phone fastboot Screen
Battery OK
Ok to Program
Transfer Mode:
USB Connected

tr.sertac said:
Mui ICS rom install after reboot fail.
RSD tlie used stock rom,error Phone Return Fail
My Phone fastboot Screen
Battery OK
Ok to Program
Transfer Mode:
USB Connected
Click to expand...
Click to collapse
u tried to flash miui? thats not even for rsd

Was you stock 2.3.5, 2.3.6 or on the ics leak before trying to fxz?
Sent from my MB865 using xda app-developers app

Please search!
Ok, so this is how you fix your issue:
If you want to flash the MiUI ROM you NEED TO BE ON ICS (4.0.4) FIRST!
If you are on Gingerbread (2.3.5 or 2.3.6) the install the ICS leak for YOUR CARRIER.
There are a couple of different types of ICS leaks out there depending on your carrier, install the proper one for your phone.
Once you get on ICS the MiUI ROM is installed the BOOTMENU NOT RSD LITE. It's not even the right file type for RSD lite.
I will not give links as you can find them your self with the search bar. I would personally advise against the MiUI ROM as it is VERY buggy right now, and honestly man, if you don't know what I'm talking about you SHOULDN'T BE MESSING WITH YOUR PHONE.
Especially if you were trying to flash the damn thing through RSD lite... for pete's sake.
READ. SEARCH. RESEARCH.
THEN REPEAT.

+1 well put and agreed.
Sent from my MB865 using xda app-developers app

One thing that I've found...be sure that your USB cable is plugged directly into the computer, and not into a hub. I can do everything through a hub with mine EXCEPT fxz back to stock...and so when I tried and it stuck on the same step that you're on, I (and pretty much everyone else that I asked) was stumped. With all the crap that I tried, it really was something that easy, and yeah, I'll admit it: dumb. There really is a reason that tech support people ask dumb questions to start off with.

I've tried everything but I can not friends.
I installed the ICS Mui and format / Webtop after having had this error please help
"Invalid CG Version" with the stock rom try to install rsd lite Phone Return'' failed'' error.
I do not know what to do

Breathe Fall....
Okay mate, one question at a time.
What are you trying to install? RSD lite is ONLY used for installing fxz files and other various file types.
Sent from my MB865 using xda premium

Sounds like he tried to fxz back and is getting the cg error Jim has a fix for in the stickies.
Sent from my MB865 using xda app-developers app

I bricked my A2 need help plz, ve
hi, Last night i install update file which make me stuck in boot animation, I tried to flash FZX files by RSDlite5.6 but cant proced after satge 2 out of 18, i tried every thing i knew to flash it back but i couldn't, and also I tried to install a rom from recovery ( by holding volume UP and down and press power then recovery then again volume up +down and from option apply update from sccard, and it give me "E:signature verification failed install aborted". please can anyone help me, please.
my device is atrix 2 mb685 ATT
my rom is SCv5

Holy font sizes, Batman.

[Q] maybe i brick my phone

i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?

This whole mess started when you tried to flash MEARET firmware on your AT&T phone. NEVER mix firmware!
And trying recovery at this point is not going to work, as the ICS zip is just a large patch file for 2.3.6. And since it failed on the fxz, a portion of your system is missing so ICS won't install. You need to fxz back.
What step is the script falling at? A screenshot would be helpful.
And for the future, please post questions in the Q&A form.
Sent from my SAMSUNG-SGH-I727 using xda premium

you mean at 3rd step?
sorry.please move this thread at q&a

Yes the script from step three is what's going to save you here.
But we need to know where it's failing at.
Sent from my SAMSUNG-SGH-I727 using xda premium

i can see that problem is with cbt, recovey and cdrom partition.

Uh oh.
Which ICS version did you install? Please show need the thread.
I need to know which leak it was.
Sent from my SAMSUNG-SGH-I727 using xda premium

Blur_Version.55.13.25.MB865.ATT.en.US.zip

Well I hate to tell you man. But you are soft bricked until we find an fxz for ICS.
Recovery and cdrom are failing because cdt.bin isn't flashing. And we haven't found a fix for this yet.
Although the strange thing is that this shouldn't be happening on the first leak... but it is...
So you're bricked mate.
Sent from my SAMSUNG-SGH-I727 using xda premium

ok, i will wait.
thanks.
but please explain to me.i had a motorola a1200 and a siemens sx1.when i flashed a firmware, all the flash memory erased and new data wrote at flash.if i had bootloader, all was fine.the only method to brick a phone was to replace the battery when flash the bootloader(or flash false bootloader).
at A2, why when i write a new bootloader and new mbr(and partition table?) is necessary to flash the same or newer edition of firmware?this is because bootloader is locked?
i thought when i flash a new firmware, all the flash memory erased and writes new data(at the begining the bootloader, after mbr with partition table, after the image(i think this is the kernel of linux) and all other the data)

macnick said:
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
Click to expand...
Click to collapse
Use rsdlite and flash the Asian or Chinese stock firmware worked for me when I had this issue now I'm running 4.1.1 cm10 jb and its awesome!
If this works for you hit my thanks button
P.s phone must be in fast boot mode
Sent from my MB865 using XDA Premium HD app

Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...

macnick said:
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app

macnick said:
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
whiteboi-hakz said:
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!

Fall of Enosis said:
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Click to expand...
Click to collapse
Dude it works and he can then reflash his fw so what's the big deal the one I bricked was at&t non international and that method worked great but I'll take your advice man
Sent from my MB865 using XDA Premium HD app

i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)

macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
OK well was worth a try I guess ay try his method and let's us know
Sent from my MB865 using XDA Premium HD app

macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.

Fall of Enosis said:
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Click to expand...
Click to collapse
Thanked you as earned it man
Sent from my MB865 using XDA Premium HD app