Develop Bugs

Need help with my EVO

Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?

xarttyx said:
Alright so last night i ran the DCupdater and saw the damagecontrol v3.1.2 update. So i downloaded it and tried running that. Thats when my evo started freaking out and the sd card kept getting disconnected. After all that nonsense it got installed. But then as my phone restarted it was in for the loop of watching the HTC EVO 4G logo. Thats when i tried going to one of my backups and that seemed to work. So then after that i when back to damagecontrol v3. But that messed everything up even more because now im stuck on v3 without sd card. When i try going into the bootloader it wont let me. When i hook up the phone to my pc via usb it wont let me see the sd card contents. I tried doing the:
fastboot oem enableqxdm 0
fastboot reboot
but that had no effect and the cmd wouldnt even recognize the command
what do i do?
Click to expand...
Click to collapse
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot

mongoose8p said:
before you enter those commands you have to hold power and volume down and go into fastboot on the phone - after that connect it to the computer
click start - run - CMD
After that
type cd "location of your android sdk tools folder" - OR cd "drag the folder of your tools folder into the prompt"
THAN
type the commands -
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
where do i find that folder... im sorry i dont really know much of this

i'm assuming you are using windows. it's the location of your \android-sdk-windows\tools\ folder from when you installed the android sdk in order to root in the first place. it is also the location of adb. if need be, do a search for adb.exe and it should point you directly to the location of everything you need.

It keeps saying "the system cannot find the path specified". I dont even know what to do. This sucks.

it might be under a different path, where did u install ur android sdk?

i don't really remember. i found it though searching for adb and i guess i have 2 folders of it... zipped and unzipped... but i tried putting both path names in there and that went nowhere

When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.

awesomeindeed said:
When you search for adb or your android sdk tools folder, go into that folder and hit Shift+right click and "open command window here" then use your commands.
Click to expand...
Click to collapse
that option does not pop up.. im running xp if that helps

im still having trouble figuring out what to do.

xarttyx said:
that option does not pop up.. im running xp if that helps
Click to expand...
Click to collapse
copy the path of the folder with adb.exe in it - start - run cmd - command "cd path of adb folder" - then follow the instructions above

[Q] sdk device not found

Well I want to command my htc desire from cmd but I am not beeing successful.
I type/get (phone in Fastboot mode):
c:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
c:\Program Files\Android\android-sdk\platform-tools>adb shell
error: device not found
This what I have in Windows "Device Manager" ADB Interface (Installed correctly did not have any "Yellow exlamation icon"):
"Android Bootloader Interface"
any ideas?

Yes, ignore that as mine too said the same. Here's my instructions that I recorded so that I can remember (old age) :-
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Click to expand...
Click to collapse
Note that mine is not located in the 'Program Files' directory so you will need to change that to suit. From there you should be able to run fastboot commands. The 'path' command I had to set due to ADB being in a different directory to Fastboot so running any fastboot commands failed as it was looking to use ADB which doesn't reside in the same directory.

If you are using fastboot, you want to type
Code:
fastboot devices
rather than adb devices. ADB is for use when the phone is normally booted rather than in bootloader/fastboot.

parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?

Try a different USB cable?

Or another usb port. And make sure you installed all necessary drivers correctly.
Sent from my HTC Desire using XDA App

Why should i try another cable if with this cable I transfer files, windows check all drivers etc... already tried in another pc -.-
what should i see on device manager for the htcdesire device when it is on fastboot?

maybe try using safe mode (if using windows) it could be a firewall or a program blocking the connection

but tell me what should I see on device manager when my htc is on fastboot

portelaux said:
parva, i tried that but nothing changed
C:\sdk\tools>fastboot reboot-bootloader
< waiting for device >
C:\sdk\tools>fastboot devices
and nothing... happens ... My device is there! (Android Bootloader Interface)
more ideas?
Click to expand...
Click to collapse
Are you sure that everything is in that directory? Only by default it installs to 'C:\Program Files\Android', I simply removed the 'Program Files' directory but you haven't even got an 'Android' directory now. Reinstall it and start again maybe, using defaults. You're directory structure may or may not be the issue here but we could be here until this time next year fixing something that is unrelated.
Reinstall the SDK and only remove the 'Progam Files' part of the directory then follow my instructions again.

portelaux said:
but tell me what should I see on device manager when my htc is on fastboot
Click to expand...
Click to collapse
If all is well, when you type "fastboot devices" in your terminal window , you should see something of this format, meaning your connection is good.
"fastboot H3567FYH5577"

Copy the content of Platform-tools to tools. And try ADB that way - if the drivers are correctly installed it should work.
And you must have the USB Debugging option enabled (settings> applications> developement).

Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all

portelaux said:
Well thanks you all anyway...
My sdk device control started working ^^ ... i dont know why but if already find devices etc
thanks you all
Click to expand...
Click to collapse
Please add "[SOLVED]" to topic's title, to help other users.

[Q] cmd fastboot access denied

I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.

mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
Try creating a new fastboot folders and updating your HTC drivers. If the need arise, I can share with you my fastboot files

mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\

convict_moody said:
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\
Click to expand...
Click to collapse
Hi convict_moody, I have tried all that you suggested and went as far as removing all traces of my HTC drivers and
fastboot folders from my computer and tried it all from scratch and still no luck.
I recently did a HTC update to 4.2.2 and the Hboot is 1.73 with S on just if that info is of help?

Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin

