Related
UPDATE:
I'm thinking I could download rom manager and use it to install the stock rom... but given the trouble that I had with flashing roms before:
(My phone had a working version of Axiom 2.4 on it. I decided to try to flash a few new roms (gummy, liquid, codename android) and all had the same issue, they would boot, go to the upgrading android screen, finish that and go straight to the homescreen without the "welcome to android/activating" screens, then freeze after 10 seconds requiring a battery pull. Sorta led to this mess)
I'm not sure its a good idea.
Any thoughts? I really just need to get rid of the lock on the splash screen.
I'm considering just letting it sit till an ota comes out and either A: relocks the phone so I'll return it, or B: effs it so badly I can return it.
Drop box + 4G can be an annoying workaround for usb functionality.
Having some trouble with the GNex.
I was stuck in recovery, now I have it booting with minimal apps in my nand of a stock rooted rom. (Minimal apps as in I have none of the system apps I uninstalled nor any user installed apps. Luckily I do have the android market)
However my underlying issue with the USB remains.
I am unable to connect it to a computer and have it recognized, whether the phone is booted (trying to mtp or whatever so I can see the files) or in adb or fastboot. The same error 43 comes across on both of my computers. The phone DOES charge via usb.
I'd like to return it to VZW claiming a broken usb, but the phone is still unlocked, and it shows the unlocked icon with the google splash screen. Is there anyway I can relock the thing and return it, or alternatively does anyone have any ideas on getting the usb working? I've tried both the pdanet method of drivers and the ones from the samsung site to no avail.
Thanks in advance!
You could try reinstalling the USB drivers. I'd suggest downloading pdanet on your computer and run the wizard.
Edit: I should have read your last paragraph. Sorry :/
Sent from my Galaxy Nexus using xda premium
Found this on the GS2 forum.
http://forum.xda-developers.com/showthread.php?t=1203802
People had success cleaning their phones USB port with a toothbrush.
Sent from my Galaxy Nexus using xda premium
El Daddy said:
Found this on the GS2 forum.
http://forum.xda-developers.com/showthread.php?t=1203802
People had success cleaning their phones USB port with a toothbrush.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Didn't seem to work but thanks for the tip!
Okay, this might not be the place to get some divine intervention to start (or stop) happening, but I'm really starting to get a nervous breakdown and I desperately need some help. I'm going to tell you my story, because it's my last resort before throwing this phone in a fire and never buy anything Samsung related ever.
So the phone came out of the box and for some magic reason I got the bootloader unlocked and phone rooted. It all started with installing CWM I think. This stopped my phone from taking OTA updates. Of course I could have known, but for some reason I installed CWM. I don't know why! I regret it, I don't even want a different ROM installed, I thought it was necessary to root the phone. So when I got the OTA, at first I was like YEAH YEAH, but then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. It was 2 in the morning and I had to get up early to go to Dublin for two weeks. This was really not the time...
So after trying a few times of getting the OTA update message again and failing every time I got it, I started searching. Yes, CWM is installed so you can't OTA they all said. Nice, now I hate on the back laying androids AND CWM. Of course the one to hate is me, but I already hate myself so that's no use. Anyway I used the Galaxy Nexus Toolkit 5.6 to put back stock recovery. Now I had to wait a few weeks again before the update turned up again... By this time the phone started to be REALLY slow when scrolling through the home screen(s). It also is empty before the day is done, but I don't know if that's because of the phone being f'ed up or because I'm too demanding.
Anyway, back to the story. Finally the update came about a week ago, and again I was like YEAH YEAH! But then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. To make things more fun it did a reset of my Go Launcher, 7 screens of widgets and autistic arranged shortcuts gone... Of course I wanted to try again, so this morning the OTA came again and had the same result. By now I killed quite a few, so this has to end, but don't worry there is more torment ahead.
I can't figure out what is wrong now, so I thought, f~ this s~, this phone deserves a full undress and back to the womb operation. So installing all Galaxy Nexus Toolkit v6.0 stuff and drivers. Connect phone, start toolkit, choose 3 (GSM 4.0.2. build ICL53F), phone turns up in main menu, try to put back recovery, -waiting for device-...
It stopped... Or it didn't really stop, it just stood there saying, -waiting for device-... So again a few innocent people died. Tried a different choice, (relock bootloader, just to give the phone a good beating) -waiting for device-...
I raged, pulled my hair, again killed a few, silently cried in a corner and finally started typing this eulogy...
Please kind sirs and madams, help me get this phone back to stock 4.0.4, accepting OTA, bootloader unlocked and rooted, I'm really desperate...
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
How do you proceed?
First you need the SDK for you system
http://developer.android.com/sdk/index.html
After this you have to start the SDK manager and install "Android SDK Tools" and "Android SDK Plattform-tools" if you are using Windows you have to install USB drivers too. You could find this under the point "Extras".
After that you have to download the factory image to clean your device, once.
(Notice your SD-Card gets wiped)
https://developers.google.com/android/nexus/images
Look for right version, which fits to your device.
Now you have to bring your telefon into the bootloader by pressing all 3 buttons at the same time Volume+/Volume-/Power. After this you have to unlock your bootloader if you don't already done this.
Now plug in your phone into your computer an go into the unpacked folder from your factory image. There would be an file called flash-all. You have to run this file. Now your phone is flashed with stock rom, stock kernel newest baseband and stock recovery. Now you get ota updates from google. After this you should look for an howto root your phone in the developer section. You don't have to install clockworkmod recovery for rooting. But clockworkmod isn't change the ota. You get OTA with cwm.
Hope i understand your problem an you could understand my bad english. But i want to help. If some questions ask here into the thread.
regards
theSlack said:
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm out of the house a lot, leaving for Brussels in a couple of hours. I don't want the hassle anymore. I just want to be able to leave the house to go to another hotel and update OTA. I don't have time for all this flashing stuff.
Sent from my Galaxy Nexus using XDA
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
If you want to head back to stock ROM, then one of the ways to do it would be to install Android SDK & then follow the instructions from Google developers site.
Else you can try using the Galaxy Nexus Toolkit to do this for you. I think the latest version is 5.7.
Android SDK - http://developer.android.com/sdk/installing.html
Android Images - https://developers.google.com/android/nexus/images#yakju
Galaxy Nexus Toolkit - http://windows.podnova.com/software/5996358.htm
smsmad said:
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
Click to expand...
Click to collapse
Ah yes, I now see where I went wrong with the toolkit, I didn't put the phone in fastboot. Stupid...
How is the stock recovery supposed to look like? After putting back stock recovery with the GN Toolkit, I press 'vol+/vol-/power' and choose recovery. It then displays the belly up android with exclamation mark. Is that the way it should be? Am I doin' it wrong?
yes it is the stock recovery. But you dont need it. Flashing everything into fastboot mode(bootloader)
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
If you flashed the latest Factory-Image there is no OTA out there. It is the newest version of ICS for your Device.
Maybe i don't understand what you mean with failing OTA. Could you explain it a little bit more?
As I said in the long story, I'm currently 4.0.2. and every time when my phone says, "You have update 4.0.4. standing by, please reboot" it fails.
i would prefer to flash the factory image and root your phone again
then you have a cleaned phone and OTA should work but you don't need them because you are at latest version.
https://developers.google.com/android/nexus/images
i wrote how you could flash it page before, remeber you wipe your data from sdcard
Lex_Michdeandroid said:
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
Click to expand...
Click to collapse
I don't know if I can answer why the OTA isn't working (I'll leave that to smarter men than I), but having an unlocked bootloader and root access won't stop the OTA. I had my phone in that state when the 4.0.4 update came out and all was fine, just had to run the command to get root of my phone again as OTA removes root.
Ah great! S~ has just hit the fan, it's bootlooping after trying option 8 (flash stock rom from google). Oh I really am going to kill myself sooner or later...
Edit: not killing myself yet, just had to pull the battery... Let's see what I f~ up next...
Very strange you problems i don't know the Toolkit and don't know how it flash the stock rom. But i could imagin that it only flash rom and not the other things like recovery and so on.
Try out the hard way without toolkit and use sdk and included batch file into the factory image. it is the clean way and you see whats done.
Ok, I now rebooted the phone after option 8 in the toolkit and it seems I'm running 4.0.4. I have to go to Brussels now for two weeks, but I'll try to post some screenshots later. I'll also be back to thank all of you for holding my hand, I just don't have the time right now. Of course this won't be my last problem (I still have a TF101 that needs some RMA action), but I hope I won't be needing too much time consuming support anymore.
Just got in the hotel, and unable to use my phone in Belgium. No available network... Wifi works, 2G/3G works in The Netherlands, 2G/3G unavailable in Belgium...
Screenshot of my device: http://oi46.tinypic.com/34xp89y.jpg
Sent from my Galaxy Nexus using XDA
Just tried my SIM in a different phone, problems are with my network. Phone works with different SIM, so false alarm.
Sent from my Galaxy Nexus using XDA
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
msedek said:
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I rather eat my own shhhhh... shorts than buy something with an apple on it. With the help of you guys it always works out fine, it just takes a life or two.
Sent from my Transformer TF101 using XDA
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
Galaxy Nexus(Verizon CDMA)
ICS 4.0.4
Build number: IMM30B
Unlocked
Not rooted
I was hoping someone here might be able to help me with my Galaxy Nexus. My Mac, PC, or Linux box won't recognize my phone anymore. I've tried multiple battery pulls, cords, driver updates(Windows 7), an have wiped the phone. My Nexus 7 is recognized by all 3 PCs so it seems like a phone issue.
When I first got the phone, it had 4.0.2 on it but the battery life was horrendous so I manually flashed 4.0.4 IMM30B instead of waiting for the official OTA. I have read on another thread that someone with the same version of ICS had the same USB issue. They ended up returning the phone. I have a feeling that this is software related and not hardware.
So my question is, is it possible for me to go back to stock 4.0.2. It seems like Odin and fastboot all need usb. I read that a factory format may be possible using a dialer code(*2767*3855#), but when I tried it it didn't do anything. Probably worth noting that I didn't take any backups before flashing.
only thing i know without a USB is mobile ODIN.
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
Thanks for the response Zep but from what I understand Mobile Odin requires root
Zepius said:
only thing i know without a USB is mobile ODIN.
Click to expand...
Click to collapse
Are you sure it's not a driver issue?
If you can't use the USB port AND you don't have root AND you don't have a custom recovery, I don't think there is much else you can do.
Sent from my Galaxy Nexus using Tapatalk 2
Efrant is correct. I think you should try manually installing drivers for Galaxy Nexus. There are few helpful instruction on how to install drivers on xda
kraymondksc said:
Galaxy Nexus(Verizon CDMA)
ICS 4.0.4
Build number: IMM30B
Unlocked
Not rooted
I was hoping someone here might be able to help me with my Galaxy Nexus. My Mac, PC, or Linux box won't recognize my phone anymore. I've tried multiple battery pulls, cords, driver updates(Windows 7), an have wiped the phone. My Nexus 7 is recognized by all 3 PCs so it seems like a phone issue.
When I first got the phone, it had 4.0.2 on it but the battery life was horrendous so I manually flashed 4.0.4 IMM30B instead of waiting for the official OTA. I have read on another thread that someone with the same version of ICS had the same USB issue. They ended up returning the phone. I have a feeling that this is software related and not hardware.
So my question is, is it possible for me to go back to stock 4.0.2. It seems like Odin and fastboot all need usb. I read that a factory format may be possible using a dialer code(*2767*3855#), but when I tried it it didn't do anything. Probably worth noting that I didn't take any backups before flashing.
Click to expand...
Click to collapse
On you windows box, what do you see when you plugin your phone with the device manger window open? Is nothing detected at all?
Are you using the same cable between the nexus 7 adn the Gnex? If not, the cable you are using with your Gnex may be a charge only cable or it could be damaged.
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
don't use windows..
Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles
chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Could you walk me through your fix?
Mods please delete double post sorry
ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.
I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave
if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium
Samsungs older drivers: uploaded.net/file/hdh0f1xd