Database Info

[Q] Tried to Install MIUI, Now Stuck

Welp I am one of the stupid ones and installed MIUI on my Infuse, and like everyone else, I'm stuck on the boot screen. I looked at the post on the same topic and tried to do it but couldn't get it to work probably becuase the computer says that its an Unknown device instead of a Samsung device.
So my question is what do I do now that my computer doesn't recongize the phone as a device anymore?
Thanks to all that can give help.

http://forum.xda-developers.com/showthread.php?t=1116251
And lesson learned - never install a ROM from another phone.

Yeah I know that now. Foolish mistake I know I shouldn't have made.
But, I have tried using that but when I connect the phone to the computer it shows to be an unknown device and Odin doesn't pick it up at all. My problem is, is that the computer doesn't recognize it as an Android Device anymore. Is downloading the drivers from Samsung going to help?

I'll have to leave that to someone else - I use Heimdall on a Linux box, I've never flashed from Windows.

Oh, ok. Well thanks for your help .

I fixed my problem. What I had to do was get another computer that doesn't have the Samsung Drivers or Kies installed and then install them. Once that was done Odin found the device and I was able to restore it.
So there's a tip for anyone who can't get their device to be recognized by the computer or Odin itself.

Or just uninstall/delete those drivers?

Entropy512 said:
I'll have to leave that to someone else - I use Heimdall on a Linux box, I've never flashed from Windows.
Click to expand...
Click to collapse
i have started to do this to since i got the infuse. ill tell you i dont miss driver issues one bit! linux/bsd/mac/whatever rock as long as you have supported hardware and that is becoming less and less of a problem these days.

re: Now Stuck
You need to try and pull the battery out and put it back see if you can get the phone into "download mode". If you cannot get it into download mode by doing that or using the up/down volume and power key combo then I would suggest that you purchase a "jig" on ebay. (they cost under $10 bucks shipped).
Here is the ebay link for the jig:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
With a jig all you would need to do is to remove battery, plug the little jig into the usb port of phone and replace the battery, then wait 5 seconds or so and the phone will be in download mode allowing you to use Odin3 and flash back to "stock rom" to start with..
Best if you did that using the "Ultimate Unbrick" stock froyo rom after that
you can install infuse 1.5 custom rom or Bionix or the defused custom rom or any other rom.
Here is the link for the Ultimate Unbrick:
http://forum.xda-developers.com/showthread.php?t=1116251
Good luck.

nstong said:
Or just uninstall/delete those drivers?
Click to expand...
Click to collapse
I tried that but it didn't work on my computer, but that's just my computer that could work for someone else. If that doesn't work though, you can get another computer and install the drivers on them and that should work.

SamsTechAnswers said:
I tried that but it didn't work on my computer, but that's just my computer that could work for someone else. If that doesn't work though, you can get another computer and install the drivers on them and that should work.
Click to expand...
Click to collapse
Where are you trying to uninstall the drivers from? I have windows 7 and went to device manager or whatever and took it off there. Then reinstalled kies, worked perfect after.
Sent from my SAMSUNG-SGH-I997 using XDA App

Entropy512 said:
http://forum.xda-developers.com/showthread.php?t=1116251
And lesson learned - never install a ROM from another phone.
Click to expand...
Click to collapse
and.... do not touch if it works properly

I guess this is a good sign. Our phone is gaining popularity because new people are buying it and trying dumb things with it

Xoom bricked seen as APX in devices need drivers

Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?

Have you downloaded drivers from motodev?
Prior to the bricking, could you connect to your computer?

It will connect but it just shows up as APX in the devices and says its missing drivers. I went to moto and downloaded USB drivers but still does the same thing. The xoom does nothing when plugged in.

Windows 7 or XP?
Sent from my MB860 using xda premium

Windows 7. I did manage to get some drivers to install. Don't know if their the rite ones though. I clicked on let me choose such drivers, found some in SDK for htc,Samsung,and Motorola. Chose Motorola and it had several adb drivers clicked next and they installed. So now it just shows it as APX in the devices but no longer has the missing drive issue. Still no sign of life when trying adb or fastboot.

