I accepted the forced OS upgrade over the weekend (I think it was for Pie) on my Samsung Note 8. Upon restart, it is no longer accepting my encryption password and I can't get to my home screen. Yes, I know my password, and yes I'm freaking out (so any help would be appreciated!). I would like to not wipe the data off my phone.
So far he's what I've tried on my own:
Restarting/rebooting the device
Samsung Sync to try and back up
Find my mobile (both the android version and samsung version) to try and back up the device. No dice.
Load to bootloader (but device not recognized)
I'm down to three tries before the Factory Reset Protection (FRP) kicks in. (any way to extend number of tries is a separate, but equally important question.)
I finally started brushing up on adb and ran "adb devices". Server starts and it recognizes the device (whew!) but it's "unauthorized" which I assume it has to do with my encryption. Again, I have no access to the settings menu in order to enable USB debugging, so going into the GUI is not possible.
I also tried this:
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
[email protected]:~# adb kill-server
[email protected]:~# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
[email protected]:~# adb backup -apk -shared -all -f ~/android/backup.ab
adb: unable to connect for backup: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Again, the fact that ADB is recognizing the device is a good sign in my opinion, just need to get past that so I can backup and pull the data off my phone. If there are any how-to's or steps that show what I can do to fix my actual problem and get my phone back to the way it was on Saturday, that would be AWESOME.
I haven't tried rebooting without the SIM inserted or wiping cache partition from the reset screen, but I'm willing to try that if anyone thinks that'll do it.
Please help.
Related
I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
Hi,
all of a sudden, my XT1039 Moto G has entered a never ending bootloop that goes like this:
- powers up, motorola animation runs fine
- if the sim is inserted, it lets me tap the numbers for 5 seconds, then it soft reboots by itself
- if the sim is not inserted, it loads fine, it lets me do what I can do in 5 seconds, then it soft reboots by itself
my XT1039 is totally stock, unrooted, the last app I've installed is a flashlight app from the Google App Store, to turn on and off the back led, three days ago, and has been working fine for three days since then.
What I have done so far:
- booted android to safe mode: 5 seconds, and it bootloops again
- booted to recovery and wiped the cache partition, rebooted to android and the problem is still there
- when powered off, held the vol up and down buttons for two minutes: somebody wrote it worked for him, it doesn't work for me
- tried all the other options on the recovery menu (Factory, BP Tools, QCOM), but they all seem to do nothing, and get me again to the bootlooping
- booted to flashboot with an otg cable and a usb pendrive, hoping a magic "backup to usb" option would show up, but it doesn't
- disconnected the battery for 5 minutes, and replaced it with a known good working one out my wife's XT1032 (same battery model), still no luck
now I'm almost ready to boot to recovery and wipe data/factory reset, but I still would like to copy the Pictures folder out of the device first, so I tried with adb:
- installed the Motorola (and the universal too) drivers on my Win 8.1 and downloaded a recent version of adb.exe (Android Debug Bridge version 1.0.32)
- during the 5 seconds of bootloop life, I can browse the XT1039 folders from Win 8.1 explorer, but 5 seconds is too short to do anything
- booted the XT1039 in flashboot, but the command adb devices doesn't see my device
- while in flasboot, navigated in Recovery --> Apply Update from ADB, the Win 8.1 alerts me there's something new on the USB chain, and adb devices says:
List of devices attached
TA98601*** sideload
but in the sideload mode it seems I can't run the pull command to get my files out of the damned device, every command like adb pull, push, shell, returns the same error:
error: closed
Is there anything else I can try to get my files out of the XT1039, before restoring it to factory ?
Any hint is highly appeciated, thanks
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Professor Gibbins said:
I can see that you were able to boot into recovery, and assuming that you are using a recent version of TWRP, you can attach the device to a computer via USB while in TWRP. and copy the pictures folder that way.
Hope this helps
Edit: It sound like you were using the stock recovery, so boot into fastboot mode and flash the recovery with instructions from here.
Click to expand...
Click to collapse
You can't install TWRP with a locked bootloader, and unlocking the bootloader wipes data...
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Professor Gibbins said:
Of course. It never actually occurred to me that the bootloader would be locked.
Although, have you tried running
Code:
adb kill-server
adb start-server
and trying the 'adb pull' commands again?
Click to expand...
Click to collapse
Yes, unfortunately the bootloader is locked, the phone is stock as if just bought out of a shop.
Here's the sequence of commands ran while in fastboot
C:\adb>adb kill-server
* server not running *
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
C:\adb>adb pull /system/app/Settings.apk
error: device not found
and the here's the sequence of commands ran in fastboot-->recovery --> apply update from ADB (the only option I've found that seems to enable some adb functionality)
C:\adb>adb kill-server
C:\adb>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\adb>adb devices
List of devices attached
TA98601*** sideload
C:\adb>adb pull /system/app/Settings.apk
error: closed
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
I'm trying to disable some apps through ADB but when the
Click to expand...
Click to collapse
You can't see the device while on fastboot mode of you type adb devices.
You need to make sure debugging is on in the developer preferences.
ADB appears to be working just fine for me.
When using adb make sure you have debugging enabled and grant the popup on screen
adb is not fastboot. You can use adb on twrp or booted system. Fastboot is on bootloader mode.
Also need to make sure that the proper USB drivers on the computer are installed/updated.
Cj214 said:
Hey guys so question.
Is ADB broken with Android 10 at the moment? I updated through the installer.
Now when I get on fastboot mode and type fastboot devices, I see my phone poop up. But I can't see ADB devices it gives me a no devices found.
*ADB debugging is on
If I do ADB reboot bootloader while the phone is on, it works and it also gives me the device under list when I type it while the phone is on.
Any of you have seen this?
Click to expand...
Click to collapse
This is working exactly as intended, and not exclusive to Android 10, but rather has been the case as long as I can remember (Jelly Bean? KitKat? Maybe much earlier?):
adb: Only works when booted to OS or in TWRP. Debugging required to be toggle on in phone settings. Does not work in bootloader-fastboot mode.
fastboot: Only works in bootloader-fastboot mode. Debugging is not required to be toggled on.
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Bringer1 said:
D:\OnePlus3\Fastboot>adb sideload stock7.zip
opening 'stock7.zip'...
connecting...
adb server version (40) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Thats what adb gives to me...
Click to expand...
Click to collapse
Sounds like another adb server is still running. What does adb kill-server and then trying again do
a second adb server was running.
TNX
Can I mount system rw using adb enabled recovery img from the following link:
https://forum.xda-developers.com/7t-pro/development/recovery-oxygen-os-stock-recovery-adb-t3991865
Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.
Try using the latest platform tools from Google.
batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).
On my Rooted Pixel 4a, I can use:
Fastboot - I flashed the latest update firmware as well as the rooted boot image
ADB Over WiFi - This is the most comnon way I connect for ADB
ADB While the Android OS is running
What I cannoit get woirking is ADB while in recovery mode,
If I go to recovery and connect via a high quality cable, I can see the device with
Code:
adb devices
C:\Java\x86\Android\android-sdk\platform-tools>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
091????????490 rescue
Click to expand...
Click to collapse
But none of the below works
Code:
>adb shell
error: closed
>adb connect 091XXXXXXXX490
cannot resolve host '091XXXXXXXX490' and port 5555: No such host is known. (11001)
>adv shell 091XXXXXXXX490
error: closed
What am I doing wrong? how can I connect in recovery?
Stock recovery?
WillisD said:
Stock recovery?
Click to expand...
Click to collapse
Yes.
DiamondJohn said:
What I cannoit get woirking is ADB while in recovery mode
Click to expand...
Click to collapse
I always thought that adb from recovery was a TWRP thing?
I did adb reboot recovery. My phone has an Android on its back, with "No command" on the screen.
Code:
$ adb devices
List of devices attached
xxx unauthorized
$ adb shell
adb: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
I got the same thing booting to recovery by holding Vol down at boot.
Booting to rescue (another option on the boot menu) got me the same thing on my screen and the same symptom you saw.
Code:
$ adb devices
List of devices attached
xxx rescue
$ adb shell
error: closed
Are you sure this is supposed to work with the stock recovery?
a1291762 said:
Are you sure this is supposed to work with the stock recovery?
Click to expand...
Click to collapse
Actually no, i guess it was an assumption, and the response to adb devices, gave me further hope.
However,, it does respnod to ADB. As is seen, it provides a list of devices. But, maybe one can't shell out while in stock recpvery. Which goves me an idea, maybe we can send commands from the command window in windows/linux. eg adb shell ls But it wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
DiamondJohn said:
It wouldn't make sense that it would allow root, which negates what I wanted to be able to do in the first place. ie recovery from a bootloop by selectively editing the data partition. in my previous case, it was to disable a single magisk module.
Click to expand...
Click to collapse
Yeah, it certainly seems to be speaking adb...
I didn't think to try...but maybe adb push and pull work?