Database Users

Urgent help needed. Locked out of phone.

I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I tried looking for troubleshooting guides, but unfortunately Marshmallow no longer has a "forgot code?" option. Also, I tried Android Device Manager, but it tells me since my phone already has a lockscreen, I no longer need to add a password (which I intended to do, in order to know said password)
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.

xdmatt said:
I was poking security options within my phone, and I accidentally locked it with a pattern that I cannot recall.
I would greatly appreciate any help, since I really don't want to factory reset, since I got lots of pics I don't want to lose.
Click to expand...
Click to collapse
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
edit: this does not work on marshmallow[tested]
i think this will help you http://forum.xda-developers.com/note-4/orig-development/bypass-lock-screen-pattern-password-pin-t2948336

bablu048 said:
google is your friend http://www.addictivetips.com/android/how-to-bypass-disable-pattern-unlock-on-android-via-adb-commands/
Click to expand...
Click to collapse
hopefully he enabled the usb debugging option

pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.

pijes said:
hopefully he enabled the usb debugging option
Click to expand...
Click to collapse
bablu048 said:
nope, this does not help. Just now i tried this on my device..if the device is locked adb doesn't recognize the device. this method does not work on marshmallow.
i don't know about lollipop. maybe it works.
Click to expand...
Click to collapse
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!

xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.

bablu048 said:
you don't need to be rooted to access recovery and install files.
for future reference see the 2nd link i posted. I haven't tried that yet, i'l report when i try.
Click to expand...
Click to collapse
He wouldn't have been able to use it because you need a custom recovery to flash that file.

Well... I guess you know the system works? Probably not great for there to be an easy or sure-fire way to unlock a phone if you don't know the security details.

If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.

AtomicStryker said:
If it's just data you need, recovery mode should allow you to copy it off the device via USB (if you didnt encrypt the device). Getting into a phone you really locked yourself out of is probably not possible.
Click to expand...
Click to collapse
i want to know how to copy data from the device through recovery. do you know the process or where to find a guide?
edit: thanks for the idea. i hadn't thought that way.

xdmatt said:
Unfortunately, my phone is stock and non rooted, but luckily I could guess the pattern.
I still would like to know for future reference, since Android Device Manager did a great job at getting my phone's location and making it ring... just not unlocking it!!
Click to expand...
Click to collapse
For preventative measures, Tasker is your friend. Have a "Plan B" microSD with a special .txt file on it, and have Tasker detect SD inserted and scan that file. If the file matches, then Tasker should wipe /data/system/gesture.key and password.key, and sqlite3 into settings.db and "update system set value=0 where name='lock_pattern_autolock' " to unlock your device.
In the case of an aftermath, it is now (as of today) possible to recover files/photos from the lockscreen without root, ADB, or custom recovery. Just an internet connection, linked Google account, and access to the notification drawer. I just published my first app, Locked-out Phone Backup, that is similar to the old Screen Lock Bypass Pro for Gingerbread, but instead recovers files instead of disabling the screen lock, so no root is required!
Hope this answers your question!

Well, try some password remover.

ADB does not see my US996

I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?

Did you activate developer settings with USB debugging

ewingr said:
I found a very small number of posts about how to get ADB to recognize the V20, but no success. I did just install the latest platform tools.
Any suggestions?
Click to expand...
Click to collapse
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.

FijNNY said:
Did you activate developer settings with USB debugging
Click to expand...
Click to collapse
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
jinkerz9430 said:
i see you have decided to root it now LOL! well. first things first. go into developers options and activate debugging. mode. If there is OEM unlock option, also activate that (after all you are going to root, but be aware because it will erase all your data) Also install the proper drivers for your phone on the computer. All these are critical. after that you should be able to detect your device. But just in case, what update of ADB have you downloaded? I used one from the pixel's section on XDA which allowed me to see the prompt box and give permission to my computer to access and make changes to my device.
Click to expand...
Click to collapse
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
adb -d shell pm grant com.suyashsrijan.forcedoze android.permission.dump
Click to expand...
Click to collapse
All being on the same line.
Any idea if that's a bad idea?
[edit]
I just found that I can do a similar command for Greenify and have it do an aggressive doze. I think I'll try that. I may pop back into my Journey thread to update what's going on.

