i have a sky elite 5.0LW with lollipop that wont boot past the splash screen. i have the boot.img, but i cant get the phone recognized thru windows or mac. when i connect to windows, it goes thru the process of installing drivers for it, so its recognized. but adb turns up nothing. ive read just about everything ive come across to get this to work. ive tried 6/7 cables, installed programs, installed drivers, used USBDEVIEW to delete drivers and then re-installing them. used different computers-windows and mac. im not real familiar with using mac for this. ive never had so much trouble with ADB. the phone wont go into bootloader thru the phone recovery options, it just re-starts the phone. im at a loss. im hoping someone with more experience with this issue can help me out. this has me frustrated and determined me at the same time!
Related
I've just recently rooted my CDMA Hero using the unrevoked method and I had a lot of trouble figuring it out. I some how got the adb drivers to install on my phone (I was so annoyed by the time they installed I wasn't even paying attention when they did) but now they have disappeared (I think because I downgraded the phone to get it out of a booting screen loop) and I can't get them to re install no matter what I do. Im running on windows 7 64 bit and even when the bubble pops up and says that new drivers are installing when I go to type in
Code:
adb devices
it tells me that no internal or external paths can be found. Any tips for installing these would be greatful. I want to still use adb in the future.
Yeah nevermind. I was charging my phone via computer and an installing drivers bubble just so happened to pop up after I had been tinkering with loading themes. Figured I'd go ahead and give a shot to see if it was the drivers I needed turns out it was.
No idea what really went down but I'm glad i got adb working properly lets hope it's more permanent
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
1stx2 said:
Is anybody else having problems with usb debugging mode not working? I have been trying to root with CASUAL all afternoon and I can NOT get usb debugging mode / adb mode to work. Any suggestions on what I could do to make it work?
Thanks guys/girls.
Click to expand...
Click to collapse
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
travisn000 said:
I'm having the same issue.. just bought it and this is driving me crazy! I'm i the process of removing drivers and crapware from verizon, and then figured I would try drivers direct from samsung.. I'll let you know if I have any luck.
Click to expand...
Click to collapse
It's absolutely crazy isn't it? Please let me know if you figure out the problem. I don't consider myself a noob about rooting/romming/etc but this is making me feel like i just started today!
EDIT:::: I finnally got my phone to connect to my moms laptop but it still wont connect to mine. I got CASUAL to recognize the phone but I'm kind of scared to do it now since my first phone connected perfect the first time and when I started having other problems and needed to send it back and usb debugging WOULD NOT work. I don't want to leave it stock but I don't want to go through what I went through with the first phone again
Ok, I finally got my phone rooted, unlocked using casual. I had to use my moms laptop ( hp, windows 7, 32 bit ) to unlock it, our desktop ( windows xp 32 bit ) to use odin and my laptop to transfer music, vidoes, etc..... Now i absolutely hate installing drivers and windows in general. You would think being 1 of the top-of-line smartphones, **** like this wouldn't be so difficult.
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
travisn000 said:
It seems this is a driver issue.. I still couldn't get it to work. I'm guessing that either the old GNex drivers or maybe a windows driver. I recall having a similar issue with another device and I had to go through device manager and remove certain drivers and install others.. That doesn't explain the failure I had with linux thought.. perhaps my adb is out of date??
After updating adb removing/installing various drivers in an old XP install was able to get the phone to be recognized by CASUAL, but casual would would reboot the phone to a "Downloading" recovery screen, and just hang.. CASUAL seemed to be waiting for this screen, but could'nt tell that it had it ???
Click to expand...
Click to collapse
Yep that's the same thing that happened on my windows xp based desktop, it would boot into download mode but it wouldn't recognize the phone. It's got to be a driver related issue though. I had similar issues with my gnex but that was nothing compared to this catastrophe.
Sent from my SCH-I605 using Tapatalk 2
I finally got mine done.. gave up on windows drivers and went back to linux.
I had to switch to a disto that used gksudo & dpkg in order for the CASUAL app to work properly (..my distro of choice is PCLinuxOS, but it doesn't use gksudo or dpkg).
http://pastebin.com/4NnjMHT4
Okay so I have finally come to a point where I am going to need some help On my journey to root this phone, which is my first time rooting a verizon phone, i have learned that verizon is a *****. This phone is the GN2 VRAM3 SCH-i605. I have already flashed the keis update for this back to 03/29/.2013. I basically followed the guide, and have just been effin around doing things a bit differently everytime because it usually fails right away. I have been using zadig from heimdall to replace drivers, I have a windows 8.1 computer with the full Android sdk installed, obv with adb and fastboot, and i also have a windows 7 pc with the sdk tools installed and zadig and all that stuff. I have been trying to use casual, and this bad boy has been fighting me the whole way, This is the furthest I have gotten and was wondering if anybody had any other suggestions for me to get this guy to run through successfully. Thank you very much in advance.
Ok, so like an idiot I accidentally wiped my entire device when going to flash a new ROM. The old OS is gone, the new image is gone and the backups are all gone. Annoying, but not a big deal, right? Wrong. My device is no longer being recognized by the computer, at all.
I have tried ADB, ADB sideload, mounting, new drivers, old drivers, the toolkit, rewiping the device, different USB ports, different USB cables, and different computers with different versions of windows.
At every turn, I am unable to move data from the computer to the device as the following error is returned: error: device not found.
I've been working on this for several hours, and I'm not new to problems in recovery or with ADB, but I'm at the end of my rope on this one. Any and all help is appreciated.
EDIT: I managed to finally get a ROM over on the device. I don't have time to post the solution tonight but will tomorrow.
Mind to share the solution as I have been in the same dumb situation