Database Info

Pattern lock forgotten (yup)

Hi, I know there are several threads and I'm pretty sure I'm screwed but I just wanted to check with you all before I wipe all my memories :
- OnePlus One unrooted
- Enabled the pattern lock screen yesterday, and dk if I'm stupid or what but it won't recognize the pattern today (it's probably me - anyway result is the same)
Attempts :
- Google Android Device Manager, no use (tells me that there is already a lock screen so it can't switch to password lock)
- adb won't recognize the phone cause nothing is enabled on it (developer mode or whatever)
- phone is recognized on fastboot but, well, since it's unrooted, I don't think I can do much
Can I say bye bye to my data?
Thanks!

This is old one, but see if this helps:
http://phandroid.com/2014/05/13/forgot-lock-pattern-android/

Unfortunately OnePlus One doesn't have that option ("Forgot Pattern ?")
Thanks anyway for the answer!

instant5 said:
Can I say bye bye to my data?
Click to expand...
Click to collapse
Yes. This would be the perfect time to unlock the bootloader and put a custom recovery.

OK so from what I understand unlocking the bootloader would wipe the data right? I'm seeing recovery tools that scan the phone in order to find deleted files. Does the wipe data clears everything or would that make sense to do something like this and try to recover what I can :
- unlock bootloader
- install custom recovery
- find a way to enable USB debugging for the recovery tool (ie, if possible, not install a full system in order not to overwrite recoverable files) : is that possible with a custom recovery?
- run the recovery tool
Is there a step that doesn't make sense?

Install CWM over stock recovery

My friend has a J4+ for which he forgot Pattern lock. its on latest pie update - J415FXXU2BDSP
His USB debugging is off, OEM unlock is off.
Now, he wants to unlock the phone, but doesnt want to lose data because he has some sensitive data which would help in his divorce case.
I thought of using recovery to delete the gesture.key file, but his recovery is stock.
So, need to install custom recovery first.
Tried to install TWRP from Odin, but failed because of FRP lock.
Tried Aroma installer from SD card, but it says signature verification failed.
Any way I can get custom recovery installed on his phone?
I know CWM would work, but couldnt find it anywhere for this particular model (i believe CWM is very old now).
Any help would be greatly appreciated.
Thanks in Advance.

Nobody forgets a pattern lock if you regularly use the device.
Even then mine is the same for all devices, so even if I hadn't used a particular device for a good while I'd still know it.
Some one elses device by any chance?

ashyx said:
Nobody forgets a pattern lock if you regularly use the device.
Even then mine is the same for all devices, so even if I hadn't used a particular device for a good while I'd still know it.
Some one elses device by any chance?
Click to expand...
Click to collapse
Good thing you don't manage devices at a big company then...
Some people manage to forget passwords after 4 hours of work. :silly:

Using ADB in recovery mode - recovering files from a locked phone

Hello, here's my problem: I accidentally put a schematic as a code on my phone that I immediately forgot. Now that I only have access to the lock screen, I can't put my phone in file transfer mode because I'd like to retrieve it before resetting my phone (which is, by the way, a Redmi Note 6 pro up-to-date, not rooted, no TWRP, and the bootloader is still locked). It's possible to use ADB to retrieve files, but I can't allow access to the computer from my phone either, so ADb is unusable when my phone is turned on. Nevertheless, it's obviously possible to use it in recovery mode, if you have the right drivers. I went to look for them, but during the installation, Windows tells me that a better driver, ADB devices, is already installed, and I can't install my driver. I obviously tried to find a way to ignore this warning, notably by asking during the manual driver installation to search the hard drive, but it tells me via this method that no driver is contained in the indicated directory (which is wrong, at least from what I see, the necessary files are all there).
So I search either :
- a driver that won't have this problem and that will allow adb to work in recovery mode;
- a way to force the installation of this driver;
- another way to use ADB in recovery mode;
- another way to recover my files while the phone is locked and I can't give it access to the computer.
Otherwise, any idea that can solve my problem is fine with me.
Thank you in advance and have a nice day!

https://c.mi.com/thread-2207444-1-0.html
For drivers.
And use OrangeFox Recovery

He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog. https://www.androiddata-recovery.com/blog/how-to-retrieve-deleted-data-from-xiaomi-redmi-phones
On method 4 is maybe a reason for your matter.

ALcAtRas500 said:
He can't install any custom rec. The phone not unlocked. I don't think you have a Chance to get your data. For future make the most files that you don't wanna Lose on a sd card not on intern storage.
Update: on little search on Google i found this Blog.
On method 4 is maybe a reason for your matter.
Click to expand...
Click to collapse
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...

Kyrela said:
Thanks, I will try this and and I'll up the topic and say whether or not I passed. And don't worry, I won't make that mistake twice, that'll teach me...
Click to expand...
Click to collapse
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...

Kyrela said:
The message wasn't sent... well, I was saying that the website was affiliated with a software, and was totally lying since the data recovery function is only compatible with samsung. So it looks like there's no solution for me...
Click to expand...
Click to collapse
Unfortunately for you you cannot recover your files. As your phone's bootloader is locked and even though some softwares claim to work even with formatted phones they don't because of encryption and this new type of formatting where the data gets destroyed. Even It happened to me once I had unlocked and rotted my phone by for some reason when I was going back to stock ROM my phone data got destroyed dueto my carelessness during encryption and that's the story. After that I tried different softwares to recover photos but non of them worked. Only thing is you can get your Device unlocked

Question BYPASSING DISK ENCRYPTION [SM-A125F]

Hello everyone,
So I've been off the fourms for quite some time, woun't go in detail about that. And as some might know I've broke my LCD touch screen. I got a replacement and replaced it with no isuess, works perfectly.
But...
I forgot the gesutre key I set on this phone because I haven't used it for months, and used my other A217F for the replacement.
I haven't been doing anything related to android so I forgot quite the stuff I use to know. My question is how can I bypass the disk encryption and pull the GESTURE.KEY from USERDATA. It OEM unlocked, rooted via magisk, and runs TWRP custom recovery. This is quite the older version of TWRP. I can flash it to the new one but the SYSTEM root is still under encryption. Idk if maybe I can dissasemble it from the SCATTAR, or pulling it via ADB (wich probably woun't work). I also want to help others who want to achive this so that's also one of the points for this thread. I'll list some of the info of this phone:
SM-A125F
BUF9 firmware SW_REV 1
Patched BOOT and VBMETA images via magisk
Custom recovery (TWRP)
Fixed IMEI and BASEBAND
Thanks,
Krypton

You can't bypass encryption.That's the point of it.To make sure the data is unreadable without the right key.If there was a way to read encrypted data without the key then it would be pointless

jesus201820 said:
You can't bypass encryption.That's the point of it.To make sure the data is unreadable without the right key.If there was a way to read encrypted data without the key then it would be pointless
Click to expand...
Click to collapse
Yea Ik the point is it can still be forceivly disabled via running unsinged firmware. It's OEM unlocked, I should have every ability possible.

Brick. Stuck at "Qualcomm Crashdump"

Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.

Ganapatya said:
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Click to expand...
Click to collapse
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.

lm089 said:
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
Click to expand...
Click to collapse
Thank you for your reply.
is your phone running stock OOS or some custom ROM?
Click to expand...
Click to collapse
Stock OOS, android 10, last release.
Then: how much do you know about flashing recoveries, ROMs etc.
Click to expand...
Click to collapse
I have basic experience installing customs roms, rooting, twrp, unlock fastboot...following tutorials, of course.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
Click to expand...
Click to collapse
here someone says that in theory it would be possible if you have the usb debugging enable, but silly me I had it open but I deactivated it I think, so I'm not sure if I have access or not.
OnePlus 6 Stuck At "Qualcomm Crashdump" Screen All A Sudden | Data Retrieval Critical
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in. I was using my OP6 normally today and while I was...
forum.xda-developers.com
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
and then finally try to recover anything that is in you backups.
Click to expand...
Click to collapse
but if I do all that flashing process any backups that are in the internal memory will be erased, right?
I had photos, files, whatsapp chat history, documents...etc and they were all in the internal memory. It is not a great loss but it is important for me to be able to recover it.
in your current situation it may be extremely difficult if not impossible to secure any personal data now
Click to expand...
Click to collapse
for me it is more important to recover the files than to recover the phone. your words are discouraging
I have read other posts and maybe being able to install on top (dirty install) the same rom I have, would leave the system as it, is being able to access my files. Not even installing the whole rom but extracting the boot image from the rom and then installing it. but I don't know if I can install a rom or boot image from fastboot, or if I need to have a working TWRP first.
It is said here:
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82257413
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82261087

Ganapatya said:
your words are discouraging
Click to expand...
Click to collapse
of course that is not my intention. I just try to be realistic
As I wrote in my post, my knowledge is quite basic. I know what I read , and what I experienced with my different devices. So again: you may find instructions and real-life stories showing you ways out of there.
My experience is that you cannot connect your OP6 phone to your PC via ADB while in bootloader / fastboot mode.
a) It's either one or the other: bootloader <=> fastboot or recovery / system <=> adb. Other devices may have different options but we're not talking about Samsung but about OP.
b) I did some additional research last night but I couldn't find a single source talking about *read* access to user data from fastboot. All you can do there is flash i.e. overwrite partitions
c) keep in mind that most probably your personal data are encrypted. So even if you find a way to access your personal data from bootloader / fastboot you may not be able to read it
d) I never used MSMtool, never had to. But I did some more research about it. It looks as if you could re-flash stock ROM using that tool but to the cost of wiping everything. At least that is what the tutorials I found are saying
That said I'd say you don't have much to lose and can go trying out some things.
From my experience the qualcomm crashdump error can have it's source in a malfunctioning recovery solution; I had that when flashing a wrong TWRP version that would not be in harmony with the previously flashed OOS firmware.
From what I read our devices don't have a separate recovery partition, instead it somehow lives somewhere/somehow in the boot partition (experts: please don't crucify me if that is wrong ). So if that is the case one idea would be to extract the boot image from the stock ROM image then flash that to /boot/ from fastboot. Don't know whether that really works and helps, but in theory you would have a default boot partition and kernel *without* a conflicting recovery solution.
In case you're successful you may be able to boot into system and make backups of everything that's valuable to you.
Again: this is extremely wild guessing here, and you'll have to read in a bit on how to properly extract parts of the ROM image.
I also would *strongly* recommend that you continue asking for help in a more technical thread like the LOS19.1 one or Funk Wizard's thread about unlocking and flashing our OP6.
I wish you all luck you need!

I think your best bet it a HW solution, get someone to:
1. replace the modem IC, it's the possible cause of the qualcomm crash
2. solder a direct connection to the internal memory so you can recover your data