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] Can you unroot without using a PC?

I'm new and I hope I'm not posting this in the wrong place or re-posting an old question, but I have been searching on this and other sites for days and haven't been able to find anything pertaining to my question, so sorry in advance If I'm not posting this correctly.
I have a rooted epic touch with rogue boot loader installed and UnNamed rom installed. I really liked the way it was running until I had some kind of malfunction happened and now the battery charge light won't shut off and the battery drains within a couple hours of standby time. the phone is only a couple months old and would like to take it to the sprint store as I'm assuming this is an obvious hardware issue. My problem is that my pc doesn't recognize my phone anymore so I can't flash back to stock and get rid of root, voiding my warranty. I have tried uninstalling and reinstalling kies and stand alone drivers multiple times with no avail. I've tried with the battery and sd card removed and have also tried on multiple pc's (2 win7 and and xp machine). every time it says the drivers weren't installed successfully and to replace the device being connected.
My question: Is there a way to revert to stock off of the internal memory of the phone? I know there are zip roms you can flash from the boot loader but I was wondering if there was a way to flash a rom from zip and install the original boot loader as well as get rid of root? Any help I can get would be extremely appreciated and again I apologize if I am wasting anyone's time by asking in the wrong place or re-asking a question.

Ok so I downloaded the Calkin's_Stock_Rooted_EK02_ROM_v1.0 and got it on my sd card via dropbox. Flashed and now have a stock rom on it which I think is a step in the right direction.
The only thing is now I have clockwork boot loader and still rooted. and still not recognizing on pc. anyone know of an unrooted zip with original boot loader?

I couldn't get my PC to recognize either of my 2 E4GT's, each due to a different reason, both issues were resolved by going through each step in sfhub's debugging checklist:
sfhub said:
This post is for the FAQ section:
Why is the install stuck waiting for device to be connected?
Your phone isn't being recognized by your PC as an Android device.
When the drivers are installed and the phone is properly recognized, you should see the following in start->run->devmgmt.msc
Code:
Android Phone
SAMSUNG Android ADB Interface
Modem
SAMSUNG Mobile USB Modem
Until you get the SAMSUNG Android ADB Interface to show up, neither ADB nor this script will work.
Here is a debugging checklist:
1) dial ##UPST# (##8778#) in the dialer and verify AP (or ALL) is checked (if CP is checked, phone won't be recognized as an Android device)
2) restart the ADB server (choose Option G to stop the server, it'll get started automatically by the script)
3) verify USB Debugging is ENABLED
4) verify USB drivers are installed (Win7-64bit see below)
5) try a different usb cable
If you are in Win7-64bit try changing the default install location for the drivers:
If you see an error like this:
Try running the CMD prompt (or e4gtauto-sfx.exe) as Administrator. Right-click on the CMD icon (or e4gtauto-sfx.exe) and select "Run As", then select Administrator.
If that doesn't work, try disabling windows firewall.
Click to expand...
Click to collapse

I went down that list and everything seemed to be in order but still no recognition by pc. I kept uninstalling and reinstalling the drivers and switching usb ports and it finally installed the drivers successfully long enough for odin to recognize it and to flash back to stock. As soon as it was done the machine stopped recognizing it again. Lucky break I guess. So I can now return it to sprint and deal with the hardware issue.
I would still like to find a zip file like the tar that I flashed that installs stock recovery and non rooted ek02 rom and kernel from cwm, if that's even possible.
Thanks Godswrath, for helping me out.

You could use wifi explorer to get files on to sd card and mobile Odin to flash the tar file back to stock....
Sent from my SPH-D710 using xda premium

Lol....I am a noob.
They make a mobile Odin? That would have saved my like 4 hours....

ADB device offline - after upgrading TWRP and 4.2 ?

So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?

Nobody?

hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
hxdrummerxc said:
Nobody?
Click to expand...
Click to collapse
only thing i can think of right now, before suggesting omap flash or odin, would be try a different usb port, another computer, another OS!

try installing the latest CWM recovery and see if it helps.

