Related
Was trying to use a one-click root/unlock program for the Nexus 7. Apparently all the drivers did not install correctly. My tablet rebooted into bootloader mode, but is not responding to any volume button or power button pushes, or any combinations of button presses that I could think of.
I'm stuck at the "Start" bootloader screen. The text in the bottom left says the following:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 3.34
BASEBAND VERSION - N/A
SERIAL NUMBER - [...]
SIGNING - not defined yet
LOCK STATE - LOCKED
Click to expand...
Click to collapse
ADB is no longer detecting the tablet as being detected, and no fastboot commands did anything at all.
I have no idea how to do a hard reset on this tablet, and can't find anything about it. Somebody? Anybody? Help?
edit: Power + VolDown seemed to work, but I had to hold it for quite awhile... much longer than I ever expected. Phew.
Did you get it to reboot normally? Go do a search for the Nus 7 image files. It will be a life saver.
Sent from my Nexus 7 using Tapatalk 2
sc4fpse said:
Was trying to use a one-click root/unlock program for the Nexus 7. Apparently all the drivers did not install correctly. My tablet rebooted into bootloader mode, but is not responding to any volume button or power button pushes, or any combinations of button presses that I could think of.
I'm stuck at the "Start" bootloader screen. The text in the bottom left says the following:
ADB is no longer detecting the tablet as being detected, and no fastboot commands did anything at all.
I have no idea how to do a hard reset on this tablet, and can't find anything about it. Somebody? Anybody? Help?
edit: Power + VolDown seemed to work, but I had to hold it for quite awhile... much longer than I ever expected. Phew.
Click to expand...
Click to collapse
As long as you have boot loader mode your in good shape. Download the system images from https://developers.google.com/android/nexus/images#nakasijrn84d and flash the images via terminal or cmd prompt
Sent from my Galaxy Nexus using xda premium
I have got the exact same problem. I have tried to flash the stock images to the device but as the bootloader is locked it won't work. Does anyone have any other solutions?
Edit: How long roughly should you have to hold down power and VolDown to hard reset the device?
conor253 said:
Edit: How long roughly should you have to hold down power and VolDown to hard reset the device?
Click to expand...
Click to collapse
Until it turns off.
You can also pull the back off with a fingernail or something and pull the battery connector, it isn't too hard.
Google brought up this topic. I received a used Nexus 7 bought from Amazon Warehouse Deals today. It seems that whoever had it before me botched something, as I cannot get past the initial boot. I was able to get to the bootloader mode, and the info near the bottom of the screen is identical to the original poster. I've never learned how to root or unlock a device before, but before I even try to learn that, I would highly appreciate if someone here can let me know if such a fix is even possible since the lock state is marked as "locked". If the bootloader is not unlocked, how will I reinstall the original firmware correctly?
Thanks so much to anyone that can help me. The physical device seems great - no creaks or screen lift, and very little backlight bleed. It'd be a shame to have to return this if I can just figure out how to undo whatever the previous owner messed up.
You can easily unlock it but before you do that, can you get into recovery? Make sure your device is connected to a powered on PC before going into recovery. Once in recovery, you can attempt to restore to factory.
I plugged the tablet into my MacBook before entering the bootloader screen. When I select "Recovery" from the options available to me, it just brings up the white Google logo and then the screen cuts to black.
Glad to know I'll be able to unlock the device... I was just worried that the fact that it is locked in its current state might make such a task difficult. Guess I'll start looking into how to go about unlocking the device - thanks for your help!
Well, problem I'm running into is that I can't put the tablet into the correct mode to be recognized by a program like mskip's Nexus 7 toolkit. The only part of the tablet I can access in the fastboot or bootloader menu (not sure of the correct term...), so when I attempted to connect the device up to my computer to use the program, it just got hung up on attempting to find my device. All the instructions talk about putting the tablet into USB mode and such, but I can't actually get into the OS to change any settings.
I only know how to do it on a PC. Maybe someone with a mac can chime in.
I do have access to a PC; could you explain what is needed? Thanks!
Go here, download and install the android sdk. Once complete, the android sdk manger will open. From the sdk manger, also install the android platform tools and google USB driver. Other options are not necessary.
http://developer.android.com/sdk/index.html
Then come back here for additional instructions. I'll be here for the next hour.
Done and done. Thanks very much for your assistance! What's next?
Now, go to the installation directory of the android sdk and you should see several files and folders. Of the folders, there should one labeled "platform tools" and another labeled "extras".
Go in to the "extras" folder then "google" folder. Within the google folder, there is a folder labeled "usb-driver". Just make sure the usb driver files and folders are in there.
Now, put your device in bootloader mode and connect it to the PC. Your PC will start installing the drivers. If it succeeds then double check it in device manager. If it does not, you need to manually install the drivers from device manager and point it to the "extras" folder as the location of the driver.
When the drivers are properly installed, in the device manager, it should say "android bootloader interface" under "android device" or something similar to that. If it doesn't, review the previous steps as you can’t go any further if the PC does not recognize the device.
Okay that is done - I see "Android Device" listed under Device Manager, as well as an entry for Google Nexus 7 Bootloader Interface... next?
Presuming the drivers are properly installed, go back to the android sdk installation folder and go in to the "platform-tools" folder. In that folder you should see several folders and files including “adb.exe” and “fastboot.exe”. Once in that folder, press the "shift" key AND the right mouse button to bring up the context menu. In the context menu selection, click "open command window here" and a command window will open up.
With your device still connected to the PC and the device in bootloader mode, in the command window, type “fastboot devices” without the quotes. If the drivers are properly installed, it will display your device’s serial number in the command window. If it does not, you have to review the above steps and correct the issue before proceeding forth.
The serial number is displaying; progress! Now?
Very good!!!
Once it displays your device’s serial number, you are all set to start flashing the factory image. Leave the device connected to you PC and leave the command window open. Go here and download the factory image:
https://dl.google.com/dl/android/aosp/nakasi-jro03d-factory-e102ba72.tgz
Once downloaded, extract it using winrar or whatever archive decompressor you are currently using. When extracted, you should have the following files:
bootloader-grouper-3.34.img
flash-all.sh
flash-base.sh
image-nakasi-jro03d.zip
Copy the “bootloader-grouper-3.34.img” and “image-nakasi-jro03d.zip” files into the “platform-tools” folder.
Or, just read this: http://forum.xda-developers.com/showthread.php?t=1907796
Ok, did that. Then?
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
simms22 said:
do it the right way, dont use toolkits.
to unlock the bootloader, go into the bootloader(fastboot), connect the divice via usb, type..
fastboot devices(to make sure your device is visable)
fastboot oem unlock(to unlock the bootloader)
if you get an error, reboot the bootloader and try again. i had an error the first time on my replacement seven, second time it unlocked.
Click to expand...
Click to collapse
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Try a manual update
AndiS21 said:
After Android tried to update itself to the newest version, it seemed that this failed and has caused a "boot failed" message. The tablet refuses to go into recovery mode, its marked as red. The only accessible mode is going into bootloader. After reading many forums and trying my luck with toolkits of all sorts (Nexus 7 Root Toolkit, Nexus Root Toolkit, Android SDK commands), the bootloader refuses to unlock. I have successfully installed the usb drivers since my pc recognizes the device. fastboot devices recognizes the devise but adb devices doesn't. The bootloader is locked and nothing else is accessible, whats worse is that through all of these toolkits and commands bootloader refuses to unlock, trying to unlock it always results in a failure message (unknown error). Commands such as format, unlock or erase fail in reviving the system. Anyone have any experience with this? I have searched for over a week now and im terribly frustrated by this. :silly:
Click to expand...
Click to collapse
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
dave_uk said:
Reflash the bootloader?
edit: making VERY sure that you DON'T erase the existing bootloader first.
Click to expand...
Click to collapse
fortunatley though bootloader doesn't allow any command even the erase, it wouldn't allow me, nor formatting it as well. So i think the bootloader is intact. This is the screen i get from pressing Power and Vol Down.
pettymro said:
You can try a manual update. Download the update and run adb sideload. That was not working for me, cause my Nexus it's allready updated, but hopefully it will work for you.
Click to expand...
Click to collapse
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
try do it on another pc
AndiS21 said:
Thanks for the reply, i tried this several times, each time rebooting bootloader, but the command still posts an error in unlocking the bootloader. Recovery and Restart bootloader are marked in red font, Start is in Green, Power off White. I also tried flashing the recovery, since its inaccessible but because of bootloader being locked in won't allow me. :S Anything else you know that can be done ?
Click to expand...
Click to collapse
Can you post here the error message?
Israafiyl said:
Can you post here the error message?
Click to expand...
Click to collapse
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
AndiS21 said:
Sure here it is. When i type in fastboot oem unlock, the message to unlock on my nexus comes up and when i click yes to unlock does the procedure start and end with failure.
Click to expand...
Click to collapse
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Israafiyl said:
I don't know if fastboot let you flash the stock bootloader/recovery without unlocking but you may try:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot flash recovery recovery-stock-jro03d-nakasi.img
Click to expand...
Click to collapse
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
AndiS21 said:
thanks for the files, but bootloader won't allow me to change a single thing on it. Trying to flash recovery or the bootloader results in Failure result:bootloader locked!. :S
Click to expand...
Click to collapse
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Manual update
AndiS21 said:
As i have come to learn, adb can only function when debugging is enabled, in my device it wasn't unabled. Also the recovery program cannot be opened so sideloading through commands cannot be done. At least according to how some forums described the How To sideload through adb
Click to expand...
Click to collapse
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Israafiyl said:
try one more time with a different port/pc if it daesn't work it may be a hardware fault, i think a corrupted sd.
(you will have to send it to warranty but don't worry, asus have a really good assistence, you may have a new nexus in a less than 2 days)
Click to expand...
Click to collapse
I tried it on the laptop too, even changed the drivers to universal naked drivers, but nothing! Restart bootloader is with red, clicking it wont reboot the tablet, also recovery mode red, the only working button is the Start (green) but that leads to boot failure and power off.
pettymro said:
Use the volume up/down keys to navigate to "Recovery mode", then press the power button.
When the Android with the red exclamation point appears, hold down power first, followed quickly by volume down and volume up. (So that to start, you're holding down power, then you're holding down all three). After 2-3 seconds, release all three keys.
Use the volume up/down keys to select "apply update from ADB," then press power to select it.
On your computer, open up a command prompt or terminal window.
Using the command line, navigate to the folder containing the ADB executables and the update file.
type:
adb.exe sideload <update filename>
On my Nexus with Jelly 4.2 usb debugging is not enabled too, but I still get the option in recovery mode menu. Operation not succesful cause I cannot upgrade from 4.2 to 4.2. I will wait for another update and then try it again. Good luck!
Click to expand...
Click to collapse
recovery mode cannot be opened, the text font is red on the tablet and clicking it does nothing. :S
Also tried to completley flash the device but unable to. Going back and doing an fastboot oem unlock yields the same feedback.
Unlock Bootloader on 4.2
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
After some research into my issue, i have discovered that other users have posted "unbricking" solutions through a program called nvflash, when the device is put in APX mode. But unfortunatley i've yet to find a nvflash solution for nexus 7. I will experiment with the commands and what the others have reported as a solution.
ErnestoV31 said:
Hello, I was wondering if the bootloader in 4.2 can be unlocked the same way as it was on 4.1.2? I recently got a new nexus 7 and updated to 4.2.
Thanks and Cheers!
Click to expand...
Click to collapse
Yes it can.
Sent from my GT-I9300 using Tapatalk 2
SOLVED
See my most recent post in this thread
______________________________________________________________________________________
Firstly, I've spent the last three days scouring XDA and some other forums searching for solutions and trying various options.
The screen on my N4 has cracked and I've lost the use of the bottom half of the touchscreen. This means that I can't unlock my phone.
The phone is insured and will be repaired, but there are photos of my son's first birthday on the internal memory that I don't want to lose. I'm concerned that the phone will be factory reset during a repair or I'll receive a replacement. I'm trying to access the internal memory remotely to backup these files before I send the phone off. The problem is that I hadn't enabled USB debugging before the accident. The phone is completely stock including the bootloader.
So I can access via fastboot but not via adb.
Q1: Can I pull file from the internal memory via fastboot
Q2: Can I enable usb debugging via fastboot
Q3: The phone is set to display as an MTP device in windows but as I can't unlock the screen, none of the files are showing. Is there anyway around this?
Q4: Purely via fastboot, can I unlock the bootloader, install CWM so to use ADB within it and then return to a stock bootloader?
I think they're my options. Any answers to the above or alternatives would be appreciated.
All of the other threads regarding this, the users seem to either already have CWM installed or they're looking to perform a factory reset. I did consider resetting the device via the bootloader in order to bypass the screenlock but I understand that on the N4 this wipes the internal memory as well.
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
EddyOS said:
Unlocking the device isn't needed to pull the files from it, just plug it in and get what you need from the internal memory
Click to expand...
Click to collapse
On mine if I plug it in it appears as an MTP device but with no files. I then have to unlock the screen and select USB something-or-other from the notificationss bar, then the files appear in windows.
Strange, mine never needs to be unlocked...I'm using Windows 8 Pro btw but it also works fine in work on Vista Business
Only other thing I can think of is the fact I'm unlocked and running a custom ROM, I've never used my N4 stock. It was on CM within 30 mins of receiving the unit!
So over the last week I've managed to solve my problem. I've seen several other people asking for help with no luck so I'm posting this here in the hope that the search function will bring it up.
Firstly, my phone was completely stock running 4.2.2, unrooted, with the locked stock bootloader. USB Debugging WAS NOT enabled. I had pattern lock enabled when I dropped the phone. The screen cracked and the bottom half of the touchscreen was unresponsive.
The phone was insured, but I wanted to backup photos from the device before sending it off for repair/replacement.
HOW I FIXED IT.
Please note, you need at least some part of the screen to be working, specifically, some part of the screen where the pattern lock is.
You only need two pieces of software. The Android SDK and the Nexus 4 Toolkit http://forum.xda-developers.com/showthread.php?t=1995688
If you are running 4.2.2 you will need to update the toolkit. I also had the standard issues of installing the USB drivers for the N4. You need to get to a point where is shows up as an ADB device in Windows Device Manager.
As I didn't have USB debuggin enabled I couldn't connect tothe phone via ADB, but if you put it into recovery mode you can use Fastboot. Hold down the power key to turn the device off and turn it on while holding down Vol Down to load up recovery mode.
If you then start the N4 Toolkit, you should see the device listed as a fast boot device.
From within the toolkit unlock your bootloader.
Flash a temporary bootlader, (option 10) as the touchscreeen was broken it has to be CWM.
Once in CWM you can start to use ADB. Open up a DOS command prompt in Windows, go to your SDK/platform tools folder/ to access ADB.exe and you can use the pull command to copy folders to your PC. At this point, instead you can use applications like ADBexplorer or DroidExplorer to do the same thing through a nicer GUI.
If you'd like to still be able to use your phone, although without the touchscreen, you can load an unstable image to get into android and then use ADB to start changing system settings.
Firstly, before exiting CWM, clear the cache. Without doing this the phone jsut hung on the Nexus symbol while loading the image.
in the toolkit go to root/unroot options and select load unstable image(option 4 and then 6). This will fire you up into Android and it should be set up as you left it.
I wanted to enable bluetooth so to use a keyboard (I didn't have a mouse but this is a better option) from the DOS window type the following command
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
You should eventually get a pop-up on your screen saying that a request has been made to enable bluetooth. Hopefully your screen is working enough to select enable.
Then I use the workaround to disable the sceenlock, found here -> (http://www.addictivetips.com/androi...e-pattern-unlock-on-android-via-adb-commands/) I found method 2 worked for me. I imagine this will be stopped in a future update.
Method 1
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Method 2
adb shell rm /data/system/gesture.key
If either of these methods are successful you will be able to unlock the phone with an pattern, hence why you need to be able to touch some part of it.
From then, my bluetooth keyboard was already mated to my phone to I was able the navigate the menus to turn on USB Debugging, turn-off the screen lock and a few other bits and pieces I needed to do.
I then restarted (I was still working within the unstable image) and on reboot, all my changes had al been applied. No screen lock, bluetooth enabled and USB Debugging enabled.
Hopefully this will be of help to those in a similar position. Thanks has to go to the toolkit though which provides all the necessary access to carry this out.
I should probably add, you can use the toolkit to relock the bootlader if you're concerned about that and if you can't click the screen to enable bluetooth or mate a keyboard or mouse, once you have USB Debugging enabled you can use software like Screencast to control you phone's screen from a PC.
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Does unlocking bootloader via toolkit not wipe everything? How are you unlocking bootloader and still able to pull data off?
EDIT: it appears fastboot oem unlock on the Nexus 4 *does not* wipe data!
Carpetboy said:
So typically, just as I fill my claim to repair my nexus my wife drops her, smashing the screen even more than I did so she has absolutely no use of her screen. I went through the process again and though I'd post it in a more simple fashion.
1. Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Hope this simplifies the process
Click to expand...
Click to collapse
Please HELP, i can get to step 5...but then, when I try to use ADB via cmd (ie. adb shell), it says "error: device offline". what can it be? I don't know if this is a driver related issue (i've tried the toolkit drivers and the SDK drivers)...i'm desperated, I can't access the phone!!
Thanks in advance
not working for me
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Thanks for the guide.
Im curious on why youd want to boot an unstable(temporary) image after pulling the files using ADB in CWM recovery. Why not just wipe cache and reboot normally into Android ?
usb debugging without screen?
compsmart said:
i'm in same boat with cracked screen. i can get CWM installed but i cant enabled usb debugging without touching the screen so i cant get adb working. how did you turn on usb debugging without the screen
Click to expand...
Click to collapse
Can someone please walk me through how to do this? My screen is completely broken, but I can still turn on/off, I have reason to believe debugging is off because when I connect the phone (a Samsung galaxy sII skyrocket) to my Toshiba laptop via a micro USB, it makes a sound to signal that it's connected. Drives E and F then open up (but are empty) and then disappear. I have no idea what's going on but I absolutely cannot lose all of the data on this phone. Pictures and videos from my old blackberry Torch are on here too, making up about 4 years of my daughter's life that I would lose if I cannot retrieve. Also, I am not super -tech savvy, so if someone could help me I would be forever grateful.
Please!!
:crying:
almost the same issue
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
bob mc bob said:
I have an Asus memo pad 10 (smart) some of the core apps have been corrupted, (keyboard, UI, launcher etc all the essential stuff) I've been trying to reinstall my UI and launcher from my computer when i found out that USB debugging was disabled. the tablet is basically unusable, i have no way of enabling from the tablet itself. is there a piece of script or something i could run from my PC to enable it?
any help would be greatly appreciated :crying:
Click to expand...
Click to collapse
My screen became unresponsive a while back. I ended up getting and OTG cable and plugging in a mouse. This allowed me to do everything as if the touchscreen was working. There's also an app called MyMobiler that let me plug in my device over USB and control my screen from my PC. Those two helped me enable USB Debugging, flash a custom ROM, root the phone, backup everything I needed, then restore the phone to stock. I hope this helps.
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
HikerMan said:
*Sorry for bumping such an old post*
Thanks for the really useful guide!
Could you or someone just confirm to me that unlocking the bootloader does not factory reset? The reason I'm doing this process is to access my personal data so it's important that I can keep it all.
I ask because at the unlock bootloader stage it implicitly warns me that there'll be a factory reset.
Thanks again!
Click to expand...
Click to collapse
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Unlocking to bootloader will wipe your device
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
HikerMan said:
In that case, I am confused as to how OP managed to unlock his bootloader. He actually states that the purpose of this was to retrieve data, like me.
Also, in a previous comment in this thread by jw95275, they claim that "it appears fastboot oem unlock on the Nexus 4 *does not* wipe data".
I am concerned about the conflicting answers so far, so will hold off for an explanation before I do anything. Thanks for the response!
Click to expand...
Click to collapse
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
npjohnson said:
You should just be able to "fastboot boot recovery.img" and boot CWM and then use ADB. W/O unlocking the BL
Click to expand...
Click to collapse
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
jinglejuice said:
This did not work for me. I have a Nexus 4 with a broken digitizer, locked bootloader, and usb debugging disabled. I need to grab some data off.
I've tried `fastboot flash recovery {{recovery .img}}` and `fastboot boot {{recovery .img}}` without unlocking the bootloader first, and via both methods, I get back "FAILED (remote: not supported in locked device)"
So I'm not sure how people are able to get into custom recovery without first unlocking BL/losing all their data. Can someone explain?
Click to expand...
Click to collapse
On some (few) Motorola devices (not nexus 4), you can fastboot boot without unlocking the BL.
Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.
That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.
Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
Sent from my Nexus 7 using xda premium
@OP
The recovery you describe is the stock recovery. If you used an OTA process after rooting, probably that is what overwrote the CWM install you did previously - so that explains why you see what you do when you boot to recovery via the bootloader menu.
When you use the "reset by holding the power button down for 30 seconds" you are crashed the running OS and potentially corrupted any filesystems which are mounted "rw" (read-write). So, that might explain the bootloops that occurred thereafter.
You have a couple options, but before you try any of them, I would suggest that you observe the "power state animation" that occurs for about 10 seconds when you plug the tablet in to the charger with the tablet turned off: it shows you graphically how much charged the battery has. If the animation starts with a nearly all black battery, and then "fills up", the battery is still deeply discharged; if it is all white, or mostly all white, and the animation only "tops off" the battery, it has a good charge.
If that animation shows a battery which is still discharged, I would try to solve that problem before doing anything further. It was a low battery condition that got you into trouble in the first place; no point in making things even worse.
OK. Well, if you weren't a toolkit user, I would suggest a couple things that could be done manually using a custom recovery to attempt a repair of the /data filesystem, or rescuing your raw data for a later data recovery effort. But they involve command-line stuff, so me mentioning it is a waste of time. Suffice it to say that if you still have an unlocked bootloader and functioning drivers on your PC, you can re-install whatever custom recovery you want (using either fastboot or Wugfresh) and then use the capabilities of that custom recovery. Given that you didn't even realize that your custom recovery went missing until now, that's probably also a waste of time too - I probably can safely assume you don't know what its' full capabilities are.
So, flash a custom recovery and perform a reformat of the userdata partition ("Wipe Data" in TWRP, don't know what it is in CWM). You could even try taking a Nandroid backup before doing this, but the problem with doing this is that by default it will try writing to /data - so under the presumption that your userdata partition is hosed up, writing a whole lot of stuff to it (the backup) may not create a reliable backup image(s). With TWRP you could write backups to an external device, though.
That leaves a factory reset. If you do it with the stock recovery (simultaneously press power and vol-up for about 1 second after the recovery splash screen shows up to get the menu), it will erase EVERYTHING in the /data partition - including your everything in the psuedo-SD card.
Without any further learning on your part (abandonment of toolkits), it seems like the stock recovery factory reset is the least-effort solution for you. As I said, this will destroy ALL of your data on the device, but your device should return to a bootable condition. If you made any Nandroid backups and got them off the tablet, you could restore them after installing the custom recovery which made those same backups.
good luck
As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.
Sent from my Motorola XPRT
Defibrillator...
Sent from my Nexus 7 using xda app-developers app
@bftb0
Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.
@FitAmp if this don’t work I may be taking your advice hahahahahaha!!!
bricked
slybunda said:
bricked
Click to expand...
Click to collapse
@slybunda May I ask why you say bricked?
Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.
I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.
http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html
It is NOT bricked.
Dr Asqueroso said:
@slybunda May I ask why you say bricked?
Click to expand...
Click to collapse
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Dr Asqueroso said:
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Click to expand...
Click to collapse
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.
If you have a Windows XP box, you could try the following...
Download my copy of the FASTBOOT/ADB files for XP...
http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip
Unzip to a folder on the Windows Desktop.
Unzip and copy the files from nakasi-jzo54k into the same folder.
You should now have a folder with the following files in it...
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
-----
Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.
Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).
Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...
Code:
fastboot devices
It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat
This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.
Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).
Good luck.
Rgrds,
Ged.
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
Open the bat file in notepad.
Sent from my Galaxy Nexus
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Dr Asqueroso said:
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Click to expand...
Click to collapse
Sometimes it's easier to 'just do' than explain 'how to do'...
Here is the modified 'flash-all.bat' script, with the line removed.
http://dl.dropboxusercontent.com/u/37483979/flash-all-MD5_ a687082ef3179feb40ba108436dc5768.zip
------
Maybe I'm just being overcautious when it comes to BOOTLOADER stuff...
It's entirely possible you could just run the original 'flash-all.bat' as is... without problems... as many people do, and as Google intended.
So, it's not critical you delete bootloader-grouper-3.41.img or run the modified .bat file... just ensure you have a damn good USB connection and power to both devices before you do.
Rgrds,
Ged.
---------- Post added at 12:55 AM ---------- Previous post was at 12:41 AM ----------
Dr Asqueroso said:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Click to expand...
Click to collapse
Sending /system has always been problematic for me as well... you need to change to a different USB port on your PC.
Using the Vol. Keys navigate to RESTART BOOTLOADER... disconnect and reconnect to a different USB port, and try again.
If you're BOOTLOADER is showing 3.41, don't worry about it. The issue was never about the version, but about flashing it.
This will be taken care of later, with the OTA upgrade.
Rgrds.
Ged.
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Dr Asqueroso said:
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Click to expand...
Click to collapse
2 hours is way too long... it should take less than 5 minutes to flash back to stock.
I suspect a USB connectivity issue... open another command prompt window, and type
Code:
fastboot devices
If you don't see a SERIAL NUMBER, then your FASTBOOT connection has died...
Try again, from a different USB port... and maybe a different USB cable.
----
You are actually getting somewhere though... your screenshot indicates that 'boot' went over successfully.
Don't give up hope - persevere!
Rgrds,
Ged.
Ok I'll try it again when I get home from work...
Okay followed all the steps but I think the tablet is not going to play nice... I just can't get past the sending system bit.
The 7 is now showing
Fastboot Mode (in red)
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.18
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx (now showing my number)
Signing - not defined yet
LOCK STATE - UNLOCKED
My CMD prompt window is yet again just showing sending system and nothing. Been like this for the past 30 mins or so... I've swapped my USB ports over tried and the process a few times and still no joy. I think I've been defeated.
It looks like the 7 will have to go back... but can I make a warranty claim from Asus in it's current state or will I have to lock it somehow??
Failing that I'll "lose" it and claim off the house insurance.
Oooops the CMD window is doing something different...
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.656s]
writing 'boot'...
OKAY [ 0.203s]
sending 'recovery' (5446 KB)...
OKAY [ 0.719s]
writing 'recovery'...
OKAY [ 0.219s]
erasing 'system'...
OKAY [ 0.094s]
sending 'system' (471804 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5264.891s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\android-sdk\platform-tools>
Anyone with any suggestions as to my next move?
Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.