Related
I have an HTC M8 phone and I set a pattern lock, and then stupidly forgot what it was. Everyone has been telling me to do a factory reset, but some of my photos are not backed up anywhere and I do not want to lose them. I need help either figuring out how to get into my phone, or how to recover the pictures that are on my locked phone. I have my Google account information, but that does not seem to be any help really. Please help!
Thank you!
Do you have a custom recovery? Even if not you should be able to boot to recovery, connect to pc, and in cmd prompt where your adb is(usually platform-tools in the Android sdk) type
adb pull /sdcard
That will download your entire sdcard to your computer. Could also just do adb pull /sdcard/DCIM to only get the camera pictures, other pics are in /sdcard/Pictures
Sent from my Nexus 6 using Tapatalk
After you enter the wrong pattern enough times, does the phone give you the option to sign on via your Google login?
Be aware that the security passwords and patterns exist for a reason, and its not commonly discussed here how to circumvent them. Such knowledge can be used by criminals that steal phones.
Also, I know this doesn't solve your issue, but its far too common to see posts like this. Waiting for a disaster to happen is not the right time to realize you should have been backing up your data. With all the options (SD card, sync to PC, cloud solutions - some built in) there is really no excuse not to be doing so.
redpoint73 said:
After you enter the wrong pattern enough times, does the phone give you the option to sign on via your Google login?
Be aware that the security passwords and patterns exist for a reason, and its not commonly discussed here how to circumvent them. Such knowledge can be used by criminals that steal phones.
Also, I know this doesn't solve your issue, but its far too common to see posts like this. Waiting for a disaster to happen is not the right time to realize you should have been backing up your data. With all the options (SD card, sync to PC, cloud solutions - some built in) there is really no excuse not to be doing so.
Click to expand...
Click to collapse
No , it does not give me that option which is frustrating as that is what many have told me to do. And yes I know, I'm kicking myself for not backing everything up. It has been a few months since I uploaded everything to my laptop. And at this point I was trying any possible option, and was given this forum to try to find help.
I am not sure to be honest... I'm not very knowledgeable about all this which is why I am having such a hard time. How do I boot to recovery? And every time I connect to my pc, it wont let me get any photos from the phone.
HolyAngel said:
Do you have a custom recovery? Even if not you should be able to boot to recovery, connect to pc, and in cmd prompt where your adb is(usually platform-tools in the Android sdk) type
adb pull /sdcard
That will download your entire sdcard to your computer. Could also just do adb pull /sdcard/DCIM to only get the camera pictures, other pics are in /sdcard/Pictures
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
megan.marie42 said:
I am not sure to be honest... I'm not very knowledgeable about all this which is why I am having such a hard time. How do I boot to recovery? And every time I connect to my pc, it wont let me get any photos from the phone.
Click to expand...
Click to collapse
If the phone is stock (never rooted, bootloader unlocked, etc.); and you don't know what custom recovery is, than you don't have it.
I plan to unlock my bootloader, but not rooting the phone yet, want to see if I can live without root. But in case I find out I couldn't I don't want to wipe my device again, thus unlocking now before actually moving all my stuff over from my old Nexus.
My question is, does it have any drawback to unlock bootloader? Does it actually affect anything (besides the hyper-annoying nag screen on boot), that would make it better just to leave it locked, and do the wipe and everything only if I ever decide to actually root it? Tough decision, I'd love to hear your opinions.
Thank you!
Assuming you aren't flashing TWRP, right?
Drawbacks... Security, maybe? Can't really think of anything else. OTAs will still work, as will all the usual upsides.
Upside, you can flash the latest factory images as soon as they are released.
PhoenixTank said:
Assuming you aren't flashing TWRP, right?
Click to expand...
Click to collapse
Yes, no flashing nothing, just a plain fastboot oem unlock, then pretending to be a basic user with a locked phone. I wonder if from the OS side anything can be perceived by apps, security/integrity checks, etc.
Yeah, then nothing in android will know, apart from the checkbox you need to enable in developer options.
Only when you change the boot or system images, does it really flag up anything. Hope that helps.
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
It stays checked. I haven't tried to unchecked it yet
IVBela said:
Addendum in case someone comes by this thread: unlocking makes you lose device protection features, or at least checking the box that lets you unlock does. Not sure what's going to happen with the checkbox after actually doing the unlock, will soon find out.
Click to expand...
Click to collapse
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
sordup said:
What are these 'protection features' that we would be losing if checking the OEM Unlocking (I assume you mean?) box??
Click to expand...
Click to collapse
This. So far this is the only drawback I found.
IVBela said:
This. So far this is the only drawback I found.
Click to expand...
Click to collapse
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
It may work with casual thug. Sophisticated thief will turn device off, reboot into bootloader, wipe device and take possession. Device protection is meant to discourage theft.
https://support.google.com/nexus/answer/6172890?hl=en
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
There are three sets of drivers needed. One for fastboot, one for adb and one for MTP. When device is in fastboot mode you use command "fastboot devices" or Mac equivalent.
gleggie said:
Not really sure what device protection does, as Android Device Manager still works.
Android Device Manager lets you remotely locate, lock, wipe, or ring your phone. So for example if someone stole your phone and you have Android Device Manager installed, you can locate it, and also lock it until the police can find it.
Click to expand...
Click to collapse
This doesn't help if they get your device and factory reset it. If they factory reset it before you have a chance to lock it down then you are screwed. With device protection even when you factory reset it, it will prompt for the previous google account the phone was set up with. If your bootloader is unlocked and they are knowledgeable thieves then they can just reflash everything and wipe it out fully.
I work at Swappa and we see this all the time. Someone will sell their device, factory reset it and send it to the buyer. The buyer gets it and can't set it up because device protection was enabled and it prompts them for the previous google account info that was tied to the phone when they try to set it up
Jemmy Ducks said:
I'm having some difficulty getting my Mac to recognize my 5x. I am able to connect to the phone with USB debugging normally when I first plug it in. The command ./adb devices lists the phone, and I am able to use adb reboot bootloader to reboot into fastboot mode. But once rebooted, the computer loses contact with the phone: ./adb devices returns nothing. Has anyone else seen this? Got a fix? Thanks. I should also note that I have enabled unlocking the bootloader in developer options.
Click to expand...
Click to collapse
I tried using fastboot anyway, despite seeing no devices listed, and lo and behold, it worked. Bootloader unlocked for flashing.
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
rbox said:
I need to come up with the best way to control recovery for the FireTV Stick. Right now, I'm leaning towards requiring USB ADB and having people use the mouse emulator. And then the bootmenu would not auto boot and you would need to manually select what to boot every time. Unless someone else has any better ideas?
Click to expand...
Click to collapse
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
deanr1977 said:
Would you not be able to make it boot normally like it auto loads on the aftv2 but instead of saying select left to boot normal or right for recovery you could say you have 6 seconds to use a certain adb command to enter recovery? (But not in those words HAHA) maybe auto display the ip address of the stick on-screen at the same time at the top of the screen?) I don't know if this is possible or not but just helping with sum ideas? Good luck mate
Click to expand...
Click to collapse
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
rbox said:
I guess I could autoboot after some long delay, I don't think 6 seconds is enough, something like 10 or 15 would probably work. It would have to be USB ADB, and not network ADB, because getting wifi to work is a little tricky. I looked into it when I was working on the FireTV2 stuff, and wound up shelving the idea.
Click to expand...
Click to collapse
Sounds ok though, for a working recovery I'm sure most users wouldnt mind waiting a few more seconds so if something goes wrong It can be undone/saved via a backup
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
rbox said:
So I found some information for setting up an ad-hoc wifi network, so I'll look into if that can be used for easier wifi...
Click to expand...
Click to collapse
You know best mate
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
ImCoKeMaN said:
Is there any way to see if it got stuck or didn't boot last time, and then boot to recovery once after that? like a file that gets touched early in boot and then deleted later? not sure if that really would make sense, but an auto recovery on failed boot would be pretty awesome. maybe ANY adb input on boot at all, counts as boot recovery so it can be faster? 1,
enter or something?
Any way to just detect if a pc is connected via adb and if so, then boot recovery?
Not sure if these will be useful, but wanted to share the ideas that came to my mind. I definitely would like it to standard boot to OS if possible though.
edit: actually if a-a cable was used on original fire tv didn't it auto go to fastboot?
Click to expand...
Click to collapse
So I can't figure out what happened the previous boot. Would need to modify the kernel for that. So I can detect if you're plugged in to the wall versus plugged in to a computer. But I think some people plug theirs into the tv usb port, and it would probably detect that the same as the computer. So maybe if it's wall, always boot straight, and if it's not plugged in to the wall, it's either plugged in to a tv or a computer, then it will show the bootmenu. You'll have I don't know, 10 or 20 seconds to adb shell in and run a command that will boot to recovery, otherwise it'll boot normally.
I was playing around with adhoc wifi, and I coudln't seem to get anything to work. Once I get recovery starting I may play around with it some more. The good news is I'm like 95% done for FireTV1... I think I figured out all the way I can possibly brick the stick, so I can avoid doing it. Haha. That was one of the reasons I wanted to get the FireTV1 working first. Because FireTV1 and FireTV2 I have ways to recover, the stick if anything goes wrong it's pretty much a lost cause.
Unfortunately, I'm not going to be able to work on much in a few days, for a while, so it'll probably be 2 weeks before I can release something for FireTV1 and really get stuff going for the Stick.
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
highspeedfelon said:
If I remember correctly one or more android devices I have seen would auto boot recovery if device failed to boot a certain number of times. A delay at boot could be as long as you wanted since its not like people reboot the device often. Another though is if the stick can detect the difference between a reboot and a power-on, maybe the delay could be different between them. If I wanted to reboot to recovery there are apps that can do that, so delay for a reboot could be shorter than one for power-on.
Click to expand...
Click to collapse
Thanks. I'll play around with some of these ideas too.
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
2WhlWzrd said:
The PC with dual operating systems come to mind. Where 1 OS is set as default and you have 30 seconds (default time, but adjustable) to choose the 2nd OS. If no choice is made it boots to the default.
Click to expand...
Click to collapse
That's how it works, the problem is how to make the selection. On FireTV1 and 2 it's with a keyboard. But you can't do that for the stick.
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
malfino said:
Use the power cycle as the trigger. The bootloader should have a time window (6 seconds) where a file (/cache/boot_recovery) is written to flash and removed after the time window has closed. If someone power cycles the device during this window, the file remains and can be checked during start up and evaluated.
For example.
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
2s user power cycle
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> found
0.2s booting recovery
0s Booting up.
0.1s checking file which indicates recovery in (/cache/boot_recovery) -> none found
1s Show begin of recovery time window -> touch /cache/boot_recovery -> countdown 6 seconds
7s rm /cache/boot_recovery
7.2 booting normal image
Click to expand...
Click to collapse
Interesting... very brute forcy, but it could work.
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
dafunkydan said:
...in Addition, one could think of a small little app called reboot to recovery, that does nothing more than writing that little file to cache and reboot?
Edit: and thank you so much rbox for your efforts! Im on aftv1 and completely rely on your magic thanks mate!
Click to expand...
Click to collapse
That would be a great idea, maybe put the apk as a systems app so it can't be deleted by mistake would also be a good move
Sent from my SM-G900F using Tapatalk
OK. So time for some good news. I figured out how to get wifi going on the FireTV2. So using the same method, I'm pretty sure I'll be able to get it going on the Fire Stick. If it all works out, you won't need USB to control it. In other news, I think I've figured out how the wifi remote works, and I think I may be able to make it work in recovery too. I won't hold up the FireTV 1 recovery for it, so I'll release that as is without wifi and without the remote working, and then as I'm working on recovery for the Stick, I'll get wifi and remote working for everything. I had some issues with the FireTV1, so I don't know if I'll be able to get wifi working for it.
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
No. There will be a few options.
ImCoKeMaN said:
Hmm will the new WiFi remote be a requirement? I have the original with the bt remote. I did like that timing method as an option though as I plan to have stick to travel and not have otg most of the time so slightly faster default boot would be nice.
Click to expand...
Click to collapse
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
highspeedfelon said:
I think by wifi remote he means the app for android not another device. If you havent tried the app its pretty handy.
Click to expand...
Click to collapse
No, I mean the physical "Voice Remote" that uses Wifi Direct. I think the android app probably uses a complicated Amazon protocol that requires more than I can throw at it in recovery.
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
beefriendly said:
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
Click to expand...
Click to collapse
This tool might work for you. Ive never used it myself but it looks promising. It supposed to be able to control your phone on your pc.
For the custom recovery, it should tell you what model you have when you boot into download mode but the TWRP for the note 4 has been unified so it should work either way. This link is for the most recent version. Get the .tar file if you're looking to use ODIN to install it.
Thanks for the reply! The tool you inked to requires USB debugging switched on. I was looking at it previously but didn't consider it because of this. I have USB debugging off, and the process I described with the dr phone windows application /download mode, doesn't turn usb debugging on.
Is there a way that I can flash a recovery for the note 4 that has USB debugging enabled from the start? If anyone knows please describe the process or post the link.
I think I need step by step instructions or screen shots for what to do with the Note 4 twrp recovery. I am trying to acquire a second phone so I can view the screen and know what buttons to press, but so far it is not looking like I have enough information to do sms backup from the twrp menus..on the device when I can't see the screen.
I see reference to being able to use adb commands to control the twrp recovery / backup process, but so far I haven't found anything that will help for my particular situation. If anyone knows what adb commands to use to pull the note 4 sms files , or a backup that includes them, PLEASE let me know.
thanks again
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
Click to expand...
Click to collapse
do you have the default recovery ? or a custom one ?
zoey_96 said:
Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
Click to expand...
Click to collapse
No
loopypalm said:
do you have the default recovery ? or a custom one ?
Click to expand...
Click to collapse
Default, which doesn't have many options on Xiaomi. :/
loopypalm said:
No
Click to expand...
Click to collapse
Sad to hear that. Are there any alternative options that could solve my problem? I'd really rather not factory reset.
zoey_96 said:
Default, which doesn't have many options on Xiaomi. :/
Click to expand...
Click to collapse
if you had twrp or similar your problem would be solved ...
zoey_96 said:
Are there any alternative options that could solve my problem?
Click to expand...
Click to collapse
not as far as i know, ask in ADB thread if you find any
Updated with extra info in case anyone else has any ideas.
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Elinx said:
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Click to expand...
Click to collapse
Do you mean that the reason it doesn't accept the correct pattern anymore is for security? I would have thought it would still accept the correct one, at least after several tries of the same thing. Being completely locked out even when you know the correct password is a little strange to me.
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
Click to expand...
Click to collapse
Howdy bro (I also have a Xiaomi Redmi Note 8).
I've been almost two intense weeks reading and watching the XDA forum, trying somehow and I did not find the way to unlock it .... Besides that I have the Bootloader disabled it makes me more difficult, because for that I need to format my phone and is what I do not want .... Already today is my last day of searching and I think I will have to leave my memories behind and Format my cell phone.
I leave you a thread of a user that explains well the process of why you can not:
A Comprehensive Guide to getting Past the Android Pattern Lock Screen
So, here's the situation I’m in. Also I am 99% sure I got something wrong so please tell me. I’m past the pattern lock screen so ADB won’t directly work to unlock the lock screen. If I was at a pattern lock screen, I could use ADB to unlock the...
forum.xda-developers.com
and several more of the many threads that I searched, maybe it will help someone:
[Xiaomi] How to unlock phone after forgetting the password.
Hello, today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs. I have Poco F2...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[GUIDE] Unlock bootloader without losing user data.
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data. 0 - Read the whole guide before proceeding and proceed at your...
forum.xda-developers.com
[GUIDE] Redmi K20 Pro - Unlock & Root Information, Links, Tools and Instructions
Like many, I was overwhelmed with information when trying to unlock, flash, and root my phone. After many failures, I decided to compile the good information all in one place. I hope this helps. If it does, please consider buying me a beer...
forum.xda-developers.com
Recovery without data loss
Hi Community, you are my last salvation. I am owner of Pixel 4a 5g since half a year and now it cannot boot anymore. I see only the google-"G" and the loading bar nothing else. I can start the Boatloader but before i do a factory reset i need to...
forum.xda-developers.com