So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5
In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.
Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.
Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.
Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first
Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.
Related
So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!
Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.
Will this work even if my device WAS Android 4.2.1 JOP40D?
Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.
styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)
styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!
You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
kmad86 said:
I received a nexus 7 from a family member that has a X on it. I downloaded Nexus 7 Toolkit 4.0.0 and tried the stock reflash and all (option 9?) and it finally seemed to complete correctly after randomly closing a few times but now it's still stuck on the X.
How do I know my build to make sure I am selecting the right image? I just googled my baseband and the version 4.1.2 popped upbeside it in searches so I went with that.
It seems like I can't get the most recent update to the toolkit unless I pay for it, but I only planned on using it once and don't even know if that would solve my problem. If i knew for sure it would, sure I would purchase it. Any idea what I might be doing wrong?
Thanks
Click to expand...
Click to collapse
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
MarioES said:
I know this may seem kinda silly, but I had a really similar problem and I solved it by going into Recovery and wiping everything, then I was able to flash another ROM from too manager.
Click to expand...
Click to collapse
Yeah, that was the first thing I tried.
kmad86 said:
Yeah, that was the first thing I tried.
Click to expand...
Click to collapse
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
MarioES said:
If that didn't work I'm afraid a manual flash is your only option, don't think any toolkits will work.
http://forum.xda-developers.com/showthread.php?t=1781250
Check that out, pretty straightforward and should do the trick.
Click to expand...
Click to collapse
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
You need to download the Android SDK for that so you can have the fastboot program. Download and install that first then you can proceed to flashing a rom using the fastboot command.
kmad86 said:
I'm a rook when it comes to the command stuff. Some quick questions and I think I can be on my way.
1. How do I open a command prompt to my ADB and Fastboot directory? I have no idea what that means. Do I make a folder on my desktop titled Nexus 7, and inside that put something?
2. I can't boot into Android so what do I do when it says "if you're booted into Android" do I just put it in fastboot and say good?
(The last command prompt stuff I did was in 2002 for my computer using Windows XP it's been a while. Kinda rusty)
I appreciate the help guys, I'm learning! I guess I could send it in, but I like the learning experience and challenge.
Click to expand...
Click to collapse
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
MarioES said:
I'm not very good at this stuff either, and a manual flash was the first thing I tried. You'll get it!
If you can't boot into Android skip step 3 and go to 4, which is the same (just that you're loaded into the bootloader, which you should be able to access).
About the other issue, google it and look for a londatiga.net link (can't post links as a new user). All you need is the Android SDK
Click to expand...
Click to collapse
I found FastBoot in the Platform-Tools folder, but I double click it and a command prompt looking screen pops up, but disappears.
EDIT: Got it.
Thanks for the help
Ok, so I figured out the command prompt.
For those of you searching for this, and in the same situation as I, I clicked on Start>and searched Command where my command prompt popped up as C:\users\admin> and i was really confused. From there my Toolkit was in Desktop>Nexus 7 Stuff>Toolkit>ADT Bundle>SDK>Platform-Tools.
I typed in command prompt "cd desktop" and enter. Then I was at C:\users\admin\desktop> From there I entered "cd nexus 7 stuff" and enter. and on to toolkit, then the next until I was at platform tools. Then I followed the instructions and whala!
(Now I am stuck on writing "boot") i've searched and found nothing.
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
yes
Sent from my Nexus 4 using xda app-developers app
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well
Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.
spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?
g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.
No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app
I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium
Everything I found on this says volume + and power, which kicks me into download mode, not fastboot.
I've gone into adb and typed adb reboot bootloader, but that just restarts the phone and turns in on like normal.
I google the how to enter fastboot mode on LG G2 and can find plenty of post about being stuck in fastboot, but nothing on how to get into fastboot in the first place.
Found a tutorial here about setting up and using fastboot and thought I was set until I got to the part about "and using fastback", where it just says:
Make sure you have android debugging turned on in your phone (not really needed for fastboot but you do need for ADB), plug it into your computer and boot into fastboot mode...
I felt like watching "Much ado about nothing" when Denzel says; "The learned constable is too cunning to be understood"
Any direction is appreciated.
Hmm, I may have written that guide... Just checked and yeah should have been more clear I'll change that up. It should have read the USB debugging was needed for adb (not for fastboot) so when you can issue
adb reboot bootloader
But after that I did mention to check device specific forum for answers on how to get into fastboot/bootloader and being I've never held an lg g2 I took a quick look around.
Unfortunately the only way that I found that people said works every time is to wipe recovery to get into bootloader mode as the recovery you guys currently have disables something due to a patch getting custom recoveries to work
So yeah, I would advice to speak with someone knowledgeable about your specific device before you just wipe recovery
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Out of curiosity, is there something specific you need to do with fastboot or are you just curious about your phone?
Click to expand...
Click to collapse
the current thing I've been trying to straighten out is that despite being rooted and installing TWRP, I can't install ROMS. I tried CM 11 and Hellfire so that I could put kitkat on, but gave the following:
Error executing updater binary zip.
One of the answers I found said that I had to go back to TWRP 2.3 (I'm using 2.6) and I believe that's where the whole bootloader thing came into play, because it was the way to 'downgrade' -
So then I found Philz touch 6 (as I understand it a mode of CM 11), but here he talked about fastboot and lokifying items. Here's the link:
http://forum.xda-developers.com/showthread.php?t=2554053
In the end it still comes back to the "can't load ROMs" issue. Just want a completely stripped down Kitkat that I can add the stuff I want without the bloatware.
Thanks in advance.(and the thanks button was hit on your reply)
For KitKat you should need a newer recovery with SELinux support which I believe is 2.6.x and newer for twrp, 2.3 I doubt would work if there even is one for your phone
But yes fastboot is often the best way to change recoveries but not the only way.
If there is a flashable.zip you could install new recovery from old
If your current ROM supports the flash image binary you can use a terminal emulator
You can use adb to install
Or even apps from the market
I would look for the latest recovery for your device, twrp, cwm, shouldn't matter so long as its new and then find what way works best changing for your phone.
The update-binary issue is often a sign that you need to change recoveries
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Unfortunately without having your device I don't know if I can give you the best answers but feel free to ask
Best of luck!
Click to expand...
Click to collapse
Thanks again. I have adb and the script for loading TWRP 2.6.xx. I unrooted and rerooted the phone, because I wasn't sure how to replace the recovery... Now I think I realize that I could just find another recovery image and place it in the same file as the loki flash and that will flash it (At least that's what I understand at present).
If that's the case, then downloading the Philz touch 6 would work... but not wanting to brick it, I'm still asking and reading.
Hello Guys.
I am having a similar issue. I have a new ROM that will not run because of a faulty lg set up wizard that always force closes and I can not get passed it and a nandroid that for some reason is corrupted. So. This fastboot seems to be a dead end it looks like a quick learning curve of ADB is the only viable answer. I have installed all SDK Manager with ADB Tools and also the required Jarva JDK and LG drivers. The phone is turned on (at the beginning of the faulty setup wizard) In CMD my device is found when typing in 'adb devices' So. I am already to push a new ROM over to the phone.
Do either of you guys know the adb command?
Help would be appreciated.
Thanks
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
I found that the best way was to load flashify, that did the trick so I could start trying out ROMs... so no on to the next step - finding a 4.4.2 stripped down stock and the LG stuff I actually like.... thanks again.
demkantor said:
You can't actually flash a new ROM with adb, but you can either push it phone with adb and then flash in recovery. Or if your recovery has an option for adb sideload then use this.
Also setup wizard crashing is usually the fault of wrong gapps or not wiping before flashing a rom
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
dodge3003 said:
Thanks for the reply!
I know it's not possible to flash a ROM via ADB. I have everything set up, ADB etc, etc. My phone is turned on and adb is seeing it but I can not work out the command to push. Every time I try to push I just get a long list of ADB instructions (I think they are) but nothing gets pushed. I have read lots of instructions on how to make the command but I still must be doing something wrong.
Here are my parameters;-
adb push/C:\Users\dene\Desktop/cm-11-20140210-SNAPSHOT-M3-d802.zip/sdcard
Am I missing some spaces I am not aware of? Are all my slashes the right way round and in the right places? Is my 'sdcard' destination designation correct seeing as there is only internal storage on the G2?
Another problem I am having is that ADB has no problem seeing my sevice EXCEPT when I boot in to recovery (TWRP). When in recovery I lose coms between my device and pc. Hence I can no do TWRP ADB side load (I have tried). I have all the correct LG drivers loaded. Except MTP keeps failing to install? Any ideas?
Not to be mardy about it or hassle you but I am fairly house bound and live out in the country and really require my mobile phone. I have spent many hours trying to figure this out. Any help with the above would be much appreciated?
PS. I did a very thorough wipe, I always do. The gapps are built in to this ROM!
Thanks
Click to expand...
Click to collapse
I HAVE SOLVED THE ISSUE! Thanks for your assistance mate but in the end I just went back to stock using this amazing thread:-
http://forum.xda-developers.com/showthread.php?t=2432476
in conjunction with this amazing video;-
http://www.youtube.com/watch?v=IixQjo_hyz8
So! I am now un rooted and back to stock. Time to start the rooting ana ROMing all over again.lol
Thanks
Glad to here!
You need a space after push
But it usually easier not to enter the location of a file while pushing so cd to the directory first like
cd C:\Users.....
Then once there adb push /nameoffile /locationonphone
But if you don't want to cd, I see you have widows, depending on version you can just right click in the folder your file is located and choose open cmd here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Need Help
As I thought I bought LG G2 D-802, but it was D-800 and I accidentally install the lollipop of D802 and now it's in bootlap.... I can only get into fastboot and whenever I try to flash .img of D-800 or D-802 it just stuck at "writing .img"
What to do to unbrick the phone and bring it back to live. I tired the adb and fastboot cmd method on windows 10 and windows 7 but no success. It's just stuck at writing .img file.
I know. You guys have heard it all before...but
I was using WugFresh to re-flash back to 4.3 from 4.4 and the recovery was taking so long. After an hour of running, I was moving the device to a coffee table when the cable fell out.
Hay, why isn't a message include in WugFresh like the backup process as to approximately how long this process takes? That brings up another issue in general with these old N7s is that these micro-USB female connectors get loose after so many years of use, makes connecting and charging difficult.
But I digress.
I have read often in the XDA forums about a factory reset ‘from bricked feature’ in WugFresh, but I can not find that feature anywhere where ‘bricked’. anything is. If it is there, where is it?
Anyway, how can I recover the bootloader and everything without having to learn doing everything via a cmd line or .bat process?
These are the facts:
Nexus 7 2012, 8g, re-flashing back to 4.3 from 4.4, using Nexus Root Kit
v1.8.2, Flash Stock + Unroot (I had read in XDA Forum somewhere where it was suggested to go back to a factory vs to use this option).
The N7 is currently has one of 4 states available: Bootloader screen (with below stated status), Google initial screen (with "Start" Showing and "Booting failed" in the upper right corner), or it can Power off. Recovery Mode is an option, but does nothing but cycles to the Google initial screen.
In Fastboot mode the status says this:
FASTBOOT MODE
Product name - grouper (it got that far)
Variant - grouper
HU version - E3
LOCK STATE - UNLOCKED
Bootloader Version - N/A
Serial Number - 015d2109ab281807
SIGNING - not defined yet
Of course I can't get an MTP connection to Microsoft XP, but an "Unknown
device" error shows up under USB when I connect the cable. No drivers from WMSDK kit or any from WugFresh worked.
Oh, and by the way, the WugFresh backup didn't work for me. It saved next to nothing, but I have another type of backup that works, so no worry.
GOT ANY SUGGESTIONS?
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Looks like it will be fine follow the sticky for reflashing a factory image.
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Don't use toolkits for flashing devices just learn the adb commands its much safer. The reason there is no time for completing a flash if it varies with devices.
FYI the wugfresh option you are looking for is return to stock/unroot with soft bricked checked
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Click to expand...
Click to collapse
{Q} Thanks Captain, I have been following the Guide instruction, but I have some other questions before I proceed.
In your Quote above you said “follow the sticky for reflashing”, I don’t know what you mean by a “sticky” and I have looked though a lot of the pages after the "[GUIDE] Flashing a Factory Image with fastboot / return to stock" and I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Since I didn't know that answer, I went a head and read the whole Guide and other questions popped up: If I have to download Java SE JDK will the Version 6 I already have work? The Oracle website you directed me to won’t let me download Version 8; however, Android SDK did accept Version 6 to install.
I did re-download all the drivers as instructed and put the JWR66V bootloader into the place of the JWR66Y one and then inserted bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, and flash-base.sh all into <my sdk directory>\platform-tools as the Guide says.
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
I don’t know what you mean by a “sticky"
Click to expand...
Click to collapse
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top.
I can not find “reflashing” mentioned yet. Did you mean to go directly to the "Flashing the Factory Image" section in the Guide and follow that?
Click to expand...
Click to collapse
Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Now that I think I have it all ready to go, will I still have to run the Adb cmds to install Drivers?
Click to expand...
Click to collapse
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Now its Driver installation issues
Captain Sweatpants said:
A sticky is a thread that a mod has "stickied" meaning that it won't move down the forum but stays at the top. Yes that's what I meant.
Just follow the whole guide and take it slow if you have been relying on toolkits like wugfresh this will be a not of a learning curve
Yes you still have to install drivers you shouldn't need adb to do that just make sure windows has the correct adb and fastboot drivers installed. If you have been using wugfresh NRT the drivers should be OK.
As your device is soft bricked where the guide says use the command adb reboot bootloader you will need to manually enter the bootloader by pressing power & vol +
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
{Q} Installing the driver now seems to be the issue. I tried a couple of things:
1. I know this was not exactly appropriate, but I went into Device Manager, located the USB “Unknown Device”, tried to update
the Driver after selecting it, directed the screens to both the ‘supposed’ drivers in WugFresh and Adb subdir’s. None took.
2. Then I forced a new device though the Control Panel’s, Add New Hardware, navigated to “Add a new hardware device” and
selected “Google Nexus 7 ADB interface”, and it created the new device. The Device Manager showed and error on the
device, so I refreshed it with the Adb driver, with no different results.
3. I then added the device driver “Google Nexus Bootloader Interface” via Add New Hardware
4. I rebooted the computer. After it came back up…
5. I looked at the Device Manager with no change in the status of any of the Android or the Unknown USB Device.
6. I insured the N7 was in bootloader mode by rebooting with volume keys/on key.
7. I went ahead and ran “adb drivers” cmd after entering the “cd’ cmd. I got the following:
Bear with me as I have no screen printing capability at this time.
>Command Prompt screen:
>C:\<adb dir>\platform-tools> adb devices
>List of devices attached
>C:\<adb dir>>\platform-tools>
And as you can see, NO listing showed.
So what’s next? I have another XP computer I can try this on, but I will have to get all the Abd stuff over to it 1st. While you answer I will try that.
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
Captain Sweatpants said:
Your Nexus in fastboot mode is not an adb device so it won't show up. Change your command to fastboot devices and it should work.
If you are still having driver issues download USB deveiw and remove anything that looks like a Nexus bootloader interface or adb device.
Click to expand...
Click to collapse
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
nickynooner said:
OK, I have tried what you said with no results. If you would be willing to work with my computer directly, I have a method of allowing you to see what I see. The 2nd computer I have the N7 on right now have very little personal stuff on it, and I would be willing to let you access it. I have set up a temporary e-mail address [email protected] you can send an e-mail to with your e-mail address, and we can correspond directly, thus I can give you the access you need. I know you are else where in the world, so I would be willing to leave my computer up for you to see it all when you like. What do you think?
Tell me the final score of Zebre and your teem, what date it occurred, and what the sport is so I know it is you. Send the answer to the e-mail above, so I know it is you. I’ll only give you a short time to respond.
Click to expand...
Click to collapse
It wouldn't work as I would need to be able to press buttons on the nexus.
If none of this is working then try wugfresh NRT again make sure you have the most up-to-date version from www.wugfresh.com its 1.8.2
The option you are looking for is unroot/back to stock there is an option for soft bricked make sure that is ticked
Sent from my Nexus 7
Hit thanks if I've helped
The Fat Lady Just Sang an Unhappy Song!
Hi Captain,
Thank you for all of your help and patience with me. I have read a lot more about the status of my device through looking at the XDA forum about other devices that have the kind of issue I do, and I have concluded mine is HARDbricked. I went ahead and ordered another motherboard off of eBay. My device was an 8G and I got a 32G replacement, making sure it was for my age of my N7. XDA forum and other websites say the boards are interchangeable. I was thinking about buying a new device anyway and this way I can upgrade and still have the same familiar device with no learning curve of a new one.