What mode is it in when you are attempting to connect it to your computer?
Sent from my MB860 using xda premium

It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.

ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?

Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?

ericman77 said:
Bricked Xoom built a program cable but fails to install drivers when connected. I tried going to devices and troubleshooting searched for drivers but none were found.
Any idea of what i can try next?
Click to expand...
Click to collapse
ericman77 said:
It's just a black screen. Won't turn on at all even when pressing volume+power. All it does is the white light comes on when charging. Can't get recovery mode or fastboot.
Click to expand...
Click to collapse
darchiuk said:
I have the same problem.. doing my head in trying to fix it. I have tryed everything i can think off. Anyone out there know how to fix it in apx mode using a factory cable ?
Click to expand...
Click to collapse
qoole33 said:
Did you ever find a solution to this issue?
I currently have a black-screen bricked Xoom. I have tried all the 'soft-unbrick' methods, I can _NEVER_ get anything to appear on screen. The only signs of life are with a 'factory cable'
With this 'factory cable' I am able to see 'APX' in my Device Manager. I can make it 'reboot' by doing the volume up + power which makes the device disappear and reappear. No other key combinations have any effect.
I am able to install either the Nvidia NVFlash drivers. However NVFlash doesn't work. Possibly due to a lack of SBK (Secure Boot Key).
I am also able to install the "Universal Naked Driver" which makes the device show up as an "Asus Transformer APX" However neither fastboot or adb seem to see the device.
Does anyone have any suggestions how I can unbrick my Xoom?
Click to expand...
Click to collapse
Dear all,
I got the same thing.
I installed the driver from nvflash drivers. And I ran several commands to try, it showed no bootloader was specified. I guess maybe I damaged my bootloader. Does any of you unbricked your xoom?
Here is a link to my post, which showed my tries.
http://forum.xda-developers.com/showthread.php?t=1838002
Anyone could help us? Thanks a lot.

Wow, i've been on that Wagon for a long time. http://forum.xda-developers.com/showthread.php?t=1838002 Now I just gave up cause I don't think anyone has gone past installing the drives after it detecting as APX.

Thanks for your kindly reply.
So, you mean there is no hope.
Actually, I sent it to another MOTO local service center again. After one week, they told me they tried to restore the software in two steps, but only the first could be done, and then went back to brick again. And they thought there might be some damage on “the kit” of motherboard, and if I want to repair, the whole motherboard must be replaced totally.
If you still have the bricked XOOM, would you please try to draw the BCT and config.cfg from your device?
Again, I did another search. Although there is no available bootloader.bin, BCT and config.cfg for XOOM, I guess there might be possible to use SAMSUNG P7510's files, because the hardwares are almost same, and it's heard that P7510 could use XOOM's ROM.
Sent from my ZTE U970 using xda app-developers app

[Q] Need help getting my T959V connected for flashing/rooting.

Problem: Cannot get my Samsung T959V to connect to the computer in order to flash/root. Always gives the same "USB Device Not Recognized" error when I plug it in to the computer.
My Progress: Before you guys throw this questions out, let me tell you what I have tried so far. I have been trying to get this damn thing connected to the computer for about 3 weeks now. I have sat down on my computer going through the xda forum in detail trying to find an answer. I know the process of flashing and the xda contributors have some great guides to help us along the way, a big thanks to all ur hard work, but no matter what, I cannot get the phone in download mode or get it connected to the computer.
* I have read the Download Mode post and tried all 5 ways without luck.
* Have read all things related to Keis Mini and how it sucks when it comes to the T959V and other ppl have had the same problem.
* Have tried connecting in Keis mode, usb debugging mode but still the same error.
If someone can help me get my phone connected to the computer, I am sure I can take of the rest since everything is available on the SGS4G Bible, thanks for that also.
Is there anything I have missed or not tried yet? Please help. Thanks in advance for anyone who reads this post as it is my first. Usually I don't have to post since all the documentation is always up-to-date and available but this problem is killing me
Additional Information: Bought the phone from a cell-phone store I use to work at. Has Android 2.3.6 on it. Have done the factory reset and tried to get it to connect, no luck. Not sure if it has been flashed before, pretty sure it hasnt but the flashed download mode method didnt work also. Have android-sdk installed and have tried pointing the .inf file to the google usb-drivers in the sdk, no luck. Download both 32-bit and 64-bit drivers for this phone from multiple locations, still no luck trying to connect. Have also tried multiple computers and multiple v9 cables, no luck.

Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.

