Database Info

i little problem i encountered :/

I just got a new mytouch because i lost my old one :/
last time i did the rooting through the gold card method, now i tried the one click method and it went horribly wrong, i belive i got root, i tried to boot up with a new image but i just stays stuck on the mytouch logo, i can go into fastboot, but when i try to go through fastboot through my computer, the computer doesn't recognize my phone(it doesnt show the serial number) should i install the drives all over again? right now i have i connected to my computer through usb, and it says "fastboot usb".
i have looked though the forums but i didnt find a specific answer, so please if im going to get bombed, all im asking is for a little help.
thanks in advance

ok so..
ok so i fixed my drivers and it detects my phone, but now when i am trying to fastboot it it doesnt let me

you are sure you installed the drivers correctly? can you make it to the recovery screen?

if u try adb devices in cmd using adb from sdk does it give you something like HT9623465? cos that should be fine, also if you're using the sdk try uninstall the driver and then copy the 'usb driver' folder contents from the sdk into the 'tools' folder so everythings in the same place and then refer to that directory for driver installation (windows detects it as android 1.0 device when in fastboot and the drivers are different from normal mode). forgive me if im wrong

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!

I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk

Did you try a fastboot command like fastboot devices?

Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.

Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >

[Completed] fastboot will not recognise device (HTC One M7)

I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit

pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
Sorry to hear about your trouble. We cannot provide technical support nor can other members reply to your posts here on XDA Assist but fortunately there is an XDA area dedicated to the HTC One (M7) at http://forum.xda-developers.com/htc-one which would be a good starting place. I suggest you post your question with all relevant details in the friendly Q&A forum there at http://forum.xda-developers.com/htc-one/help where the experts familiar with your device will be best able to guide you.
Good luck!
EDIT: Member has now posted in the suggested area. Thread closed.

Recovery mode seems to clobber the USB driver on Windows 10

Similar questions to this have been asked before but got no replies so, in desparation, am asking again.
Bought my phone second hand. On starting, it shows the Vodafone logo so assume it's branded.
About Phone -> Software Information shows:
Android Version: 2.3.5​HTC Sense version: 3.0​Software number: 2.10.161.5​
HBOOT shows:
*** UNLOCKED ***​SAGA PUT SHIP S-ON RH​HBOOT-2.00.0002​
Now for the problem:
I'm trying to set S-OFF and root the phone but my PC, running Windows 10, is unable to communicate with the phone when it's in Recovery mode.
The entry for My HTC under Android USB Devices in Device Manager disappears once I start the phone in Recovery mode and connect it to my PC via a USB cable.
At this point Device manager on my PC shows under USB Controllers an entry for an unknown USB Device (Device failed enumeration) and the Hardware Ids show as USB\UNKNOWN.
I'd really appreciate someone familiar with this area throwing some light on what could be going on here and perhaps giving me some pointers on how to resolve this.

there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE

Layer_DE said:
there is one quick fix http://forum.xda-developers.com/htc-one-s/general/guide-fix-fastboot-windows-8-1-t2858337 (for me it worked with the old win 10)
if it doesnt work: the fastest way is to seek a friend with windows 7 and s-off the bootloader
if its s-off you dont need the "fastboot" mode
here is an tutorial http://forum.xda-developers.com/htc-desire-s/general/installing-cm13-untouched-htc-desire-s-t3456585 if you have luck it works with your win 10 too
IMPORTANT: DO NOT UPDATE TO ANDROID 4.0.4 IT KILLS THE POSSIBILITY TO S-OFF YOUR PHONE
Click to expand...
Click to collapse
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.

bacoms said:
Thanks for replying but, following the links you gave they all ended with a brick wall. Using VirtualBox I tried using Window 7 and even Windows XP. All attemprt failed miserably.
In all cases Device Manager showed the MyHTC driver installed under Androis USB Devices and working normally. Running command 'adb devices', when the phone was running normally, worked fine but USB connection is lost every time when booting into HBOOT, making fastboot etc impossible.
I've reached the point where I can't waste any more time on this having wasted far too much already. I don't like giving up but this has got me.
Click to expand...
Click to collapse
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices

Layer_DE said:
the problem is simple on a windows hosted vm usb passthrought doesnt work with unknown devices
Click to expand...
Click to collapse
If I can drum up any enthusiasm to continue, I'll try and borrow a PC running Windows 7 and try again.