Develop Bugs

[Q] After Rom Update, Phone Cant Connect To Mobile

Updated my Rom last night to its current nightly version. Thought everything was good. Leaving for work the next day I notice I don't have ANY cellular signal. Thought it might have been the update so I wipe cache/ dalivk/ format system. Install older version of rom. Same thing happened. No cellular signal NOR could my phone activate. I went into my settings/ status/ and noticed everything had been nulled out to zero. My phone number, MIN, PRL, and Username. Any idea how I can restore this? I tried flashing several different roms but the same thing happens. I also tried unrooting the device and get stock rom to perform a system reset but that did not work. Any suggestions. I tried searching for a solution but couldn't find any. Thanks!

jsusgeek said:
Updated my Rom last night to its current nightly version. Thought everything was good. Leaving for work the next day I notice I don't have ANY cellular signal. Thought it might have been the update so I wipe cache/ dalivk/ format system. Install older version of rom. Same thing happened. No cellular signal NOR could my phone activate. I went into my settings/ status/ and noticed everything had been nulled out to zero. My phone number, MIN, PRL, and Username. Any idea how I can restore this? I tried flashing several different roms but the same thing happens. I also tried unrooting the device and get stock rom to perform a system reset but that did not work. Any suggestions. I tried searching for a solution but couldn't find any. Thanks!
Click to expand...
Click to collapse
Flash a Touchwiz ROM and enter ##72786# into the dialer. Make sure the Touchwiz ROM you flash matches your baseband (ND8, MK3, MD4, etc).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My ROM: WICKED X

bilgerryan said:
Flash a Touchwiz ROM and enter ##72786# into the dialer. Make sure the Touchwiz ROM you flash matches your baseband (ND8, MK3, MD4, etc).
My ROM: WICKED X
Click to expand...
Click to collapse
Thanks for the reply! I did that and still doesnt work.
Baseband: L710VPUDN8
Rom: Conquest-Singularity-9.4 (This is NOT the rom that caused the error!)

jsusgeek said:
Thanks for the reply! I did that and still doesnt work.
Baseband: L710VPUDN8
Rom: Conquest-Singularity-9.4 (This is NOT the rom that caused the error!)
Click to expand...
Click to collapse
Have you tried Odining stock ND8?
My ROM: WICKED X

bilgerryan said:
Have you tried Odining stock ND8?
My ROM: WICKED X
Click to expand...
Click to collapse
I tried that too. I went to stock ND8 and tried to factory reset and debug but the status and prl were stilled zeroed out.

jsusgeek said:
I tried that too. I went to stock ND8 and tried to factory reset and debug but the status and prl were stilled zeroed out.
Click to expand...
Click to collapse
I would say call your service provider then.
My ROM: WICKED X

I finally got it! 8 hours of research and I finally got it fixed NO THANKS TO SPRINT -(shouldnt be a surprise really)
Anywho! If this happens to anyone, I hope this helps:
1) Downloaded and install the appropriate Samsung USB drivers.
2) Download and install the "freeware/demo" version of DFS
3) Put your phone in DIAG mode:
* phone -> ##DIAG# (opens Diag screen)
* Open "Qualcom USB Setting" menu and select "DM + Modem + ADB", hit "Ok"
* Select "CDMA Modem"
4) Plug your phone into your computer via USB
5) Open DFS and click the connections button (a plug) you should see your Samsung device listed.
6) Your phone should now be connected! Select your phone from the dropdown in DFS (upper left)
7) Enter your MSL/SPC in the left box and click the button to send the code, you should see an "Unlocked" success message in the console
8) Enter the device code "01F2030F5F678FF9" or "2012112120131219" in the PWD box, click the button to send the code, you should see another "Unlocked" success message in the console
9) You should be able to read/write codes at this point.
10) Once you correct your HEX/DEC, press the disconnect button. Then remove device from PC.
11) Go back into ##DIAG# and change your settings back.
12) Restart phone... Viola!
Hope this helps! Now I'm going to bed!

