Help needed to bypass Lock Screen - Android Q&A, Help & Troubleshooting

Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this

If powered on, and plugged in to PC, is it 'seen' at all?

robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it

If it is seen, there is a chance you can get data off it.

You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli

Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error

XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe

Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli

Related

[Q] Impossible Rooting Polaroid PSPR355

Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.

[Q] How to recover data from a locked, not-rooted, AT&T HTC One M7?

Hello all,
I have a friend's above mentioned phone. He has not modified the phone in any way. He said that a couple days ago, it just stopped functioning properly (no drop, water damage, etc.) When powered on, it just hangs at the HTC screen. I can get to the bootloader. My goal is to recover photos from the device (he has all of his baby's pics on it, no backups).
I have adb and fastboot installed on my computer and they work with my own devices. My computer can see the One via fastboot ("./fastboot devices" outputs the phone ID), but my computer can't see this HTC One via "./adb devices". I suspect that this phone isn't in USB debug mode.
I've read that unlocking the bootloader will erase all his data... where should I start in my adventure to rescue his baby pictures and insure that he will name his next child after me?
ayhindot said:
Hello all,
I have a friend's above mentioned phone. He has not modified the phone in any way. He said that a couple days ago, it just stopped functioning properly (no drop, water damage, etc.) When powered on, it just hangs at the HTC screen. I can get to the bootloader. My goal is to recover photos from the device (he has all of his baby's pics on it, no backups).
I have adb and fastboot installed on my computer and they work with my own devices. My computer can see the One via fastboot ("./fastboot devices" outputs the phone ID), but my computer can't see this HTC One via "./adb devices". I suspect that this phone isn't in USB debug mode.
I've read that unlocking the bootloader will erase all his data... where should I start in my adventure to rescue his baby pictures and insure that he will name his next child after me?
Click to expand...
Click to collapse
HTC offered a free 25gb Dropbox account with the One M7... If your friend did not take advantage of this offer and set the phone to auto update photos and videos their is probably nothing you can do now to save them.
adb only works in custom recovery and when the phone is booting up with usb debugging enabled... so any adb commands will fail. fastboot will work in the bootloader but is very limited in the functions it can do .. flash rom/ruu/firmware , unlock/lock bootloader , erase cache , reboot ..etc nothing really useful to you. A factory reset from recovery will also destroy all the photos on the device. This is one of the main reasons I unlock and flash a custom recovery on my phone the first few days i get it. you just have so many more options when the custom recovery is installed.
Hello, back again with a similar issue on a different phone.
I was unable to recover data from my friend's phone, but I was able to get it running again! I get it back to him and he informs me that the gremlins from his device must have somehow gotten into his wife's phone...
She has the same device, an AT&T One X (M7). Her device presents in the same as his (bootloops to the white HTC screen), but she has no data she wishes to recover. She'd just like it to work again.
I run through the same steps as I did with his first device, but things don't play out as I expected. I get it unlocked and get TWRP 2.7.1.2 installed without incident. However, the phone still bootloops into the white HTC screen.
What is my next move?
Thanks!
Did you clear the cache?

Alcatel One-Touch Root Help

