Related
Hi people
I've been trying to unlock the bootloader to root my nexus s 2.3.3 for 2 days now and have tried everything i can find in all the related threads but my computer wont see the phone when in fastboot mode.
Im getting really fed up as i do not know what to try next.
Anyone had this problem before?
Any help would be much appreciated.
Jon
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Andrew421 said:
Have you tried the PDA.net way to install the drivers for fastboot? Google: PDA net
Click to expand...
Click to collapse
Yeah I've tried that too but computer does'nt see the phone in fastboot mode so i cannot update the drivers at all.
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
kenvan19 said:
What do you mean by it cannot see it. Also, what OS are you running? Often times the phone is detected via fastboot when ADB fails (this happens to me all the time).
Click to expand...
Click to collapse
Hi, when i put the phone in fastboot mode the computer doesnt see the phone in device manager but it does see it when not in fastboot mode. Im running windows 7 64.
Hey man, I had the same issues. It took me a total of 12 hours to root my phone and I tried everything . I was stuck trying to unlock the bootloader for hours. The problem for me was that the driver couldnt be found. I tried the pda net and it kept saying that the drivers were installed. Assuming your using windows, go to devices with the phone plugged in and you should see the device named something different with a yellow exclamation mark..... right click and hit update driver software. Then find the file pdanet and point it to update with that file. If this doesnt work, theres a file in there I believe its called android_usb or android_winusb and you push "have disk" and force install from that file . then it should see your phone. this was the only way i could get it to work was by pushing have disk and pointing it at the actual android 1.0 driver becuase the google usb package didnt have it (at least at the time). Im new to the forum, so bare with me if my directions aren't too great, just thought I'de try to help you out bc it was so frustrating!. Also, here is a good link in the xda forums for you to check out http://forum.xda-developers.com/showthread.php?t=875580
also,,,are you getting the "waiting for device" message when you type fastboot oem unlock? these instructions are for if you are experiencing that... Its basically not found becuase there is an android 1.0 driver that you have to force to update. good luck!
Thanks for the replies am now downloading the sdk onto the wifes laptop as hers is win 7 32 so hope there is less issues. fingers crossed.
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
mattdub1 said:
i did mine with win 7 64 i tried 32 as well but my 64 worked better for me.... i looked at the driver details with my phone plugged in to see what drivers are on there .. you need the wdfcoinstaller , the winusb coinstaller, and the winusb.sys. if you find the device when plugged in to your computer and goto details and then hit update driver and then point it specifically at the android_usb.sys file in the pda net for android folder then it should work. the google drivers thru sdk don't contain this one file and its the one that makes the whole process work. Let me know if this works for you
Click to expand...
Click to collapse
Have the same drivers installed but computer still doesn't see the phone when in fastboot mode. It worked perfectly on win7 32 on other laptop and I managed to root. still trying to get it to work on win7 64 as this is my main OS.
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
also, you did make sure to dowload the google usb package and get the right sdk version correct? I cant see any other reason that the phone wouldn't be recognized. I also believe you need usb debugging on
http://forum.xda-developers.com/showthread.php?t=878786 check out this post... VERY good guide and this is what helped me on the 64 bit 7. it sounds like your missing the fastboot driver which allows the computer to see the device in fastboot mode
mattdub1 said:
glad to hear,...just out of curiosity, how did you get it to work on the 32 bit version?? Id like to know for future reference,,, and also are you getting the waiting for device error in fastboot mode?
Click to expand...
Click to collapse
On win7 32 it was really easy once all the necessary programs and files were downloaded I first connected the phone switched on in normal mode with USB debug on and installed the drivers. Once in fastboot mode the path for the drivers was already there from the previous driver install I just selected the bootloader driver and the rest is history
Sent from my Nexus S using XDA Premium App
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
mattdub1 said:
which one was the bootloader driver? did you get it from the google usb drivers or the pda net ones?
Click to expand...
Click to collapse
it was the google usb drivers when i went update drivers on my system the path is
C:\android\android-sdk\extras\google\usb_driver.
Then go to option 'let me pick from a list of drivers on my computer' Which brings up three options:
Android ADB Interface
Android Bootloader Interface
Android Composite ADB Interface
Choose the Android Bootloader Interface hit next and yes to install.
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
noj78 said:
Ok so on my win7 64 system i think that somewhere along the line i installed the wrong driver and broke the link although i can find the device in fastboot mode in devices and printers\unspecified but there it no option to upgrade drivers
Click to expand...
Click to collapse
If you can see the phone in fastboot what else do you need?
deleted!!!!!!!!!!
I can see it in fastboot mode but not in device manager where it should be.
I can only see it in devices and printers where there are no driver options.
Okay, so put it in fastboot mode and try to run a fastboot devices real quick.
Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...
singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.
Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly
hi my mate has and s4 9505 and he wiped the hole phone like a noob and it wont enter recovery and in odin nothing will flash tried pit file and also stockrom it either gets stuck on setting up connection or stuck on pit mapping part tried adb devices command but its not picking up the devices the drivers will be on his comp as he has all ready flashed things via odin before on the s4 any ideas people cheers
strikerdj2011 said:
hi my mate has and s4 9505 and he wiped the hole phone like a noob and it wont enter recovery and in odin nothing will flash tried pit file and also stockrom it either gets stuck on setting up connection or stuck on pit mapping part tried adb devices command but its not picking up the devices the drivers will be on his comp as he has all ready flashed things via odin before on the s4 any ideas people cheers
Click to expand...
Click to collapse
Try that:
You can use this software to repair Your dead Samsung i9505 and similar (m919, i337, L720 etc)
Note, You need to install QHUSB Qualcomm drivers first.
After flashing with this software, You need to flash phone with official firmware and PIT file, otherwise phone will be dead again, and You'll need to repeat the process.
If You get errors reported by this software (command prompt window), You'll have to replace the eMMC chip first.
Click to expand...
Click to collapse
Warning ..I never tried that..
source
Please report back if that worked for you.
Thank's
ausdim said:
Try that:
Warning ..I never tried that..
source
Please report back if that worked for you.
Thank's
Click to expand...
Click to collapse
thanks will try this
I'm in this exact same position. Can you please post back with your results as to how it goes.
Thanks
EDIT - I simply changed USB ports and it worked fine!
oblique1 said:
I'm in this exact same position. Can you please post back with your results as to how it goes.
Thanks
EDIT - I simply changed USB ports and it worked fine!
Click to expand...
Click to collapse
no such luck for us and that the other thing didnt work either :/
Did you install the drivers for the phone?
Did u put phone in download mode and flash with odin?
If so, trying closing all kies process, changing usb port and run odin with admin. Flash pit file and stock firmware.
lzk123 said:
Did you install the drivers for the phone?
Did u put phone in download mode and flash with odin?
If so, trying closing all kies process, changing usb port and run odin with admin. Flash pit file and stock firmware.
Click to expand...
Click to collapse
yea drivers are installed and yea vol down power and home in to download mode we uninstalled kies and installed drivers on own same thing then we re installed kies and same thing tried the 4 usb ports on him comp and when a flash pit or stock rom odin doesn't go past setting up connection
ran the adb command adb devices and it just doesn't seem to be picking up his device
strikerdj2011 said:
yea drivers are installed and yea vol down power and home in to download mode we uninstalled kies and installed drivers on own same thing then we re installed kies and same thing tried the 4 usb ports on him comp and when a flash pit or stock rom odin doesn't go past setting up connection
ran the adb command adb devices and it just doesn't seem to be picking up his device
Click to expand...
Click to collapse
Did u restart the com after reinstalling kies? Try restart computer now and flash.
yea every time a install something and uninstall some thing allways reboot the comp
strikerdj2011 said:
yea every time a install something and uninstall some thing allways reboot the comp
Click to expand...
Click to collapse
What error shows up when u flash stock rom and pit again?
it just stays on setting up connection on odin thats it doesn't go any more past that point
strikerdj2011 said:
it just stays on setting up connection on odin thats it doesn't go any more past that point
Click to expand...
Click to collapse
What odin version are u using? Are u sure you have properly installed kies or drivers? The latest kies version? Try disabling antivirus and installing latest kies.
tried with odin 1.85 3.04 and 3.07 and yea latest kies i uninstalled antivirus to be on safe side as i no it can conflict with odin and stuff
The problems you are having are purely driver issues. Try flashing the phone on another computer.
robogo1982 said:
The problems you are having are purely driver issues. Try flashing the phone on another computer.
Click to expand...
Click to collapse
ok thanks will try it on mine 2 moz cheers
Let us know if it worked
Try a different data cable it worked for me
Sent from my GT-I9505 using xda premium
Well I've had some problems too today and there a couple of things you might want to try (I'm sure one of them will fix it):
- Pick a different USB port (preferably one in the back)
- Try a different USB cable (I used one from my Nexus 7, didn't work. Tried with the original S4 cable, worked)
- Uninstall Kies and the Samsung drivers from you control panel -> programs
- Download the Samsung USB Drivers again (google it) (do not install them yet)
- Download and install USB Deview (google it) and delete every driver of Samsung you come across in the list (just right click and click delete)
- Disable your internet access and reboot
- After rebooting install the Samsung Drivers (without an internet connection)
- Plug in your phone after you've installed the drivers and enable USB Debugging
- Reboot
- Enable your internet connection again
- Try to flash again in Odin (it should work now)
If this won't work, I don't know what will. A different USB port, cable, fresh/original drivers (not the ones Windows Update may try to install for you), etc is probably what you'll need to get it working.
thanks for every ones help we installed a fresh copy of windows 7 and installed every thing again and it worked fine defo must of been driver related :laugh:
Cheers now flash away like there's no tomorrow
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it
djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.
Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app
So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind
What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app
access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...
well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.
I have a G360P Boost Mobile version. I rooted the phone using Kingoroot and things were working great.
I rebooted the phone at one point and now the phone only boots in Download Mode.
It doesn't seem to be recognized by Odin or by Kies either.
Any ideas?
***EDIT***
More Info, I'm using Windows 7 x64
I tried ODIN v3.09 and then v1.85 and Kies v3
I have tried multiple USB cables in multiple ports.
Just for future reference I was able to exit download mode by disconnecting USB cable and holding down the power button for 10 secs.
SMcC2 said:
I have a G360P Boost Mobile version. I rooted the phone using Kingoroot and things were working great.
I rebooted the phone at one point and now the phone only boots in Download Mode.
It doesn't seem to be recognized by Odin or by Kies either.
Any ideas?
***EDIT***
More Info, I'm using Windows 7 x64
I tried ODIN v3.09 and then v1.85 and Kies v3
I have tried multiple USB cables in multiple ports.
Click to expand...
Click to collapse
Install samsung drivers... google
Sent from my GT-N7105 using Tapatalk
SMcC2 said:
I have a G360P Boost Mobile version. I rooted the phone using Kingoroot and things were working great.
I rebooted the phone at one point and now the phone only boots in Download Mode.
It doesn't seem to be recognized by Odin or by Kies either.
Any ideas?
***EDIT***
More Info, I'm using Windows 7 x64
I tried ODIN v3.09 and then v1.85 and Kies v3
I have tried multiple USB cables in multiple ports.
Click to expand...
Click to collapse
honestly like someone mentioned here install the samsung drivers for your phone. I had the same problem, it not being detected until I did that. As far as the rebooting go back to stock. Flash the stock image with odin, or remove root and hard reset the phone using recovery. Hope that helps.
I guess I had assumed that when I installed Kies that the correct drivers would have already been installed. I downloaded the drivers from the Samsung Website HERE and was able to flash the stock firmware via ODIN. From that point I was able to boot up and install system updates. Thanks you two for the help.
sm-s820l firmware
SMcC2 said:
I guess I had assumed that when I installed Kies that the correct drivers would have already been installed. I downloaded the drivers from the Samsung Website HERE and was able to flash the stock firmware via ODIN. From that point I was able to boot up and install system updates. Thanks you two for the help.
Click to expand...
Click to collapse
Where did you find the stock firmware? I have been looking all over and it seems all other models have it downloadable but this model.....Please help! Thanks!
metallifan24 said:
Where did you find the stock firmware? I have been looking all over and it seems all other models have it downloadable but this model.....Please help! Thanks!
Click to expand...
Click to collapse
I googled for a bit and didn't find much other. The results suggested it was a Tracfone model. If that's true I've always had problems finding firmware for Tracfone models, but have sometimes managed to get away with using a firmware from a similar model.
Samsung 820L Product Page (No downloads here )
Phones that may have similar firmware???
If you run out of options I would suggest trying Kies - may not hurt at that point.
help
I tried to root using odin nowim stuck in download mode and it wont connect to my laptop ive download drivers kies odin PLZZZZ HELP!!!
Get Odin to recognize your phone
Try powering off your phone with it plugged into your computer then use the button command for download mode again that helped me......
I'm having an issue and I think it's because I've flashed to many files
I can't get my galaxy core prime sm-s820l to accept any flashed Roms stock or custom I've even tried twrp and stock recovery
The only thing I can access is download mode and most of the time it won't connect to Odin I can get it to connect using the method above. Someone please help
I have minor experience with Odin and Roms I've been playing around with my infuse 4g for a while