Database Develop

Spy on Wife - Bypass Pin with Demo code?

http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?

owen1978 said:
http://forum.xda-developers.com/showthread.php?p=40782218
In the above thread, does this method work with the stock sony Xperia T firmwares
please can you post your firmware version (stock only, no cm, no aokp or custom roms) and let me know
if it worked.
Basically I want to access my wifes phone and check her messages as she has been acting weird
I tried the service menu trick on her phone but it didn't work which means her phone has more up to date firmware i believe
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.

BarneyJ said:
Just tried that for you, it didn't work; the Emergency dial screen wouldn't accept the *#*#73556673#*#* code.
The lock screen WAS disabled whilst the Demo was active but as pressing the power button to wake the screen was immediately rerunning the Demo I'm sure that would get noticed. (Xperia T firmware 9.1.A.1.141).
Might have time to test out the 2nd link you posted later.
Click to expand...
Click to collapse
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much

owen1978 said:
1) Did the demo run?
2) Did you then press home button to go to the home screen?
3) Did you then bring up dialer and type in the demo code again to disable the demo?
http://www.youtube.com/watch?v=gRelLSb0vgw&feature=youtu.be
In the video when the demo is running he taps it to bring up the home button, did this work on yours?
Thanks v much
Click to expand...
Click to collapse
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.

BarneyJ said:
1) The Demo ran when the phone was already unlocked and I typed in the code from the dialer - on first run it even prompts you that it will change the screen unlock password.
2) Yes pressing the home button went to the Home screen (at this point if you switch the screen off then back on the Demo reruns).
3) Yes I did.
The code doesn't seem to work at the Emergency Call screen on my Xperia T, or perhaps the phone he's using in the Video doesn't have the most current firmware.
Click to expand...
Click to collapse
It is possible you can test the zip file method?

I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.

BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
ahh ok, neither does her phone so that wont work.... never mind thanks for your help

Had a thought what if I flash an older version of firmware which has the service menu security hole?
Would just have simply plug her phone in, flash it, and then let it restart (wiping only cache and dalvik, if they are available in stock recovery)
So she won't lose any of her data and won't be any wiser?
hmmm....

BarneyJ said:
I'm on my way to work now, I'll try the 2nd thread a little later. I'll have to try Method B in that thread because I don't currenty have CWM recovery on my phone which is required for Method A using the Zip file.
Click to expand...
Click to collapse
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated

owen1978 said:
EDIT found this
http://forum.xda-developers.com/showthread.php?t=2244741
Can someone confirm it works on xperia T?
Click to expand...
Click to collapse
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled

owen1978 said:
Ahh was reading too quickly method b doesnt require CWM... ok, if you can give this a try and get back to me it would be much appreciated
Click to expand...
Click to collapse
matt4321 said:
I've tested a similar method on windows that worked on my T on JB.
all it needed was a
adb shell
su
rm /data/system/gesture.key
Click to expand...
Click to collapse
This of course has limitations, the device needs to be rooted and usb debugging must be enabled
Click to expand...
Click to collapse
Well I suspected that USB debugging would need to be enabled to use the B Method in that thread you linked and what Matt has said Tally's with this; I've now had time to try and can confirm this.
Matt's commands worked when I substituted 'password.key' instead of 'gesture.key' in the 3rd line (I had a PIN lock set) - 'gesture.key' seems to be for when a pattern lock is set, and 'password.key' for PIN lock.
Method B in that thread is missing the 'su' line that Matt has above, so failed with 'Permission Denied' when trying to delete the .key files - works once you add the su command.

MIUI Global 7.2.4.0.0 uses A LOT of RAM. (?)

Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.

proag said:
You have a fake rom. 7.2.4.0.0 is not an official MIUI rom and newer was. 7.2.4.0 is an official rom.
You should flash the official rom.
Click to expand...
Click to collapse
Thank you. I didn't notice the extra zero and didn't think it was unoffical.
Sincerely
John

