Had a good look around but don't seem able to find the answer
My daughter has an unrooted Nexus 7, for which the pass number has been forgotten
Have tried to hard reset to no avail, have used the standard methods shown on the net
The thing goes to a google logo or just freezes whether I connect to pc or not
Have downloaded nexus 7 toolkit, but cannot install drivers (option 1)
Have downloaded pdanet to install adb/fastboot, but it tell me its unable to tether
Remember that I am unable to get onto the tablet so I am unable tick usb debugging
When I connect the device, the autoplay option opens, however using "open device to view files" is empty
Finally, I can follow instructions but don't have a clue what most of it means, so be gentle
Any help appreciated
How long have you let it sit at the logo?
Sent from my Nexus 7 using Tapatalk 2
Over 5 minutes, it then goes to the log in number square
had another go, pressed power button when in recovery screen, went to google logo then an android with red warning triangle, then back to log on number pad
Related
So after reading and trying how others on here fixed that very same problem I deiced its time to make a post and ask for help because those other methods did not work.
Ok I did something stupid and I went ahead and did a factory reset to my kindle. Yes I know it was a complete noob thing to do and I should have known better seeing that I have rooted and flashed ROMs on all my other android devices and never once did something that dumb but I did it this time. Now I do have a back up made and had it safely stored on my PC.
Problem is that I can't get into recovery it stuck on the FFF logo and holding down the button only brings it back up. When the device restarts windows recognizes it as an unknown usb device and won't connect and Adb also wont recognize the device or show that it is connected. So now I need to ask someone who is more knowledgeable then me on what to do next. Any help will be appreciated
Ok update: Was able to solve my own problem using the Kindle fire utility and by uninstalling the drive for the kindle through the device manager, then using the drive install_drivers.bat in the KFU folder to reinstall the drivers. I next unplugged my kindle from the pc, turned it off by holding the button on the kindle in and then restarted it with the usb plugged into the pc. My Pc recognized my kindle and I was then able to use KFUs Bootmode menu and once in there used option 1. to boot it in normal mode. Hope this helps anyone who was stuck like I was. My memory of which adb commands to use was a bit rusty but using the KFU helped with that part.
I have tried many options. My Nexus died shortly after a KitKat update, but it may have been frazzled by a faulty car charger.
Cannot access recovery mode.
Cannot get PC to see ADB device
Would replacing the USB board help?
Out of warranty so willing to try almost anything.
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
xateeq said:
Search for naked drivers and install them, then remove previous drivers from device manager and update.
And please provide as much info as possible about your setup before asking a question.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hi, I was only ever stock. Unrooted, but had USB debugging.
I sideloaded KitKat when it came out and installed the Google Experience launcher. Received an OTA a day later that was only 1-2Mb.
The sideloading worked perfectly using the adb sideload kitkat.zip.
The evening after the OTA and the unit died. It is possible that it was a car charger, but I think highly unlikely as it never affected a Kindle or Xperia Z. But now I cannot get the PC to even see that the device is connected and neither can I get Recovery Mode to fully start. I select Recovery Mode and all I see is the Google logo. I have tried all sorts of button presses to get the android on its back with the red triangle. I may have missed something obvious so any suggestions would be a help.
Connect to wall charger if u cant get it to charge then it is ok,
try changing ur data cable that ur using to connect it to pc.
if ur tablet was not connected to charger when it dies then it is not the carger. OTA usually mess things up on modified/ rooted devices.
Hi, Thanks for the response.
I've tried all my cables. I can get the unit to charge no problem. It is just that I cannot get it to recover itself.
Powering on freezes on the Google logo and the CPU overheats like a really good overheating thing.
I go into the bootloader and if it doesn't freeze I can select all the various top level options. I have tried selecting Recovery mode and I cannot get that to work either. If I select Recovery mode and hit the power button it once again freezes on the Google logo. I have tried holding the volume up and pressing the power, but nothing happens. The only option I have is to power off again.
I had hoped that the nexus Root toolkit would help, but as it is never seen or recognized by the laptop I think I am totally screwed. I am thinking that my best hope is to sell it for spares. Unless there is a way of resetting the machine without a computer or being able to access recovery mode. I haven't seen anything like this.
I have a Generation 1 32GB Nexus 7. It has just been Factory Reset using the Pow, Vol +. Vol - combo to enter recovery and then using the Pow, Vol + combo to get to the menu to do a factory reset. I did this because my Nexus 7 was stuck on the X screen after several months of not being used, due to purchasing a more robust tablet.
I have successfully gotten past the X screen and I am not looking at the Welcome screen to select my language. On this screen I am getting what seems to be an infinite number of pop ups stating:
Unfortunately, Currents has stopped
Unfortunately, the process com.google.process.location has stopped.
Unfortunately, Google Play services has stopped.
Unfortunately, the process com.google.process.gapps has stopped.
Not in this order, but perpetual none the less.
I am able to get them to stop after several minutes of pressing OK, and I am then able to proceed to the select WiFi screen. Here, My nexus 7 is not finding any networks, where my GS4, laptop, and desktop all find 20+ wireless networks. My network is hidden, and I have attempted to connect to it via 'Other Network..." However it instant informs me unable to connect. I have also attempted a WPS connection and instantly I am told:
WPS failed. Please try again in a few minutes.
I have since tried every couple of minutes while typing this, ensuring my router is in WPS mode as well.
I very distinctly remember there being a skip button on this screen in the past, because when i purchased it was opened it in the car and was messing around with it before I got home, however no matter what voodoo I perform, nor how many times i restart the process and come back to this screen, I am unable to continue the initial setup.
Here is what I know FOR SURE about the state of the Nexus 7 prior to All my troubles.
1. The bootloader is unlocked, as I see the unlock icon on the Google splash screen.
2. It was previously set to USB debugging mode, however i am not sure if this gets reset when factory resets are performed.
3. I have installed apps to allow the USB port to connect to a dongle to attach external storage devices, this was unsuccessful, and prompted the purchase of the new tablet.
4. I have previously installed several custom ROMs, rooted, and in general messed around with the software successfully many many times. All were working fine.
5. The last ROM was the 4.2 Stock ROM
I have since updated my Nexus Root Toolkit program that I have been using since Wugfesh released it, and I am currently unable to get past the "checking ADB status". The program itself is not detecting the Nexus 7 in any regard, nor is my PC when connecting to the cable. I have tried several cables that are working for my phone, and have tried several ports that are also all working for my phone.
I have uninstalled all the drivers, and re-installed all of the drivers, and I have ensured they are the correct ones.
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen.
The Wifi was for sure working the last time I used the Nexus 7, as I was using it to control a Chromecast in my bedroom and play games.
Any help would be greatly appreciated, as I would like to not have to concede to scrapping my Nexus 7.
tzelo said:
I have a Generation 1 32GB Nexus 7. It has just been Factory Reset using the Pow, Vol +. Vol - combo to enter recovery and then using the Pow, Vol + combo to get to the menu to do a factory reset. I did this because my Nexus 7 was stuck on the X screen after several months of not being used, due to purchasing a more robust tablet.
I have successfully gotten past the X screen and I am not looking at the Welcome screen to select my language. On this screen I am getting what seems to be an infinite number of pop ups stating:
Unfortunately, Currents has stopped
Unfortunately, the process com.google.process.location has stopped.
Unfortunately, Google Play services has stopped.
Unfortunately, the process com.google.process.gapps has stopped.
Not in this order, but perpetual none the less.
I am able to get them to stop after several minutes of pressing OK, and I am then able to proceed to the select WiFi screen. Here, My nexus 7 is not finding any networks, where my GS4, laptop, and desktop all find 20+ wireless networks. My network is hidden, and I have attempted to connect to it via 'Other Network..." However it instant informs me unable to connect. I have also attempted a WPS connection and instantly I am told:
WPS failed. Please try again in a few minutes.
I have since tried every couple of minutes while typing this, ensuring my router is in WPS mode as well.
I very distinctly remember there being a skip button on this screen in the past, because when i purchased it was opened it in the car and was messing around with it before I got home, however no matter what voodoo I perform, nor how many times i restart the process and come back to this screen, I am unable to continue the initial setup.
Here is what I know FOR SURE about the state of the Nexus 7 prior to All my troubles.
1. The bootloader is unlocked, as I see the unlock icon on the Google splash screen.
2. It was previously set to USB debugging mode, however i am not sure if this gets reset when factory resets are performed.
3. I have installed apps to allow the USB port to connect to a dongle to attach external storage devices, this was unsuccessful, and prompted the purchase of the new tablet.
4. I have previously installed several custom ROMs, rooted, and in general messed around with the software successfully many many times. All were working fine.
5. The last ROM was the 4.2 Stock ROM
I have since updated my Nexus Root Toolkit program that I have been using since Wugfesh released it, and I am currently unable to get past the "checking ADB status". The program itself is not detecting the Nexus 7 in any regard, nor is my PC when connecting to the cable. I have tried several cables that are working for my phone, and have tried several ports that are also all working for my phone.
I have uninstalled all the drivers, and re-installed all of the drivers, and I have ensured they are the correct ones.
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen.
The Wifi was for sure working the last time I used the Nexus 7, as I was using it to control a Chromecast in my bedroom and play games.
Any help would be greatly appreciated, as I would like to not have to concede to scrapping my Nexus 7.
Click to expand...
Click to collapse
If you have a twrp recovery and a otg cable
You will have a few more options
Reply if you have those
tzelo said:
The only troubleshooting step I am not able to confirm is that the device is in fact in USB debugging mode, as I am unable to continue off of the WiFi screen..
Click to expand...
Click to collapse
Tapping all four corners of the screen will skip the WiFi part of setup not sure if the order you tap them in matters. Other than that boot into fastboot mode and follow the sticky for flashing a new factory image. Fastboot does not need USB debugging enabled.
Sent from my C5303 using xda app-developers app
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.
Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.
adnanahmed008 said:
Hello guys, my friend give me Galaxy A3 A300F. This device has many issues.
1. Device stuck on black screen with text "Samsung Galaxy A3" in middle & "Powered by android" in bottom. (I'm talking about the very first screen)
2. After 20 minutes, it proceeds to coloured samsung logo animation and boots up.
3. I noticed that it heats up during booting process & after too.
4. After boot up, it will restart automatically after few minutes.
5. If it holds up after booting for few minutes, i tested whether my computer detects it but i got no signal. I check it under DEVICE MANAGER and i found nothing. (With & without USB debugging enabled)
6. When i connect it to computer, the device start charging but there's no notification of USB plugged in.
7. I dial up *#0808# or whatever to configure usb settings to USB + ADB. Still there is no connectivity.
8. No IMEI found.
9. I put it in DOWNLOAD mode and connect it to PC but still there is no detection.
10. The still have access to stock recovery but no sign of detection. No adb devices found.
11. And ofcourse, ODIN did nothing.
I think that if somehow, PC detect it, then i'll do something.
Now, if you guys have any method left, plz share it. I'm so interested to fix this device. Waiting for your messages.
Click to expand...
Click to collapse
First thing that you need to do is to talk with your friend if he has a valid warranty and tell the problems to him.
Method 1 (if he can't fix it, then it's your time to make a difference)
If you ever get the connection, try to google as fast as possible on how to install the stock rom for the A300F to your device (if you need any help, I will... just toss me a ???PRIVATE??? message and...yeah :good: )
Just try, it's always good to try and since this is the socail era, you have help just everywhere in the internet