Related
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
erica_renee said:
is there no nv flash for this device.. this is what you need. to boot into nv flash and flash the boot-loader.. .. I think this is the only way. There is another thread that talks about this.. Not sure if they managed it or not but they were very close i think..
Click to expand...
Click to collapse
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
mateorod said:
Yeah. I used NVflash on the wife's transformer 101. I saw that thread, but i think the resolution was that they finally got close enough to find out they didn't know what they were talking about.
That sounds worse than I intended it. I mean that they simply weren't very experienced NVflash users and so they didn't know what they were missing until they worked at it. Seems a while away, if ever.
I have a second Nexus 7, i am wondering if i can do something with the hardware, maybe. Is all of the storage in one chip? I have the 16 gig, i seem to remember the 8 gig has n actual emmc.
I am going to try and stay away from devices with virtual sdcards from now on. This was just a folder in storage, WTF? I am not even sure how this is possible. Hardlink mayhem, presumably. The device had only ran stock.
Click to expand...
Click to collapse
yea there is only one storage device inside the nexus.. its all symlinked
If you could get the driver going, send a adb reboot-bootloader command, the bootloader should work then.
Will the next nexus have a longer screen?
Same problem here.
mateorod said:
I deleted a folder in /data that had some installed software in it. Once I deleted it, the N7 immediately began spitting FCs at me, Aldiko keystore, the WinnIME app, some .pngs, all FCs.
I rebooted and it hangs on the Google screen. I can get into the bootloader by holding volume down, but the menu usually navigated by volume buttons stays on Start and the power/enter button does nothing. No recovery, obviously.
Most depressing, fastboot and adb do NOT work. The closest analogs to this problem I have found through this search is people who accidentally erased their bootloader. It looks like mine may be corrupted, which could end up being no better.
I am out of town and away from my primary Android computer. The one I have with me is Windows, with an Ubuntu VM that has the SDK and confirmed working ADB and fastboot usually. No dice now, like I said.
When I plug in the tablet through USB, the Windows host attempts to install MTP drivers and fails. I would try and install the Windows SDK and try to get a connection through some of the Windows drivers, but the internet where I am cannot take it.
Any ideas? I am thinking the device is toast, but since I would be the first I have heard of to be able to get into the bootloader and still brick, I thought I would open it up to the community.
Details: I HAD CWM, no more. Stock, rooted only.
Click to expand...
Click to collapse
Hi, everyone!
I've got the same problem with my Motorola Razr D3 (XT920). After a system update, something bad happen while the system tried to install the last patch realeased by Motorola. I still can access the bootloader but nothing is working.
So I wonder if any of you guys have figured out how to reinstall the bootloader.
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.
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.
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.
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Wish39 said:
Wrong forum dude. This forum is for the 2012 Nexus 7, not the 2013 Nexus 7.
Click to expand...
Click to collapse
Oopsie daisy.
Thanks, I will repost in the proper forum!
drjboulder said:
Oopsie daisy.
Thanks, I will repost in the proper forum!
Click to expand...
Click to collapse
It's fine. People make mistakes sometimes.
Also it looks like something majorly screwed up your Nexus 7. Hope you find a solution to fix it up sooner or later.
drjboulder said:
I need help reviving a Nexus 7 2013 Flo 32G.
This tablet has sat forgotten and dead for a couple of years. I am trying to bring it back to life. It has been several years since I have done any rooting and flashing on Android, so I am looking for a little guidance. I honestly do not recall what has left the device in its current state. But, basically it has no OS installed. The boot-loader version is FLO-04.04. I can get into recovery. The installed recovery is TWRP v2.8.6.0. I do not possess any Windows machines. I have Android Debug Bridge version 1.0.39 installed on Ubuntu 16.04.3 LTS. MTP is enabled.
But that is it. I am not able to locate the device through ADB using ‘adb devices’. As I say it has been several years since I have rooted around Android or used ADB. I did not use Linux the last time I was doing things like this. So, I am stuck as to how to proceed. I was hoping it was going to be a pretty straightforward process of picking a ROM and GAPS and flashing.
Of course not even being able to ABD into the device leads me to believe that, while not in over my head, I made need some help going forward.
Anyone care to volunteer some first steps?
TIA
Click to expand...
Click to collapse
can you connect through fastboot?