jsusgeek said:
I finally got it! 8 hours of research and I finally got it fixed NO THANKS TO SPRINT -(shouldnt be a surprise really)
Anywho! If this happens to anyone, I hope this helps:
1) Downloaded and install the appropriate Samsung USB drivers.
2) Download and install the "freeware/demo" version of DFS
3) Put your phone in DIAG mode:
* phone -> ##DIAG# (opens Diag screen)
* Open "Qualcom USB Setting" menu and select "DM + Modem + ADB", hit "Ok"
* Select "CDMA Modem"
4) Plug your phone into your computer via USB
5) Open DFS and click the connections button (a plug) you should see your Samsung device listed.
6) Your phone should now be connected! Select your phone from the dropdown in DFS (upper left)
7) Enter your MSL/SPC in the left box and click the button to send the code, you should see an "Unlocked" success message in the console
8) Enter the device code "01F2030F5F678FF9" or "2012112120131219" in the PWD box, click the button to send the code, you should see another "Unlocked" success message in the console
9) You should be able to read/write codes at this point.
10) Once you correct your HEX/DEC, press the disconnect button. Then remove device from PC.
11) Go back into ##DIAG# and change your settings back.
12) Restart phone... Viola!
Hope this helps! Now I'm going to bed!
Click to expand...
Click to collapse
ok, so I have the same issue, and did lots and lots and LOTS of looking around, and this seems to be the only appropriate way to do this. HOWEVER, every time i try to connect my phone to dfs, it doesn't read it correctly, either with the msl or ignoring it, or any of the 16 digit passwords I've come across for s3 basebands. SO... I'm just wondering what rom/modem combo you used. I've come to the conclusion that using a different rom with the corresponding baseband will allow me to properly connect to dfs. help please?? lol... thatnks in advance

I know this thread is super old, just thought that id add that I was able to connect to dfs and nv tools with cm11 and nfc baseband. Worked right away, was able to pull all the needed info/files, and get my spc without contacting carrier [emoji14] then just reflashed wicked x
Sent from my SPH-L710 using Tapatalk

[Q] USB Debugging mode blocked by Server?

Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!

I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging

jac10000 said:
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
Click to expand...
Click to collapse
It does not show up ever, unplugged or plugged in.

Jacobsen Chief said:
It does not show up ever, unplugged or plugged in.
Click to expand...
Click to collapse
Ok try this :
Solution 1 : Have you switche the activate button ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode

jac10000 said:
Ok try this :
Solution 1 : Have you switche the activate button ?
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
Click to expand...
Click to collapse
None of those things worked... Ive never seen this before. Here is a screenshot

I think it's a bug with lollipop and it seem that the solution is the factory reset

jac10000 said:
I think it's a bug with lollipop and it seem that the solution is the factory reset
Click to expand...
Click to collapse
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?

And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1

jac10000 said:
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
Click to expand...
Click to collapse
I tried installing the KDZ though TWRP, but when it failed I decided to go ahead and just update it with the LG Software. I had read other articles on rooting the G3 with Lollipop, so I didn't really worry about re-rooting it until I ran into this problem.
For installing with the KDZ, I extracted Modem, Boot, and System.imgs, but the System.img failed. And yes with KitKat, I could use debugging.

facing the same problem myself, did you ever find a solution? because this is getting really frustrating

Dragontype191 said:
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Click to expand...
Click to collapse
Update, I made a post over on the US Cellular forums and if anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!

Dragontype191 said:
If anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Click to expand...
Click to collapse
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.

To Enable USB Debugging mode that is blocked by Server you have to dissable McAfee Mobile SECURITY

Jacobsen Chief said:
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
Click to expand...
Click to collapse
Click on revoke USB debugging authorization. Click ok. Turn off developers option on the verg top. Turn it on again and voila you now have an option to put a check on usb debugging. Hope it works for you...
LG G3 Android 5.0 user

Jacobsen Chief said:
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
PLEASE PLEASE PLEASE READ! This is probably the fix to this problem all because of a stupid built in app that the g3 includes now and it has to do with McAfee Security.
If it worked mark this up for those future people who have issues!!
Okay so i found out what the problem was. I used to own and lg g2 but recently got the g3. Im with sprint fyi...but anyways i was tinkering around with it being 17 and stupid i bricked the phone, so i eventually got it fixed again. Previously my phone was rooted but now it wasnt so then i went back to get developer options activated and usb debugging active as well, however i ran into this problem. This stumped me because i had it rooted before. So then i was thinking what did i give accsess to that i hadnt before that isnt allowing usb debbugging...well it had to be an app since this didnt happen to me before and it had to be an app that i hadnt used before i bricked my phone and then i thought it has to be a built in app since no third party app would have that permission to say something like "disabled by server policy" then i realised okay what does the g3 have that the g2 doesnt have and is built in.....Mcafee security and Lookout! And it made sence because when you check the box for usb debugging you are making your android less secure! So i entered the McAfee app tapped settings ---> and the first option should be "lock down device" TURN THAT OFF! That right there is your culprit now go back to dev options and you can now enable usb debugging again please rate this up so people can see what was going on and how to fix it. No need to reset your phone. Also let me know if this worked. I have got nothing but positive feed back so far.

