Discussion in 'Android Devices' started by KellyDraves, Dec 8, 2014.
do you think it is having trouble reconnecting to the pc after the adb reboot-bootloader?
Maby u have a bad data cord
I'm starting to think/hope that might be it too. will grab another and give it a try.
Try a different USB port on pc
If that doesn't work, don't forget about Kelly Drave's deal with ??04
i used a brand new cable in a differnt port and got stuck at same place. i dont know why the phone reboots but doesn't reconnect. very frustrating. i will try to do what Kelly did but I just might switch to metropcs since they have free tethering now and some inexpensive plans
If u decide to get new phone get a zte warp4g its on boost Mobile great Dev and Roms I'm on it now
Next time you can pull just the apk from a nandroid from Nandroid Mgr
Some cables are "charge only" wires..
I for got about that thanks that could be the problem
Hey, I sort of skimmed through the last 3 pages on here. Are you still having issues McBad?
can i assume if i can copy stuff from the phone to pc via the cable then it is not charge only?
yeah. I'm stuck. after I do adb reboot the pc no longer sees the phone. I entered the adb devices command and it produce a list of devices which seems to show my phone A00003t...etc . then when i doo the adb reboot-bootloader I noticed something...
the computer makes a noise similar to the video of the phone disconnecting but the reconnecting noise is not the same. instead of the single"dadu" i get a "dududududu" and adb device no longer sees the phone. if i try fastboot devices command it doesnt return anything and if i try the fastboot boot recovery.img is goes to waiting for device...
I would think so
Correct. Sort of.. Some devices won't get picked up by PC if USB debugging is on.
What's the solution to that?
Just uncheck USB debugging (on device), if it was on. My HP Notebook was like that. And when unchecked, immediately got the Phone + SD card display window. Hope it's What'cha needed..
Another thing.. You may have to add dependencies/pkgs like udev tools, Fastboot & ADB stuff.. or something. Not 100% sure about ur system, specifically tho.
one of the usb devices connected to the computer has malfunctioned and computer does not recognize it
that is the error i get after adb reboot with debugging off.
it also says "device driver software was not successfully installed"
holy smokes i think it is working... got as far as "adb sideload awe.zip" now waiting for that to finish...i think. been over 5 min.
hmm. now we're looking at 45 min and it still says "starting adb sideload feature" . if it doesnt happen and I end up canceling it, what should I do?
i had those udev tools. but not on the pc that is making progress
I'm sure there's more, but.. I'm uncertain about anything to do with Windows
Linux? I go thru Software mgr and add anything that may be potentially helpful
ok. i got it to work with the L awe rom. i now have a rooted phone with no text messaging app. and when i try to log in to my google account and get an app there is a two step notification which sends a code to my phone via text messaging..lol. i can figure that out though
thanks for everybody's help. i have no idea why it worked on one pc but not the other but I think it had something to do with the device driver software incorrectly installed. the second pc i used prompted me to let it look for the driver. it found it and then we moved past the adb reboot hump. I'm not sure what I will do now with this rooted phone but I am grateful to you all for getting it successfully rooted. hopefully documenting my ineptitude might help others in the future. though maybe not since this phone is kind of old.
if anyone has any tips on stuff i should do since it's rooted in this L Awe rom i am all ears.
Have it sent to email & Log on with a PC to verify.
There may be a USB port incompatibility issue, like previous to USB 2.0 or something..??
I dont know. the pc it failed on is from last year while the one it worked on is from 2011. both windows 7.