Why hallo thare XDA peeps
Ive finally decide to root my Note but Im quote not getting parts of the rooting guides here. I think I need to install the ADB drivers but Im not sure.
Ive downloaded the KK9 file from this thread. When I run the "not-rooted-yet.bat" file, it stops at "waiting for device" and it wont go further untill I start superonelick and press "root" then it continues with various errors. I assume that I dont have the ADB drivers installed. How do I do that? From CMD? Or by manually choosing some drivers downloaded when I updating the drivers with device manager??
EDIT: I found a newer version of superoneclick and it worked i think Running that kk9 file seems to work now, no errors Now I just gotta try to install CVM and some good working room
adb drivers
search for kies @ google and install..you will get adb drivers
I solved it thanx to newest SuperoneClick and I didnt want to install bigass bloatware Kies either.
Related
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
You even title your question Q and don't post in the Q&A section?
Sorry, I didn't realize I was still in the Android Dev section when I started the thread. I was in a hurry.
If a Moderator will please move this to the Q&A section!
you are running fastboot from the SPL arent you...if not you need to boot up with (Cam+Power)
you need the engineering spl, hardspl, or haykuro spl for fastboot. you also need to make sure fastboot is active on the phone (make sure it says fastboot on it in the bootloader. if not, press the back button)
Yes, sir done all of the above. ADB works great. Boot into spl - shows Fastboot USB. I just get "waiting for device" in the command window. This should be a windows setting, driver install process, or something that either I am missing, doing wrong, or that I don't have installed. But, I have attempted everything I can find on the net. I worked at it for about three hours the other night. The wife was pissed b/c I was on the computer for so long.
Well is fastboot devices showing up under device manager?
it is most likely a driver error. note that if you have haykuro's spl, he has different drivers for it. you will need to get them from his google code page
ok I'm trying to get the PSGroove so what is fastboot? An app? Please explain
shaneaus said:
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
Click to expand...
Click to collapse
If you cannot get the sdk usb drivers to work for you when your entering into fastboot, try installing htc sync. It has additional drivers that may work. I have attached a driver pack that i use.
Hi, can anyone help im pulling my hair out here, when i try to download kies onto my windows 7 pc, it gets as far as unpacking but then it keeps saying something about windows installer and a file cannot be found and to check its there. I dont know where to check cos i cant find windows installer anywhere. i had it installed before on this laptop but it was an old one, and when i tried to update it keeped getting stuck on the thunder thing, so i uninstalled it (uninstalled everything i could find to do with samsung kies) i have also tried using the samsung kies uninstall on there website. So now when i try to reinstall it it wont install. Please help!!!! thankyou in advance,,
Downlod this
http://www.softpedia.com/get/Security/Secure-cleaning/Windows-Installer-CleanUp-Utility.shtml
Install it then, on the list, select Kies and hit "remove"
then, reinstall kies, should work
THANK YOU THANK YOU it worked a treat
I try to install newest custom rom supernova 4 infinity and message is above:
Formatting SYSTEM:....
Formatting CACHE:....
Formatting DATADATA:....
Formatting DATA:....
Deleting files...
Copying files...
e:failure at line 17 :
copy_dir PACKAGE:system SYSTEM:
installation aborted
now my phone is bricked (Expensive stone) because my usb debugging is off and the odin do not recornize my captivate in downloading mode!!
What i can do now? How i fix debugging ON that i can flash my phone again to stock etc..
USB debugging has nothing to do with it.
you need to get ODIN to recognize your phone. sounds like driver problems
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
USB DEBUGGING HAS NOTHING TO DO WITH DOWNLOAD MODE!
usb debugging only has an effect if you are ALREADY booted or currently BOOTING beyond the splash screen. it doesnt matter for download mode...period.
Elisha said:
In CWM, check to see if you have the option to Root. If you do, apply Root and try flashing the rom again.
I had similar issues with 2 roms with similar errors and I had to apply root in CWM and re-flash and it went trough fine.
Click to expand...
Click to collapse
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Pirateghost said:
this is one of the most ridiculous things i have read today. root also only applies to the OS....from within recovery or download mode, you arent in the OS...so root doesnt mean SH** within recovery
Click to expand...
Click to collapse
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Elisha said:
Don't be a dip****,. I was stating my experience.
From stock 2.1 I could not install Continuum v4 in recovery and got a similar error for E:/
I had to flash a SpeedMod based kernel in recovery and root first before the rom would go all the way trough to flash properly!
It only happens to certain roms...other roms can just flash in recovery from stock no problem without rooting first.
Click to expand...
Click to collapse
This statement thus proves you have no idea what you are talking about. When you understand how a Rom flash works, then you can come back to the discussion. In the meantime, try reading an update-script or 2
Sent from my HTC Vision using Tapatalk
energy83 said:
I install odin drivers for captivate 32bit and my windows 7 don't recognize my phone, also odin do not recognize.. i test Downloading Mode.. Is usb debugging off or on with Downloading Mode?
also sdk manager installed with google samsung drivers..
Anybody else that having this recognize issues with windows 7? what to do that recognize are working
Click to expand...
Click to collapse
You said that you installed the 32 bit drivers for windows 7? Unless you are running a netbook or installed Win 7 on an older computer you probably need the 64 bit drivers. Most newer laptops these days are 64 bit OS. You can check by right clicking on "my computer" and selecting properties. It will say whether you are running 32 or 64 bit.
I also recommend downloading kies (samsung sync software). You can get it off the Samsung website under downloads. Once it's installed and opened, under tools, you can select install drivers. Go through that process and then close kies (make sure it isn't still running in your system tray), open odin and try to connect in download mode again. Don't forget basic troubleshooting like trying a different USB port if the first one doesn't work the first time.......
I was able to use adb on my Windows 7 x64 Home edition prior to rooting
After using z4root to root my Galaxy S - I9000 running Froyo
no matter what i tried , i was always unsuccessful
I unrooted using z4root and tried it but it didnt work..
Rooted it again didnt work
Thought may be to delete the device in device manager and then reinstall it using the drivers provided by Android sdk and NOT the windows update one...
Followed many others steps by various blogs and i know i am not doing it incorrectly but still it doesnt work...
I have tried to put everything in an image ,an expert mite need to understand my problem
If you are not able to see the image properly try this:
imageshack.us/photo/my-images/856/galaxysu.jpg/
Did you make sure that in your SGS, Settings/Applications/Development the USB debugging mode is ticked?
Have you tried to reinstall Kies (to install / reinstall necessary drivers)?
stiwipl said:
Did you make sure that in your SGS, Settings/Applications/Development the USB debugging mode is ticked?
Have you tried to reinstall Kies (to install / reinstall necessary drivers)?
Click to expand...
Click to collapse
What i did was deleted everything under Universal Serial Bus Controllers, uninstalled Kies and drivers of Samsung and restarted my box. and installed Kies again, set usb debugging again and connected it and Voila ! It works flawlessly now
Thanks a lot for your advice. Was getting mad after following so many posts on the internet. Finally everything is working fine now...
Hey XDA.
For long i have been trying to get a custom ROM for my android, but to be able to do that, i need to unlock bootloarders for my device.
I have been trying for a couple of months now, and everytime i try, i hope that it will work this time... but i always end up quitting, because i always encounter some problem, i cant seem to resovle.
I was wondering if anyone would like to help me through, step by step, until it actually works.
This is what i have tried
- I have entered the system configurator, and it says yes to that my device can be unlocked.
- I have enabled all the developer options descirbed everywhere
- I have downloaded the Android SDK, with the google USB drivers.
- I have gotten my unlock-code from Sony
But everytime i try to follow the steps from Sony, I get an error when coming to install the drivers.
The tutorial says, that when i plug the usb-cable to my computer, i would be prompted to install some drivers... I dont, it automaticly installs something called "S1Boot Fastboot".
Then i enter my device-manager, finds the device, and updates drivers manually from my computer.
But when i point to the downloaded drivers, i get this error:
Windows found a driver-software for your device, but encountered an error while trying to install it.
Windows ADB Interface
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tampered with.
The files i have downloaded are all those Sony told me to download, from the official distributors... I got no idea how to solve this issue!!
Can anybody please help to fix this issue, or guide me through another way that works?
I have given up trying...
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
electrash said:
Download flashtool, and instal drivers from his directory (flashtool and fastboot) drivers.
Also instal PC Companion, but restart pc after instal (PC Companion also installs drivers)
Also, you might turn of driver signature checking if you are on windows 8.1, google it.
Click to expand...
Click to collapse
I agree with this. I just did it the other day.
I'm using a Win 8.1 laptop and it was driving me mad. I followed the information regarding changing some of my start up settings on the laptop and flashtool installation of drivers worked. Follow this. http://forum.xda-developers.com/showthread.php?t=1913245&page=6
In my case i had Flashtool installed, but when i went to install the drivers for my z1 , the windows installer would always fail. After using the information on that page I Linked, it worked straight away!
Good luck .
Thanks alot!
Thank you very much guys, that was just what i missed!
Glad you finally got it!
Sent from my C6903 using XDA Free mobile app