Develop Bugs

Bricked - Can I save my phone??

Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers

Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App

You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.

I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.

I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.

celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.

That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers

celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.

Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.

No worries. Glad you got it sorted.

I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?

[Q] Use computer to turn phone on?

So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.

If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.

Can someone guide me in the direction I need so I can do this adb reboot?

chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.

I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.

I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.

I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.

If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk

[Q] Kindle 2nd gen issue

Hello all.
This is my first post and my first experience with android devices so please go gentle.
I recently purchased for £20 a kindle fire 2nd gen otter.
The reason it was so cheap was that it is stuck in a bootloop.
The friend I bought it from intended to bring it back to life and install CM to the device but never got round to it. So I took it on as my little project.
I have been scrolling through pages and pages of google and this site for research but have hit a brick wall.
I purchased a factory or fastboot cable knowing I may well need it. I also have the original cable.
When trying to boot the device I get the usual kindle and fire logo orange as of it's booting then every 10 seconds or so the screen will go black and back to the kindle fire bootloop.
I have tried to use the normal cable to link to my desktop on windows 7. When doing this the device will not show up in device manager at all.
When I plug it via a fastboot cable it boots into fastboot with a green flashing light on screen and is recognised as an otter prod 04 on device manager.
I have installed the latest sdk. Also fastboot.
I have changed the windows environment variables under path on the PC and can successfully run fastboot in a command window. I can also issue adb commands through also a dos command window so I know both are working correctly on my PC.
I have typed in fastboot devices
I have also typed in adb devices.
When I issue either or these commands my device will not be found through the command window. It just returns a blank.
I know this is due to drivers not working correctly so have opened device manager. Update driver , have tried the android sdk path for drivers have also tried my adb drivers. I have also downloaded the latest Google USB driver and none will install. I have a programme running that allows any unsigned driver to be installed on win 7 so I know it's not that.
All I have returned is cannot install drivers for otter prod. 04
The only thing it will accept is choosing from a list of devices, Then android. And installs as adb device or adb composite device, this is obviously useless as I can't boot device into normal mode to be able to use it as adb or issue commands to it.
I have tried everything. I know this kindle is save able I just don't know how. My end result is make it bootable, root device and install CM
I have trawled through loads of pages of info and tried tried and tried for answers but nothing works. Can anybody shed some light on the issue for me.
Many thanks in advance

Just thought id add, I have also tried all timed variations of holding down the power button
I have also let device run flat and recharge. Have also tried a different PC and USB port.

Hello Vincent,
ADB stands for Android Device Bridge (Just wanted to point that out since you are new to Android).
The ADB Composite Device driver lets your computer and your Kindle Fire device communicate with each other. This includes ADB as well as fastboot.
Install the ADB Composite Device driver in Device Manager and then go to the command line window and type fastboot -i 0x1949 devices and it should now show up in fastboot.
Now flash the stock bootloader, recovery, and system img files to your device. After that, you should see it boot successfully.
Hope this helped, and don't be afraid to ask me more questions about your device!
phiftyopz
Sent from my iPhone using Tapatalk

Why can't I get Windows to recognize a G4 in Fastboot mode?

I'm trying to unlock the bootloader on my daughter's G4, and I have run into a heavy snag. I get "code 10" (driver can not start) when it's in fastboot mode, but I'm fully able to connect with adb when the phone's up and running. This is not my first rodeo, and I'm sure the USB cable works (original cable), I have enabled USB Debugging (or ADB wouldn't work in the first place) and I think I have done everything else that should be done. But the damn thing won't work on any of my computers, under Windows 7 or 10. Driving me nuts! Also when it's booted up I see it as an LG Mobile ADB interface, but when it's on Fastboot it insists that it is an MTP device, even if I have set it as a PTP device when it's booted up. Can anybody please tell me what I have to do to get this to work? Another thing is that if I run "adb reboot-bootloader" (or even the wrong syntax (at least I think the dash should be there) "adb reboot bootloader", which LG's page says), it will not boot into fastboot/bootloader, it reboots into Android. So I have to get into the setup by holding in vol + and plugging in the USB cable. But I don't know if this is related.
Edit: Oh, btw, I have tried to find the latest drivers, so far I'm on 4.0.0.0. They are dated May 2015.

Unable to get xA2 in fastboot mode

Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks

jaw2floor said:
Hi there,
strugggling to get the xa2 into fastboot mode so I can flash a new boot.img and root. I've enabled OEM unlocking and installed the USB drivers. the command 'adb reboot fastboot' doesn't work, just reboots the phone. adb over usb works fine. The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED. I use 'fastboot devices' to see it if it connected. I've tried this on 2 PCs now to no avail
I'm thinking maybe the fastboot drivers are wrong?
Does anyone have any other suggestions or help?
Thanks
Click to expand...
Click to collapse
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:

