Related
been looking around on here. im stuck now
Ok iv unlocked and have root and can load into Clockwork 5.5.0.2
But when in Clockwork i get
E:can't mount /sdcard/
When i reboot the nexus now all i get is the Google Logo with the unlock Padlock.
Once it did load back into OS and then rebooted it self now stuck on Google logo and Unlock padlock... i Didnt copy over my ROM too the SDCard....
How do i get back into the OS
Flash the factory Google images via fastboot. Search the forum. There a quite a few threads with step by step instructions.
Sent from my Galaxy Nexus using xda premium
Try pressing the volume down button and power button until you reach recovery. When you a red triangle, press Vol+/Vol-/Power at the same time, you will now see a menu, select factory data reset.
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
??
throwbot said:
I've been in your shoes, and I doubt a factory reset will help. If I were you, I would download the stock images first (lte or GSM nexus?). After that, try seeing if your drivers are configured and that tour phone is being recognized by your computer when it is plugged in with the USB cable. The drivers will need to be configured for when the phone is showing the Google logo, but also configured again when the phone is in the boot loader. (Ask if you need more instructions for this).
OK, what worked for me was locking and then unlocking my phone again. Type fast boot OEM lock, and if the drivers are good then the boot loader will lock. Then type fast boot OEM unlock and it will wipe everything--even Android backups. It shoud also delete the problem. After that you can push files to it from the computer but you might have to configure your drivers again (I did). Hope this helps, it worked for me.
Click to expand...
Click to collapse
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
NxsLS said:
I can connect the phone and lock n unlock the bootloader. so the USB drivers ar working. but iv got no way of pushing the files onto it
Click to expand...
Click to collapse
Have you tried flashing via fastboot? I would assume if fastboot oem unlock/lock works, then flashing using fastboot/android sdk should work.
...though, as a non dev, i have been wrong before
what do you mean by "pushing the files"? What are you trying to push?
Sent from my Galaxy Nexus using XDA App
Good, make sure you boot loader has been unlocked. You can use a program like the root toolkit (I don't think I can put a link to a different website) but he root toolkit for the nexus should help you push the stock image to your phone. Go to droid-life (.com, cough cough) and there is a set of instructions for returning back to stock. You can also use those same instructions to try and get her back up and running. Try the root toolkit they have on there, too. The only problem you might run into is having your phone set to USB debugging after unlocking the boot loader, bit it should still accept fast boot commands while I'm the bootloader
---------- Post added at 09:48 PM ---------- Previous post was at 09:42 PM ----------
sorry, by pushing the files I mean pushing the stock image file (the stock software, including the stock operating system, stock bootloader, and stock radios). A rom is a custom tweaked version of the stock software. When you unlock the bootloader, if you don't have stock software on there (which you wont if you were running a rom when it crashed) then it might erase everything, including the from you were running. You will have to push that stock software (stock image file) back to your phone using commands from your computer
no worrys o2 just sending me a new nexus :x
report lost n stolen :x only £30 ex
NxsLS said:
report lost n stolen :x only £30 ex
Click to expand...
Click to collapse
I hate that.. because you didn't know what you were doing and screwed up your phone someone is supposed to provide you with a new one? As a few posters have already said, it should be a fairly easy fix. You didn't even acknowledge that you tried any of the suggested fixes. If you're going to mess around with your phone make sure you know what you're doing, or at the very least exhaust all potential options to get yourself out of a soft brick. I'm sure an experienced Android user could have you up and running in 10 minutes. It's no wonder providers don't want to unlock bootloaders on some phones.. Jesus...
i tryed all i got it too boot back into the OS but reset itself and locked in google with unlocked padlock. so gave up and will not make the same mistake of not copying over the rom after the root n unlock.. i have flashed/unlocked my samsung s2 with ODIN which was easy but the Nexus i used Galaxy Nexus ToolKit
Hey
I know this is a greatly discussed topic but I have been through countless threads and tried everything so please bear with me! Long story short, my phone is in a massive rut at the moment and nothing seems to get it out of bootloop (tried fastboot, odin etc; yes I'm not an expert at all but I'm not exactly a noob). Odin is/was my last hope and for some reason Windows XP seems to keep crashing it the minute I hit start. I read through numerous posts on the Galaxy Nexus forum and have also tried numerous other methods including trying to go back to stock via fastboot and toolkits, trying to flash .img files individually etc etc etc and I basically need all the help I can get if someone wouldn't mind? The phone does turn on to fastboot and is detected on toolkits and drivers are fine.
For those who need the info its a i9250 GSM maguro (UK version i.e. without google wallet) running JB 4.1.1. I did try to flash maguro ICS 4.0.4 and when I go into fastboot, the bootloader version has changed to PRIMELA03 whereas I'm sure JB isn't that but I may be wrong! The phone crashed 2 nights ago and ever since then it gets stuck in bootloop when switched on, the images are noisy and fuzzy as if the phone has some kind of virus and nothing flashes on it! Fastboot just crashes requiring a battery removal all the time. Odin crashes too so I cannot flash any other firmware. The phone is not rooted but the bootloader is unlocked and I have no SD card (obviously).
Sorry if I have posted in the wrong thread or done anything I shouldn't have -_- I just need help so someone PLEASE guide me in the right direction!
Thank you in advance!!
Update: I just tried to flash JB back over the bootloader version and it changed from PRIMELA03 to PRIMELC03 so the bootloader version does change however nothing else seems to flash!
Update 2: Think i finally managed to mess my phone up. Got the yellow exclamation mark triangle between a phone and pc -__- anyone have any insight on how to go around this? Everything I have read up has more or less got to do with all other variants of Gnex other than GSM!
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
bk201doesntexist said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=1925468
Sent from my i9250
Click to expand...
Click to collapse
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Devzz said:
Tried this last night, even now, OMAP works when the phone is connected and runs the .bat file perfectly however it has NO effect on the phone, as soon as I try to boot it just comes up with the > phone!PC < screen, however ODIN does detect the phone so I am convinced it isn't a full brick! Odin however doesn't go through the process of flashing it just says FAIL in red on top once I start the process because I cannot get the phone into download mode or fastboot.
Click to expand...
Click to collapse
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
slim207rc said:
Question from me, how did you get fastboot to work on your windows xp?
Keeps crashing as soon as I want to open it on mine
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Devzz said:
Well I didn't use the conventional way; I had a the Wugs nexus toolkit (Yes I know xda doesn't take kindly to toolkits but I only use it to launch the ADB command prompt cos I don't really know how to use the SDK toolkit method) from which I launched the command prompt and used fastboot commands through that to try flash .img files to the phone. Unfortunately it all failed even when I could access fastboot. Now Odin doesn't let me flash anything either; It just says failed.
Sorry if this doesn't answer your question but that's how I went about doing the whole fastboot bit If you mean it crashes when you open cmd maybe try launch cmd through Wugs?
Click to expand...
Click to collapse
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
slim207rc said:
I'll just have to give it a shot. Thanks anyways though:thumbup:
Sent from my R800i using xda premium
Click to expand...
Click to collapse
No problem
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...
I posted this Q in the sticky in general, I apologize for re-posting it but I don't know if that thread is followed much
A friend's flo suddenly bricked (error mounting cache) and he was on stock un-rooted
Since he doesn't mess with his device usb debug was not enabled at the time it bricked
So adb lists no devices, but fastboot works.
Even though fastboot works, when trying to unlock bootloader it hangs at "erasing userdata"
so there's no way in moving forward from here
I apologize if it's a common question, I did look around a little bit before asking but i come from a completely different device
Thank you for any help
Rudjgaard said:
Even though fastboot works, when trying to unlock bootloader it hangs at "erasing userdata"
Click to expand...
Click to collapse
Looks like its on stock recovery. Try erasing the cache through stock recovery 2-3 times. If it doesn't work you have to unlock the bootloader to flash the cache.img partition. It does take some time to wipe the userdata when unlocking it for the first time.
Code:
fastboot erase cache
Code:
fastboot flash cache cache.img
Thank you very much for your reply. It is stock recovery.
Clear cache from recovery was the first thing I tried, but it gives an error since it can't mount it
How long does it take the process to unlock bl the first time?
I looked at some yt videos and they talk about 10-15 seconds,
both times i tried I waited for over 15-20 minutes..
Rudjgaard said:
Thank you very much for your reply. It is stock recovery.
Clear cache from recovery was the first thing I tried, but it gives an error since it can't mount it
How long does it take the process to unlock bl the first time?
I looked at some yt videos and they talk about 10-15 seconds,
both times i tried I waited for over 15-20 minutes..
Click to expand...
Click to collapse
I don't remember it correctly but that much time should be sufficient. You can give one last try by waiting for 30 min to an hour.
IF you are not successful in unlocking the bootloader, then you may have to send it for warranty services. Maybe an issue with emmc...dunno really then.
Btw which usb port u r using? USB 3.0 has some issues with it. So try with 2.0
Although I've never used it I've heard a lot about a nexus toolkit on XDA that has a capability to flash system.img if the computer recognizes the tablet an I don't think you need an unlocked bootloader or USB debugging
mugzylol said:
Although I've never used it I've heard a lot about a nexus toolkit on XDA that has a capability to flash system.img if the computer recognizes the tablet an I don't think you need an unlocked bootloader or USB debugging
Click to expand...
Click to collapse
Thank you, I know about usb port issues so I already tried all of them as well as different usb cables with no result
I found a few people which had the exact same problem as mine and they didn't really find a solution most sent it back for warranty
Some of these people talk about corrupt memory so there wouldn't be much to do in that case,,
Which toolkit is that?
I am on ubuntu and had a really hard time finding one that wasn't just for win..
I found one in nakasi thread which now also supports flo, but it always gets stuck at same point of bl unlock
Like I said, I've never used a nexus toolkit so i really have no idea what toolkit to use but there a lot of threads in the nexus 7 2013 q and a where it fixed peoples devices that wouldn't boot.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Ok, i'll try looking for it,
could someone though please tell me if the fastboot unlock process requires adb enabled or if it should work no matter what?
I'm starting to think that nand memory is corrupt therefore it's not accessible in any way and rma is only solution
Rudjgaard said:
Ok, i'll try looking for it,
could someone though please tell me if the fastboot unlock process requires adb enabled or if it should work no matter what?
I'm starting to think that nand memory is corrupt therefore it's not accessible in any way and rma is only solution
Click to expand...
Click to collapse
Fastboot should work without USB debugging enabled.
I did a bit of research, its called the wugfresh nexus toolkit. I think that one is the best. Sadly you are on Ubuntu, you can install wine from the software center to run .exe files but I doubt that it would work through a Linux terminal because its designed for command prompt
Sent from my Nexus 7 using XDA Premium 4 mobile app
---------- Post added at 09:08 PM ---------- Previous post was at 09:05 PM ----------
React os will run .exe and its free but I doubt you want to lose your Ubuntu data.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Thank you guys for your help
I can get my hands on a win laptop it's not a problem, more the hassle of installing adb and the rest then cleaning up
But if we put all elements together so far i'm pretty certain it's hw failure
Do you think it could reasonably take more than 1hr to unlock bootloader if there was a lot of data on?
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.