hxdrummerxc said:
So I have had my Galaxy Nexus since the day it came out, I rooted it before I even activated it.
Like many, I have used all sorts of different ROMs over the year period.
I have never had any problems with adb or anything. I have pushed and pulled files and all of that numerous times.
Until yesterday, I finally upgraded my recovery from an really old (first touch based recovery) to the newest TWRP. It worked fine. I put my phone into fastboot mode, and was able to flash the new recovery through the command prompt (adb/fastboot) on my PC. Then I switched to a new 4.2 rom (Paranoid android 2.99)
So today, I wanted to try some editing on some system files, so I went to go pull some files off of the phone (using adb of course), but now it just tells me that my device is offline.
I tried
"adb kill-server"
"adb start-server"
"adb devices"
It lists my device number, but just says "offline"
I tried to update everything. (Samsung main Drivers - Google's USB SDK drivers - and the newest version of android-sdk)
Also made sure that my USB-debugging was set on my phone.
Even if I put my phone in fastboot mode, it doesn't recognize it anymore. Which is weird because just last night it worked perfectly fine when I upgraded my recovery. I am frustrated to no end...... Can anyone else tell me what I might be missing here?
Click to expand...
Click to collapse
Try going to settings and look for something related to Root Access and it would have three options:
1. Apps only
2. ADB only
3. Apps & ADB
Choose the 3rd.
You might have to hunt the exact location under Settings where this option will be available as I don't remember them exactly.
Hit Thanks, if this helps...

I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.

hxdrummerxc said:
I looked, but I don't see those settings anywhere.
I tried multiple USB port's. Switching from my USB 3.0 ports to my 2.0 ports. nothing. I can still access the phone storage. So I know it is still connecting to the PC. I could try to boot up linux, but I don't have any of the driver's and sdk tools on my linux drive, and from what I heard it was hard to get it all running in linux.
I guess I could try to change recoveries from TWRP to the newest CWMR,
but last time I turned my phone off, put it in fastboot mode, adb didn't recognize it. So im assuming it won't let me flash anything. Unless fastboot sees it but adb doesn't?
I mean my phone is working perfectly fine, running the new recovery and rom. But I have to be able to connect to adb. Not only for modding but in case of an emergency where I would need to flash.
Click to expand...
Click to collapse
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.

freezer2000 said:
I understand your situation... Since you were not able to locate the option suggested, a little Googling answered it's location, check for same and confirm:
Settings > developer options > root access > apps and adb
This should hopefully help resolve the issue.
Hit Thanks, if it helps.
Click to expand...
Click to collapse
hi. i try all this ways. i know that my usb debuging have problem, in development option i'll checked this, and it says enable. but infact it's not enable and still i got device offline error.
also i use z4root app and when i touch on root, it says that rooting need usb debuging enable (please enable it)!!
then move me to development setting to enable that, but this was checked and enable.
is any way that we make device online from my phone? for example using terminal emulator to turn on usb debuging or turn it off. this way is only my way! any one know some trying this?
i also use usb debugger app, but it move me in settings too! LOL
i need enable my device to root that.
thanks every one

I know this is an old topic, but if somebody else googles it, I had that offline issue, the solution was to upgrade adb : http://stackoverflow.com/questions/10680417/error-device-offline

You simply need to upgrade to the latest version of adb. Went thru this a few weeks ago.

Trying to restore after wipe, but ADB is not enabled

I unlocked, and rooted my nexus 7 using the Nexus Root Toolkit.
Everything was good until, after a few days, I tried turning on my device but got stuck on the "X" loading screen. After googling for a bit, I figured a factory reset would do the trick. I tried to factory reset the device in TWRP, but was confused by the two buttons and accidentally wiped everything (in adv wipe with everything checked).
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.

I did the same thing. This will help you get back to square one.
http://forum.xda-developers.com/showthread.php?t=2382618
Sent from my Nexus 7 using Tapatalk 2

poootythang said:
Now the next problem is that I don't have USB debugging enabled (I recall turning it off for some reason). When i run "adb devices", nothing comes up and so i can't push anything to the device (and everything is wiped). Is there a command i can run, or file i can edit while in TWRP recovery mode to enable it? It seems i can't do anything without it enabled.
Click to expand...
Click to collapse
Regarding how to most quickly get you back up and running, it is probably easier to just flash the stock images as mentioned above.
Regarding your adb issue, if you can boot into TWRP and are using a known good USB 2.0 port (sometimes 3.0 gives issues), then adb should already be running (ie what usb debugging enables is running)
You probably don't have drivers installed for adb running under recovery. The regular drivers don't work.
See this post:
http://forum.xda-developers.com/showthread.php?t=2391236

The ADB drivers from SDK is only for when in Bootloader and booted into ROM for needing USB Debugging. This is the driver you need in addition to what you have you've already installed to use ADB while in recovery otherwise you will see "Flo" under Unknown Devices in your computer Device Manager.

Thank you everyone. The new drivers and restore guide worked perfectly.

GPS lock and Lollipop problems

Hello wonderful helpful android wizards out there! I humbly seek your help.
I recently purchased an unlocked HTC M8 AT&T and had it unlocked so I could use my prepaid carrier (Simple Mobile). I have two issues I would like help with:
1) I cannot get a gps lock at all. I have made sure the device is in high accuracy mode and I have tried downloading and refreshing aGPS data via the GPS status app.
2) I am trying to upgrade to lollipop using the provided RUU file on the HTC website:
http://www.htc.com/us/support/htc-one-m8/news/
I am currently running 4.4.2. I was hoping that upgrading to the latest firmware might solve my GPS problem as a bonus, though I obviously want lollipop anyway to just generally be up to date. HTC sync manager works fine, but when I run the RUU file, it says the phone is not connected. I have tried the PB99IMH solution posted here that seemed to work for many people:
http://forum.xda-developers.com/show....php?t=1928439
The roadblock I have hit is that I cannot copy the zip file onto my Android. I keep getting the error "The device has either stopped responding or has been disconnected." I can copy other file to the phone just fine. I tried fiddling with the permissions of the file, but I honestly don't really know what I'm doing with those.
So those are my problems. I would greatly appreciate any assistance.

While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.

Tachi91 said:
While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.
Click to expand...
Click to collapse
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.

semantik said:
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.
Click to expand...
Click to collapse
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.

Tachi91 said:
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.
Click to expand...
Click to collapse
Ok, i finally got the update to work, but I am still having GPS issues. Any ideas?

I am also having GPS issues. Everything else on the device works fine, it just never finds any satellites. Any help or updates would be nice.

I'm having GPS problems as well. I'm on CM12.1. It used to work fine, but I've been playing with it trying to get LTE to work, and somewhere in there, my GPS stopped locking.