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
Related
he said he bricked it trying to upgrade to ICS.
is the sticky at the top still the way to unbrick it? i noticed that a couple links were dead in the first post. granted i didn't go through all 17 pages, just wanted to make sure there wasn't anything newer then whats already been posted.
edit: he did say that the screen is showing s/w if that matters
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
LurkerRWO said:
Was it bricked by flashing a o2x rom? I think that may be the hardest brick I have heard of but still fixable. I believe if that is the case than following the sticky should restore the baseband and everything else.
Honestly though I would first try just reflashing CWM via nvflash, boot into recovery and load a stable GB rom. If that works, great.
Click to expand...
Click to collapse
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
im on windows 7 if that matters
and after i boot into recovery the screen is just flashing black. any ideas?
everything i do with flashing it just sits at the prompt saying "flashing" and nothing else happens.
blackbeasst said:
he just said things went haywire when trying to flash ICS. i've been messing around with the sticky but can't get anything to work....yet!
Click to expand...
Click to collapse
You apparently you did not even read the first post. XP only, will not work with Windows 7.
"As many have stated, pushing the v21E_00.kdz via the KDZ_FW_UPD program does work. It's just touchy.
This is a step by step guide to get you back in to working shape.
Note: You MUST do this via a PC running Windows XP. Running Vista/7 in compatibility mode is not going to work, period.
Edit: As an alternative, a virtual environment running XP will do the job. Those steps are up to you."
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
LurkerRWO said:
That's not true. I updated the baseband using win7 on my first try. No need for comparability mode.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Can confirm that too. Was working fine on 32 bit win7, using the method from the stickies upgrading wind's June baseband.
Sent from my LG-P999 using xda premium
duple and lurker, thanks for the confirmation that it works with 7
when i try and push the kdz i get the dreaded phone not found.
ok im on my xp machine here at work and heres what i got:
Part 1: Download the files you will need below.
V21E_00.kdz
KDZ_FW_UPD_EN
One-Click-G2x-recovery-flasher-06-16.rar
LG USB Drivers G2x
Part 2:
1) Install the LG G2x USB drivers to your WinXP machine.
2) Extract the entire contents of the One-Click recovery in to a folder and keep it handy.
3) Remove the battery from the phone. Hold both volume buttons and plug in the USB cable. If you are asked for a driver, look in the APX folder where you extracted the One-Click recovery archive.
4) Run OneClickRecoveryFlasher.exe and flash the stock recovery. Wait for the process to finish and close all windows and unplug the phone.
no problems with above steps. after that nothing works. when i put the battery back in and turn on thats when i get the flashing black screen, not back to the s/w screen.
5) Put the battery back into the phone and turn it on. You will be back at the S/W Upgrade screen. This is where you want to be! Now plug the USB cable back in to the phone. If everything is up to snuff you should have no driver problems at this point.
6) Extract KDZ_FW_UPD_EN.7z in to a folder. Inside is a msxml.msi. You need to run and install this first!
7) Run KDZ_FW_UPD.exe.. Leave the type set to CDMA and the phone mode set to DIAG. DO NOT CLICK ON "Read phone information"
8) Click the folder icon and load the V21E_00.kdz
9) Click launch software update (and pray!)
ok just for craps and giggles i tried booting into recovery and actually got the box with arrow and android! but it then reboots back to the lg screen and then flashing black screen
WOOT! finally able to get into CWM recovery!
is all that needs to be done now is install a stable rom?
double WOOT! back up and running. time to test the functionality of if though!
edit: can't find the sim and no service.
blackbeasst said:
double WOOT! back up and running. time to test the functionality of if though!
Click to expand...
Click to collapse
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
DupleX01 said:
Delighted to hear that. So, another confirmation of the "old" folks stating it's 99.9% un-brickable.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
and im a tard. sim was inserted bass akwards
blackbeasst said:
and im a tard. sim was inserted bass akwards
Click to expand...
Click to collapse
Congrats man.
Sent from my LG-P999
wifi seems to be flaky. keeps scanning and dropping work and home network
also it appears that the market wasn't on that version of the rom. is that a quick fix?
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
DupleX01 said:
Now you have the recovery and baseband sorted, start from scratch and do a full wipe(including system internal/external SD). Then flash a stable ROM Weapon/EB to make sure everything is good. Just my 2 cents
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
blackbeasst said:
im was lucky to get it up and running, so im still a flashing noob! but what is considered a stable rom for this phone?
i grabbed one from cyanmod earlier today. i think it was from around 3/13?
Click to expand...
Click to collapse
You were lucky, indeed!
A CM nightly can be stable too, however I would flash either Weapon or Eagles Blood for a couple of days to have a piece of mind that everything is working cool. The most important would be a proper full wipe (cache, dalvik, system under mounts and storage, battery stats and imho internal and external SD too) too get rid of the previous mess caused by the unsuccessful flash, etc.
Sent from my LG-P999 using xda premium
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.
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
i recently tried to install jellybean but the rom did not work on nexus s, i stupidly removed the only working rom from my 'sd' card and now my phone only boots into a black screen, i have tried to put a known working rom on my phone but every pc i try to connect my phone to says the device has malfunctioned and windows cannot install software. i have tried to use adb but that also cannot find my device. am i looking at getting another nexus with a broken screen and using my working screen to gain a decent phone back or am i missing a vital programme that will fix my utter cockup? thanks in advance
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Are you familiar with adb? Because unless you have the right drivers, you phone won't be recognized. Also, usually your computer won't notify you when you're connected and able to use adb, you have to start the interaction through cmd.exe. this being said, try adb again to move a rom or backup into your device.
Also, can you boot into fastboot? If so, is there a warning message or anything?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i am only famililar with adb to the point of rooting, i have tried to download the drivers but only can see .dll files in the driver folders no option to install said drivers. i can get into power and vol up if that is fastboot?? the problem been is i installed a rom which was meant for the nexus s and i didnt read all comments and later found out it does not work with the nexus. i now cannot access the sd storage to put a working rom onto it . when i open cmd and type adb shell it says device not found. brains ready to explode right now. any help on adb is greatly appriciated
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Fast boot is when you phone is off, you turn it on by pressing volume up+power at the same time. Let me know if there is a warning text in red at the top.
Do you know how to flash factory images? Because you may be able to do that to get a stock os on your phone. It would wipe everything, however. Flashing a factory image doesn't require you to open SD storage. I'd link you to the thread with the tutorial, but I'm on mobile :/ ill post it if i get a chance, i know its floating around in the nexus s android forums
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i do not know how to flash factory images, im am very much a noob to rooted phones and playing with software.
i can get into fastboot and at the bottom it says
usb control init
usb control init end
top says fastboot mode
product name herring
hw version rev 11
bootloader version i9020xxka3
baseband version i9020xxkd1
carier info eur
ser 33304eb5103500ec
lock state unlocked
my laptop does not recognise the phone so i dont know how to flash a factory image. this is the cmd sequence i get
adb shell
error device not found
tried mounting sd card and data but no joy
also tried mounting usb storage.
all i get is device has malfunctioned and will not run
tried downloading google usb drivers and samsung drivers all to no avail.
fingers crossed you can tell me something i dont know as i really cant afford to buy a new phone
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
Well it seems you sdcard isn't dead, which is good! When mine was, fastboot gave me an error.
Now IMO, you should be able to flash a stock recovery image. This will clear everything you have on ur phone, but it should get it back to working condition.
Ill post a tutorial on how to do it tomorrow, that's the soonest i can get on a computer. It is not that hard, and it helps when you're already somewhat familiar with adb. I used to be a noob too, now I'm slightly less noobish!
So as i said, i think i have a solution, ill post how tomorrow, when i have a PC (in on mobile right now).
Cheers, i hope i can fix your phone!
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
much appriciated and i hope you can too. thank you thank you thanks you
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
FirePoncho86 said:
Alright, so this is the guide to install a factory image: http://forum.xda-developers.com/showthread.php?t=1572307
What a factory image will do, is restore your phone completely to a new like state. That being said, you will lose anything you have on the phone (picture, music, etc..). I don't know of any other way to help, so if you're willing to lose everything, but get your phone working, continue reading.
-First, you have to determine what model on Nexus S you have. If you're on AT&T or Rogers, you have an I9020A, and you have to download the "sojua" factory image. If you're on T-mobile, or have the version with an S-LCD display (as opposed to the normal AMOLED), you have to flash the "soju" factory image. If you're not sure what version you have, let me know what carrier you're with.
-Second, download the Factory image corresponding to your phone from the link I posted, as for version, that's up to you, but I recommend 4.1.2 (JB).
-Third, Make sure you have all the right drivers, and the android-sdk installed. You should already have this, since you've use adb before.
-Fourth, follow steps 1,2,3 and 4A in the link I posted above.
Follow these instruction, and if you do not understand them before doing the procedure, just ask a question here! good luck!
Click to expand...
Click to collapse
still adb cannot find device.......... any links for known drivers for nexus s on win 7 64 bit?
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
You might need to reinstall the android SDK and drivers, there should be a link in the link i sent you to show how to do that.. If adb still doesn't recognise, your main board might be fried
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
reinsalled sdk tools, still phone not recognised by laptop. gonna try get a cheaper android and flog this one on ebay as someone else might know how to repair it. thank you for your time and help but it appears its all in vain......... damn stupid phone!
[deleted]
Rodya234 said:
the phone is probably fine if you can get into fast boot.
Click to expand...
Click to collapse
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
FirePoncho86 said:
What I'm saying! You can get it to boot, but just not into anything..
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
i wish someone could just see this, pdanet asks me to connect my phone to finnish installing the drivers, problem is the phone is NOT RECOGNISED i know exactly what you are all saying to do but my phone will not connect at all. more than happy to post it to one of you guys on here to fix but like i said ive tried everything and have pulled nearly all my hair out in the process
Samsung repair? I know what you're talking about, it happened to me, I was completely bricked, all I could so was send it to Samsung repair..
Sent from my Nexus S using xda app-developers app
Damn, if only you could get it recognized you'd probably be able to flash custom recovery through fastboot and I guess you'd be able to install from sd without data loss.
Sent from my Nexus S
Hey guys!
Was trying to solve the restart loop problem by installing a MIUI rom, but I am now stuck on this screen that says..
Stuck on AP Fastboot Flash Mode (S) (Boot Failure)
Battery OK
OK to Program
Transfer Mode:
USB Connected
Invalid CG OTV(CG: webtop): Invalid SP Data
Invalid CG Version (CG: webtop)
Invalid CG OTV (CG: webtop)
Any thoughts or help would be highly appreciated
Did you find the proper fxz for your base firmware and flash it?
Need more info about where you are coming from, what you did to get this problem, and what you have tried..
Sent from my MB865 using xda app-developers app
I am not sure what fxz is...but from what I know, it was on 2.3.6 and next update was failing and it was restarting..so I rooted the phone, installed the bootstrap...tried installing miui from there.. it restarted and now I am on that screen...
Have not tried anything else after that... I was looking around and it seems, I should flash something from fastboot mode? I am currenty downloading the ics fastboot files... planing to use RSD lite to install it...
Is that right approach?
Thanks for your help through...much appreciated.
EDIT: Its an AT&T Atrix 2 if that helps..
So, you were on 2.3.6? The 4.0.4 update failed?
If so, then you should probably be using the 2.3.6 fxz/sbf/fastboot/firmware files - flash those to go back to stock GB, then ota update to ICS the normal way (unless returning to GB is important to you - if so, find ICS leak #1 and install that instead of the ota update after restoring stock 2.3.6).
And yea, you need to be on ICS base to install miui (unless there's a GB version I didn't know about).
Sent from my MB865 using xda app-developers app
Edit: you seen this thread? http://forum.xda-developers.com/showthread.php?p=32113181
Links to the att-us 2.3.6 and 4.0.4 fastboot files are there.. Just read carefully and ask if you're not sure.
It's important to know if you were on 2.3.6 or 4.0.4.. and if you just tried to install a new ROM (system only) through custom recovery, or if you flashed something else through fastboot.
I was surely on 2.3.6, but it was not stable and was rebooting quite often ...it was also trying to download the next update, each time the phone was on...but it would just restart before the download could ever finish...
I rooted the phone after that, installed bootstrap.apk to get into clockwork recovery, then tried installing the MIUI which was based on 4.xx something .... but that failed and I got stuck in that screen....
So, basically, I should download AT&T 2.3.6
http://sbf.droid-developers.org/edison/InlineFlashing_edison_5.5.175.25_cfc_p3_APBP.xml.zip
use fastboot and follow these steps?
Fastboot erase system
Fastboot erase userdata
Fastboot update romfilename.zip
Fastboot reboot
OR
Try to use RSD lite instead?
One more problem though...I tried using the fastboot erase system command...and it tells me Battery low...
I have the phone on charger now, but the Fastboot screen comes up again and I am not sure if it will charge this way?
Any thoughts?
Thanks in advance.
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
alteredlikeness said:
You need to charge somehow (wall charger, macgyver method, another battery, friend's phone, at&t store, etc).. It doesn't charge in fastboot mode.
Then try RSD lite..
Otherwise, you would need to use moto-fastboot commands. See the files in the zip package here for examples (you can look at the .bat files for the proper commands): http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
jackdowsan said:
Thanks for that, I was able to do all that and now the phone is on 2.3.6 ..but the original problem is still there...the phone keep on restarting.. any ideas what the issue might be?
Click to expand...
Click to collapse
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
alteredlikeness said:
So it just reboots at random? Or it boots to Fastboot mode everytime?
If it's random reboots, you might have a hardware issue in your phone.. And you could ask AT&T for a replacement (they will most likely just give you a new Atrix HD since our A2 has been EOL'd).
If it boots straight to fastboot everytime, then there's something else.. not sure what, but I have seen others post of that issue.
Click to expand...
Click to collapse
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
jackdowsan said:
It reboots every 3-4 mins or so... Also noticed, it says under settings, that radio if Off and there is no IMEI number...also I cannot seem to turn off the Airplane mode..
Does that indicate something?
Click to expand...
Click to collapse
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
alteredlikeness said:
Hmm.. Yea.. What the heck did you do to it? Did you erase your cid? Do you have a backup of it? If not, sorry to say, but you may be out of luck...
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
jackdowsan said:
I was only doing a OTA update and I ended up in this mess of reboots, then I tried installing the 4.something MIUI, then fastboot files of 2.3.6...and now in this mess
I dont have any backup files or anything...if there any way I can go to stock maybe? or maybe if I can somehow manage to go to ICS, this might be fixed? No ideas :crying:
Click to expand...
Click to collapse
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
alteredlikeness said:
You did go back to stock 2.3.6 (the fxz should have flashed all stock images/files)... but if your cid is gone (not positive though that that is your problem), there's no getting it back (it is specific to each device).
You could try forcing the update to 4.0.4 by following this: http://forum.xda-developers.com/showthread.php?t=1779968 - but not sure it will install the update if it can't recognize your phone. You are sure it is an AT&T phone, right?
Unless some other members here have some ideas, not sure what else to try... except calling AT&T for a replacement if you bought it under contract. Just tell them that an over-the-air update failed and the phone keeps rebooting..
So, I wonder, did the OTA update start installing, then fail (a while after installation started)? Maybe that messed things up.. Usually, if it fails right away at the beginning of installation during the system checks, then it should be no issue.. But if it was interrupted later during the install, then that can cause major issues.
Click to expand...
Click to collapse
tried updating to 4.0.4 but it fails ...I have attached the screenshot.. what can this be?