Hey guys,
So my LG G3 finally took a dump on me and I decided I'm done spending 600+ dollars USD on cell phones , so I picked up this Alcatel One-Touch Allura for around 120$.
There doesn't seem to really be any information about the device online, or even any reviews. I've been trying to root it on my own but am having no luck.
None of the "one-click-roots" work that I tried (surprise surprise). ADB doesn't run as root. For some reason ADB only works while the phone is on, and not in recovery, for the most part... I've installed the USB drivers that you can find on the phone under the CD USB option, I've tried universal Android USB drivers, I've tried updating my Intel USB drivers, but still nothing. ADB will not work while in recovery. The phone goes --start adb-- and then nothing, it just sits there. I AM able to use ADB when I hit "apply update from ADB" so I can kind of get ADB to work in recovery, just not where it says --start adb--, that still doesn't work even after I come out of the adb update menu. I tried to load a few things through sideloading but they all fail because of failing signature verifications.
Anyway, I can get it into recovery but I can't get into the bootloader, and the "allow oem unlock" option doesn't seem to really do much from what I can tell, since I can't even get into fastboot. This seems like a pretty solid device and I like the specs/aesthetics, but I would really love it rooted. I've never really done much with android before so please excuse any terms I may have used incorrectly.
Of course I will be more than happy to try any suggestions/answer any questions I can about the device. I would post a pic of the recovery screen but I need to boost my post count first..
Turns out kingo root works.
Meepbob said:
Hey guys,
So my LG G3 finally took a dump on me and I decided I'm done spending 600+ dollars USD on cell phones , so I picked up this Alcatel One-Touch Allura for around 120$.
There doesn't seem to really be any information about the device online, or even any reviews. I've been trying to root it on my own but am having no luck.
None of the "one-click-roots" work that I tried (surprise surprise). ADB doesn't run as root. For some reason ADB only works while the phone is on, and not in recovery, for the most part... I've installed the USB drivers that you can find on the phone under the CD USB option, I've tried universal Android USB drivers, I've tried updating my Intel USB drivers, but still nothing. ADB will not work while in recovery. The phone goes --start adb-- and then nothing, it just sits there. I AM able to use ADB when I hit "apply update from ADB" so I can kind of get ADB to work in recovery, just not where it says --start adb--, that still doesn't work even after I come out of the adb update menu. I tried to load a few things through sideloading but they all fail because of failing signature verifications.
Anyway, I can get it into recovery but I can't get into the bootloader, and the "allow oem unlock" option doesn't seem to really do much from what I can tell, since I can't even get into fastboot. This seems like a pretty solid device and I like the specs/aesthetics, but I would really love it rooted. I've never really done much with android before so please excuse any terms I may have used incorrectly.
Of course I will be more than happy to try any suggestions/answer any questions I can about the device. I would post a pic of the recovery screen but I need to boost my post count first..
Click to expand...
Click to collapse
Meepbob said:
Turns out kingo root works.
Click to expand...
Click to collapse
Have you been able to find a working recovery for this phone? I picked up one tonight for $89 after shattering the screen on my Nexus. I'd appreciate your input.
Yes Kingo Root works, and I used supersume to use supersu instead of kingos superuser. Now does anyone know if there is a custom recovery or custom rom for Marshmallow?

Help with my passcode locked Tracfone LG Rebel 4 - LML212VL - Download Mode