jhenrikb said:
Hello. Couldn't find a post related to this. I'm not a lazy browser, been on XDA for many years through many phones. Just haven't had the need for a user account until now.
I see the 7.2.4.0.0 version is removed from MIUI websites and i can think of a few reasons already.
Does anyone else have this problem too? I have the 3GB version and normally start out with 1.7gb RAM after a boot. Gradually over the day (even after closing apps) it goes slowly down to 200mb and i have to do a reboot.
Or Does anyone have the 6.5.30 version and could tell if it uses up the RAM over time?
Sincerely
John
Click to expand...
Click to collapse
You are on an un-official modefied version.
The fake version is 7.2.4.0.0 <- your version.
The real official and supported by Xiaomi version is 7.2.4.0

Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!

androFRUST said:
Hi,
Hope I can get some help. I recently just picked up a unit and am on 7.2.4.0.0. Realised it was a fake rom but I seem to have trouble flashing the global rom or the china stable rom. Believe my bootloader is locked at this point and have applied through the unlock miui website but that will take at least 10 days or more to get the SMS.
Frustratingly, I have seen some solutions on the miui forum and there was one proposed solution, of which many were finding success, that includes booting to recovery mode and then hitting shift + [flash] when connected to the Chinese miPCsuite. My update only goes by to mid 50% levels and then its stuck on for several hours! Is this a USBC to USB port incompatibility issue (if it was it wouldn't have recognized the phone right?) or is my phone just beyond saving ? At this point, im not confident in using other solutions as they look highly technical and some have highlighted that their phone has bricked in doing so.
Appreciate any advice! thanks. PLEASE HELP!
Click to expand...
Click to collapse
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all

TheUltrametricSpace said:
if you already tried the simple steps as stated then there are no more simpl steps left.
Do an EDL flash and make sure you clear all, and be aware that most Mi flash stuff works best on Windows 64Bit.
Click to expand...
Click to collapse
Thanks for the reply! Before proceeding, I actually received the SMS to unlock the bootloader but im still at work so I cant go back and attempt the unlock. So just trying to manage my expectations here.
Is it safe to assume that all I need to do now is log in to the unlock tool by miui and unlock? because im still on 7.2.4.0.0 (the unofficial discontinued rom) and I have no way of flashing it to any other roms. My last attempt last night was again, stuck at 52% after a nights worth of wait! TT
---------- Post added at 03:01 AM ---------- Previous post was at 02:49 AM ----------
xtachix said:
What he said, download the latest, both files can be obtained HERE
-MiFlash tool - step 1
-official fastboot rom - step 2
install the MiFlash tool
extract the downloaded rom (tgz) then extract the output file (tar) > make sure you copy the path of the directory where you see all the files like flash_all flash_all_lock etc..
reboot your phone into fastboot mode (you can access this by turning off your phone, hold vol - and power)
make sure you have adb on your pc
type this: the first line is optional to see if the phone is recognized.
Code:
fastboot devices
fastboot oem edl
edit: I should mention, do not panic, the screen of the device will turn black but will still remain on.
launch the MiFlash tool
Click on Refresh, you will see a device right now in the list called COM (some number) >>>> it will be ticked
Paste the copied directory path into the white... uhh search bar thingy . or just click Browse and select the appropriate path.
Click Flash
edit: once done, simply unplug your phone and restart it by pressing the power button.
That should be all
Click to expand...
Click to collapse
Thanks for the help. I will attempt this as a last resort. I just received the SMS to unlock my bootloader. Hopefully its as simple as logging in and unlocking so I can get rid of this pesky 7.2.4.0.0 supposed "Global" rom.

i have successfully flashed to global rom!!! but now i have no audio coming from the speakers!!!! is it just my luck!!!??? and after reflashing again.. its completely dead.. its goes into the sign in to miui welcome page and just goes insane.. like to the point where i cant even select options and and random menu sounds keep coming up.. cant even turn off i had to reboot to fastboot.. is a goner? sighs..

7.2.4.0.0 to Resurrection Remix (CM13)
- unlock bootloader
- flash TWRP with fastboot
- install Resurrection Remix
- install GApps
- reboot, now it's say Google play stopped.
- go back to TWRP
- wipe data
- reboot and everything is working

MAY 2018 security update.

I received the update and didn't check whats new. Anyone has the change log? Anything new?

Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk

Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes

Stransky said:
Are you on 8 or 8.1 as I am on 8 and still on 1 Feb
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Am on 8.1 global variant. How are you still on Feb?

Scarkinyua said:
Am on 8.1 global variant. How are you still on Feb?
Click to expand...
Click to collapse
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk

AchinPakhi said:
dual volte support(Indian variant got this one the may 2018 security update..don't know about other variant)..Trusted face is back in smart lock.. front and back camera switch icon change in camera app.. and improve system stability.. I forgot if there's any more changes
Click to expand...
Click to collapse
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"

They've also removed the functionality in which you can navigate using the fingerprint sensor ?

After the may 2018 update I noticed some 4G connectivity issues: no more internet. By moments, the phone would switch to 3G and then internet would work.
I thought I did something bad, so I reset APNs, etc. no luck. I even completely wiped the phone, but that did not change anything.
Then I saw this thread on Nokia forum:
https://community.phones.nokia.com/support/discussions/topics/7000025066
For now, by forcing 3G, I can get internet all the time, but I hope this fix will be temporary.

Scarkinyua said:
Excuse my ignorance sonhow do you activate trusted face. I have already set up "my face"
Click to expand...
Click to collapse
ah sorry for a super late reply.. if u have already set up trusted face then it's already been activated.. just lock the screen and turn on using the power button.. there will be a small face icon at the bottom middle of the screen .. when it recognized ur face it will show a unlocked lock(open lock) icon.. then just swipe up the screen...

TA-1062
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one

Stransky said:
Because I am on 8.0 and no update available from Nokia. Believe I have to get it via VPN.
Sent from my Nokia 7 plus using Tapatalk
Click to expand...
Click to collapse
Much easier with the roll back firmware and sideload using ADB or straight from recovery.
Done the ADB and got 8.1 April version (no wipe and everything seem to work fine).
After that got OTA update to May security patch.
More here: https://forum.xda-developers.com/showpost.php?p=76546067&postcount=56
It may be working without enrollment to developer preview. Someone uploaded the zip.

Alfaroerik87 said:
Hi, I can't update my phone to may security patch. I try to restore the phone but can not find the update. My phone is the TA-1062 variant with android one
Click to expand...
Click to collapse
I'm also stuck on 8.0 1062.

Flameboy42 said:
I'm also stuck on 8.0 1062.
Click to expand...
Click to collapse
I'm on 8.1 :/

Alfaroerik87 said:
I'm on 8.1 :/
Click to expand...
Click to collapse
What's your location?

I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?

tkiafar said:
I was also stuck on 8.0, till I decided to go with manual method and update to 8.1 (I am in Ireland). I installed the 8.1 image with local method, no ADB needed. After that the updates were pulled without a problem.
If you want to follow the same procedure please find the topic "How to convert a Nokia 7+ from China Variant to Global" from the main Nokia 7 page and download "B2N-213B" which is 8.1. Ignore "B2N-3050", that is P preview which is very unstable. Place the file in the main directory of phone and dial the code provided in that thread. If you have the global variant there is no need to rename the file. To find the variant go to settings>about phone>build number. 00WW is the global while 00CN is the Chinese. (Thanks to hikari_calyx for making this possible).
It is likely that Nokia pulled the 8.1 updates off because of the stability issues on 8.1. The only issue I experienced after update was the NFC force close once. I enabled "show all force close in the background" from developer options, without that I wouldn't be notified, and after that I used NFC successfully, though the phone only recognizes my card near the camera! That is a terrible range for NFC, may cause serious issue for Android pay as payment devices have all sort of indentations on them. Anyone else had this issue?
Click to expand...
Click to collapse
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
Flameboy42 said:
What's your location?
Click to expand...
Click to collapse
I'm from Chile

Alfaroerik87 said:
file not found with that metod. my phone is 00WW. where is the main directory?
---------- Post added at 03:09 AM ---------- Previous post was at 03:08 AM ----------
I'm from Chile
Click to expand...
Click to collapse
Main directory is the same directory you open first when you connect your device for file transfer, that contains "alarms , android, data" directories. I put the file there without renaming it, and dialed the code. There are posts on the same thread that cover file not found issue, check them out. In any case if it doesn't find the file the only option is ADB sideload.

Face unlock was added
Face unlock was added and security patch updated to may
Scarkinyua said:
I received the update and didn't check whats new. Anyone has the change log? Anything new?
Click to expand...
Click to collapse

Hello everyone, Please I need real help

I had a rog phone 2 with this Version 16.0631.1910.35 WW
Since the update was released, I am tried to update
So, I cannot made it I rooted my phone in somehow, I lost with the steps
So, the phone was started again without update, but it’s always starts on bootloader screen
So, I formatted my phone few days ago and the phone was stacked in booting menu
Every time same thing even when I connected it on the pc only detect the device but no storage or anything
So how can I use my phone again without any of these problem
How can really make as factory condition again without root or bootloader screen
With full performance
Thanks for support
Appreciate your concerns

Fathi Moh. said:
I had a rog phone 2 with this Version 16.0631.1910.35 WW
Since the update was released, I am tried to update
So, I cannot made it I rooted my phone in somehow, I lost with the steps
So, the phone was started again without update, but it’s always starts on bootloader screen
So, I formatted my phone few days ago and the phone was stacked in booting menu
Every time same thing even when I connected it on the pc only detect the device but no storage or anything
So how can I use my phone again without any of these problem
How can really make as factory condition again without root or bootloader screen
With full performance
Thanks for support
Appreciate your concerns
Click to expand...
Click to collapse
You are not alone bro.. it's bricked.. still waiting for mine to be shipped to china for repair

oberio28 said:
You are not alone bro.. it's bricked.. still waiting for mine to be shipped to china for repair
Click to expand...
Click to collapse
thanks for reply
thats mean i have to send it to factory fix ??
no other idea ???

Fathi Moh. said:
thanks for reply
thats mean i have to send it to factory fix ??
no other idea ???
Click to expand...
Click to collapse
If you can get your computer to recognise the device in fastboot mode using adb command to check its recognised you could maybe flash the 1910.35 raw firmware for it using the flashall_AFT.cmd within the firmware folder. I'm at work now but will provide more info later and possibly links to adb and firmware

reg66 said:
If you can get your computer to recognise the device in fastboot mode using adb command to check its recognised you could maybe flash the 1910.35 raw firmware for it using the flashall_AFT.cmd within the firmware folder. I'm at work now but will provide more info later and possibly links to adb and firmware
Click to expand...
Click to collapse
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes

Fathi Moh. said:
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes
Click to expand...
Click to collapse
Sorry for the delay in reply. I'll have a look and provide steps shortly
---------- Post added at 08:37 PM ---------- Previous post was at 08:15 PM ----------
Fathi Moh. said:
thanks for your support
I think maybe recognize the device in fast boot mood
but I wish to help me with full steps and links when u get back
thanks again
best wishes
Click to expand...
Click to collapse
Had a thought, saves me a lot of time re-writing it... Use the link to my thread that uses 1910.35 raw firmware with working links and steps.
As you already had WW 1910.35 version on the phone before, the fingerprint may have already been changed by you or the previous owner. Basically, ignore step 0. You can't boot into the android system to install the app which unlocks bootloader anyway.
Follow each instruction exactly in order of steps 3, 5 (ignoring the fastboot cmd to flash boot img), 1 then 2.
You'll be doing things in that order because you want to install adb fastboot first. In summary... After installing adb fastboot to the root of C drive on your pc, navigate to that adb folder in C drive, double click the cmd-here.exe. A cmd window will open. Then put the phone into fastboot mode and connect it to pc using the side port of the phone. Type and run the cmd 'fastboot devices' on that cmd window. If successful in recognising your phone it will show a serial number/device id. Then do steps 1 and 2

reg66 said:
Sorry for the delay in reply. I'll have a look and provide steps shortly
---------- Post added at 08:37 PM ---------- Previous post was at 08:15 PM ----------
Had a thought, saves me a lot of time re-writing it... Use the link to my thread that uses 1910.35 raw firmware with working links and steps.
As you already had WW 1910.35 version on the phone before, the fingerprint may have already been changed by you or the previous owner. Basically, ignore step 0. You can't boot into the android system to install the app which unlocks bootloader anyway.
Follow each instruction exactly in order of steps 3, 5 (ignoring the fastboot cmd to flash boot img), 1 then 2.
You'll be doing things in that order because you want to install adb fastboot first. In summary... After installing adb fastboot to the root of C drive on your pc, navigate to that adb folder in C drive, double click the cmd-here.exe. A cmd window will open. Then put the phone into fastboot mode and connect it to pc using the side port of the phone. Type and run the cmd 'fastboot devices' on that cmd window. If successful in recognising your phone it will show a serial number/device id. Then do steps 1 and 2
Click to expand...
Click to collapse
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated

Fathi Moh. said:
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated
Click to expand...
Click to collapse
Glad you got it working again! ?

Fathi Moh. said:
Thanks a lot, you are the One
You made my day on
I am happy to get back my Rog phone 2 to life
Really, I am so glad for you
It’s works 1000000%
Thanks again for your big support I am really appreciated
Click to expand...
Click to collapse
Oh, and well done, I forgot to give you the link to my thread!

Question Occasional Silent Mode problem

Every now and then I miss an incoming call because my Zenfone 8 has mysteriously switched itself into vibrate only or silent mode.
The only way I can see for it to do this by itself is the power button has to be pressed to access the lock screen, then a volume up or down button has to be pressed to reveal the volume slider, then a tap the ringtone icon (at the top of the volume slider) will switch to vibrate only mode, or two taps will select silent mode.
All of this would have to happen while it's in my pocket, even though pocket mode is enabled!
Any ideas how I can prevent this sporadic silent mode problem?

Try turning face recognition off.

landsome said:
Try turning face recognition off.
Click to expand...
Click to collapse
Thanks for your suggestion, but Face Recognition is not enabled - I use a pin code lock. I have enabled Smart Screen in the Display section (screen stays on longer if a face is detected) but the problem happens even when the phone has been in my pocket for some time....

Sorry, in my case it disappeared. Are you on Android 12? If not, maybe try it.

Thanks. Still waiting for Android 12 OTA....

Tom100% said:
Thanks. Still waiting for Android 12 OTA....
Click to expand...
Click to collapse
Why? For me it solved a dozen problems, battery chief among them.

Tom100% said:
Thanks. Still waiting for Android 12 OTA....
Click to expand...
Click to collapse
If you are on the latest android 11 build, you can simply download the latest Android 12 firmware file from the zenfone 8 support page (Bios download section) and then drag the zip file at the root of the phones storage (with the Downloads , Pictures, etc. folders). After that is done, simply reboot the phone wait a minute or two and it will ask you to start the update process. Just tap the notification and it should start

Adaoh said:
If you are on the latest android 11 build, you can simply download the latest Android 12 firmware file from the zenfone 8 support page (Bios download section) and then drag the zip file at the root of the phones storage (with the Downloads , Pictures, etc. folders). After that is done, simply reboot the phone wait a minute or two and it will ask you to start the update process. Just tap the notification and it should start
Click to expand...
Click to collapse
Thanks for your help. I was waiting for the OTA in case I messed things up - but now will have a go. Thanks.

Tom100% said:
Thanks for your help. I was waiting for the OTA in case I messed things up - but now will have a go. Thanks.
Click to expand...
Click to collapse
Could you please post a link to the firmware file that I can download to my phone and simply reboot to start the update - this sound so much simpler than all the other references I've found to much more technical procedures for manually updating to Android 12. Thanks.

Tom100% said:
Could you please post a link to the firmware file that I can download to my phone and simply reboot to start the update - this sound so much simpler than all the other references I've found to much more technical procedures for manually updating to Android 12. Thanks.
Click to expand...
Click to collapse
Yeah here you go, (latest direct download from Asus) you can do it all from the phone without a computer, just move the zip file out of the downloads folder to the Internal storage option (root directory).

Thanks again, Much appreciated!