I forgot my PIN.
My screen's sensor is off (it acts up where I can't even enter guesses even if I knew my PIN.
Is there a way that I can use ADB to access the pictures and video from my phone? That's all I want to do.
I don't know if you can access files via ADB if the screen is locked, but it is possible to use ADB commands to unlock your device with your PIN. Here is a guide. This will only work if you already have USB Debugging enabled and your PC's ADB debug key is authorized on your device.
V0latyle said:
I don't know if you can access files via ADB if the screen is locked, but it is possible to use ADB commands to unlock your device with your PIN. Here is a guide. This will only work if you already have USB Debugging enabled and your PC's ADB debug key is authorized on your device.
Click to expand...
Click to collapse
I doubt that USB Debugging is activated - at the time that I bought that phone, I don't know if I knew about ADB commands.
The PC that I am looking to use wasn't built at the time that I bought that phone either.
Does that mean I cannot use ADB commands to unlock my phone?
Vanatoon said:
I doubt that USB Debugging is activated - at the time that I bought that phone, I don't know if I knew about ADB commands.
The PC that I am looking to use wasn't built at the time that I bought that phone either.
Does that mean I cannot use ADB commands to unlock my phone?
Click to expand...
Click to collapse
If USB debugging wasn't enabled and the PC wasn't authorized, then no.
Related
I have a program thats called SHAREKM and when i plug my phone into the computer, it recognized the phone is there but it doesnt give the authorization for debugging on the phone. I was told that with 4.3 you have to authorize every computer thats plugged in........I noticed this when I tried to use REVONE......I had to use a ADB version higher than 1.0.29 or something like that in order for it to show the authorize computer on my phone. Anyone have any ideas how I can get this to work? Thanks much!!
Alright I got it to work, I just had to download the 1.0.31 ADB zip and then ADB to my phone from my computer, accept the authorization and it worked!!
After flashing back to Mk2 and trying to regain root using safe root. The installer will not see the phone no mater what I do. I've redone drivers, tried multiple computers I've enabled and turned on Debugging. All of that. EVERYTHING else see it. But not ADB it sees my Galaxy s3 no problem.
I first rooted the phone without safe root. But I can't find anything anymore I tried to use terminal emulator but the phone blocks it. Anyone have any Ideas? should I reflash MK2 in odin?
XRSTOY1 said:
After flashing back to Mk2 and trying to regain root using safe root. The installer will not see the phone no mater what I do. I've redone drivers, tried multiple computers I've enabled and turned on Debugging. All of that. EVERYTHING else see it. But not ADB it sees my Galaxy s3 no problem.
I first rooted the phone without safe root. But I can't find anything anymore I tried to use terminal emulator but the phone blocks it. Anyone have any Ideas? should I reflash MK2 in odin?
Click to expand...
Click to collapse
Did you connect as Media device? Then try adb devices.
Yes I did as Media device but what do you mean by adb devices where is that? I did try to find it in a adb shell no luck I tried a totally different computer as well no go.
XRSTOY1 said:
Yes I did as Media device but what do you mean by adb devices where is that? I did try to find it in a adb shell no luck I tried a totally different computer as well no go.
Click to expand...
Click to collapse
"adb devices" is a command using the ADB utility. It lists what devices it sees connected.
For example, no phone:
C:\temp\android>adb devices
List of devices attached
Click to expand...
Click to collapse
Phone attached:
C:\temp\android>adb devices
List of devices attached
32cec1eb device
Click to expand...
Click to collapse
It's also possible that USB debugging got somehow disabled - settings/more/developer options/usb debugging. Make sure it's selected.
k1mu said:
"adb devices" is a command using the ADB utility. It lists what devices it sees connected.
For example, no phone:
Phone attached:
It's also possible that USB debugging got somehow disabled - settings/more/developer options/usb debugging. Make sure it's selected.
Click to expand...
Click to collapse
can you also toggle the revoke USB debugging authorization to reset the communication with adb?
decaturbob said:
can you also toggle the revoke USB debugging authorization to reset the communication with adb?
Click to expand...
Click to collapse
Yes, that also can get it re-enabled. Unplug, revoke authorization, unlock the phone, then re-plug it and re-authorize.
In those cases, however, the phone will show up in "adb devices" as "offline".
Thanks I did ADB devices and it showed my device but it said offline, I tried the Revoke Authorization but I can't get the phone to ask if the computer is ok?
Problem solved
I tried the Revoke Authorization but I can't get the phone to ask if the computer is ok prompt. I did a full factory reset and cache wipe four times still only shows offline. I rebooted into recovery saw load update from ADB and adb start-server and got host but couldn't load the install.bat
Problem solved follow this guide
http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html
XRSTOY1 said:
I tried the Revoke Authorization but I can't get the phone to ask if the computer is ok prompt. I did a full factory reset and cache wipe four times still only shows offline. I rebooted into recovery saw load update from ADB and adb start-server and got host but couldn't load the install.bat
Problem solved follow this guide
http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html
Click to expand...
Click to collapse
That's one I wouldn't normally think of - if that worked for you, then it means that you had an old, out-of-date version of ADB on your system.
Thanks for letting me know about the fix, as it's a pretty hard one to detect and easily fixed one you know about it.
IT IS the one that came with saferoot didn't work,
XRSTOY1 said:
IT IS the one that came with saferoot didn't work,
Click to expand...
Click to collapse
Saferoot comes with adb 1.0.31 - the same files as the one in the post you pointed to. I'm not sure what happened here, but it doesn't matter as you now have it fixed.
Hi, first of all sorry for the spelling, i'm from Argentina and my english is not the best.
i have a samsung s3 phone with a broken screen. I think also the touch-system is broken.
I want to access the device via VNC to configure it as a media server, or a camera or maybe buy the mhl cable and use it as a smart-tv.
I tried to install every app available but all of them requires me to authorize the adb interface (i have it enabled).
on the adb command linethe phone shows as "unautorized"
i tried the solution of rebooting the phone on recovery-mode and change the adb hosts files to have it autorized with no luck.
In my several tests i think i broke the download mode and recovery mode because now it doesn't seems to reboot in those modes, it always boots in normal mode no matter wich keys i press.
So, now i have a working cyanognemod rom (i don't remember wich version, if it's a 5.0 or 6-0 rom).
I don have acces to recovery mode.
I dont have access to download mode.
I don't have wifi connected.
I have adb enabled.
I dont have adb autorized.
I tried the vysor app, the teamviewer app etc.
Is there any app to access the phone (vnc, or edit system files remotely) without autorize the adb interface?
I bought a usb-jigg (it on its way) but i think it wont help, maybe it will allow me to enter download mode, but if i flash a new stock or custom rom i will be in the same place, because i dont have a way to autorize adb whitout a working screen
So, i woinder if there's an app or script to authorize adb, or directly to access the phone wihout having to enable it
Thank you in advance
Greetings
Is there a list on the phone of authorised computers for adb communication?.
Some devices have a popup that asks if adb is allowed for that pc when you connect via usb.. You might have accidentally blocked it or even missed the prompt..
A shot in the dark but worth a try!.
Beamed in by telepathy.
shivadow said:
Is there a list on the phone of authorised computers for adb communication?.
Some devices have a popup that asks if adb is allowed for that pc when you connect via usb.. You might have accidentally blocked it or even missed the prompt..
A shot in the dark but worth a try!.
Beamed in by telepathy.
Click to expand...
Click to collapse
i tried that with an usb-otg adapter and a mouse with no luck
i can't find any possible solution. There has to be one.
i think there must be an app or script to authorize adb
Hello, did you find any solution on this issue? I have a Samsung phone with a broken screen, I can access the system via twrp via adb shell. but I don't know how I can integrate a vnc server. I will be glad if you help. thanks
I've waited 17 days after linking my Mi account to my Mi8L. I've unlocked more than half a dozen Xiaomi phones, so it's not new to me. However, it stops at 99% and spits out an error message in Chinese. Does anyone know what it means? https://drive.google.com/open?id=1dl6tPZdx7HfFwxQWel3hhjl9doFE5s8S
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible.
You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Sorry for my bad english
Also, check this thread:
http://en.miui.com/thread-4456547-1-1.html
Snowdine said:
It means you haven't been using the phone for the necessary amount of time, so unlock isn't possible. You're probably on a shop or chinese variant that need you to wait 30 days until unlocking.
Click to expand...
Click to collapse
It's strange because when I tried previously, it told me I had to wait 15 days, and I waited longer than that (I took note of the date and time).
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
rinampa said:
I do not know if you can help me, I was unlocking the Mi 8 Lite requested 15 days to wait after this period I was unlocking and to my surprise the fastboot mode when I connect the USB cable it erases and I can not unlock.
Developer options enabled, usb debugging enabled and oem unlocking also recognizes more when I log in to fastboot it shuts off
Click to expand...
Click to collapse
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
Do you have adb and drives for my 8 lite?
rinampa said:
Do you have adb and drives for my 8 lite?
Click to expand...
Click to collapse
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
SubwayChamp said:
Download from here SDK Platform Tools and unzip it preferably in your main drive, you can do all the adb/fastboot processes inside this folder for easier task: https://developer.android.com/studio/releases/platform-tools
And here they´re the USB drivers for our device, choose from Mi 8, it´s the same https://www.xiaomigeek.com/download-xiaomi-usb-driver-windows.html
Click to expand...
Click to collapse
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
rinampa said:
Unfortunately I do not know what happens adb fastboot does not work, I did all the procedure I rebooted in option 7 I installed adb drive the curious one and that the pc recognizes the device opens the internal storage is difficult, I have always unlocked my devices.
Click to expand...
Click to collapse
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
SubwayChamp said:
I'm not sure if you're doing it rightly. Adb works when device is on and fastboot when device is in bootloader/fastboot mode.
When you type for first time adb devices with device power on then you have to see a message from your android screen asking if you want to allow USB debugging, you have to tap on always allow and then in ok.
Provide some screenshot from your pc to see the fail.
Click to expand...
Click to collapse
Yes I am aware I have experience always unlocked my gadgets something strange here on my pc or on the device I will try on another pc thank you attention you are correct, thank you.
SubwayChamp said:
Try starting the process from adb, don´t use hardware buttons and see what happens.
With device on connect to pc and pay attention that pops up a message "Allow USB debugging" then tap on "always allow" and "ok".
Now type
Code:
adb devices
to see if pc is recognicing and if it is ok type
Code:
adb reboot bootloader
.
Open normally MiFlash Unlock and sign in to your account and follow the scrren on instructions. Provide some screenshots if something fails.
Click to expand...
Click to collapse
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
rinampa said:
I did as I wrote I entered the fastboot mode with adb and fastboot and the black screen with something written on top of the mini-screen that can not read appeared again, I open the unlock box and this occurs.
Click to expand...
Click to collapse
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
SubwayChamp said:
Plz provide some screenshot from your pc to see what happens on fastboot windows and on MiUnlock Tool; it could happen that you were missing something.
Click to expand...
Click to collapse
This is so after connecting fastboot mode with MiFlash Unlock
rinampa said:
This is so after connecting fastboot mode with MiFlash Unlock
Click to expand...
Click to collapse
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
SubwayChamp said:
Ok, your pc is not detecting your device connected in fastboot mode.
Try uninstalling all the drivers; those that you don´t use and those related with Xiaomi devices and install Mi PC Suite just to get installed the drivers https://mipcsuite.com open it for first time and connect it with your device on just to update drivers between both but when you´ll go to use MiFlash Unlock close it.
The USB cable used for your device is not to be shared with other devices so any of them creates a kind of data map on data wires and pc can have a sort of mistake trying to detect your device rightly.
Then to make all these steps start the process from adb as mentioned before sending with adb command to your device to bootloader/fastboot mode, this is just to confirm that pc is detecting it at both levels; adb and fastboot.
Click to expand...
Click to collapse
É Ask me to update my device use Miui beta 10 9.4.25
rinampa said:
É Ask me to update my device use Miui beta 10 9.4.25
Click to expand...
Click to collapse
Uodate it, maybe this corrects some issues
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
rinampa said:
I discovered what is written on the upper left side of the screen, press Key to shutdow. According to research I did not advance anything is USB input problem try on another Pc or a USB Hub cable.
Click to expand...
Click to collapse
Of course, this is what´s written.
When PC detects device connected on fastboot or download mode then it holds it to avoid that it reboots while some data is transferring from and to each other.
If you put device on fastboot mode without connecting it to any PC then it will shutdown in 4 seconds aprox.
But like your case when PC detects that a device is connected but not in any transferring mode then it prompts to shutdown device.
For this I said that your PC is not recognicing it at fastboot mode, and installing again the drivers could solve the issue.
alxsduarte said:
Same with me.
Use Mi Unlock 2.3.803.10 (old version).
Works perfectly.
Click to expand...
Click to collapse
You right work ?
So i forgot the PIN number on my old phone which was not rooted, had no recovery software (Cwm, Xrec, etc.) installed on it, and has usb debugging and auto-mount disabled. We don't know the google account associated with the phone. Basically all I have is the phone and a usb cable. Is there a way to get the user data out of it? Adb won't recognise the device btw. I do apologise if it's a stupid question. The phone automatically connected to the wifi, and I'm on Linux, if that helps. But I managed to get into recovery but adb only recognises the device in sideload mode. The files inside the phone is extremely important to me because it contain photo of my family member that were passed away.
Phone: Vivo V7 Plus
I wanted to try brute-force the PIN with program but unfortuntely the phone will cool down for 7000 second (3hours+)
A phone typically knows of 2 USB modes: ADB & MTP. If MTP mode was enabled and phone supports a USB-C connection then it should be possible to fetch the user-data you're interested in.
jwoegerbauer said:
A phone typically knows of 2 USB modes: ADB & MTP. If MTP mode was enabled and phone supports a USB-C connection then it should be possible to fetch the user-data you're interested in.
Click to expand...
Click to collapse
Hi, first of all thanks for your respond. In order to enable MTP i need to have the phone unlock right? how can i enable MTP if the phone is locked ?
All I know is that ADB is the door to any Android device and nothing than that.