I have a passcode locked LG Rebel 4 - LML212VL and cant get into download mode.. Ideas?
I need to recover a clients data and the only way for me to do this is through LGLAF or with a box that can remove the pattern lock.. However all ive managed to get to is recovery and that is it.. No download mode.. Being a Tracfone i know fastboot is disabled but download mode should not be. Now seeing that it is passcode locked is there a chance a security feature is blocking me from getting to Download mode??
Any help is much appreciated.
@noidodroid
If device is accesable in ADB mode, why don't pull out the data in question?
Code:
adb devices
adb pull <remote data location> <local location>
jwoegerbauer said:
@noidodroid
If device is accesable in ADB mode, why don't pull out the data in question?
Code:
adb devices
adb pull <remote data location> <local location>
Click to expand...
Click to collapse
Yeah if I could enable ADB i would do this. However i'm stuck on passcode screen. Know any ways?
noidodroid said:
I have a passcode locked LG Rebel 4 - LML212VL and cant get into download mode.. Ideas?
I need to recover a clients data and the only way for me to do this is through LGLAF or with a box that can remove the pattern lock.. .
Click to expand...
Click to collapse
The LG tools like LGUP will change the mode when necessary.
They do it by sending an AT command... AT%DLOAD
What next then? The data is still encrypted...
:fingers-crossed:
@noidodroid or whoever might need this.
Here is how to use AT...
First check in Device Manager (devmgmt. msc) what COM port LG is using - under the Modems.
Then use Putty terminal or similar program to give the command(s).
Or "blindly" by using dos prompt. (You don't see the answers. )
First get the port to use and then echo the command.
Code:
[B]reg query HKLM\hardware\devicemap\SERIALCOMM[/B]
\Device\LGANDNET[B]MDM0[/B] REG_SZ [B]COM##[/B] <--use this
\Device\LGANDNETDIAG1 REG_SZ COM$$
[B]echo AT%DLOAD>\\.\COM##[/B]
AT commands taken from my LG's /system/bin/atd , laf probably have some more...
AT#CLS, AT$LGAPP, AT$NSRI, AT$PRL, AT%AATEND, AT%AATFULL, AT%AATINIT, AT%AATORDERSET, AT%AATSET, AT%AATSTART, AT%ACCEL, AT%ACS, AT%ALC, AT%ANTCONF, AT%ANTINFO, AT%BAROMETER, AT%BATL, AT%BATMP, AT%BATT, AT%BATTLEVEL, AT%BATTTEMP, AT%BATTTEMPINFO, AT%BCPE, AT%BCPL, AT%BLEDSTART, AT%BLEDSTOP, AT%BTAD, AT%BTLER, AT%BTLET, AT%BTTM, AT%BUILDDATE, AT%CALCK, AT%CALDT, AT%CAMP, AT%CAMPREQ, AT%CHANGEWTR, AT%CHARGE, AT%CHARGINGMODEOFF, AT%CHCOMP, AT%CHECKFOTAPACKAGE, AT%CHIPSET, AT%CLOCKSTATUSCPU, AT%CLOCKSTATUSGPU, AT%CLOCKSTATUSSETCPU, AT%CMDLOCK, AT%CMPCPUFULL, AT%CODECRC, AT%COMPASS, AT%COVERDETECT, AT%CPUFULL, AT%CPUFULLINFO, AT%CSN, AT%DATST, AT%DBCHK, AT%DBCOPY, AT%DBDUMP, AT%DCTEST, AT%DETACH, AT%DEVICEID, AT%DEVICETEST, AT%DLOAD, AT%DTLOGCAT, AT%EARJACK, AT%ECALL, AT%EFUSECHECK, AT%EFUSEENABLE, AT%EFUSERESULT, AT%EFUSEVERIFICATION, AT%EMMCSIZE, AT%EMMREJECT, AT%EMT, AT%ENCRYPT, AT%ENCRYPTMOUNTDATA, AT%ENCRYPTONBOOT, AT%ETM, AT%FBOOT, AT%FIDOCHECK, AT%FIDOERASE, AT%FIDOWRITE, AT%FILECRC, AT%FKPD, AT%FLIGHT, AT%FMR, AT%FPCKBOARD, AT%FPRICRC, AT%FPRUBSTAMP, AT%FPSPI, AT%FPZONE, AT%FRST, AT%FRSTSTATUS, AT%FSM, AT%FSMDRESULT, AT%FSMMIC, AT%FSMMODE, AT%FSMRESULT, AT%FSMSTART, AT%FSMSTATUS, AT%FSMVERSION, AT%FTM, AT%FTMMAGIC, AT%FUELRST, AT%FUELVAL, AT%FUSE, AT%FUSECHECK, AT%FUSG, AT%GERANCAPDISABLE, AT%GKPD, AT%GNSS, AT%GNSS1, AT%GPIO, AT%GREBOOTSTATUSCLR, AT%GSTATUS, AT%GSTATUSCLR, AT%GWIFI, AT%GWLANSSID, AT%GYRO, AT%HALLIC, AT%HDCP, AT%HDCPERASE, AT%HDCPID, AT%HDCPST, AT%HMEXT, AT%HWVER, AT%IDDE, AT%IMEI, AT%IMEI2, AT%IMEI3, AT%IMPL, AT%IMSTESTMODE, AT%INFO, AT%IRRC, AT%ISSIM, AT%KCAL, AT%KEYLOCK, AT%KPHVERSION, AT%KSANTITHEFTSTATUS, AT%KSCHECKLOCK, AT%KSDOUNLOCK, AT%KSGETEXTRA, AT%KSGETLAFLOCK, AT%KSOSTYPE, AT%KSSERIALNO, AT%KSTYPE, AT%KSUNLOCKSTATUS, AT%KSWITCH, AT%LCATT, AT%LCD, AT%LCDCAPTURE, AT%LCIMSSETCFG, AT%LED, AT%LEDON, AT%LGANDROID, AT%LGATSERVICE, AT%LGPWD, AT%LOGSAVE, AT%LOGSERVICE, AT%LTEAUTHFAIL, AT%LTECALL, AT%LTERFMODE, AT%LTL, AT%LTR, AT%LTRST, AT%MAC, AT%MAINCAMERAID, AT%MAXCPU, AT%MAXCT, AT%MDATE, AT%MDMLOG, AT%MDMPVS, AT%MEID, AT%MIMOANTCHECK, AT%MINIOS, AT%MLT, AT%MMCCONTENTSINTEGRITY, AT%MMCFACTORYFORMAT, AT%MMCFORMAT, AT%MMCISFORMATTED, AT%MMCTOTALSIZE, AT%MMCUSEDSIZE, AT%MOBICORE, AT%MOBICOREERASE, AT%MODELNAME, AT%MODEMCHK, AT%MODEMRESET, AT%MOT, AT%MPDECISION, AT%MPT, AT%MSN, AT%MTSLOG, AT%MTSLOGERS, AT%MTSLOGGET, AT%NCM, AT%NFC, AT%NTCODE, AT%NTCODECHANGE, AT%NTSWAP, AT%ONECMD, AT%OPNAMEREAD, AT%OPRESIZECHECK, AT%OSPPWDINIT, AT%OSVER, AT%PCBREV, AT%PMRST, AT%PNUM, AT%POWEROFF, AT%PRECPUFULL, AT%PROCCAT, AT%PROPTCAT, AT%PROXIMITY, AT%PROXIMITYCAL, AT%PSCAT, AT%PSELFDE, AT%PST, AT%PTNCLR, AT%QEM, AT%QFUSEVERI, AT%RADIATIONRESULT, AT%RAMSIZE, AT%RCT, AT%REATTACH, AT%RESTART, AT%RFDEVCHK, AT%RPMBMANUALPROVISIONING, AT%RPMBSTATUSCHECK, AT%RTC, AT%SAATRESULT, AT%SATPC, AT%SATPC2, AT%SCHK, AT%SDCHECK, AT%SELFDRESULT, AT%SEQCPUFULL, AT%SERIALNO, AT%SETREV, AT%SIMID, AT%SIMIMSI, AT%SIMOFF, AT%SIMPWDINIT, AT%SIMTRAY, AT%SLEN, AT%SLTYPE, AT%SPTCHK, AT%SPTLOCK, AT%SPTUNLOCK, AT%STARTDAYCHECK, AT%STARTFOTAPACKAGE, AT%SUBCAMERAID, AT%SUFFIX, AT%SULC, AT%SURV, AT%SWCV, AT%SWFV, AT%SWOV, AT%SWV, AT%SYSCAT, AT%TESTPATTERN, AT%TETHER, AT%THEME, AT%THERMALENGINE, AT%TOTALCRC, AT%TOUCHFWVER, AT%TOUCHLOG, AT%TSENS, AT%ULCV, AT%ULCW, AT%USB, AT%USBIDADC, AT%USBMODE, AT%USERDATASIZE, AT%VCOIN, AT%VLC, AT%VSLT, AT%VSLT2, AT%VSLT3, AT%VSLT4, AT%VZWAPNE, AT%VZWHM, AT%VZWIOTHM, AT%WALLPAPER, AT%WEBFLAG, AT%WLAN, AT%WLANCH, AT%WLANPING, AT%WLANR, AT%WLANT, AT%WORKFRSTMODEON, AT%XOTEMP, AT+CCLK, AT+CFUN, AT+CGMI, AT+CGMM, AT+CGMR, AT+CNUM, AT+CSDF, AT+CSO, AT+ESLP, AT+ESUO, AT+FUMO, AT+GCI, AT+GMI, AT+GMM, AT+LED, AT+MTC, AT+OMADM, AT+PRL, [email protected], [email protected], [email protected]
CXZa said:
@noidodroid or whoever might need this.
Here is how to use AT...
First check in Device Manager (devmgmt. msc) what COM port LG is using - under the Modems.
Then use Putty terminal or similar program to give the command(s).
Or "blindly" by using dos prompt. (You don't see the answers. )
First get the port to use and then echo the command.
Code:
[B]reg query HKLM\hardware\devicemap\SERIALCOMM[/B]
\Device\LGANDNET[B]MDM0[/B] REG_SZ [B]COM##[/B] <--use this
\Device\LGANDNETDIAG1 REG_SZ COM$$
[B]echo AT%DLOAD>\\.\COM##[/B]
AT commands taken from my LG's /system/bin/atd , laf probably have some more...
AT#CLS, AT$LGAPP, AT$NSRI, AT$PRL, AT%AATEND, AT%AATFULL, AT%AATINIT, AT%AATORDERSET, AT%AATSET, AT%AATSTART, AT%ACCEL, AT%ACS, AT%ALC, AT%ANTCONF, AT%ANTINFO, AT%BAROMETER, AT%BATL, AT%BATMP, AT%BATT, AT%BATTLEVEL, AT%BATTTEMP, AT%BATTTEMPINFO, AT%BCPE, AT%BCPL, AT%BLEDSTART, AT%BLEDSTOP, AT%BTAD, AT%BTLER, AT%BTLET, AT%BTTM, AT%BUILDDATE, AT%CALCK, AT%CALDT, AT%CAMP, AT%CAMPREQ, AT%CHANGEWTR, AT%CHARGE, AT%CHARGINGMODEOFF, AT%CHCOMP, AT%CHECKFOTAPACKAGE, AT%CHIPSET, AT%CLOCKSTATUSCPU, AT%CLOCKSTATUSGPU, AT%CLOCKSTATUSSETCPU, AT%CMDLOCK, AT%CMPCPUFULL, AT%CODECRC, AT%COMPASS, AT%COVERDETECT, AT%CPUFULL, AT%CPUFULLINFO, AT%CSN, AT%DATST, AT%DBCHK, AT%DBCOPY, AT%DBDUMP, AT%DCTEST, AT%DETACH, AT%DEVICEID, AT%DEVICETEST, AT%DLOAD, AT%DTLOGCAT, AT%EARJACK, AT%ECALL, AT%EFUSECHECK, AT%EFUSEENABLE, AT%EFUSERESULT, AT%EFUSEVERIFICATION, AT%EMMCSIZE, AT%EMMREJECT, AT%EMT, AT%ENCRYPT, AT%ENCRYPTMOUNTDATA, AT%ENCRYPTONBOOT, AT%ETM, AT%FBOOT, AT%FIDOCHECK, AT%FIDOERASE, AT%FIDOWRITE, AT%FILECRC, AT%FKPD, AT%FLIGHT, AT%FMR, AT%FPCKBOARD, AT%FPRICRC, AT%FPRUBSTAMP, AT%FPSPI, AT%FPZONE, AT%FRST, AT%FRSTSTATUS, AT%FSM, AT%FSMDRESULT, AT%FSMMIC, AT%FSMMODE, AT%FSMRESULT, AT%FSMSTART, AT%FSMSTATUS, AT%FSMVERSION, AT%FTM, AT%FTMMAGIC, AT%FUELRST, AT%FUELVAL, AT%FUSE, AT%FUSECHECK, AT%FUSG, AT%GERANCAPDISABLE, AT%GKPD, AT%GNSS, AT%GNSS1, AT%GPIO, AT%GREBOOTSTATUSCLR, AT%GSTATUS, AT%GSTATUSCLR, AT%GWIFI, AT%GWLANSSID, AT%GYRO, AT%HALLIC, AT%HDCP, AT%HDCPERASE, AT%HDCPID, AT%HDCPST, AT%HMEXT, AT%HWVER, AT%IDDE, AT%IMEI, AT%IMEI2, AT%IMEI3, AT%IMPL, AT%IMSTESTMODE, AT%INFO, AT%IRRC, AT%ISSIM, AT%KCAL, AT%KEYLOCK, AT%KPHVERSION, AT%KSANTITHEFTSTATUS, AT%KSCHECKLOCK, AT%KSDOUNLOCK, AT%KSGETEXTRA, AT%KSGETLAFLOCK, AT%KSOSTYPE, AT%KSSERIALNO, AT%KSTYPE, AT%KSUNLOCKSTATUS, AT%KSWITCH, AT%LCATT, AT%LCD, AT%LCDCAPTURE, AT%LCIMSSETCFG, AT%LED, AT%LEDON, AT%LGANDROID, AT%LGATSERVICE, AT%LGPWD, AT%LOGSAVE, AT%LOGSERVICE, AT%LTEAUTHFAIL, AT%LTECALL, AT%LTERFMODE, AT%LTL, AT%LTR, AT%LTRST, AT%MAC, AT%MAINCAMERAID, AT%MAXCPU, AT%MAXCT, AT%MDATE, AT%MDMLOG, AT%MDMPVS, AT%MEID, AT%MIMOANTCHECK, AT%MINIOS, AT%MLT, AT%MMCCONTENTSINTEGRITY, AT%MMCFACTORYFORMAT, AT%MMCFORMAT, AT%MMCISFORMATTED, AT%MMCTOTALSIZE, AT%MMCUSEDSIZE, AT%MOBICORE, AT%MOBICOREERASE, AT%MODELNAME, AT%MODEMCHK, AT%MODEMRESET, AT%MOT, AT%MPDECISION, AT%MPT, AT%MSN, AT%MTSLOG, AT%MTSLOGERS, AT%MTSLOGGET, AT%NCM, AT%NFC, AT%NTCODE, AT%NTCODECHANGE, AT%NTSWAP, AT%ONECMD, AT%OPNAMEREAD, AT%OPRESIZECHECK, AT%OSPPWDINIT, AT%OSVER, AT%PCBREV, AT%PMRST, AT%PNUM, AT%POWEROFF, AT%PRECPUFULL, AT%PROCCAT, AT%PROPTCAT, AT%PROXIMITY, AT%PROXIMITYCAL, AT%PSCAT, AT%PSELFDE, AT%PST, AT%PTNCLR, AT%QEM, AT%QFUSEVERI, AT%RADIATIONRESULT, AT%RAMSIZE, AT%RCT, AT%REATTACH, AT%RESTART, AT%RFDEVCHK, AT%RPMBMANUALPROVISIONING, AT%RPMBSTATUSCHECK, AT%RTC, AT%SAATRESULT, AT%SATPC, AT%SATPC2, AT%SCHK, AT%SDCHECK, AT%SELFDRESULT, AT%SEQCPUFULL, AT%SERIALNO, AT%SETREV, AT%SIMID, AT%SIMIMSI, AT%SIMOFF, AT%SIMPWDINIT, AT%SIMTRAY, AT%SLEN, AT%SLTYPE, AT%SPTCHK, AT%SPTLOCK, AT%SPTUNLOCK, AT%STARTDAYCHECK, AT%STARTFOTAPACKAGE, AT%SUBCAMERAID, AT%SUFFIX, AT%SULC, AT%SURV, AT%SWCV, AT%SWFV, AT%SWOV, AT%SWV, AT%SYSCAT, AT%TESTPATTERN, AT%TETHER, AT%THEME, AT%THERMALENGINE, AT%TOTALCRC, AT%TOUCHFWVER, AT%TOUCHLOG, AT%TSENS, AT%ULCV, AT%ULCW, AT%USB, AT%USBIDADC, AT%USBMODE, AT%USERDATASIZE, AT%VCOIN, AT%VLC, AT%VSLT, AT%VSLT2, AT%VSLT3, AT%VSLT4, AT%VZWAPNE, AT%VZWHM, AT%VZWIOTHM, AT%WALLPAPER, AT%WEBFLAG, AT%WLAN, AT%WLANCH, AT%WLANPING, AT%WLANR, AT%WLANT, AT%WORKFRSTMODEON, AT%XOTEMP, AT+CCLK, AT+CFUN, AT+CGMI, AT+CGMM, AT+CGMR, AT+CNUM, AT+CSDF, AT+CSO, AT+ESLP, AT+ESUO, AT+FUMO, AT+GCI, AT+GMI, AT+GMM, AT+LED, AT+MTC, AT+OMADM, AT+PRL, [email protected], [email protected], [email protected]
Click to expand...
Click to collapse
Right on man! These are definitely helpful. I was using some AT tools and a script to run all commands in a database i have to see which were compatible with certain LG phones but I never got to finish the project. Now my only problem with this phone. here is i get no modem / com ports. I think it is possibly a security feature? I could see LG locking out people from download mode when phone is passcode locked unless they goto recovery and wipe it...
I need to find another way to do this or a way using FWUL, MAID etc (once modem recognized) unless someone knows how to get the modem to work.
Thanks for the wonderful information bro i will definitely save it and make use of it. Love toying around with AT commands, always have.
noidodroid said:
Now my only problem with this phone. here is i get no modem / com ports. I think it is possibly a security feature? I could see LG locking out people from download mode when phone is passcode locked unless they goto recovery and wipe it...
I need to find another way to do this or a way using FWUL, MAID etc (once modem recognized) unless someone knows how to get the modem to work.
Click to expand...
Click to collapse
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
CXZa said:
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
Click to expand...
Click to collapse
Yeah I have never had an issue getting those ports until this clients passcode locked tracfone. I think tracfone locks down everything.
I know there are some methods of getting LG's into certain modes on zero % battery but haven't tried this yet.
Unfortunately and i guess fortunately lol this phone went back to the client. They are having to go back through notes to find possible entries. Good luck to them.
Thanks for the help everyone!
CXZa said:
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
Click to expand...
Click to collapse
At what point is recovery showing the com ports? And are you just checking Device Manager or? And how to get into laf download mode to enter recovery from? LAF download is this the normal old download mode? If so i have never been able to switch over to recovery unless it is using some AT command that works (i have tried a handful and none work in download mode so far - LG Phoenix 4)
Also thank you 1000% again for the AT commands. I already found what i need and client is bringing phone back to me so i will give it a whirl and see what happens. Already locking up various LG phones here just to try it out.. IF you have any confirmed working AT commands and such lmk privately if you want and when done i can swap with you what all I have found to work the most. I was reading on security forums about how repairing imei, unlocking and other such actions are taken out using serial port for the most part and can be done in terminal (well it is one way) but not a lick of more information have i found on the topics yet. Just 3 white hat security forums. heh
Right when recovery starts for maybe minute or two. Doing something in recovery which prevents continuing to the normal boot doesn't help. Shows in device manager.
In MTK devices one can run multi_init in laf mode and as it fails it will go to the recovery. In Snapdragons is there such? IDK, but you might be able mount a sdcard formatted as ext4 and try to run it from there. I have run some programs that way - I believe, but cannot really remember much. What I did I tested if I could modify multi_init to boot into bootloader. It run but just normal boot happened. But maybe it could be modified to boot into edl?? Renaming it to something that can be run maybe needed...
Interesting to see what you've found out about AT commands, if you're willing to share.
PM if so, LG is watching me already...
(happened to found the LGUP v1.17 and shared here, it's package was removed next day - plus some others...)
Very cool. I never thought of doing any of that. I especially like the EDL idea. I might run some of that by eliwiggy a previous admin and wiz with Samsung devices to see what he says also.
I had a break through in FRP removal using AT commands recently. I found a way to get out from some locked LG devices using SVC stuff and AT commands. Nobody is doing this AFAIK... As for screen locks no success yet on newer devices. I will get in touch with you and we can chat.
Hmm so you can't get into download mode. Why don't you reset the phone first then connect to the internet when it asks and then find a way to open up a browser. If you can open up the browser you can download and install apk's and what not. That's how I FRP unlocked my Aristo 2.
I have done this already. No way into browser on the device i tried it on. Weird device too.. MS210.. I have been able to bypass this device no problem before until someone updated the firmware i think.. Mindboggling..
Anywho here is how i bypassed it and so far i think this method should work on all similar. I couldn't get security patch level as i had to give device back to the client. :-/
New Way to Bypass LG - Google Factory Reset Protetion on VARIOUS Devices!!
New Way to Bypass LG - Google Factory Reset Protection on VARIOUS Devices! Ignore the poor grammar, typos etc.. Bits and pieces from notes. --needed-- bluetooth (needed) data cable (needed) computer (needed) Factory reset phone, forward...
forum.xda-developers.com
Credits for app goto those Yemen Fellas who have so far been able to bypass anything in front of them LG/Samsung Carrier - Sprint!! Tracfone --> FRP/Unlock
Credits also to @CXZa as if it weren't for him i probably would not have looked deeper into AT commands.
noidodroid said:
I have done this already. No way into browser on the device i tried it on. Weird device too.. MS210.. I have been able to bypass this device no problem before until someone updated the firmware i think.. Mindboggling..
Anywho here is how i bypassed it and so far i think this method should work on all similar. I couldn't get security patch level as i had to give device back to the client. :-/
New Way to Bypass LG - Google Factory Reset Protetion on VARIOUS Devices!!
New Way to Bypass LG - Google Factory Reset Protection on VARIOUS Devices! Ignore the poor grammar, typos etc.. Bits and pieces from notes. --needed-- bluetooth (needed) data cable (needed) computer (needed) Factory reset phone, forward...
forum.xda-developers.com
Credits for app goto those Yemen Fellas who have so far been able to bypass anything in front of them LG/Samsung Carrier - Sprint!! Tracfone --> FRP/Unlock
ALL YOU HAVE TO DO IS FACTORY RESET....THEN DURING SET UP TURN WIFI ON....THEN HOLD NEXT AND WIFI SWITCH AT SAME TIME...AND IT BYPASSES
Click to expand...
Click to collapse
Finish by setting lock pin then skip to start up...then developer options oem unlock and usb debugging...then factory reset from settings menu....$$$$
KtownJeff said:
Finish by setting lock pin then skip to start up...then developer options oem unlock and usb debugging...then factory reset from settings menu....$$$$
Click to expand...
Click to collapse
Bypass FRP LG Velvet Android 10 - Bypass frp Without PC
How to Remove FRP LG Velvet Android, How to bypass google account LG Velvet Android 10, Remove FRP LG Velvet Android ? All process can be done easily from
www.techeligible.com
Nice. I will check it out.
KtownJeff said:
Bypass FRP LG Velvet Android 10 - Bypass frp Without PC
How to Remove FRP LG Velvet Android, How to bypass google account LG Velvet Android 10, Remove FRP LG Velvet Android ? All process can be done easily from
www.techeligible.com
Click to expand...
Click to collapse
I wonder if anyone has found a way to carrier unlock these LG Velvet devices yet.. From what i hear nobody has. But there is always someone or some team.
If you just reset it and once you get to the wifi select screen, just click the button to turn wifi off and the next in bottom right at same time. It will continue setup offline and let you choose pin to get in.

I am currently being locked out from my SM-J200BT and now I want to bypass the lockscreen without losing any data. Any suggestions?

So, I am currently having this Samsung Galaxy J2 TV (SM-J200BT, Android 5.1x) that I have been locked out for a couple of months now and I still have some important data there to be fetched out from the device, therefore leaving the factory reset option as the last resort. I have tried using Dr Fone and iMyFone but my device is not listed on their supported devices at the moment. I also have tried using ADB but unfortunately, USB debugging is disabled on the phone. At one point, I even have considered to apply the method which involves copy-pasting a long list of numbers and pasting it into the password field then crashing the lockscreen, but unfortunately again, the phone does not even allow me to copy nor paste anything while it is locked. I also have considered using the GSD tool to install the phone's boot.img file for this matter but the file that I have downloaded for my device seems to be unsupported or corrupt according to the software and carrying the next step into Odin just doesn't do anything either (TWRP included, since the 'galaxy j2lte' file was the closest one I could find).
The only possible solutions that I could think of, at least to some extent, that is still giving hope at the moment is to somehow find a roundabout method in activating USB debugging while the phone is locked or have a proper firmware/file that can help me succeed in installing into the phone and unlocking it using Odin or some other method, while at the same time, NOT LOSING ANY DATA. Any help or suggestion is widely appreciated, thanks in advance.
To access internal storage media ( userdata ) in case of a FRP lock phone's Android must be rooted and USB-Debugging must got enabled.
jwoegerbauer said:
To access internal storage media ( userdata ) in case of a FRP lock phone's Android must be rooted and USB-Debugging must got enabled.
Click to expand...
Click to collapse
It seems that I don't have much choices to select from here at the moment, do i?

Categories

Resources