• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

charging only to MTP or PTP

maksimus

Newbie
Oct 22, 2020
14
0
My Nokia 2.2 screen was locked and I forgot the password but I'm having the USB debugging turned on, on my phone.. but the USB behaviour is set to CHARGING ONLY.. I made too many attempts that the phone asks to make my every next trial after 84000 seconds approx.. Is there anyway to recover all the call lists and app data from my phone?
 
MTP mode won't actually help you: USB file transfer that way isn't available with the screen locked even when MTP mode is set (I have my default USB connection mode set to MTP but can't actually use it without unlocking).

USB debugging doesn't require MTP: it works perfectly well with the USB connection set to charge only (I just tested to make sure before typing this). So the problem is more likely that you need to authorise the USB debugging connection, and if you didn't tell it to not ask again with that particular computer you would need to unlock in order to authorise (I know the authorisation has changed a bit over the years, so I'm describing the current situation with Android 11, as that's what I'm using).

Unfortunately I don't have an answer: if USB debugging isn't working with the screen locked I can't think of a way of accessing the data which doesn't require unlocking the screen.
 
Upvote 0
Normally after a number of failed attempts you should see a forgot password option pop up on the screen and have an option to enter your Google account credentials.

Screenshot_20201022-124411~2.png
 
  • Like
Reactions: ocnbrze
Upvote 0
Unfortunately I can't think of one. Actually if I could it would be problematic to post it publicly (because anyone can read it, so this would be telling any thief how they could access their victim's data!), but if ADB isn't responding (whether because USB debugging is off or the computer hasn't been authorised to use it, or the authorisation has expired) then you need to unlock the screen to use that.

Which doesn't really leave anything on an unrooted device. If you have a custom recovery then there would be ways, but that seems unlikely to me (as you've not mentioned it). Installing one requires unlocking the bootloader and I don't think Nokias have unlockable bootloaders, plus unlocking the bootloader performs a factory reset on most phones, and in many cases you need to enable bootloader unlocking first, which means getting pas the lock screen again. So unless it's already been done, it won't help now.

And that's the same for every other solution I can think of: there are things you could use if you'd already installed them or set them up, but doing that now requires getting past the lockscreen.
 
  • Like
Reactions: ocnbrze
Upvote 0
Oh, whoa, this is a completely different situation from what I'd thought: the problem is purely on your computer. And it is actually proposing a solution.

So have you done what it says: typed '.\adb devices' rather than 'adb devices'? What happens then?

I did, but it keeps showing the same thing.. I mean it shows the path and waits for the command to enter..
Just like I showed it in the photo.
 
Upvote 0
Oh, whoa, this is a completely different situation from what I'd thought: the problem is purely on your computer. And it is actually proposing a solution.

So have you done what it says: typed '.\adb devices' rather than 'adb devices'? What happens then?

See, this is what it looks like... No response.
Shows the path and still waits for my command.
 

Attachments

  • IMG_20201025_062446268.jpg
    IMG_20201025_062446268.jpg
    229.3 KB · Views: 211
Upvote 0
'.\adb' won't attempt to communicate with the phone because it doesn't specify a command (though I'm a little surprised it didn't return a list of adb commands)

Try '.\adb devices', and if that responds with your serial number you can try other adb commands in the same way.

Otherwise maybe reinstall adb.

Thank you #Hadron, will try and keep you posted.
 
Upvote 0
#Hadron, all the day I've been trying different ADBs, disconnecting and reconnecting the phone, changing physical ports, 'kill-server' and 'start-server' commands... And when I accidentally typed 'kill server' instead of 'kill-server' 👇 this came up, a list of adb commands.. but the device still showed as unauthorized.. what does it mean.
 

Attachments

  • cam_tmp_1.jpeg
    cam_tmp_1.jpeg
    223.9 KB · Views: 201
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones