Going back to Stock Sense - HTC Droid DNA

Hello,
I am new to these forums, therefore I cannot post into a Development thread.
I rooted and flashed a ROM on my phone (Genome 2.0 to be specific.)
It was a fine ROM, but I actually prefer Sense 4.1+ for right now and wish to go back to stock due to support reasons for my company as well. I saw a thread where you can use RUU. However, I cannot get the program to detect my phone (the dreaded error 170.) I also am in the process of using the ZIP file method where you grab it from the temp while RUU is open (getting it on my SD card has been another story.)
However, in the event I cannot get this to work, can someone who has got their DNA back to stock from root/ROM please give me some troubleshooting for the drivers? HTC Sync isn't detecting my DNA when there are no drivers. I wish to know how to remove ALL drivers for this phone from the device manager so it is as if I never had this device connected to my PC. I believe if I had these removed, it may help a lot of the issues I am having.

After hours (about 5 hours total) of checking into this, I figured out that it was trying to install the windows USB drivers for whatever reason. I just manually uninstalled whatever drivers it was trying to install (in this case, it showed up as Android 1.0 in the device manager.) I reinstalled it and manually browsed to the HTC folder in x86 Program Files after downloading and installing HTC Sync. It installed these drivers, showed up as MyHTC Phone, and I profited from my bloated factory Sense 4.1+ phone
In case anyone else was wondering, here are the steps:
http://forum.xda-developers.com/showthread.php?t=2017525
Let me amend his steps:
1. When you boot back into your bootloader, go into Fastboot.
2. Make sure you uninstall any PDANet drivers or all drivers you had on your phone while rooted/ROM'd up.
3. Download HTC Sync Manager and install.
4. Disconnect your phone from USB and reconnect.
5. Install drivers manually from HTC folder in Program files x86.
6. Run RUU.
Going to attempt to unlock the bootloader again, shouldn't have any issues since I took care of that initially before I rooted this phone. I hope that I have solved a few people's issues who might have been like me scourging the internet hopelessly for help.

Related

Can't downgrade Orange HTC Hero

Hi there,
I'm trying to follow the guide at roothtchero.co.uk, but I can't even downgrade from 2.73.61.66.
When I try and run the official 2.73.61.5 ROM installed from the HTC website I get a 171 error when once the phone fastboots(?) my phone screen goes white with green text showing the phone name and date, and then orange highlighted white text saying RRU USB. Then there's nothing, and the waiting for bootloader message on the ROM software just times out.
Can anyone give me some advice how to fix this?
I've also created a GoldCard, (I used the 2GB micro SD that came with the phone), and have rebooted the phone, but I've noticed no change.
Any help would be really appreciated.
Cheers,
Blaise.
go into device manager and make sure your Hero phone, shows up as MY HTC. if not, make sure you've got the right drivers installed for your phone. Once you've done that, you can downgrade to .65 Orange ROM without needing the Goldcard Method
install the latest htc sync too
Thanks chaps,
So I've been checking out the device manager in the background when I try and perform the update, here's what I noticed.
I have Developer mode turned on, with my phone.
When I plug my USB into my computer under ADB Interface I have My HTC and HTC Sync is green.
When I run the RUU software HTC Sync disconnects, and I have to wait a good while for it to show green before I can run the update successfully.
When the phone reboots into bootloader mode I have a warning symbol under ADB Interface with a driver named Bootloader
Also when I start from scratch, uninstall, reboot, then reinstall everything, my Hero installs the HTC Dream composite ADB Interface in device manager as default. :S I have to manually choose My HTC as my driver.
It seems to be when the bootloader runs I get the following warning over the bootloader driver in device manager.
"Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
You need to restart your computer before the changes you made to this device will take effect."
I have already uninstalled everything, so how does this happen?
Another thing I've noticed is that I have USB Debugging enabled, should this be on or off when I perform a RUU updated?
Start > type Change device installation settings
Select No, then never.
try this http://forum.xda-developers.com/showthread.php?t=647353
This did the trick! Thanks for posting the guide.
To recap, the problem I was havin gis that all sorts of weird drivers were being associated with my Hero, for starters when I had installed the latest HTC Sync, my device was being picked up as a HTC Dream, so I changed this to My HTC.
Secondly when I ran the RUU and my phone rebooted into bootloader mode, a bootloader driver was being installed but having a conflict with another driver, it also asked me to restart my PC, I fixed this by updating the driver to My HTC again, and voila, easy update.
Thanks for all the help!
Cheers,
Blaise.