I am having the same problem and i have an LG Lucky and usb debugging is disabled by server policy and i really dont know what to do but it worked at first then later it got blocked.

help please
PokrTom said:
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
Click to expand...
Click to collapse
My debugging option is not available. Do I need to have my old sim card in place? It was from at&t. I took it out a while back. Is that why I cannot chose the Debug option? Ive tried everything on this forum.

I had the same issue. It was blocked by mcafee. I had to change it from " locked down mode" to unlocked mode, then turn developer options off and right baxk on. Then i was allowed to turn on usb debugging

Solution
Okay, so I was having the same issue. I contacted LG, Google, and finally AT&T after I tried a lot of the suggested solutions on this post. The AT&T tech support rep helped me research this issue. The issue is that an app on your phone is not allowing you to be able to debug, most likely a security app. I suppose that it thinks by allowing your phone to debug could cause harm to the device. The app that was keeping me from debugging was McAfee, which came pre-installed. When you disable this app, or whichever app is keeping you from debugging, you will then notice that the message 'USB debugging is disabled by server policy' goes away. I hope this helps you all, and happy developing!
God is good!!!

sir can you all help me for this problem? i can't update and fix my g3! ugrrrr !!!1

[HELP] Bypass PIN's phone lock and recover Google's account WITHOUT Wifi/Mobile datas