hechoen said:
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
Click to expand...
Click to collapse
Yup tried both 32-bit and 64-bit drivers on multiple computers. Tried the download mode method u said also. Trust me have tried everything I have read about and know, but no luck.

But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.

hechoen said:
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
Click to expand...
Click to collapse
Yup it charges fine. Both when I plug it into the wall and the computer. What's a jig? Don't think I have tried that yet. If something can let me know for sure its a hardware problem, then I will stop obsessing over this, hahaha. Thanks for ur help btw.

A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707

hechoen said:
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
Click to expand...
Click to collapse
Awesome bro. I will see if I have time to make the jig, if not i will just order it.
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?

Seems like a driver error have u tried one of the heimdall one clicks http://forum.xda-developers.com/showthread.php?t=1358498
They will put u back to stock with a modified rooted kernel .
If anything try and manually point to the drivers in device manager. Or download android sdk and use the google drivers ?

rangergiya said:
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Click to expand...
Click to collapse
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.

hechoen said:
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
Click to expand...
Click to collapse
As requested,
Build number: GINGERBREAD.VUVKJ6
Baseband version: T959VUVKJ6

Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.

hechoen said:
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
Click to expand...
Click to collapse
Will do. Thanks for ur help.
I downloaded the terminal emulator app and tried doing 'reboot download' but says 'operation not permitted,' any way to get around that? Or any other non-button or non-adb way to get into download mode? Other than the jig? Or is it possible to get su privileges on an unrooted device for the 'reboot' command to work in the terminal emulator app?

It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.

hechoen said:
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
Click to expand...
Click to collapse
Im trying it now but for SOC to work, i have to have the proper drivers to get my phone connected. Will see whether the drivers that come with SOC work for my phone.

No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.

Have you tried using this DRIVER SWEEPER to remove the drivers?

eollie said:
Have you tried using this DRIVER SWEEPER to remove the drivers?
Click to expand...
Click to collapse
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.

rangergiya said:
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
Click to expand...
Click to collapse
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root

eollie said:
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
Click to expand...
Click to collapse
Thanks for that link. I will try it out and give an update here.

rangergiya said:
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Click to expand...
Click to collapse
Just to make sure you had usb debugging and allow non market apss both CHECKED right?

no usb data. need to root -tf101

Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?

So im screwed right?

Zone3 said:
Long time listener. First time caller.
I have an issue. My tf101 lost the ability to transfer data about week ago. Meaning, its not detectable by computers or any usb device
The tablet was rooted but i returned to stock in an effort to fix the problem and lost root.
I have tried:
3 cables
4 PC's
1 linux box
The tablet charges fine and even trickle charges from usb ports
I narrowed down the problem to a partially corrupt bootloader. Or simply a bad flash(team rouges rec and revolution rom)
I think i may be able to fix the problem by flashing ClockWork recovery, but i need to get root access. Any ideas or am i just screwed?
Click to expand...
Click to collapse
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.

enterflux said:
No, you're not "screwed" You could always just download an over-wifi file transfer app. I'm not sure what the best ones are on the Play Store, but I'd do you research if you're gonna drop a couple bucks on one. I haven't bothered since my Skyrocket is Samsung and I already get Kies Air.
I would suggest after flashing ClockWork recovery trying out some other ROMs and kernels and seeing if that fixes your problem. I would also highly suggest Team Win Recovery Project. It's been my favorite recovery so far, not to mention the touch screen interface is fantastic.
Click to expand...
Click to collapse
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.

Did you try loading the official USB drivers?

Zone3 said:
Thanks for answering
Ive been using a combination of google drive and file expert for file transfer, but i cant flash any recovery or any rom or adbwireless because i dont have root anymore.
Click to expand...
Click to collapse
So you lost your recovery manager too?