ewingr said:
I thought sure I had turned that on, but it was off. But that was before I had done a software update to 10f. Maybe it changed back. Thanks.
Well, actually, I'm not quite ready to root. But I'll be appreciating your input when it comes time. (I forget...are you on a US996?).
Here's what I am trying to do: I am messing with apps to try to improve battery life while still not rooted. I installed Greenify again, hoping I don't have the same problem you and I discussed over in my Journey thread.
So, I just also installed Forcedoze, which typically 'requires' root. But on first run, it says that if not rooted you can give it the rights to do what it needs to do with the following command:
All being on the same line.
Any idea if that's a bad idea?
Click to expand...
Click to collapse
Hmm it wouldnt hurt to try. I mean, without root priviliges there are not changes that can affect the system of the phone internally speaking. So... What adb did you download? I used the one from the pixel because my system wouldnt show me the prompt box asking me whether i want to allow my laptop to make changes to my phone.

I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.

ewingr said:
I'm getting device unauthorized from ADB. I'm Googling now to find the problem. I am NOT getting stack overflow with it.
[fixed]
Rebooted PC and PHone. When I plugged in a pop-up came up on the phone to authorize debugging mode. That had not happened before. That got it to working.
Click to expand...
Click to collapse
see? hahaha that's what you needed to find. the prompt asking you to authorize. in my case it didnt show it until i used the adb from pixel's forum since it appear that the adb shown on the rooting method's thread is missing a file which wouldnt allow to work properly so, then after i opened the adb , it did ask me for the authorization box

How protect phone data when bootloader unlocked?

Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
From me the problem is to protect MY data if I loss the phone...
If my phone is password protected (and bootloader locked), a person that found the device can't use it directly.
It can unlock the bootloader (more or less easily) but the phone data is removed by the unlock process.
My data is sure!
But if the bootloader is unlocked the person that has found my phone can acess to the custom recovery (or load a custom recovery if I'm on stock recovery) then force a wipe of the device.
Due to that, all my security (fingerprint and lock code) was erased and the user can access to my phone and also to all the data stored in /sdcard.
My data isn't sure!
It exists any mode to use a custom ROM but maintaining my data sure?
(I'm not confidence with the Google remote device access)
Thanks in advance!

I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!

I'll be honest and I mean no offense but your data is worthless. If someone steals your device the first things done are Sim removed and devices reset or powered off. Data thieves don't get the data from stolen devices. They get it from the places we give it freely. Like shopping stores and on line accounts.

Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.

jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks

bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/

bartito said:
Hello,
I doesn't know if this is a real problem in newer Android versions.
I apologize if this problem is already solved; i'm out of Android development since a while...
...........................................
Click to expand...
Click to collapse
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.

Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Now, for that matter, having a locked bootloader either doesn't ensure that your data is safe. For example, for HTC phones, you don't even need to unlock the bootloader for flashing a custom recovery or kernel. You can turn the phone to S-Off state using some proprietary tools (without losing data) and then flash custom images over a locked bootloader.
In case of Samsung, only FRP lock prevents you from flashing custom images (that too on newer phones) but in that case also, you can turn FRP off using some paid services and then flash any custom images and run the above mentioned commands.
In case of LG, it is even easier. Professional tools exist for communication over download mode protocol and turning off the screen lock doesn't even require a custom image in LG's case. However, most newer models are not supported by those tools yet.
In case of Apple, professional tools existed that used to read screen lock over a time span of 1-4 hours in an older version of iOS. I've heard that a tool is being made available for the current versions also in the coming weeks.
So, if you are conscious about your data, it is safe as far as the you have the phone in your possession. Once you lose it, you can't be sure about what is happening with it.
But then, as said in above posts, why would the thief want to crack open the data of a common man. If you are not a common man, you should worry. Otherwise I personally really don't care.
Click to expand...
Click to collapse

jhs39 said:
Nobody can access your phone data the way you describe unless you also run your phone decrypted --which is not the default for Android or even for custom ROMs for that matter. When you boot into recovery on a phone that is encrypted TWRP asks for your pin number and without it your data is not accessible. But that doesn't mean a thief couldn't still wipe and use your phone. You need to report it stolen so the IMEI number is blacklisted.
Click to expand...
Click to collapse
Black listing the imei doesn't work everywhere. Plus while banned on xda so I can't say how. But the imei is not that hard to change.

bartito said:
Hello,
Absolutelly appreciate your anwer.
I'm a common man, but I'm a bit worried due to 2 points:
1) I'm using LastPass and I doesn't would to my passwords to fall into someone's hands if I loss the device,
2) I'm using the app from my bank to pay using NFC and I doesn't would that anyone can use it
EDIT: 3) Of course, I'm using my Google account to store my contacts data. It would be a mess if someone erase my contacts
Thanks!
Click to expand...
Click to collapse
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.

Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
sikander3786 said:
Maybe some experts can give their opinion on how to protect your data using some third party apps or by using some other options that I am not aware of. But in my opinion, a phone with an unlocked bootloader is always more vulnerable than a phone with locked bootloader.
Click to expand...
Click to collapse

