Backup with Smart Switch a black screen Galaxy S5 (Unauthorised device in adb - Root - Usb debugging ON - Unlock patern OK - Recovery accessible)

[jameslevalaisan]

Hi,
I think I've already explain everything in title.
My Galaxy S5 on Android 8 (I think) as her screen broken (black)

Before that it already wokr badly and slowly. I bought a new phone but this one break just before I can transfer data.

I can unlock the patern (I know that because the volume + buton react)
Smart switch say that the phone is locked (even it's not true). Tested on 2 PC
The phone appear in Windows but no file or folder appear.

In adb the device is shown unauthorised and even if I click where the message to unlock should be, notihng append.

The phone is connected on Wifi, apparear in Google Find it but not Samsung find it...

I think that it's already to much information...

My question : how can I do the unlock the phone and do a smart switch backup ? or an other way to transfer data.

Regards
James

 

[jameslevalaisan]

I keep my phone in recovery mode and waiting some new instruction...

 

[jameslevalaisan]

Ho **** I forget that I've taken the sd card of. That explain some error.

 

[SubwayChamp]

Ho **** I forget that I've taken the sd card of. That explain some error.

Are you totally sure you are in TWRP?

 

[jameslevalaisan]

Are you totally sure you are in TWRP?

not totally sure but I have a TWRP folder on my sd card, and adb devices show as recovery and root...

 

[SubwayChamp]

not totally sure but I have a TWRP folder on my sd card, and adb devices show as recovery and root...

Mmm, SDCard has nothing to do here, I mean you don't need it.

If your device is listed with an ID followed by recovery, then you are in recovery mode.

You can start by pulling all your internal storage if you are interested to do with a simple adb pull /data/media this will take you a lot depending on what you have there.

 

[jameslevalaisan]

Mmm, SDCard has nothing to do here, I mean you don't need it.

If your device is listed with an ID followed by recovery, then you are in recovery mode.

You can start by pulling all your internal storage if you are interested to do with a simple adb pull /data/media this will take you a lot depending on what you have there.

as I expected :
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb -s 487e969e pull /data/media
adb: error: remote object '/data/media' does not exist

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>

I know that sd card hase nothing to do here, it's just to say that if I have this folder on the sd card it's mean that I had installed TWRP.

 

[jameslevalaisan]

I put the SD card in the phone but nothing is shown in ls command

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb -s 487e969e shell
~ # ls
cache                      init.recovery.qcom.rc      selinux_version
charger                    init.recovery.service.rc   sepolicy
data                       init.recovery.usb.rc       service_contexts
default.prop               license                    sideload
dev                        oem                        sys
etc                        prebuilt_file_contexts     system
file_contexts              proc                       tmp
fstab.qcom                 property_contexts          twres
init                       res                        ueventd.qcom.rc
init.rc                    root                       ueventd.rc
init.recovery.hlthchrg.rc  sbin                       vendor
init.recovery.nano.rc      seapp_contexts
~ #

 

[iBowToAndroid]

I put the SD card in the phone but nothing is shown in ls command

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb -s 487e969e shell
~ # ls
cache                      init.recovery.qcom.rc      selinux_version
charger                    init.recovery.service.rc   sepolicy
data                       init.recovery.usb.rc       service_contexts
default.prop               license                    sideload
dev                        oem                        sys
etc                        prebuilt_file_contexts     system
file_contexts              proc                       tmp
fstab.qcom                 property_contexts          twres
init                       res                        ueventd.qcom.rc
init.rc                    root                       ueventd.rc
init.recovery.hlthchrg.rc  sbin                       vendor
init.recovery.nano.rc      seapp_contexts
~ #

If you're running Android 8, then storage is encrypted by default.

You'll have to fix the screen in order to get access to the data

 

[SubwayChamp]

as I expected :
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb -s 487e969e pull /data/media
adb: error: remote object '/data/media' does not exist

Why you targeted to a specific device with -s ID, maybe you have other device attached to PC?

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>

I know that sd card hase nothing to do here, it's just to say that if I have this folder on the sd card it's mean that I had installed TWRP.

OK, but this not really reveals if TWRP is actually installed, it could be installed after and deleted/overwritten at any time. What really reveals if TWRP is there and detecting device is what you did before with adb devices and you got listed as recovery

 

[jameslevalaisan]

Why you targeted to a specific device with -s ID, maybe you have other device attached to PC?

OK, but this not really reveals if TWRP is actually installed, it could be installed after and deleted/overwritten at any time. What really reveals if TWRP is there and detecting device is what you did before with adb devices and you got listed as recovery

the -s was just because I plug to devices during a moment

adb devices show me recovery. So you think that I have twrp but also, this command show that I have not :

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp backup SDBOM
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
487e969e        recovery

I'm not sure what I can do now.

For me the better solution will be to understand why I can not connect to my pc normaly. Ok there is a popup but click on a popup is not so complicated.

With my S4, Smart switch work even if I doesn't authorise RSA key.

 

[SubwayChamp]

the -s was just because I plug to devices during a moment

adb devices show me recovery. So you think that I have twrp but also, this command show that I have not :

C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb shell twrp backup SDBOM
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
^C
C:\Users\James-23\AppData\Local\Android\Sdk\platform-tools>adb devices
List of devices attached
487e969e        recovery

You have TWRP installed and communicating perfectly with your device.

I'm not sure what I can do now.

For me the better solution will be to understand why I can not connect to my pc normaly. Ok there is a popup but click on a popup is not so complicated.

This is because your data partition is not mounted, probably you didn't format it after to flash the ROM.

With my S4, Smart switch work even if I doesn't authorise RSA key.

The RSA key is particular for every device, you can't push it from a device to another. And you have to set it up the SmartSwitch tool app from your device.

 

[jameslevalaisan]

ok, so what can I do now ?

 

[SubwayChamp]

ok, so what can I do now ?

You can't go further with this message, "Waiting for TWRP to start . . ." you have to solve it first. Maybe you have to simulate a swipe to unlock TWRP screen and then swipe to allow modifications, it could depend on what state was TWRP previously to that.

 

[iBowToAndroid]

ok, so what can I do now ?

Fix the screen

 

[imarsh72]

Have you tried scrcpy (spelt correctly) it let's you mirror the phone display and interact via mouse and keyboard. It does need adb debugging enabled though

 

[iBowToAndroid]

Have you tried scrcpy (spelt correctly) it let's you mirror the phone display and interact via mouse and keyboard. It does need adb debugging enabled though

The very first post says that ADB is unauthorized on his device

 

[imarsh72]

The very first post says that ADB is unauthorized on his device

I took that as meaning his pc wasn't authorised, however it IS in the title, my bad