Mr Hofs said:
Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle

mrrflagg said:
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle
Click to expand...
Click to collapse
Sure you logged in as admin on the pc ?

I'm the only user of this computer, got me stumped.

Yeah but when it's not setup as admin you can have trouble

Just want to thank you all for your advice, I tried the process on a different PC and it worked perfectly. Was my laptop the whole time.
Again a big thanks to you all

adb reboot bootloader (Unlocking the Bootloader)

on the box my hpone came it it says H815, Made In Korea, I talked to LG they say it's registered in Hong Kong but it shows it's a LG-H815, No T or anything after the 8. So I have a H815. Not sure what the Hong Kong thing means...but I need to unlock the boot loader.
Following this: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
On the 'adb reboot bootloader' command it says in CMD, 'error: device 'null' not found'.
I've tried it many times. I can clearly see it as G4 in My Computer, I can go into it and see the folders on the internal memory.
http://i.imgur.com/fZ4t6Rj.png
http://imgur.com/5UBg6dB
I downloaded installer_r24.3.4-windows.exe from here: http://developer.android.com/sdk/index.html#Other
I installed the SDK Manger and installed the Google USB Drive and the Platform Tools, got the 3 files, did the cmd as you see in my image...
I never had to installed the G4 drivers or anything, it just installed it when I plugged it in and always worked.
So...?
Wish someone could help via Team Viewer..

Sounds like you need to install the drivers.... it is not so it just works for you to see the files... it is so that the computer will see the phone as an ADB and fastboot device
Install the drivers like it says to do, and test it by hooking the phone up to the computer and in a DOS box type "adb devices" without quotes, it should give you a device id.

Milimbar said:
Sounds like you need to install the drivers.... it is not so it just works for you to see the files... it is so that the computer will see the phone as an ADB and fastboot device
Install the drivers like it says to do, and test it by hooking the phone up to the computer and in a DOS box type "adb devices" without quotes, it should give you a device id.
Click to expand...
Click to collapse
tried that, got this:
C:\>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
So tried the other thing (adb reboot bootloader):
C:\Users\Owner\Desktop\tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
Just to make sure I got the right drivers, can you link me to the latest drivers for the H815?
I tried: http://www.lg.com/uk/support-mobile/lg-H815 - makes me install that support program first, but once it starts up it tells me to select my carrier, which mine isn't there and lists models, which mine isn't there.. So that didn't help. The daemon thing is new though...
EDIT: It works now and I get this... doesn't list it... someone link me good drivers or?
C:\Users\Owner\Desktop\tools>adb devices
List of devices attached
Click to expand...
Click to collapse
EDIT 2: Now it's back to the original null message only. I need some good drivers...

Broth3rz said:
C:\>adb devices
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Start your DOS box from the directory you installed ADB to. If you do not know where that is, just search for adb.exe on your computer.
When you find where it is installed, just go to that folder and shift+right click and select "open command window here"
Run your commands there and it should work.

Milimbar said:
Start your DOS box from the directory you installed ADB to. If you do not know where that is, just search for adb.exe on your computer.
When you find where it is installed, just go to that folder and shift+right click and select "open command window here"
Run your commands there and it should work.
Click to expand...
Click to collapse
Just shows 2 empty lines, I need some real drivers or something. I don't know where to get them.

Read the thread about unlocking your boot loader. Everything you have asked is in it. Your phone needs to be in the right mode, adb, fastboot, download.

Don't know what thread your talking about and I've installed the best drivers I could find. It's not seeing the phone.

I opened CMD and did"
adb kill-server
adb start-server
Plugged it in and did the adb devices and got this:
C:\Users\Owner>adb devices
List of devices attached
LGH81567593392 device
Guess I'll try the next step in unlocked when I wake up. Any reason it has all those numbers after H815?

On the 'adb reboot bootloader' command it says in CMD, 'error: device 'null' not found'.
Normally, when it says "null" not found, you haven't accepted the connection on your phone, you wont see it if the screen has blanked.
Try again and accept connection from computer on your phone.
Oh, and if you;'re having problems getting the adb.exe etc to work, try downloading minimal drivers here ( http://forum.xda-developers.com/showthread.php?t=2317790 )and install to desktop with shortcut as well. When you click the shortcut, it will create a dosbox and most commands will work from there.

Sounds like it is working. The numbers are your device id. Just proceed with your unlocking or rooting now and it should be fine.

What should be my next step in rooting after unlocked BL?
In the end I want to update my firmware and install stock Android, that is if it's just the OS, no installed apps or anything, apart form Camera, Play Store, etc.

Broth3rz said:
What should be my next step in rooting after unlocked BL?
In the end I want to update my firmware and install stock Android, that is if it's just the OS, no installed apps or anything, apart form Camera, Play Store, etc.
Click to expand...
Click to collapse
IF you have the H815 EU version, and were able to unlock the bootloader from the LG site....
http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
Finish up on that page what you have not already done......
Install TWRP (recovery) and Root.
After that, its up to you, there are a few RoMs out that are stock and or debloated, pick the one you like.
Remember to check that it is for the H815 not a carrier version.

How to get Verizon pixel xl back to stock so I can install TWRP.

Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.

It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL

Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.

Deleted

Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl

Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL

My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!

chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.

OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?

chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).

chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?

See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?

chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.

Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.

chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.

I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.

chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.

magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!

Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!

i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large