bartito said:
Of course, I agree with your affirmation at 100%
The question is: I can improve security if I keep TWRP as a recovery instead of return to the stock recovery and I lock the bootloader?
Thanks
Click to expand...
Click to collapse
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.

sikander3786 said:
I don't think you will be able to boot TWRP after relocking the bootloader. You need to test it yourself. Chances are very few because locked bootloaders prevent from booting un-signed images.
If you do manage to boot TWRP after relocking, make sure your data is encrypted. If it is not, then it doesn't matter if the bootloader is locked or not.
Also, you will need to turn off "oem unlock" option from developer options.
Click to expand...
Click to collapse
I think in the end I will stay as I am: bootloader unlocked and TWRP instead of the original recovery.
After all... I've never lost a phone...

bartito said:
The /sdcard in phones that doesn't have external sdcard, like O+5, are also protected by the encriptation?
Thanks
Click to expand...
Click to collapse
I haven't checked, but I believe it should.
nxss4 said:
Yep, like any other android, the oneplus 5 has full disk encryption enabled by default:
http://www.androidpolice.com/2015/1...ll-disk-encryption-by-default-on-new-devices/
Click to expand...
Click to collapse
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
sikander3786 said:
Well, IMO your concern is right to some extent.
With an unlocked bootloader, if there is some version of TWRP (or any other customer recovery for that matter) that can decrypt your data partition automatically or if you have ever formatted your /data partition from TWRP , or even an insecure kernel (most insecure kernels allow USB debugging without asking for authorization keys), all the thief needs is 2 adb commands and your screen lock will be turned off and all your stuff will be exposed 'as is'.
Click to expand...
Click to collapse
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
sikander3786 said:
For educational purposes, the commands are:
Code:
adb shell rm /data/system/*.key
adb reboot
Click to expand...
Click to collapse
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.

Hello,
Thanks for your anwer. I appreciate the time that have you spend on my question
I need to go to the FDE thread to learn a bit more about the process and results.
Now, I have 2 more questions...
1) If the phone is encrypted with FBE a user can remove user passwords using "adb shell rm /data/system/*.key
&& adb reboot" commands, like @sikander3786 has explained but, due to the device is encripted, it can't access to my data
and the device will require for the decrypt password when booting in normal mode or recovery. I'm correct?
2) If the device is encrypted with FBE a user can access to /sdcard even without the decrypt password in recovery (TWRP) mode but not if encrypted with FDE?
Thanks again!
Fif_ said:
I haven't checked, but I believe it should.
Uh no, OP5 with OOS 4.5.x Nougat uses File-Based Encryption (FBE), not FDE.
I know because I wrote the utility to get back to FDE, which works if you change the/fstab* file:
https://forum.xda-developers.com/showthread.php?t=3672477
Do you have a source for the first part of that information? The part where if userdata is formatted with TWRP, it is vulnerable?
I don't see how that can happen unless you run decrypted. TWRP is never involved in the encryption process. When you format userdata, it just runs mkfs. Android upon booting sees the forceencrypt flag in the fstab and then promptly encrypt the device with a default passphrase. When you later set up security, the passphrase is changed to whatever you input.
How can TWRP decrypt the files at this point without your passphrase?
Note that if you are running FBE, and run adb shell on a device that's booted into TWRP while waiting for the password, you will be able to see the file structure under /data, but most of its contents will be garbage (=encrypted).
If you're running FDE, and run adb shell on a device that's booted into TWRP, /data will be completely inaccessible.
This will remove the PIN/password phrase to get into Android, but won't give access to any encrypted files.
That may mess your phone royally as well.
Click to expand...
Click to collapse

nxss4 said:
I think you'll be fine, as the data on your internal memory should be encypted, which is enabled by default!
Click to expand...
Click to collapse
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?

anuragm13 said:
Suppose i encrypt my device, i.e., it asks for password everytime before booting...
Q1. Will booting into fastboot or recovery require the password?
Q2. If no, how can i prevent access to fastboot and recovery on an unlocked bootloader?
Click to expand...
Click to collapse
You can't, but your data isn't accessible without the password

bartito said:
You can't, but your data isn't accessible without the password
Click to expand...
Click to collapse
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?

anuragm13 said:
But one can flash custom recovery from fastboot and subsequently use it to flash custom roms.
Am i right?
Click to expand...
Click to collapse
Yes, you can flash any recovery and any rom, but phone data can't be accessible if you don't have the password.
To use the device you need to know the password or do a data format

Isn't your phone technically always safe as long as you keep it encrypt it?
Only thing a thief could do would be a reset in both cases, isn't it?

Sony Xperia XA2 - Unlocking

I'd like to start a discussion on unlocking the XA2 bootloader and rooting it. So far, it looks like for Sony devices, you need to send a request through the Sony site here: https://developer.sonymobile.com/unlockbootloader/
But there is no device selection for the XA2. This is where i'm currently stuck at. Does anyone know of any other way to unlock the bootloader?

Okay got it to unlock bootloader.
Steps:
1. Head to https://developer.sonymobile.com/unlockbootloader/. Select Xperia XA1 in the dropdown, follow steps, then get your access code.
2. Pretty much follow the steps in that guide from sony, where you get the access code. The only difference was when installing the fastboot drivers. On win 10, i had to go and follow the steps here to install android drivers: https://android.stackexchange.com/questions/129174/windows-10-fastboot-driver
After that, fastboot was able to recognize the device and unlock the bootloader.
So now, i guess i'm waiting for TWRP to be released for XA2 to get recovery and root.

I've been looking for a XA2 page for a while. Can we request one?
This is a interesting device and I hope the development community shows some interest too.
What's your impressions of it so far?

Agreed, I'm quite shocked there is no development threads as of yet for this newly released device. Already checked mine, and can see that sky mobile have left it unlockable, so I would also be interested in development for this device.

Spitfire400 said:
Agreed, I'm quite shocked there is no development threads as of yet for this newly released device. Already checked mine, and can see that sky mobile have left it unlockable, so I would also be interested in development for this device.
Click to expand...
Click to collapse
Same. I bought it off Amazon US and I didn't realize I was buying such a recent phone. To any future devs, add "Night Light" feature and swipe fingerprint to bring down notification bar to any ROMS would make this phone a great sucessor to my Honor 8.

XA2 has been perfect for me so far, coming from Nexus 5x. I mostly use my phone for reddit and podcasts, though. Just need my LineageOS on it.

i unlocked mine also

li0nh3art3d said:
i unlocked mine also
Click to expand...
Click to collapse
Hello, what about fingerprint scanner usability after unlocking? I've heard that after rooting your phone scanner may stop to work with banking and other similar apps. Maybe you noticed other changes after rooting?

Merlin K said:
Hello, what about fingerprint scanner usability after unlocking? I've heard that after rooting your phone scanner may stop to work with banking and other similar apps. Maybe you noticed other changes after rooting?
Click to expand...
Click to collapse
I haven't been able to root yet. I've only unlocked the bootloader, which hasn't caused any problems with bank of America. on my other phone rooting didn't affect bank of America, however Android pay didn't work, and snapchat can only be logged in before root and not after. once you root, you won't be able to log back in snapchat if you logout, however if you log in it'll stay logged in after root.
I've been having problems with the windows 10 fastboot and ADB drivers. i got fastboot to work long enough to unlock the bootloader but then it stopped recognizing my phone. still haven't gotten ADB to work yet ?*

li0nh3art3d said:
I haven't been able to root yet. I've only unlocked the bootloader, which hasn't caused any problems with bank of America. on my other phone rooting didn't affect bank of America, however Android pay didn't work, and snapchat can only be logged in before root and not after. once you root, you won't be able to log back in snapchat if you logout, however if you log in it'll stay logged in after root.
I've been having problems with the windows 10 fastboot and ADB drivers. i got fastboot to work long enough to unlock the bootloader but then it stopped recognizing my phone. still haven't gotten ADB to work yet ?*
Click to expand...
Click to collapse
Thx for info. Let us please know when when/if root your phone.

Merlin K said:
Thx for info. Let us please know when when/if root your phone.
Click to expand...
Click to collapse
I'm waiting for TWRP to keep playing with the drivers on windows 10. for some reason they've been giving me a major headache

The wait game begins. I'm going to wait to unlock the bootloader until TWRP and root available.
Btw can't you root without changing the recovery using ADB. I don't kno since this my first ever Sony phone.

YaKillaCJ said:
The wait game begins. I'm going to wait to unlock the bootloader until TWRP and root available.
Btw can't you root without changing the recovery using ADB. I don't kno since this my first ever Sony phone.
Click to expand...
Click to collapse
I think you can sideload with ADB once the bootloader is unlocked. I was under the impression TWRP is like a GUI for ADB. but There's something funky with the windows 10 drivers. it took forever for my phone to get detected in fastboot, and ADB never seemed to work. then, after i unlocked my phone, the PC doesn't even recognize it in fastboot anymore.
likewise, I've always used Samsung phones & odin. This is my first Sony. the lack of root is killing me ?

From what i read, adb sideload requires custom recovery.
Is anyone else on Project FI with this phone? I'm getting awful 4G and wifi performance with the XA2. Constantly losing internet access (even though signal bar is at 5 bars).

Hi guys, I managed to unlock the bootloader but I can not get into recovery mode. I tried with vol- and power button but it does not work . Did it happen to someone? Thank you all

makotech222 said:
From what i read, adb sideload requires custom recovery.
Click to expand...
Click to collapse
where did you read this? i was under the impression thst TWRP is basically a graphic user interface of ADB, which is command line interface.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
matitino said:
Hi guys, I managed to unlock the bootloader but I can not get into recovery mode. I tried with vol- and power button but it does not work . Did it happen to someone? Thank you all
Click to expand...
Click to collapse
for this, you will need a custom recovery GUI such as TWRP. I believe tht all you can do on this device by pressing volume- is access ADB, and volume+ gets you into fastboot, which can be accessed via command prompt on a PC

li0nh3art3d said:
where did you read this? i was under the impression thst TWRP is basically a graphic user interface of ADB, which is command line interface.
---------- Post added at 09:14 PM ---------- Previous post was at 09:12 PM ----------
for this, you will need a custom recovery GUI such as TWRP. I believe tht all you can do on this device by pressing volume- is access ADB, and volume+ gets you into fastboot, which can be accessed via command prompt on a PC
Click to expand...
Click to collapse
ADB sideload explicitly, not just ADB: https://twrp.me/faq/ADBSideload.html

makotech222 said:
ADB sideload explicitly, not just ADB: https://twrp.me/faq/ADBSideload.html
Click to expand...
Click to collapse
Isn't TWRP basically just the GUI of all the ADB commands? I was under the impression you could do almost everything you can do in TWRP in ADB CLI mode on a PC ?*
I was under the impression to sideload you can boot with a USB plugged into your computer and your phone press volume- Then the indicator light in the top right corner turns green, and (if the drivers on my PC would cooperate) then it would accept ADB sideload commands. Now, I am unsure of this; that's just what my basic understanding is. If I could get the damn drivers to work right, I could find out for sure ?

li0nh3art3d said:
Isn't TWRP basically just the GUI of all the ADB commands? I was under the impression you could do almost everything you can do in TWRP in ADB CLI mode on a PC ?*
I was under the impression to sideload you can boot with a USB plugged into your computer and your phone press volume- Then the indicator light in the top right corner turns green, and (if the drivers on my PC would cooperate) then it would accept ADB sideload commands. Now, I am unsure of this; that's just what my basic understanding is. If I could get the damn drivers to work right, I could find out for sure
Click to expand...
Click to collapse
I don't know nearly enough about the android ecosystem to comment, beyond what i found. I think adb sideload is a specific command, which requires twrp. But other adb may work? I don't want to risk it yet anyways.
Regarding drivers, did you try the thing i linked in my first post on this thread? My XA2 is still recognized after bootloader unlock with my method.

What do you know flashtool supports our xa2? that I know no because I tried to convert an ftf file but in the device list the xa2 is not there. also does not recognize me in flashmode despite emma recognize it. thank you

Can a custom rom remove a pin coded lock screen S8 SM-G950F?

Hi all
Android Recovery
samsung/dreamltexx/dreamlte
8.0.0/R16NW/G950FXXU4CRL2
Flashed firmware today from G950FXXU4CRJ5 to G950FXXU4CRL2
Also an Exynos not Snapdragon
I have another post on the go https://forum.xda-developers.com/showthread.php?t=3967187
I am trying to get in to my mum's phone which she has been locked out of by her nasty ex husband. It has a 6 digit pin code for the lock screen.
I have tried flashing same and new firmware as I thought maybe that will reset some settings but it didn't.
She has photos on there that she doesn't want to lose... and I cannot guarantee that they can be saved if we do a factory reset.
Is there a chance that if a custom rom was flashed it would make the phone accessable so I can get any files I want from it?
The phone is Australian so I am guessing I cannot just flash any old files, like with flashing firmware.
Any help would be greatly appreciated.
Cheers
Lee

Custom roms have different user partition therefore not compatible with stock rom. But if you have twrp installed you can remove the files wich store the lock info , simply reboot to twrp go to filemanager browse to /data/system and remove all files with .key extension and files named locksettings

randompunk said:
Hi all
Android Recovery
samsung/dreamltexx/dreamlte
8.0.0/R16NW/G950FXXU4CRL2
Flashed firmware today from G950FXXU4CRJ5 to G950FXXU4CRL2
Also an Exynos not Snapdragon
I have another post on the go https://forum.xda-developers.com/showthread.php?t=3967187
I am trying to get in to my mum's phone which she has been locked out of by her nasty ex husband. It has a 6 digit pin code for the lock screen.
I have tried flashing same and new firmware as I thought maybe that will reset some settings but it didn't.
She has photos on there that she doesn't want to lose... and I cannot guarantee that they can be saved if we do a factory reset.
Is there a chance that if a custom rom was flashed it would make the phone accessable so I can get any files I want from it?
The phone is Australian so I am guessing I cannot just flash any old files, like with flashing firmware.
Any help would be greatly appreciated.
Cheers
Lee
Click to expand...
Click to collapse
do not flash a ROM. The storage has a very strong possibility of overwriting the pictures. Best thing you can do is boot it into DL mode, throw TWRP on it, allow superuser access within TWRP and ADB into it. Also, just because it is an Australian market phone doesnt mean it needs some special firmware. You can flash pretty much any 950F firmware on it

kpwnApps said:
Custom roms have different user partition therefore not compatible with stock rom. But if you have twrp installed you can remove the files wich store the lock info , simply reboot to twrp go to filemanager browse to /data/system and remove all files with .key extension and files named locksettings
Click to expand...
Click to collapse
Unfortunately my mum is not tech savvy so TWRP is not installed, developer options not active and oem unlock not unlocked.
Yes that is all I want to do is access files to delete lock screen files.
Thanks for your advice

youdoofus said:
do not flash a ROM. The storage has a very strong possibility of overwriting the pictures. Best thing you can do is boot it into DL mode, throw TWRP on it, allow superuser access within TWRP and ADB into it. Also, just because it is an Australian market phone doesnt mean it needs some special firmware. You can flash pretty much any 950F firmware on it
Click to expand...
Click to collapse
Can you install TWRP through DL mode? I think I tried and it came back with FRP lock. I will try again though... can you recommend a version or TWRP that will work through DL mode please? If not I'll have a search for one.
I tried to flash UK firmware and it didn't work, but thats not an issue.
Once I have TWRP I'll be sorted, its just getting it on there to enable me to ADB in to it. Will I be able to ADB in to it if OEM is not unlocked etc...
Thanks for your reply

If you have frp lock on. Im sorry to say that you must wipe the data

randompunk said:
Can you install TWRP through DL mode? I think I tried and it came back with FRP lock. I will try again though... can you recommend a version or TWRP that will work through DL mode please? If not I'll have a search for one.
I tried to flash UK firmware and it didn't work, but thats not an issue.
Once I have TWRP I'll be sorted, its just getting it on there to enable me to ADB in to it. Will I be able to ADB in to it if OEM is not unlocked etc...
Thanks for your reply
Click to expand...
Click to collapse
FRP lock is gonna be tough to get around and the only real way to install TWRP is via DL mode
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
randompunk said:
Unfortunately my mum is not tech savvy so TWRP is not installed, developer options not active and oem unlock not unlocked.
Yes that is all I want to do is access files to delete lock screen files.
Thanks for your advice
Click to expand...
Click to collapse
im sorry to say this, but youre probably effed with FRP lock enabled and no develpoer options enabled, so without paying for an unlock service outside of XDA, which very well might cause this post to get removed. Ill tag someone who might be able to help, but if he can help, it will cost you some money. @Nodial you and your colleagues have any methods to help this fella out?

Thanks for the replies guys, yes I had a feeling when I came across the FRP error I would of hit the end of the road...
Might have to either bite the bullet and pay up or factory reset and see what I can recover.
Thanks again guys