Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
I believe first thing you need to do is unlock your bootloader , I just did that.. now im not sure where to go after that but first video in this thread and toolkit helps alot plus it helps you get your drivers setup.. I had issues with 8.1 x64 so I switched to a windows 7 computer and it worked perfectly
Oh yeah I forgot to mention. I am already rooted and the boot loader is unlocked. I used the wugfresh toolkit and set up the drivers again to how I think they should be and when it went through the testing procedure, it fully connected to the device, rebooted it into fast mode and then turned it back on again.
It just doesn't respond to the batch file that was in the zip
I have the same problem. I run the .bat file, and it just hangs on waiting for device. My bootloader is unlocked, and I have a custom ROM on my device. I put it into fastboot mode too, and it won't recognize it.
Did you try running the bat file as administrator? Or try a different usb port?
jstn76rs said:
Did you try running the bat file as administrator? Or try a different usb port?
Click to expand...
Click to collapse
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Just look here and use twrp:
http://forum.xda-developers.com/nex...shable-factory-image-zips-android-5-t2939599/
James_Feltham said:
Actually I didn't. That might be worth trying. Cheers
EDIT: Well that kind of worked, but it just came up with "fastboot is not a recognised internal/external command". Any ideas now?
Click to expand...
Click to collapse
you need to run the command from adb installed folder, these exe's comes with android SDK.
James_Feltham said:
Hi guys, I want to upgrade to android L now but i have to upgrade to the new bootloader. I am very unfamiliar with fastboot so I could do with some help.
I have downloaded the zip with everything I need in it. I know there are a few things I need to do before I can upgrade, i just dont know what these things are
I did just try it without doing anything (plugging in my tablet, booting to fastboot and opening the batch file but it just came up with "Waiting for device")
Im pretty sure its something to do with the drivers but currently I am clueless.
PS I made this thread because it was instructed for me to not ask for help on the thread for the rom and Im pretty sure a lot of other people are having the same problem as me. Any help would be appreciated, thanks for your time
Click to expand...
Click to collapse
What version of Windows are you running?? 8.1 is troublesome for drivers. I've had better results from Windows 7
With the nexus 7 you will want to install the kit from http://forum.xda-developers.com/nex...wugs-nexus-root-toolkit-v1-9-3-nexus-t2940401
this is the easy way to get adb fastboot and some other utilities
you can then go to the wugfresh development/data directory
open a cmd window
boot your n7 to the bootloader ( Power + Vol Down)
connect it to your computer.
in the command window
type fastboot devices
look for your nexus serial number ( should show on the bootloader screen on the nexus)
if you don't get a device showing... you will have to re-do your drivers installation......
try using the Wugfresh tool kit.
if you do see your device
use the windows bat file in the Bootloader update from Scrosler's thread.
Related
I have had this posted in q and a for over a week. Hoping someone here can help me. Mods please move if neccesary.
beastmods said:
ok i have
evo 002 hardware
used 2.2 root process used simple root after i rolled it back NOT UNREVOKED
hboot .76.200 s off
i am unable to use any fastboot commands. I am trying to flash the splash1. about tired of looking at it.
when i try to flash it i get "waiting on device" and that is all it does.
if i type "fastboot devices" then i get blank space and the back to C:/android/tools
any help would be greatly appreciated..let me know if you need any more info.
Click to expand...
Click to collapse
try installing Android ADB drivers again, that's what I did and it fixed that issue for me..
jdmsohc22 said:
try installing Android ADB drivers again, that's what I did and it fixed that issue for me..
Click to expand...
Click to collapse
Yeah I thought about that. Do I just go through the sdk installation process again?
tried reinstalling the android sdk still no luck. i will pay someone for a fix.
going to reformat my computer now and just start all over. just so weird i can run adb and shells, just only fastboot is giving me ****.
Hi guys, I know there are a number of guides out there, but I found that a lot of people are running in to the bootloop issue by using certain methods to root (ie the "ADB Method").
So what is the current safest/best method to root?
Code:
fastboot oem unlock
fastboot flash recovery clockworkmodrecovery.img
(reboot recovery)
adb push su.zip /sdcard/
(reboot recovery)
(flash su.zip in recovery)
Don't bother with any of the one-click methods or anything like that. The hardest part is making sure you get your adb drivers set up correctly, and then you're good to go.
This is about as easy and safe as it gets-
lots of options to do what you need, including removing root.. Just install it and take a look around without hooking your phone up so you dont accidently do some damage.
http://forum.xda-developers.com/showthread.php?t=1400871
Thanks,
J
What codesplice said in post #2.
Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts
qubic333 said:
Thanks for the replies! Will try codesplice's method, is there a link/thread for the latest Samsung drivers? Is using Universal Naked Driver ok?
P.S there doesn't seem to be a way to rep/thank posts
Click to expand...
Click to collapse
Yes those drivers will work. Make sure you boot your device into fastboot mode by hold both volume up and volume down an press the power button, then plug into you computer and install the drivers.
Then, when you unlock, don't forget that it will wipe your data/settings.
Sent from my Galaxy Nexus using Tapatalk
Personally I used the one-click method. I found this easy enough but you need to really pay attention when you use it or you won't understand what to do...
I did it the 'proper' way with my previous phone and I found it difficult but once you know what to do, you could easily do it again.
If this is your first time rooting a phone, I would do it the way that codesplice says, if not, take the easy route!
I just started the rooting process, and I actually didn't have to manually install any drivers.
I set my phone to fastboot mode, plugged it in and they installed automatically and fastboot recognized my phone (shows serial number in cmd when I launch fastboot.exe). Is this normal? or should I uninstall the drivers and manually install them?
Note: My device manager shows:
Android device
|__Android ADB Interface
Got root
I think windows now installs all the right drivers automatically..
qubic333 said:
Got root
I think windows now installs all the right drivers automatically..
Click to expand...
Click to collapse
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.
codesplice said:
It's supposed to, it just doesn't always work. Glad to hear you got Mission Accomplished though - and I hope you learned just a wee bit about the process along the way. Being at least familiar with fastboot and adb will help you significantly if you run into problems down the road.
Click to expand...
Click to collapse
This was my first attempt at rooting and I'm glad it went smooth, I'm not a complete noob as I do have some Linux background, but I'm completely new to the smartphone thing so my knowledge of apps and ROMs and how they integrate in the device is very limited.
Thanks for the help guys, much appreciated! Great community you have hear
Hey guys
Ok so I have a bit of a tricky problem. I got in over my head on my nexus and tried to install ubuntu mobile with a friend. Suffice to say things didn't go so great and now my nexus wont boot, when i turn the phone on it sits on the Google screen. To make matters worse, no computer I plug the phone into can see the device. The strange thing is I can still boot to cwm recovery mode but there is no longer an android image to flash from and I can't load one back on.
Any help you guys can give would be greatly appreciated.
Cheers
Zephyr737 said:
Hey guys
Ok so I have a bit of a tricky problem. I got in over my head on my nexus and tried to install ubuntu mobile with a friend. Suffice to say things didn't go so great and now my nexus wont boot, when i turn the phone on it sits on the Google screen. To make matters worse, no computer I plug the phone into can see the device. The strange thing is I can still boot to cwm recovery mode but there is no longer an android image to flash from and I can't load one back on.
Any help you guys can give would be greatly appreciated.
Cheers
Click to expand...
Click to collapse
Download the factory image from here https://dl.google.com/dl/android/aosp/takju-jdq39-factory-5e273f02.tgz. Unzip the downloaded file and you would see a file "flash all.bat". Open this file and then follow the on-screen instructions.
Done! You have flashed factory image.:good:
mannyvinny said:
Download the factory image from here*tag removed*. Unzip the downloaded file and you would see a file "flash all.bat". Open this file and then follow the on-screen instructions.
Done! You have flashed factory image.:good:
Click to expand...
Click to collapse
Hey mate, sorry its been awhile since i've been on this, gave this a go but got the following error
" fastboot is not recognized as an internal or external command, operable program or batch file"
Anyone else care to weigh in?
Zephyr737 said:
Hey mate, sorry its been awhile since i've been on this, gave this a go but got the following error
" fastboot is not recognized as an internal or external command, operable program or batch file"
Anyone else care to weigh in?
Click to expand...
Click to collapse
you need the fastboot.exe
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
you need the fastboot.exe
follow this:
Click to expand...
Click to collapse
Will that work even when my pc does not recognise the phone?
That just means you have a driver issue.
063_XOBX said:
That just means you have a driver issue.
Click to expand...
Click to collapse
The issue is on the phone, not the pc I have several android handsets that all work with this pc and I have tested with another pc, same issue. I get a charge from the pc and thats it.
Zephyr737 said:
The issue is on the phone, not the pc I have several android handsets that all work with this pc and I have tested with another pc, same issue. I get a charge from the pc and thats it.
Click to expand...
Click to collapse
No it is definitely a driver issue. Uninstall the drivers you have installed for the galaxy nexus. Then install these.
http://forum.xda-developers.com/showthread.php?t=1379875
Toro | Xylon | AK Diamond
Sandman-007 said:
No it is definitely a driver issue. Uninstall the drivers you have installed for the galaxy nexus. Then install these.
Toro | Xylon | AK Diamond
Click to expand...
Click to collapse
Forgive my ignorance, but how to do install those files?
If you uninstall all galaxy nexus drivers in device manager, and Windows doesn't at least tell you it needs drivers when you plug your phone in, then you either have a bad cable or a very messed up phone. In that case you'd have a hard time installing universal naked drivers. There's something called 'OMAP flash' you might want to search for and ask about. All I remember reading is that some people have used it to recover their phones in situations like yours. Never used it myself. Yet. You might want to ask efrant. He knows everything.
strumcat said:
If you uninstall all galaxy nexus drivers in device manager, and Windows doesn't at least tell you it needs drivers when you plug your phone in, then you either have a bad cable or a very messed up phone. In that case you'd have a hard time installing universal naked drivers. There's something called 'OMAP flash' you might want to search for and ask about. All I remember reading is that some people have used it to recover their phones in situations like yours. Never used it myself. Yet. You might want to ask efrant. He knows everything.
Click to expand...
Click to collapse
It tries to install the drivers but always fails. I'm even trying this on a virgin pc i've never connected the nexus or any android device to before. I'll look into OMAP cheers!
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Use wugs program but tick tablet is in bootloop.
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!