Hello friends,
Finding no solutions on the Web and on XDA, I need to ask you one thing :
A really close friend of mine passed away on july 13th after a damn f*cking brutal and quick heartattack. (He did'nt have time to take his phone to call emergencies) :'(
His family tried to unlock his phone to call some of his friends, to get some contacts , recover photos, etc... but unfortunately they could'nt unlock his phone because of a security PIN lock.
I know his SIM Pin code, so I could unlock the SIM to answer his phonecalls.
I know all of his passwords (Google, Gmail, etc...).
The problem is that I couldn't bypass the screen lock and recover thru Google's Account Recovery because he cuts WIFI & MOBILE DATAS (he follows my advice to save battery ).
I tried to bypass using the Quicknote trick (that allowed me to activate WIFI & BLUETOOTH), but unfortunately it couldn't connect to my WIFI (unlocked)...
Any clue ?
NO, I'm not a thief, a robber, a delinquent, so I didn't steal that phone. (Me and my wife are owner of 2 G4)
Feel free to ask me more infos/proofs via PM.
Thanks for your help and for his family.
Note : the phone isn't rooted and I don't want to do it because I don't want to wipe his (and it's) memory.

No one can help me ?

Did you check this out?
http://forum.xda-developers.com/g4/general/bypass-google-account-lg-g4-tool-t3261627

Thank you for your answer Jobella.
Why should I bypass Google account ? :/
I need to recover the PIN, so I need to connect to Internet. But unfortunately, data is off (Wi-Fi seems to be on, but doesn't connect alone to a free hotspot...), so I can't recover it.
Any clue ?

After I posted I realized you needed to bypass the phone lock screen and not the google account password. My mistake.

jobella said:
After I posted I realized you needed to bypass the phone lock screen and not the google account password. My mistake.
Click to expand...
Click to collapse
Yes.
I just need to activate datas...

does ADB detect the device? if so, you can boot into TWRP (no need to install) and delete lock files.
adb reboot-bootloader
fastboot boot "path of twrp recovery image" (ex. fastboot boot "c:\twrp.img")
once TWRP is booted, go in advanced/data/system and delete followings
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
reboot the phone, and screen lock should be gone and swipe to open.

sharpehenry said:
does ADB detect the device? if so, you can boot into TWRP (no need to install) and delete lock files.
adb reboot-bootloader
fastboot boot "path of twrp recovery image" (ex. fastboot boot "c:\twrp.img")
once TWRP is booted, go in advanced/data/system and delete followings
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
reboot the phone, and screen lock should be gone and swipe to open.
Click to expand...
Click to collapse
Hello sharpehenry,
Thanks for your answer but unfortunately, ADB does not detect the device.
Can I force connect ?

sharpehenry said:
does ADB detect the device? if so, you can boot into TWRP (no need to install) and delete lock files.
adb reboot-bootloader
fastboot boot "path of twrp recovery image" (ex. fastboot boot "c:\twrp.img")
once TWRP is booted, go in advanced/data/system and delete followings
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
reboot the phone, and screen lock should be gone and swipe to open.
Click to expand...
Click to collapse
Hello sharpehenry,
Thanks for your answer but unfortunately, ADB does not detect the device.
Can I force connect ?

if adb is not enabled you can't enable it with out unlocking the screen.
What about android device manager? I think that should let you lock the phone with a password you set. forgot you said you tried that.
Do you know any wifi networks he had it set to auto connect to? I think your best bet is to try to recreate one of them with the same ssid and wpa password so you can use android device manager to change the password.

lart2150 said:
Do you know any wifi networks he had it set to auto connect to? I think your best bet is to try to recreate one of them with the same ssid and wpa password so you can use android device manager to change the password.
Click to expand...
Click to collapse
SH*T ! That was the solution !!! I read it too late : finding no solution, I performed a factory reset ! :crying::crying::crying:
I re-activated the Wi-Fi using the "quick memo trick". And doesn't think about his own Wi-Fi.
Tanks for your help !

Samsung A7 2017 lock pattern cannot be bypassed, newly updated to official firmware

Hi friends,
this is my first post here and thanks a lot to whom paying time to answer my questions.
I am having trouble with Samsung A7 2017. My wife always uses fingerprint for unlocking her phone. 2 or 3 days ago (~20.01.2018) she has started an official regular update and it finished normally. But after a restart, the phone gave a message that at least once the phone should be opened with the unlock pattern. Both i and my wife does not know or at least could not enter the correct pattern. So, i talked to a samsung call center person, and she asked me if we have any samsung account working on that phone but unfortunately we do not have one. She told me that more probably the data on the phone would have to be erased in samsung authorized technical service.
Until then, i did not have any experience about android technically, but i am now trying to understand what booting, TWRP, CWM, odin is meaning in terms of android running phone. Actually i am an electronics engineer, i even develop some basic applications on android but this kind of informations are completely different and new to me.
The only important point is that I REALLY DO NOT WANT ANY DATA LOSS, since i have many memories, pictures, videos on that phone. Please do not get angry with me for not backing up earlier, because i am already very sorry on that and angry with myself.
Anyway, i tried following but could not have success.
1. The phone's "developer options" menu is not activated, thus "USB debug" option is also unchecked. We do not have any chance for changing this because we are unable to bypass the pattern lock screen. So as i guess ADB commands are of no use. If this information is not true please explain me how i can proceed since i do not have much information.
2. I restarted the phone, by pressing "VolumeDown + Home + Power" buttons and Downloading mode appeared on the screen. I ran the Odin (latest versions - do not know exactly since i tried many) software on my PC and tried to download TWRP on the phone but failed each time. Phone gave the massage telling about "... FRP lock". I guess this is due to a lock under developer options (something like ... OEM lock). So i could not install TWRP.
Again if my knowledge is false please tell me the true way or right information.
3. I had an idea on creating a bootable SD card so that it will boot from it and thus giving me the opportunity for installing TWRP. But i could not find much information on that.
Please help me find a suitable solution. I am actually not interested in rooting the device or installing TWRP and in fact i do not want my device warranty voided. But my first priority is extracting safely my data from the phone. So if i need to root the phone to get them it is not a problem even if the varranty vanishes. Being able to bypass the lock screen is a sufficient solution for me now but i do not know how. So please direct me in a best and simplest way and i, as a newbie, will try to understand and search what you advice with my greatest effort.
Thank you all in advance & best wishes
Tankut (Elect. Eng.)

Unfortunately I don't think that there is any way to hack your phone with these conditions... The only think I can tell you is that you can factory reset your phone without paying anyone just from the downloading mode

Didn't Google photos automatically backup your pics and videos?

Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.

In addition to my previous post, i searched for possible backup of photos and videos on google account and found some, it is a nice news. But my wife was usully using CandyCam application on the phone and unfortunately i could not find any photos or videos bakup taken by CandyCam. I could not find a way for adding the CandyCam photo or video folders in the google backup task via google account remotely(that is outside the phone)(If only i had done it before on the phone itself while everything is fine). Do you think it is possible? Thanks.

hayat_bilgisi said:
Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.
Click to expand...
Click to collapse
Stock recovery is of no use unless you are prepared to wipe/reset the device.
Are you sure you can't use Google's find my mobile?
As far as I'm aware you can reset the lock to a password which you then use on the device. You may have to wait a while for this to happen and reboot.
Also if there is a Samsung account on the device you can unlock with that.
Have you tried entering the wrong pin around 15 times (I think)?
This used to allow you to use Forgot password and enter your Google log in details instead.
Lastly there is a possible way with ADB.

When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.

hayat_bilgisi said:
When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.
Click to expand...
Click to collapse
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?

ashyx said:
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?
Click to expand...
Click to collapse
Dear ashyx,
Thanks for your reply,
Yes, unfortunately there is no samsung account on the device.
At this moment i think the device has the latest official firmware(by saying firmware, i think you mean what we install or upgrade as the operating system) which samsung published, because my wife accepted the install just a few days ago(about 20.01.2018). I do not know what this upgrade consists of or what version it is. But is it possible to revert back to previous or former releases of firmware in my situation? Can you explain me shortly how i can do this briefly? And of course, if this works - e.i. if i reverted back to a previous firmware, do you think is it going to be useful in my situation?
How should i proceed? Thanks

By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.

hayat_bilgisi said:
By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.
Click to expand...
Click to collapse
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?

ashyx said:
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?
Click to expand...
Click to collapse
Here is the recovery screen of my A7 2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[ROM][UNOFFICIAL][PixelExperience][9.0][dragon] -> 20190624 (DISCONTINUED)

DISCONTINUED
Pls find my last builds ..
https://androidfilehost.com/?w=files&flid=289293
Pls find new PE builds here ..
https://forum.xda-developers.com/pixel-c/development/rom-thread-title-2019-08-25-t3961148
Thanks to @tschmid for taking over PE !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience
What is this?
Pixel Experience is an AOSP/CAF based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
​PixelExperience_dragon-9.0-20190624-1228-UNOFFICIAL.zip
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
Installation:
1. Boot into TWRP (latest available version)
2. Wipe system, cache, dalvik and data partitions ! ( If you have encrypted /data partition - pls "format" /data via TWRP first ! )
3. Install ROM.zip
4. install Magisk.zip
5. Reboot into system ..
- The ROM does contain it's own vendor.img !
- This ROM does include Gapps already !
SOURCES:
https://github.com/followmsi/manifests/tree/dragon-pixel-pie
Enjoy

And one more ROM for dragon .. Pixel Experience
Enjoy ..

You have too much time on your hands

Awesome ROM. Was waiting for such a release... Thank you
Sent from my Pixel C using Tapatalk

Amazing thank you for keeping this tablet alive!

Simply awesome. Fantastic job. The best Pixel C custom rom.

Seems like front camera is not working (especially on Google Duo app) any work arounds?

followmsi said:
Known issues:
- Encryption seems not work - and has not been fully tested. -> Pls do not encrypt your data partition yet.
- Screen Unlock: If you set Pattern or Password the Screen unlock does not work correctly.
(Workaround: On fresh boot you will need to wait a bit longer before you enter credentials.)
(The waiting time is required on fresh boot only, the following unlocks are working normally.)
Click to expand...
Click to collapse
Got this installed today and currently using to write this message. I'm confused regarding the known issues though....
I set a PIN as it wasn't specifically mentioned, but I could not login at next reboot at all. Every time I entered the PIN, the screen would refresh back to the PIN login screen. I tried again many times, left it 10 minutes but nothing worked so I had to factory reset from TWRP in order to gain access to the tablet again.
Perhaps I have misinterpreted the known issues?
Only other problems I had was the following:
- Wifi drops off sometimes for no reason, then comes back about 10 seconds later
- Couldn't use default two-factor authentication when logging in with my Google account (i.e.. Press 'Yes' on your phone), I had to use Google Authenticator to generate a code instead. Having said this, after the factory reset, it worked this time.
- Couldn't setup the device first time around as it was unresponsive and slow, a reboot fixed this
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
And for the record, I was stock before this, followed the instructions above (Obviously had to unlock bootloader before installing TWRP for the first time).

Only issue I've seen so far is the normal navigation buttons the recents button is missing

Iggy82 said:
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
Click to expand...
Click to collapse
Wasn't that a bug we all had when we went from Android 7 to 8?
Using another launcher stops it.

m+a+r+k said:
Wasn't that a bug we all had when we went from Android 7 to 8?
Using another launcher stops it.
Click to expand...
Click to collapse
Yeah I also had issues creating a new app shortcut (by dragging an app icon from the list of apps to the home screen). Installed a different launcher and that's those problems dealt with. WiFi seems to be fine now too so could have been a local issue.
All in all, it's great to see Pie on the Pixel C, it deserves it too because the hardware is still outstanding, even in today's market.
Thank you followmsi

Thank you!
Thanks! I'm running it right now!

I have no problem creating folders on the desktop. The way to do it is to approach the icon in the upper left, diagonally. At least that's how it works for me

Iggy82 said:
Got this installed today and currently using to write this message. I'm confused regarding the known issues though....
I set a PIN as it wasn't specifically mentioned, but I could not login at next reboot at all. Every time I entered the PIN, the screen would refresh back to the PIN login screen. I tried again many times, left it 10 minutes but nothing worked so I had to factory reset from TWRP in order to gain access to the tablet again.
Perhaps I have misinterpreted the known issues?
Only other problems I had was the following:
- Wifi drops off sometimes for no reason, then comes back about 10 seconds later
- Couldn't use default two-factor authentication when logging in with my Google account (i.e.. Press 'Yes' on your phone), I had to use Google Authenticator to generate a code instead. Having said this, after the factory reset, it worked this time.
- Couldn't setup the device first time around as it was unresponsive and slow, a reboot fixed this
- Can't seem to drag apps on my home screens on top of eachother to create folders, whatever I do they always seem move the other app rather than create a new folder.
And for the record, I was stock before this, followed the instructions above (Obviously had to unlock bootloader before installing TWRP for the first time).
Click to expand...
Click to collapse
I will add "pin" to known issues on first page too.
Encryption/keymaster is not working correctly on all Pie ROMs.

Roxas598 said:
Only issue I've seen so far is the normal navigation buttons the recents button is missing
Click to expand...
Click to collapse
You can try this method to turn on recent buttons.
adb shell settings put secure sysui_nav_bar "space,recent;home;back,space"
https://www.xda-developers.com/how-...icons-or-re-arrange-the-buttons-without-root/

followmsi said:
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.[/I]
Click to expand...
Click to collapse
followmsi - Just to clarify (before I go locking myself out completely!) - If I set a pattern unlock (NOT Pin or Password), I will be able to unlock my device properly after waiting a while??

Iggy82 said:
followmsi - Just to clarify (before I go locking myself out completely!) - If I set a pattern unlock (NOT Pin or Password), I will be able to unlock my device properly after waiting a while??
Click to expand...
Click to collapse
For me it works like this .. waiting a bit longer before first pattern unlock.
Otherwise.. have a look here.
https://forum.xda-developers.com/showpost.php?p=78786907&postcount=992

Thanks for the prompt responses. One more question which I'm yet to solve regarding the 30 second bootloader unlocked wait during boot.
I've heard that if I relock the bootloader, the device will lose root and wipe itself. I don't mind a wipe, nor do I use root. So if I were to relock the bootloader, would it still boot up OK into this current ROM? Others have said it could brick the device!.....?

Thanks for this great ROM! I've been waiting for a proper Pie ROM for a long time!
I got no issues with the PIN. Got a 8 numbers PIN and it works great.
Only issue I have is the folder thing but it does not matter as I got not much apps on my tablet!
I got an issue with a notification telling me that the setup was not finished and tapping on it brought a "OK" button and a white page... Tapping OK would get rid of the notification but it would eventually come back a couple minutes later. A reboot solved this issue.

camera not working at all ...
First of all: Thank you so much!!!
wonderful ROM.
Just: the camera is not working.
Any ideas / experiences with that?
costlyman seems to have the same problem.
EDIT: working now after a few restarts - and I don't know.
Thank you in advance.