I have tried just about everything I can find to fix my Nexus 7. When powered on it shows the Google logo and hangs there. I have checked the battery connection, checked the other connections that are visible when the cover is taken off and everything is ok. I can boot to the fastboot mode. I plug it in my computer and it loads the drivers. I can a cmd line command "fastboot Devices" and it shows that my device is visible. Then I can enter the command "fastboot oem unlock. the tablet asks for the yes or no question i use the volume up to say yes and the cmd line shows unlocking and erasing but the tablet freezes and nothing happens (for hours). I then hold the power button and shut off the tablet. the command line then says failed because of to many links.
The laptop has not been rooted, this is a bone stock Asus nexus 7 2013.
I am attaching a photo of the fastboot mode screen.
My question is...I am beating a dead horse is my nexus 7 bricked permanently.
I think the problem is not being able to enable USB debugging. Is there a way to enable USB debugging when so can't get into systems in the tablet?
Thanks for the help. if you have any questions please let me know
MWGW
Related
Oh man. I was trying to root my Xoom and followed the directions here: http://wiki.cyanogenmod.org/wiki/Motorola_Xoom_(Wi-Fi):_Full_Update_Guide#Method_via_ROM_Manager
I pushed the vol - button with the power button and got "starting fastboot support" with the Red M logo.
I opened a cmd window in win 7 and got to the ADB folder and did the "ADB devices" command.
It didn't list my Xoom so i looked down and the screen was black so i unplugged it and tried to restart but it won't start...nothing...nada...zip.
Have I bricked it?
EDITED TO ADD: i found the problem...it just ran out of battery. I plugged it in and it's fine.
Word of advice, NEVER do anything to your device(s) without a fully charged or at the minimum 70% battery, just incase things get fubar'd.
Sent from my Galaxy Nexus
Hi. I've recently bought my TF700 and upgraded to JRO03C.US_epad-10.4.4.25-20121228 (JB 4.1.1). Now I want to root my device, so I first unlocked the bootloader using the ASUS unlocker. That went fine, since it says "the device is unlocked" in the boot sequence. The device boots and works properly.
Now I wanted to get to the stock recovery mode for a backup, but it fails miserably. I get to the four icon menu (RCK, Android, USB, Wipe) and select RCK. Then an android icon with a blue rotating icosahedron in its chest apears for a couple of seconds and then a "dead" android with it's cover opened and a "!" enclosed in a red triangle. After a couple of minutes, the device reboots normally (I can force that by pressing down the power button for 10 seconds).
I tried to get to fastboot by choosing the USB icon, but it does nothing (just freezes in the four icon screen and stops responding to any other buttons); the PC doesn't see an USB device of any kind. I tried connecting the USB cable both before and after selecting the USB icon with no difference. I'm sure I have at least some good drivers because I can use adb with my device when the OS is running.
I'm new to this device, so I may be doing something wrong. Any suggestions? Thanks in advance.
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
_that said:
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
Click to expand...
Click to collapse
Thank you, _that. Whatever drivers it might need, I cannot install them because no USB device of any kind appears in my computer besides my keyboard. I think I should be getting "Starting Fastboot USB download protocol" or something. How can I get fastboot to work?
Sorry, it seems it was a USB port problem! I changed the port and the fastboot device is now available in my PC. Fastboot is now able to send commands like 'reboot' to my device.
Thanks for your clarification about the stock recovery mode, _that.
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
georgepcde said:
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Good thought but no luck.
Thanks, though.
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
rgkjr1 said:
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Click to expand...
Click to collapse
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
smirneger said:
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
Click to expand...
Click to collapse
pmrmx774 said:
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
Click to expand...
Click to collapse
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
rgkjr1 said:
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
Click to expand...
Click to collapse
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
hey_joe said:
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
Click to expand...
Click to collapse
Thanks, hey_joe. I actually already tried that but decided to try again. This time it worked! I don't know what I did differently but bootloader is now unlocked!
Thanks, All!!!
Tablet ubislate 9ci hanging on bootloading
Dear sir/madam, I am new to this forum. I purchased a new tablet Datawind Ubislate 9ci. It is a 9 inch no-bluetooth tablet.
>Details:
>*.Android 4.1.1
>*.Rock chip RK2928
>*.KERNEL linux version 3.0.36 i was trying to install CWM through mobile odin and ROM manager but my tablet was not supported so i downloaded build.prop editor from google play and changed it to some other cwm recognizable model viz. Samsung, nexus etc. When i was doing the above mentioned procedure, suddenly my tablet is coming up to bootloading and hanging there only and not opening i tried to go to recovery by pressing power and vol but i am not getting recovery menu, i also tried to hard reset by pressing reset with a needle at the back but all in vain again hanging on bootloading i also tried press and hold power & vol- and several other combinations , all in vain so kindly help me and guide me Thank you
Hello there. First of all thank you for your support. I'm here because I have the same problem as OP, but first a little context.
I have already rooted my A700 before, without any difficulties. But after a crash, I restored it to factory and tried to redo the whole procedure.
So, here I am, USB driver installed (I had to modify android_winusb manually for windows to finally accept the drivers), adb up and running, adb reboot-bootloader executed and...
Acer screen, no text, just like the OP. And a yellow "Fastboot" device in my Device Manager window. So I'm stuck here. I've tried to uninstall/reinstall the google USB drivers to no avail, unlike OP. I can access the Acer recovery with the reboot recovery prompt, but I'm not confident enough to ignore the step in this tutorial.
Additional precisions : when the device is stuck with the Acer Logo (without text) trying to use a fastboot prompt (like oem unlock) only gives me the <Waiting for device> message.
I could use the Acer recovery to install a rom from external storage, but I'm unsure if it's a good idea to NOT use CWM or TWRP
Thank you, I'm starting to miss Android 4.4 (yeah, because the Acer update manager give an error 400)
Update : I did manage to access fastboot. Just as I had to modify android_winusb with the PID of my tablet when it was running, I also had to edit the file with the PID of the tablet waiting in fastboot. I didn't noticed they were different.
Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked
You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.
Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.
1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.
No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.
jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk
I have a pixel 2 I was trying to flash a rom on the phone. I have messed up terribly and now I can only boot into the screen showen below. Abd can't even recognize the device. I can switch too recover option, boot menu but what ever I choose brings me back to the same screen. Can anyone help?
Connect it to your device running ADB and fastboot and type 'fastboot devices' and you should see a serial number appear?
If it still doesn't get recognised you can disconnect the device, power off, then press and hold the power button for 10 seconds or longer until it vibrates then plug it back into the pc and try ADB/fastboot devices again. It may take a few attempts but it will work.
Good luck