I'm on TWRP 2.3.3.0., and my computer is W8 Pro. I've searched but most people seem to be able to get adb working during the bootloader at least, but not for me. I've tried sideloading a zip through the command prompt (and picking the adb sideload option in TWRP) but it tells me that adb is not recognized. I've tried using the Nexus Root Toolkit to restore a backup I have on my computer, but, yeah, no adb. I was wondering if disabling driver signature enforcement was temporary, so I went through the menus and disabled it again on my computer. I've used the cable/port that I rooted it with but I've also used different cables and ports as well. Why isn't this working? Am I bricked?
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
xbox1513 said:
Have you tried jromflasher for nexus 7? With that tool you can wipe your system, upload ROM, temporary load custom recovery, and flash the ROM.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Error 103. I think my device needs to be booted into an actual ROM.
I thought that maybe the drivers from plugging my phone in were interfering, so I used the Nexus Root Toolkit again, and went through the driver installation for a second time, deleting all the old ADB drivers and such. Well, when I tried to install the RAW drivers, I get "Windows was unable to install your unknown device," and basically it could not find the driver software and to check the company website and so on. Did I just dig myself into a deeper hole? Gah! I wish I could remember which wipe option deleted sdcard so I know to never do it again.
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
korockinout13 said:
You know you won't get adb while in bootloader? You need fastboot.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
It says "fastboot mode" on the bootloader.
Letitride said:
OP is using Win8 - might want to try to do it with a PC or laptop running Win7 or Vista OS and start fresh by loading the drivers and/or use Jromflasher - borrow a friend/neighbor's PC to see if it can be jump started, assumed that s/he cannot get it to boot into Fastboot and/or Recovery as the file systems are likely corrupted. (I have an old/aging laptop running Windows XP SP3 that's set aside for fixing often the impossible)
Otherwise, it might be time for an RMA to get it repaired by Google/Asus and/or exchange - it could cost $$ if they determined that the warranty has been "compromised" ...
Click to expand...
Click to collapse
Thanks. I'll try this later tonight. Would they RMA in this scenario, even though it is my fault? Assuming I can't get it working.
I don't understanding why you would RMA? You can get into twrp right? So you can still flash ROMs and whatnot. Just need to get adb installed on cpu
You can also try "disable driver signature check" on advanced reboot on windows 8.
Sent from my Nexus 7 using Tapatalk HD
Bullonie said:
It says "fastboot mode" on the bootloader.
Click to expand...
Click to collapse
Well....use fastboot then.
You should have done some reading before you started flashing ROM's. You dont seem to even know what fastboot is.
Have you tried downloading the android sdk from Google and installing their usb driver?
Sent from my Nexus 7 using XDA Premium HD app
Adb works in recovery and in Android OS, only fastboot works in the bootloader. Installing Windows 8 messed it up for me, but I simply grabbed the Nexus 7 driver from ASUS'S website. I suggest you read and learn how to use fastboot.
Sent from my Nexus 7 using Tapatalk HD
Related
I have no idea what i did, but my Nexus 7 formatted every file on there, there's not even a rom it can boot into....I can boot into recovery, but I have no idea how I can bring a file and load a rom on Nexus 7 because I can only get to three things..bootloader, recovery and google (unlocked) that's stuck there because of no rom.
using nexus 7 toolkit...but i'm probably doing something wrong...getting device not found.
can someone give me a noob guide on what i can try to fix this
Use the flash back to stock option with device will not boot checked on wugfresh toolkit
Sent from my Nexus 7 using xda app-developers app
the computer is not picking up the nexus 7...it makes a sound when i connect or disconnect the USB, but it doesn't show up on the computer.
really need help...i'm sure this can be fixed since i can boot into recovery or boot loader...
djricekcn said:
the computer is not picking up the nexus 7...it makes a sound when i connect or disconnect the USB, but it doesn't show up on the computer.
really need help...i'm sure this can be fixed since i can boot into recovery or boot loader...
Click to expand...
Click to collapse
Did you try installing the driver package that comes with Wugs?
Its sounds like it isnt finding the drivers to me.Are you using a custom recovery or the stock?
Try using Odin and see if it recognizes it.
Kodiack99 said:
Did you try installing the driver package that comes with Wugs?
Its sounds like it isnt finding the drivers to me.Are you using a custom recovery or the stock?
Try using Odin and see if it recognizes it.
Click to expand...
Click to collapse
i thought odin is for samsung devices...where do i download one that works with N7?
I'm trying to install drivers, but it's not doing anything but opening up pictures with how to install in Wugs.
using wugs, it does pick up as grooper under device manager, but doesn't show on the MY COMPUTER section
not sure what you mean by recover or stock, but i can get into Clockword Mod Recover 6.0.1.0...does that help?
**tried odin 3.7 but it isn't doing anything
LOL sorry I got a few devices and 2 out of 3 are samsung.
Maybe try to install the drivers in the toolkit here http://forum.xda-developers.com/showthread.php?t=1809195 ,if you can get a image on there you should be able to flash it with Clockwork if you select install from zip.
I dont suppose you made a backup with Clockwork?
If you can get adb working you can easily flash it back to stock by following this http://forum.xda-developers.com/showthread.php?t=1907796
how do i do this when i can't boot into android
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Install the abd driver - detailed instructions for installing or upgrading and existing driver on your version of Windows can be found at http://developer.android.com/tools/extras/oem-usb.html
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are connected to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
can't figure it out....
"devices not found"
djricekcn said:
can't figure it out....
"devices not found"
Click to expand...
Click to collapse
Did you install the drivers from the nexus toolkit?
And maybe try a reboot of your pc,and try unplugging usb and replugging while in fast boot.
Also check in CWM and see if a backup has every been made even if its old, its better than where you are now.
there's no backup of anything on the nexus...everything got wiped somehow. nexus 7 toolkit keep tellingthe resource loader cache doesn't have loader mUI entry" whichs tells me it's ok..
adb: unable to connect backup
unplug / reboot / different ports...basic pc stuff already done
Maybe try using a different cable,Other than that maybe try a different pc and see if it loads a default driver to at least give you access to put a zip file on it to flash,could be your driver is corrupt on that pc never heard of it installing a nexus as grooper.
Besides that I'm at a loss.
Best of luck,hopefully you get it figured out.
so...i've tried the following already just to make it clear...
i already tried all the basic pc things
-switch usb ports
-reboot pc
-use usb2
-use usb3 ports
-use a different computer (one 8, one XP)....both...i don't really know what to do cause instructions seems to be mostly in 7 and/or just not working on 8
-rebooted asus n7
if someone can give me step by step, noob guide...instead of saying try thing / that, it may help me.
djricekcn said:
there's no backup of anything on the nexus...everything got wiped somehow. nexus 7 toolkit keep tellingthe resource loader cache doesn't have loader mUI entry" whichs tells me it's ok..
adb: unable to connect backup
unplug / reboot / different ports...basic pc stuff already done
Click to expand...
Click to collapse
A lot of people who think every thing got stopped find their files under /storage/emulated/0
Sent from my Nexus 7
Clean ROM 2.5 - leanKernel 0.7
Try this to get adb working it was a fix for this guy. If adb works you can flash stock images.
http://forum.xda-developers.com/showpost.php?p=30230955&postcount=8
If you're using one of the toolkits you should be able to push an image to it.
Sent from my HTC Desire S using xda app-developers app
Kearkan said:
If you're using one of the toolkits you should be able to push an image to it.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
which is what I'm having trouble with...it's not picking up....
and can't find media player 13....only find some sort of pack..tried it...not working becuase it's not applicable with W8 even though i downloaded the W8 version..arg.
http://windows.microsoft.com/en-US/windows/download-windows-media-player
Included in Windows 8 and Windows 8 Pro, but doesn't include DVD playback. Go to the DVD playback for Windows page to find out how to add DVD playback to Windows 8. To get Windows Media Player 12 for Windows 8 N and KN editions, download the Media Feature Pack.
Click to expand...
Click to collapse
I had exactly the same problem. I was able to restore mine to stock 4.2 without ever having the Nexus 7 show up under my computer. My understanding is that it isn't supposed to show up there unless it is booted into android, but I could be wrong. Anyways, just try downloading the stock N7 firmware and installing with the Unroot and restore stock option in the Wugfresh Toolkit, and if you want root and custom recovery back, simply use the option to reroot and follow the instructions. That's what I did and it worked like a charm.
Sent from my Nexus 7 using xda premium
was able to get it working with a MAC, can't adb push on the computer i have at home...not recognizing it even after drivers installed...well it recognizes but adb doesn't.
So I got my n4 last week and I've been trying to unlock and root it to no avail. I've tried using the toolkit as well as using the method indicated in another thread on xda. I keep getting errors when trying to install the drivers.
I've been able to get the adb driver installed on win 7, but not the fastboot driver (using the toolkit).
I've even tried installing the drivers using the toolkit on a VM running xp without any luck.
Could someone please help me out with this? I remember having similar issues when rouoting my captivate, but I was able to use my work laptop to install the drivers (I don't have admin rights anymore).
Sent from my Nexus 4 using xda app-developers app
A) Proofread.
B) Reboot into recovery and plug the phone into the computer. Go to device manager on your computer, look for the USB device with the yellow exclamation point, update the driver. Reboot your computer.
estallings15 said:
A) Proofread.
B) Reboot into recovery and plug the phone into the computer. Go to device manager on your computer, look for the USB device with the yellow exclamation point, update the driver. Reboot your computer.
Click to expand...
Click to collapse
A) Wow that was bad, corrected
B) No devices were displayed in device manager when I booted to recovery. By the way, when I tried to update the drivers in fastboot mode, I kept getting errors.
Perhaps an earlier driver needs uninstalled? Check this thread: http://forum.xda-developers.com/showthread.php?t=1992345
I tried that driver, that is the driver I referenced in the OP, sorry for boy linking.
Sent from my Nexus 4 using xda app-developers app
Austin Ag06 said:
I tried that driver, that is the driver I referenced in the OP, sorry for boy linking.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I was actually referring to the comments in the thread. A ton of people had issues installing. I thought you might try some of their methods.
My N7 is soft bricked. I was installing a ROM but the file was corrupted. I can't perform a nandroid restore because I can't get into recovery. I'd push a new recovery via adb but my computer won't recognize my N7 in fastboot. I've tried installing Universal naked drivers 0.72 manually but it oesn't work. What else can I do?
There was no need to open a new thread... And you still haven't told us what os your computer has. Anyway, I personally use the official drivers from the Asus website.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
There was no need to open a new thread... And you still haven't told us what os your computer has. Anyway, I personally use the official drivers from the Asus website.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Windows 8. I found out how to get rid of driver signing requirement in Win8 and the installment worked. Thanks for helping out!
Ok, tired of waiting for the OTA KitKat update for my Nexus 7 2012 tablet, I downloaded the OTA update and sideloaded it with adb. Got a status 7 error and now it's stuck on a bootloop. Thing is, my Windows 8 laptop won't recognize the device anymore (code 43 error on device manager) when on recovery or bootloader. There's even no way to instal google's usb drivers or anything because it says the device malfunctioned. I downloaded the factory image but, obviously, can't sideload it or do anything with it.
Please give me a hand with this, I'm really desperate.
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
More detail would be nice. What did the bootloop go between? Had you installed any custom recovery like CWM?
Are you still able to access fastboot mode?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Sorry, wasn't sure what you needed. The bootloop esentially goes from recovery to off and then to recovery again. I am able to go to fastboot normally (power and volume down when off).
Wanting to root the device a while ago, I unlocked it and rooted it whitout issues. Since the 4.3 update though, it was a little more difficult to root so having no time to research I just left it at that. That's all that was done to the Nexus 7. No Custom Recovery, no ROM, no nothing. Now, waiting for 3 weeks for KitKat, decided to sideload the OTA update (I did check the version was my device's version) the status 7 error appeared and all hell broke loose with the computer not recognizing the device.
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Duplicate post. Please erase.
nobody_nowhere said:
Well, since you still have access to your fastboot menu, there isn't anything to worry about. Once you resolve the driver issue, you must be able to re flash the image.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Yeah, that's what relaxes me a bit, but I can't seem to fix it for 20 hours straight. I use this for studying.
Well, I suggest using another computer (a friend's or relatives') or installing a Linux distro like ubuntu. Oses other than Windows usually don't have such problems. I suggest you download something called adb gui which as I recall did a pretty fine job of 're installing the drivers for me.
But then, please do correct me if I'm wrong... I think that you must first use the device on adb and get the drivers installed and then only can you use it by the fastboot interface.
Sent from my GT-S5570 using xda app-developers app
I used Wug nexus root toolkit to install drivers (windows 8.1) there are clear instructions (if you click manual or something similar) how to get drivers to work.
Yeah, actually I did use the toolkit when I was trying to update to KitKat. Thing is, it doesn't work since the bricking occurred.
Yeah, I'll try on another pc, and I'll keep you posted.
Thanks
Sent from my Nexus 4 using xda app-developers app
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Johnson90512 said:
I'm having a very similar issue. Mine will try and bootup but just stays on the boot animation for as long as I could wait, 10 minutes or more. bootloader is working just fine and I should be able to use fastboot commands to resolve the issue. I'm not able to get to recovery for one reason or another, but it is updated to the latest CWM.
The trouble I am having is the same though. I cannot for the life of me get the drivers to work. I have tried it on one win8 pc, and one win7 pc. I haven't tried any of the toolkits to help with driver installation on the win8 pc yet. I also have another pc that I am going to try also has win8 on it as well. If you can get the drivers installed, please post a reply as to what you did here, and I will do the same, from what I have been able to find you and I aren't the only ones that are having this issue.
If the windows route doesn't work, I have a copy of Ubuntu that will be going on the computer to see if that resolves my issues. Also, may want to try another cord, I have a couple that are charge cords only. Once getting the drivers working it should be a very simple job.
Click to expand...
Click to collapse
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
Since you say that you do have ubuntu I suggest using that to fix your issue.... just download and execute the command fastboot from the terminal
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
It pretty much cancels out any problems with drivers.
It is easy to do.
It takes 5 minutes to boot up and test? Try it for yourself
Sent from my Nexus 5
Johnson90512 said:
Do you think that will be easier? I've not done a whole lot of work with android using linux. I have experience with both separately, but not together. any insight would be fantastic. Have you tried running a linux distro yourself to solve your issue?
Click to expand...
Click to collapse
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
nobody_nowhere said:
If I did have any driver issues, the first thing I'd do is reinstall drivers, and if necessary, Windows itself, because I like everything to be working perfectly.
But supposing that that was not an option and I needed my phone or tab real bad, ubuntu would be my first choice. Especially because the concept of installing 'drivers' doesn't exist in ubuntu.
No, that should be fine. As long as you have used terminal before and you know the basics.
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the advice, I will give it a shot this evening, and let you know if this works. I'm sure that it will.
Alright, so I got SDK up and running on Linux! It was a little bit of a pain, but it installed just fine. Once I got it all installed I was able to see the nexus 7 through fastboot! From there I was able to reinstall the bootloader. Then was able to get to recovery to do an adb push to get a rom of 4.4 on to it. 4.4 installed just fine. All problems are fixed Good suggestions guys!
Hey guys,
a few hours ago I tried flashing the new Ldroid Rom onto my Nexus 7. After flashing the rom my tablet took ages to boot up and after the bootup it said i had to enter a password to encrypt the data (i never set encryption). after entering a random password android reported that the password was right but the data corrupt and i'd have to do a factory reset. after entering twrp i realized that the device couldn't mount anything except system. i wiped/formated everything except system and tried booting into android. this time i was stuck at the google logo. after entering recovery mode again now twrp couldn't mount system and sdcard. so i formated both and now i'm here with an absolutely empty nexus 7. i tried to use adb sideload to flash a new rom but my pc doesn't recognize the device and neither does fastboot. i tried reinstalling adb and fastboot drivers, i used universal drivers, i used drivers from toolkits, i did many many pc and tablet restarts, i reinstalled android sdk several times, i used different adb/fastboot locations, i even tried using a different pc trying the same steps. no change, only thing i get is that the tablet gets recognized by the device manager as an adb/fastboot device, nothing more.
Does anyone of you know a possible sollution for my issue?
Thanks in advance
P.S.: i've been researching the internet for this issue for the past hours and couldn't find any sollutions, so please don't say stuff like "use search function"
P.P.S.: My other devices get recognized without any issues with the same cable.
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app
Masterloki666 said:
I would suggest using wugs awesome software you need to make sure all partitions are wiped and repaired to which ever format you are trying to use ext4 or f2fs and through wugs you can flash new ROM through fastboot wigs has save my ass a few times one should not try to do tedious tasks after a long night of drinking hope this helps let me know if ya need more
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply.
The thing is that the device doesn't get recognized in fastboot mode by the fastboot interface. But I'll try anyways as soon as I'm at home again...
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app
Masterloki666 said:
Wugss also has a option to restore soft bricked devices that should do the trick for ya if all else fails
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
didn't work :/ device doesn't get recognized by fastboot but it's shown as fastboot device in the device manager
OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app
Masterloki666 said:
OK check verify all partitions are set and you can try to use adb and you can push a new os I believe that should work
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
how can i do that?
http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app
Masterloki666 said:
http://forum.xda-developers.com/showthread.php?p=56749959 here's a post with syteps to fix and get you set up
Sent from my AOSP on Grouper using XDA Free mobile app
Click to expand...
Click to collapse
Will not work as my device doesn't get recognized by fastboot.
OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app
Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: DobrĂ½:
Masterloki666 said:
OK are you on the latest twrp recovery if so you can go into that and enable mtp get the ROM and gapps and all other files you want to flash and drop them onto your device the only thing is it for some reason won't let you transfer zip files that's fine just rename from zip to txt
And it should work sorry for the delay in response hope that works for you lol
Sent from my d2lte using XDA Free mobile app
Click to expand...
Click to collapse
no I don't even if I had, it wouldn't work because I have no system on the tablet...
wwarrel said:
Excuse me I do not write good English. Today I had a similar problem. Tablet remained in bootloader and laptop does not see it
I used NRT function Back to Stock and click on Soft-Bricked / Bootloop.
Tablet runs on Lolipop
wwarrel: DobrĂ½:
Click to expand...
Click to collapse
Will not work because you need fastboot for it which is not working for me...
Alright I used my macbook for adb/fastboot and there it somehow recognized my device and I could use fastboot to do a factory reset. I still don't know why two independent windows systems did not recognize my Nexus 7 but I got it fixed. Anyways thanks to everyone who tried to help me in this thread!