[Q] computer wont recognize my phone after recovery update

hey all,
ive been a member for a while, but have never posted. i usually am always reading and trying to keep up with updates, and how to's... i am currently running liberated Aria FROO8 (2.6.32.17-cyanogen-Liberty), and have been for some time. i am nervous usually when it comes to rom updates, so i dont update constantly (if anyone has a great rom i should update to, please dont hesitate to shout it out). the problem was when i decided to update to Clockworkmod recovery 3.2 from here:
http://forum.xda-developers.com/show....php?t=1003723
now, my computer does not recognize my phone, and will only charge the phone. i have tried to reinstall unrevoked, but when i go through the steps, my device manager or registers it as My Htc, and i cannot update using the drivers i downloaded. it seems that its the computer not accepting the phone and not the phone restricting anything. please, please, can someone help, i need to be able to access my phone on my computer, and i have read all 33 pages of the forum thread i linked above. what do i need to do? is there a way to uninstall the recovery 3.2? if i were to upgrade to a new ROM, would the computer still not recognize the computer. i realize as well, after the fact, that i installed the recovery meant for the Desire.
how can i get my computer to recognize this Aria without having to reboot everything and try to start from scratch, does anyone know if i need to reinstall CWM and which one would work for me. when i plugged my phone after install, its states that device driver not installed correctly. then when i run through the instructions loacated here:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
and here:
http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install
and neither load a correct driver onto my computer, my computer does not register it as Other Device/Android 1.0, it registers it as My Htc.
any help would be greatly appreciated.
thanks
sullylove
i would say use the 2.1 (NOT 2.2) RUU update to return to stock and re-run unrevoked
1st link 404s(page not found)
is there also a way to delete the CWM 3.2 i installed on the computer, i cant seem to find it anywhere, where would it be. thanks for the quick reply, there was no link though to the 2.1.
i dont understand how a newer version of CWM was installed without s-off
how did you flash it?
Try turning your phone completely off, then using volume down + power to turn it on, and then select FASTBOOT from the HBOOT menu. Leave your phone on this screen.
Then run the 2.1 RUU. You can download it from here:
http://www.megaupload.com/?d=9D9NGT6J
You are going to lose your ROM settings when you do this because this reverts your phone to stock. Then you can run Unrevoked again.
drumist said:
Try turning your phone completely off, then using volume down + power to turn it on, and then select FASTBOOT from the HBOOT menu. Leave your phone on this screen.
Then run the 2.1 RUU. You can download it from here:
http://www.megaupload.com/?d=9D9NGT6J
You are going to lose your ROM settings when you do this because this reverts your phone to stock. Then you can run Unrevoked again.
Click to expand...
Click to collapse
thanks a million! i noticed that when i fastbooted, that the computer registered a usb plug, but that was the only time it ever did, thats why i figured the problem was on the computer side, when i tried to install the 3.2 CWM for the Desire.
i followed the instructions on the page to update the CWM to 3.2. Like a moron, i skipped turning the S-Off. so when i installed it through fastboot, like it said, the phone rebooted, but the computer could not identify the phone, and so that left me with a phone that couldnt load into the computer. i also noticed, when i tried to run Clockwork Recovery through Ubuntu, i couldnt find that either. does anyone have the link to loading through Ubuntu?
two questions...does have a ROM that you recommend, the one i had seemed to work great for me, even though its a 2.2. but i cant seem to find a link for it. does anyone know where i can find it, or one better? i loved what i was using but now not sure which to choose, since soo many have been released since i originally downloaded it. thanks again for everyones help.
sullylove
the problem was with my phone and not my computer...i should have known. when i loaded 3.2 i figured that it had to be the computer since i loaded 3.2 through the computer. stupid me. normally im pretty cautious about just downloading, but i noticed that my clockworkmod had never updated from 2.5.0.7 and i saw that there were alot of them. but ill tell ya i loved the ROM I was using. just cant find it.
liberated Aria FROO8 (2.6.32.17-cyanogen-Liberty)
if anyone has a link to it, or one better, or that i should be using please let me know.
much thanks!
sullylove
For future reference, just leave your recovery version alone. Versions 3.0 and higher are actually not compatible with FR008, which doesn't sound like something you want, does it?
The ROM you've been using (FR008) is available here: http://forum.xda-developers.com/showthread.php?t=819715
There is also another somewhat newer version of Sense Froyo that is based off the the official AT&T 2.2.2 release (whereas FR008 is based on the global 2.2.0 release). The differences are minor but you can try it out and see what you think: http://forum.xda-developers.com/showthread.php?t=970272 (Skip all the way down to the bottom of the first post for the most recent version.)
no that does not...thanks for everything! i am clearly a novice, and should be more careful. and thanks for letting me know of the Sense 2.2.2. i think i might give that a shot. that seems to be a much smarter risk than just downloading an update i cant use, only to satisfy my hunger to update something. thanks again. to everyone
sullylove
so i went ahead and tried to run the factory fastboot in Hboot but the computer never recognized that anything was plugged into the usb port. My phone only charges now when plugged into the computer, even in Hboot. Hboot recognizes that the usb is plugged in, but my computer does not recognize anything, so i was unable to reset it to factory Rom, nor use the Ubuntu unrevoked, and when i tried to install the US att 2.2.2 ROM, it installed, but still the computer did not recognize any phone. am i screwed?
How do i turn off the Eng S-On in Hboot? and is there a way to find where the CWM 3.2 installed into to get it off my computer, because it seems the computer wont let the phone be recognized? When Hboot loads i receive the screen first picture that i loaded, then it goes to the HBoot menu screen, then when i plug in the usb, it changes to Hboot Usb, then i choose Fastboot which is the next screen, the final screens are what my computer registers the phone, and what drivers are installed said item. what can i do???????
sullylove
Try installing HTC Sync (leave it installed but don't have it open) before you run the RUU.
so i reinstalled HTC Sync, and the computer did pick up the phone long enough to run the aria stock rom, but now when the phone rebooted and finished installing the rom, the computer no longer registered anything plugged in. so i wasnt able to run unrekovered or now anything else, as it seems the computer still hasnt found the phone, and i can no longer do a hboot recovery to a backed up rom. it definitely seems to be the computer. but now im kind of in limbo, cant reload a back up, and computer still cant pick up the usb phone. reinstalling the computer system to factory, to clear anything that the 3.2 CWM may have installed, and i guess also wipe the sd on the phone as well. is there anything that a CWM installs onto a sd card? computer?
Next you should uninstall HTC Sync (but do not uninstall the HTC drivers), and also install the HBOOT drivers by following these directions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
After that, Unrevoked should work.
i did all of that step by step, and when i plugged the usb in during Hboot installation it never showed up as other device\android 1.0 it showed up as Android\My HTC. after installing the specific driver as per instructions, it did change to Android bootloader interface, but problem is unrevoked, nor the computer are registering any phone being plugged in. the program wont run unless it has a phone connected to computer. is there something to the sd checking missing files screen i posted? and apparently recovery can no longer be obtained.
I don't know what you could have done as far as installing drivers on your computer. Perhaps you should try starting from scratch on another computer if you have access to one.
There is also an Ubuntu LiveCD method that might work for you. I assume it's mentioned somewhere in the Unrevoked thread.
thanks, i had tried the ubuntu live cd unrevoked install option, but since the computer never registers a phone plugged into the usb port, it wont install. damn...i dont have access to another computer. could it be something on the sd drive? plus, should the hboot Eng S-On be off?
sullylove
I don't understand. How were you able to run the RUU if your phone won't show up on your computer?
As far as S-OFF, if you want to go that route you would have to use the recently released AlphaRevX beta. Unrevoked does NOT give you S-OFF.
Nothing on the SD card should matter, but feel free to wipe it if you want.
Its been a while but don't you need USB debugging enabled to run unrevoked? Maybe check that?
Sent from my cm7 Aria.
i dont know, when i reinstalled HTC Sync (when the computer installed the My HTC driver) is when the computer picked up the phone. but i havent been able to duplicate that time. USB Debugging was on and still is. i am going to try to see if a computer at work today can pick up the phone. if it does than that at least means its my computer thats not picking up my phone. if the computer does not pick up my phone, than i know its my phone and/or sd card. i honestly dont know why its not picking it up since it was able to do it for the aria rom reset. i hope i can get this rectified.
so i am at work, and so i plugged my phone into the usb at the computer at work, and it found the phone, installed drivers, or at least tried to because HTC Sync wasnt installed on it, nor My HTC Drivers. but i guess that at least means its my computer and not the phone or sd card. at least i have a starting point.
sullylove

revolutionary method stuck at 'zerging root'

i wanna get s-off and root on my wife's phone using the revolutionary method so she doesn't lose any data, problem is that I can't get the HTCDriver3.0.0.007 on my windows 7 machine to open up, i get a windows popup that asks is it ok to run this file, i hit 'ok', then that's it, setup never starts. so when i try to run revolutionary, i get stuck at the 'zerging root' step. apparently it won't get past that step until after i get that htcdriver to install.
i've made sure the phone was in usb debugging, updated windows, tried to download that same exe from other sites, and still nothin.
anybody have an idea of what to do
There's no point bothering to run Revolutionary until you get the driver installed....
Are you logged in with admin privileges on Windows ? Is a User Access Control window popping up that you don't see and aren't responding to ?
You could use HTC sync to get the drivers that's what u did...
My name is Revos I'm a recovering flashaholic running Liquid Gingerbread 3.0
the only window i get is the one asking if i'm sure i wanna run the file, i hit yes and nothin else happens. i'm the admin, i even ran hit 'run as admin' and it still nothing happened. i've tried other exe files that i have on my computer to see if they would run and they ran. it's just this one
i thought htc sync had to be disabled in order to use revo though
Sync does have to be disabled, but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Stratejaket said:
...but I think what Revos means is install the sync and connect your phone. It should at that point automatically install the htc driver for your specific device. Then remove the HTC Sync and leave the driver.
Click to expand...
Click to collapse
Don't the instructions at revolutionary.io say exactly that ?
how could i uninstall sync and not uninstall the driver with it
The installer from HTC includes multiple pieces that show up individually in Add/Remove Programs. Easiest thing is to try it...
Sent from my ADR6400L using XDA App
i FINALLY got it! i reinstalled htc sync, it was over 100 mb. then deleted it. after that, i plugged the phone in and mounted it as a disk drive, so it installed whatever drivers it needed. then mounted it as htc sync; windows installed more drivers. then i set it to charge only, enabled usb debugging and ran revolution again, and it finally worked. she's rooted!! thanks!!!
Same thing was happening to me when I was tryin to root my mom's Thunderbolt. Couldn't get past the "Zerging Root..."
So contrary to what all the guides say, I installed HTC Sync, it installed all it's pre-requisites during the install, UPDATED HTC Sync to latest version, it updated all the pre-reqs again, mounted phone to computer as a disk drive, waited for drivers to install, mounted phone to HTC Sync, waited for all drivers to install, confirmed that HTC Sync was communicating the phone, set phone as Charge Only, waited for drivers to install, unistalled HTC Sync, ran Revolutionary, waited a minute, it FINALLY got past Zerging Root!
Hope this helps anyone else who has been tearing their hair out over this issue...
Alternate solution for rooting with latest ota...if you have locked bootloader
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING THIS PROBLEM
Thunderbolt Tool
I was able to S-OFF and ROOT my Thunderbolt by using the Thunderbolt Tool located at this link... rootzwiki.com/topic/27310-all-in-one-the-htc-thunderbolt-tool
This app does it all for you, just follow the instructions.

[Q] samsung fascinate driver install problems!!! hELP!!!

i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!

[Q] Samsung Charge usb issue, please help!

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.

Categories

Resources