enterflux said:
So you lost your recovery manager too?
Click to expand...
Click to collapse
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well

Zone3 said:
Yep, and that appears to be my biggest hurdle in solving this issue.
Seems more than a few are having this issue as well
Click to expand...
Click to collapse
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.

enterflux said:
I assume you can still get into APX mode? If so, I would try running this. It's what I initially used to root my TF101, and it doesn't require you to use your installed recovery. Basically it roots and installs CWM recovery from a script run from your computer. Let me know what happens.
Click to expand...
Click to collapse
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.

Zone3 said:
Yes, the tab can go into apx mode, but the computer wouldnt know if it was in apx. Pc doesn't know the tab exists when plugged in.
Click to expand...
Click to collapse
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.

enterflux said:
When plugged in to your computer and in APX mode, check Device Manager and see if there's any unrecognized devices.
Click to expand...
Click to collapse
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...

Zone3 said:
Ive been through that. Its not a simple driver issue. Windows doesnt even acknowledge it as an "unrecognized usb device"
Linux does even list it with the lsusb command.
Same for mac.
There is no data being transfered. It doesnt even attempt usb handshaking...
Click to expand...
Click to collapse
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....

enterflux said:
Well, I'm assuming that this is no longer on stock firmware and/or too old to be still under warrantee. The only thing I can think of, unless someone else here can give you an answer, is that it may be a hardware problem and you'd have to send it in to ASUS to get it fixed.....
Click to expand...
Click to collapse
Did the OP found a solution to that? I have the exact same issue .

haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?

sad_janus said:
haha,, months after.....
But i am in the same situation...
a lost root and the USB dosnt work, exactly like the autor of this post...
any ideas?
Click to expand...
Click to collapse
You need USB to root. I had the same issue and a new USB cable fixed it straight away.

frederuco said:
You need USB to root. I had the same issue and a new USB cable fixed it straight away.
Click to expand...
Click to collapse
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,

sad_janus said:
hmmm, I'll try when I can get a new cable = (
but from what I've read some have tester with multiple cables and even so the USB dont work,,
Click to expand...
Click to collapse
If you have another PC you can try hat is the only other suggestion I have.

frederuco said:
If you have another PC you can try hat is the only other suggestion I have.
Click to expand...
Click to collapse
thanks
yeah, of curse i tried
but no luck. i try everything,
APX dosnt work, USB it is invisible for windows, in any way

[Q] Atrix 2 bricked !! Fastboot not working !! No CWM !! HHHEEELLLPPP

I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!

3mperium said:
I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!
Click to expand...
Click to collapse
See here
Sent from my MB865 using xda premium

3mperium said:
I have tried MILLIONS of method that I can found on Google.
The problem : -
1) My fastboot can't communication with the PC. (Tried all the uninstall - install - uninstall - blah blah blah)
2) Recovery current is 3e stock.
3) Stuck in the custom rom loading screen.
How to :-
1) How to flash back stock using 3e?
2) RSDLite can't work, what else can I do?
I'm despo now and my phone is bricked for a week.
Thanks for anyone who can help or solve it.
Please HELP me ~!!!!
Click to expand...
Click to collapse
This is very easy if you have an att phone. If not you will NEED to get the correct FXZ for you phone and download what I am about to link here, then put the correct FXZ for YOUR phone in the same location as in the download, and run the batch file, while your phone is in fastboot, as simple as that. If you do this RSDlite is not needed.
Link to the post with the scripts:
http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Again as it is, that is ONLY for AT&T phone, and you MUST get the proper FXZ for your phone, if it is not an AT&T phone, and put the FXZ in the same directory as the rest of the files with the script.

jimbridgman said:
This is very easy if you have an att phone. If not you will NEED to get the correct FXZ for you phone and download what I am about to link here, then put the correct FXZ for YOUR phone in the same location as in the download, and run the batch file, while your phone is in fastboot, as simple as that. If you do this RSDlite is not needed.
Link to the post with the scripts:
http://forum.xda-developers.com/showpost.php?p=36834775&postcount=108
Again as it is, that is ONLY for AT&T phone, and you MUST get the proper FXZ for your phone, if it is not an AT&T phone, and put the FXZ in the same directory as the rest of the files with the script.
Click to expand...
Click to collapse
My phone is Asia Retail. Not AT&T.
Thanks for helping.

