I've read many threads on fixing this issue, but none of the fixes I've tried are working for me and I'm kinda at my wit's end. I'll try to lay this out as concisely as possible :
Desired outcome - I need to recover my 'Documents' folder from the SD Card. After I've done this, I can reset the device to the factory image on my own.
Device - 2012 Nexus 7 Wifi, currently running 4.4.2 after the push update (Build KOT49H), and I've installed WUGfresh's Nexus Root Toolkit 1.8 on my Win7 machine. - On the nexus, I had enabled developer mode and USB debugging. No clue, unfortunately, what the most recent MTP settings were. I assume they were set to "mount as disk drive" (if I'm thinking of the correct setting here).
This morning my Nexus began looping the four-circle loading screen (formerly the X) when I powered it on. I can boot into recovery mode and restart the bootloader/etc, but couldn't break the loading loop.
Here's something I seem to be stuck on - when using the toolkit, what screen should I be working from for which tool? For instance, should I leave the tablet at the loading screen, at the recovery mode ("no command") screen, the "input adb command" screen, etc - and for which utility? It seems the ones I should be making use of are either :
Backup Utilities -> Create Android Backup File
Backup Utilities -> Backup VirtualSD Card
Advanced Utilities -> Push/Pull Files*
*On this option, should my path be /system/sdcard/Documents ?
Here's what I think I'm failing to understand - I notice that, under advanced utilities -> list devices, if I check the radio box for "ADB Device on" at the basic bootloader screen (on the device), I get nothing, but checking the "Fastboot - Bootloader" box returns the proper serial #. The only time I get a valid entry from "ADB Device on" -> List devices is when I'm at the command prompt line of the recovery mode screen (on the device).
Thanks for the help - II have tried browsing for similar issues, but after a night of struggling with it something's still not clicking in my brain. Pardon my exasperation and good on you all for being here.
Related
Following the steps from the thread http://forum.xda-developers.com/showthread.php?p=24124828#post24124828, I lost my device on fastboot command (I followed correctly all the steps).
The device freezes on the startup screen and the PC can't recognize it properly. So the next fastboot command stays awaiting the device indefinetly.
The Android ADB Interface still remains untouchable on devices panel, but as an unspecified device. So, Windows doesn't mount the internal storage and consequently it is apparently impossible to change the damages.
Does anyone know something that can be useful?
install the correct drivers for fastboot and go ahead:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i had the same problem
used this link helped get my device up again
http://forum.xda-developers.com/showthread.php?t=1422832
Hello all,
I'm having difficulty trying to run EFS Pro v2.0.70/v2.0.72 to backup my EFS folder on my GT-I9505. I get stuck at the part when it says "Initializing ADB server..." and it just sits there. I just want to point out that I had made a backup of my EFS folder on my GT-I9505 when I first got my phone (around May), but it seems to have been deleted! Anyway, I found some good steps in another thread, as follows:
Before starting, check the following:
Device is fully rooted
SuperSU (or equivalent) is active
USB debugging is ON (Settings->More->About device: Tap several times on "Build number" to enable Developer options and tick USB debugging)
Busybox downloaded AND installed (normal or smart) on your device
Microsoft .NET Framework 4.0 installed on your PC
Samsung USB driver is installed (either by installing Kies or just the driver alone.
Kies is not active (neither as application nor process, check Windows Taskmanager)
ADB fully functional ("adb devices" recognises your phone) -- (look here for a basic ADB tutorial/how to)
In case ADB is not running you need to install the ADB driver
Run EFS Professional as administrator.
Make sure to grant SuperSU access to Shell and confirm the RSA fingerprint request once they pop up on your screen.
Of course, your device should be on the home screen, not on the lock screen
I've followed all these steps, checking each methodically, and guess what, I'm still stuck at "initializing ADB server..."! I even go to cmd and type in "adb devices" and my phone shows up, I see on my phone that a shell has been granted, and yes, I am rooted, I have busybox, and Samsung drivers, .NET 4.0 framework and USB debugging, it's driving me mad, I've even tried different USB ports, and nothing!
If anyone has any suggestions, please fire away!
I have the exact same problem, but with my S3 (I9300) ...
No one who can help?
Did you get sorted my i9505 is the same and I have two phones but one wont work..
Hi All,
After seeming that I'm locked out of my own device for 72 hours, I managed to scour the net and use parts of other tutorials to successfully bypass the "you're device was reset, please log in" loop.
So I should point out I was running a Pure Nexus rom running 6.0 with a custom recovery, you're results may differ but you've got nothing to loose.
Pre Requisite
ADB and Fastboot - You don't need to spend an hour installing the whole kit, just visit http://developer.android.com/sdk/index.html and scroll right down to the section where it says "SDK Tools Only" and click on "installer_r24.4.1-windows.exe"
Once installed the SDK manager will open, now make sure the top 3 are checked which are:
Android SDK Tools
Android SDK Platform-tools
Android SDK Build-tools
And also scroll down in the list to find Google USB Driver
Once all of that is done download the latest Google USB drivers (although the SDK installs USB drivers it still shown an exclamation mark in device manager") http://developer.android.com/sdk/win-usb.html
To install those USB drivers just go into device manager and if you se Nexus 6 under "Other Devices" just right click and click update driver software and then click browse my computer and get it to scan the Google USB driver folder you downloaded.
restart your phone into recovery (Volume Down and Power button)
now again in device manager make sure the Nexus 6 doesn't have a yellow icon identifying there's a problem with drivers or that the nexus 6 is listed in other devices. If either of those are present right click and update drivers > browse from computer and select the Google USB drivers you downloaded previously.
Bypass FRP
With all that confirmed restart your Nexus and leave it on the Welcome screen.
Now, you need to get into platform tools which is located:
C:\Users\YOURUSERNAME\AppData\Local\Android\android-sdk\platform-tools
if you can't see AppData you need to enable hidden files and folders
once in platform tools hold SHIFT and right click any blank space and click "Open command window here"
then type "adb devices" and it should list your nexus under devices, if it doesn't open device manager and check your drivers.
If it does show your nexus execute this command which edited from another source:
"adb shell am start -n com.android.settings/.Settings"
Your nexus will now open the settings menu =] in settings go to "Backup & reset" then click "Factory data reset" (although it says it wipes user data, mine was untouched, I can't say the same for so you may lose some data if you proceed)
your phone will reboot and in my case it opened my custom recovery and executed a script, the phone will restart again and go to boot, hold the power button to force shut down the nexus and boot into recovery mode. In recovery mode flash a ROM, if you don't have a ROM download one on your PC and then connect your Nexus to your PC via USB and copy it over.
Once the ROM is installed you won't get the "you're device was reset" screen.
"
You left out some key details which are covered in the guide I wrote up a few days ago. Here's the link.
http://forum.xda-developers.com/showthread.php?t=3261846
Sent from my Nexus 6 using Tapatalk
this does not work, because in order to adb devices to populate anything you would of had to enable usb debugging from within the phone, and if you're locked our from FRP, you cant access the settings to turn on the usb debugging
Bootloader LOCKED .. and asking for gmail ID ??
Hi
I have a Galaxy Note 4 (SM-N910G) and don’t normally muck around with the system. I have limited experience with Android.
My phone is locked (with important data stored in it)– a couple of days ago (presumably after a system upgrade) it suddenly would not recognise my fingerprint nor backup password.
I tried unlocking the phone using Android Device Manager but although I could get my phone to ring or display text, I could not change the password after locking the phone.
I called Google who said that Android Device Manager only works on earlier Android Versions - ?4 and below and most likely my phone would be running Marshmellow.
I called Samsung who said my only option is to restore to factory settings.
I wanted to use ADB
(to enter: adb shell
cd data/system
su
rm *.key) and downloaded it and tried to use it from the c:\ prompt but I don’t have USB debugging enabled. No device was recognised when running ADB.
I had not registered for a Samsung account so I could not use Find My Mobile.
I tried to apply an update via external storage in recovery mode (I downloaded files such as Lockscreen_Security_bypassV1.1.zip or Pattern-Password-disable.zip) but unfortunately when I tried to apply them, it came up with E:footer is wrong, E: signature verification is required.
(I also tried “Android Multi Tools”).
I do not have CMN recovery loaded nor Aroma+File+Manager
My question is: should I try and use Odin (have downloaded odin3_v3.11.2.zip) and TWRP to try and enable USB debugging or try to disable footer/signature verification??
Any other suggestions to try and unlock my phone???
At the minimum this has been an education!
Thank you for your help!
Hi guys.
Today i unlocked bootloader + flashed TWRP.
The system bootek ok but i had problem with accesing to internal memory (in phone and also via cable and filesharing/MTP)
So i made again full wipe in TWRP, it cound not boot so i reinstalled from TWRP whole system image, then full wipe.
Still i have the same problem: Cant access internal memory:
Meaning i cant create on internal memory any directory from Adnroid and also whn i am connecting it to PC, i cant do that either.
Any idea ?
The windows shows me that 100GB is free but still i cant write anything.
I only see "Android" Driectory with apps data in it.
Look in the device manager for the Android device, it's most likely going to have an exclamation next to it, right click on it, go to update driver, browse my computer, let me pick from a list, choose "Android USB", then it should be recognised properly.
If not make sure you've enabled "USB Debugging" in the developer settings (Tap build number 7 times to enable developer settings).
In your notification for your device you have to choose "Transfer files" instead of "USB Charging", just tap on the "USB charging this device" in the notification tray.
Are you sure you haven't messed up the encryption on the phone too? If so then you'll probably have to reset the phone back to factory defaults and start again.
See attached image for where it should appear in your device manager
It wasnt that, After few tries of full wipe i managed to get this workig.
Finally i set phone without fingerprint and it works now. All directories are accesible.
Still i will try again with flashing TWRP back becasue it reverted to default recovery :9