faby GT said:
Hi
Install "5 seconds adb drivers"
Connect the turned off phone to PC via USB just pressing volume down button (no power) and keep pressing it until you see the LED turning green or blue.
Here u have! :highfive:
Click to expand...
Click to collapse
Hi thanks for getting back to me,
I assume you meant the '15 second installer', which I just did just install successfully. I am still unable to see the device with 'fastboot devices' command.
Other info: I have factory reset the phone, made sure oem unlock is checked, tried the same process on another computer. I can get adb mode to work fine, but the command 'adb reboot fastboot' just reboots the phone as usual

jaw2floor said:
The official method to get into fastboot 'plug in USB whilst holding vol up/down' also doesnt allow me to get itno fastboot mode, phone just stays blank with a notification LED.
Click to expand...
Click to collapse
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.

schmatzler said:
That is the correct behaviour.
Blue LED = Fastboot mode
Green LED = Flash mode (for reflashing stock firmware with XperiFirm in case EVERYTHING is broken)
Install these drivers:
https://adb.clockworkmod.com/
When in Fastboot mode, go to device manager, there is an Android device in there (may also be called MTP device).
In the device manager, install a new driver for that and use the ADB driver from C:\Program Files (x86)\ClockworkMod\Universal ADB Driver
Windows will tell you that it's the wrong driver. Install it anyway and Fastboot will recognize your XA2 now.
Click to expand...
Click to collapse
If it won't work, after that just go to devices and printers and delete Xperia XA2. It will work.
Else, after installing 15 seconds, inside device manager, update the driver of your phone (or mtp device), select local, then Android device, then fastboot. Disconnect the phone and reconnect as before (volume down)

Fastboot is VOL. UP (on this device)! (Not vol. down)
So basically turn off the device, hold Vol. UP and simply connect to USB, hold Vol. UP until LED is steady blue and you are set.
Note: VOLUME UP activates fastboot and VOLUME DOWN enables flashmode and/or recovery mode

Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off

Corias said:
Similar trouble here.
1. VOL UP + plug in USB: Blue led blinks once, then phone shows it's charging (turned off)
2. adb reboot bootloader: Phone just turns off
Click to expand...
Click to collapse
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you

BoernMe said:
I had the same issue with my XA2.
The solution (at least for me) was: different USB cable and different USB-port. As it turns out, my cable was somehow worn out (though data transfer and charging was working quite well). Going into fastboot, the blue led lit very short time and then the phone restarted. Furthermore on my PC it somehow only worked on the one USB port and not the other (both USB 3.0).
--> Maybe trying the most obvious might help also some of you
Click to expand...
Click to collapse
Did solve this by connecting to different PC. No cable/port/hub change did help. Looks like there was some trouble with drivers (though the same PC fastboots Z3 Tablet Compact perfectly).

Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?

that_random_guy said:
Same
I'm also having the same issue with my Xperia XA2 Ultra. (boy that's a mouthful)
Phone model is H3223.
Host OS is Windows 10 Pro v. 2004.
Using latest Android SDK tools (i.e. ADB and Fastboot platform tools): platform-tools_r30.0.5-windows. Got it directly from Android site.
I think I had a previous driver for Android already installed or somehow Windows got it. ADB worked, Fastboot didn't. Read online about someone on this forum getting it to work by using XZ2 driver from Sony as they evidently don't have a published driver for this device. The person who posted this solution had reported problems with this driver recently. I tried it anyway.... ADB commands work and my phone shows up when listing devices. Reboot into fastboot mode and the only thing my phone does is show a blue light indicator... no splash screen or logo. To me this means it's starting fastboot but my driver isn't working with it to recognize it as any commands for fastboot return nothing or fail. It doesn't show up under fastboot devices command.
Does anyone have a clue as to what to do?
Click to expand...
Click to collapse
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.

I had the same problems with my device XA2 H3113 and Win10.
My solution: Try it with Ubuntu. Just grab an 8GB usbstick, install Ubuntu via usb-installer, boot ubuntu and open a terminal
sudo apt update
sudo apt install adb fastboot

LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
Hey can you please provide me a link to the drivers? as I've been trying so many drivers and they don't work.

LolRoll said:
I have the exact same problem, have not managed to find a solution trying with 3(!) different laptops and 2 different cables. No idea what could go wrong. I checked the device and it says that unlocking is okay. Really frustrating.
Edit: I actually found a way! Once you manage to enter the fastboot mode (light is permanently blue) go to the device manager in windows, click on the unknown android device, and install custom drivers (either by selecting from the list or by picking the universal adb driers from a local folder). These custom drivers should be adb drivers. Once they are installed, fastboot should work.
Click to expand...
Click to collapse
works for me