Please help... My pc cant detect fastboot.
Ths script and the EXTRACTED ota file all put in same folder?
THanksssss

3mperium said:
Please help... My pc cant detect fastboot.
Ths script and the EXTRACTED ota file all put in same folder?
THanksssss
Click to expand...
Click to collapse
1. Make sure your phone is fully charged (you can't fxz below 30%)
2. Install the correct driver and boot your phone to AP Fastboot
3. You don't have to extract the fxz file. just put them to C:/ as a whole
I recommend you read the instruction again

Obviously you have to get fastboot working. that should just be a drive issue, but you can try a new cable/ usb port/ computer. What rom did you have? you should be able to get into its recovery and flash again.

lkrasner said:
Obviously you have to get fastboot working. that should just be a drive issue, but you can try a new cable/ usb port/ computer. What rom did you have? you should be able to get into its recovery and flash again.
Click to expand...
Click to collapse
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.

3mperium said:
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.
Click to expand...
Click to collapse
Hmmmm.. what does the phone say when it is in fastboot mode and plugged in? Does it say "connect a usb cable" or whatever it is, or "USB connected- ready to program" (or whatever, you get the idea)

3mperium said:
I'm on Paranoid Rom. The recovery is wiped for no reason and my current recovery is 3e ( with the vol up + vol down to make it shown). I tried 3 different cables, 1 lappy and 1 pc. It just can't recognize my fastboot.
Click to expand...
Click to collapse
I was stuck in this same situation just last week, fastboot not being recognized and all. What operating systems do you have? I tried 4 (windows xp 32 and 64bit, windows 7 32bit and windows 8 64bit), and only xp would work a few times. So maybe you can try a friend's computer with xp or anything else. Which drivers are you using? because it worked for me with Motohelper, but not the latest drivers. Either way, keep trying different usb ports especially with the Motorola cable. Let me know if anything works, good luck! :thumbup:
Sent from the Ace's MB865 using xda app-developers app

lkrasner said:
Hmmmm.. what does the phone say when it is in fastboot mode and plugged in? Does it say "connect a usb cable" or whatever it is, or "USB connected- ready to program" (or whatever, you get the idea)
Click to expand...
Click to collapse
Ya... Connect USB, data cable... I tried all my lappy + pc usb port... Non of them are working...

Aceofzeroz said:
I was stuck in this same situation just last week, fastboot not being recognized and all. What operating systems do you have? I tried 4 (windows xp 32 and 64bit, windows 7 32bit and windows 8 64bit), and only xp would work a few times. So maybe you can try a friend's computer with xp or anything else. Which drivers are you using? because it worked for me with Motohelper, but not the latest drivers. Either way, keep trying different usb ports especially with the Motorola cable. Let me know if anything works, good luck! :thumbup:
Sent from the Ace's MB865 using xda app-developers app
Click to expand...
Click to collapse
I read about other threads that said motohelper would help... I tried end user driver, motohelper, end user driver+motohelper, older version driver etccccccccc.... Only thing is hard for me to look after is the motorola ori cable... Motorola is just so imba... :good:

3mperium said:
I read about other threads that said motohelper would help... I tried end user driver, motohelper, end user driver+motohelper, older version driver etccccccccc.... Only thing is hard for me to look after is the motorola ori cable... Motorola is just so imba... :good:
Click to expand...
Click to collapse
I see, that may be why it's so hard to get fastboot to work. :/ The A2 seems to only like working with the Motorola oem cable for many people, especially with AP fastboot. Well try what you can to keep the battery charged, and try what you can.
Sent from the Ace's MB865 using xda app-developers app

I would try using Linux. if you don't want to install it, you should just be able to use a live cd of ubuntu or something. it aught to work right off the bat, no drivers needed. you will ahve to use manual fastboot commands though, no fxz (so you will need to install moto-fastboot)