Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
baleskoil said:
Hi ,
i just flashed the factory image for android 11 with full wipe ( was on last beta ).
My phone refuses to complete the face unlock configuration. Telling me that it can't add new face data and that i should remove one before retrying...
i'm rooted and i already tryed a magisk module supposed to fix face unlock but no luck
help please ? ^^
Click to expand...
Click to collapse
Did you find a solution?
Nope
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
baleskoil said:
I found someone with the same problem here :
https://support.google.com/pixelphone/thread/24855830?hl=en
Any Idea how i Can try to reproduce the same effect without having to lock/unlock my bootloader ?
Click to expand...
Click to collapse
As of right now me and you are the only two that seem to have this issue.when I get home from work I'm going to go ahead and I'm actually going to relock my bootloader and and do everything and then I'm going to unlock it and see what happens.I can let you know in this thread if it works for me and that way you don't have to waste your time unlocking and relocking
Yes please
i would say lock and unlock again and just install everything again
baleskoil said:
Yes please
Click to expand...
Click to collapse
So i locked the bootloader ,then unlocked it and did a fresh install of 11 and i have face unlock back
Good .
I need to reflash the Factory image before relocking right ?
To be safe
baleskoil said:
Good .
I need to reflash the Factory image before relocking right ?
To be safe
Click to expand...
Click to collapse
I locked the bootloader then rebooted back into the boot loader and unlocked it and then flashed
Works for me too.
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
neo_lithic3K said:
In past issues with face unlock, the fix was to perform a factory reset (Settings - System - Reset options - Erase all data) before flashing a new rom. Supposedly the chip that face data is stored is not cleared until you do a factory reset. Unsure if a full wipe clears the chip. You can try this next time ... may be easier than doing a bootloader lock/unlock.
Click to expand...
Click to collapse
I tried that and it's a no go. Looks like bootloader is the way for now.
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
seipersei said:
Hi, My face unlock is also messed up after updating to Android 11 (it keeps saying “fit face into frame” without letting me register my ugly face...)
Did you encounter the problem after rooting? I’m trying to figure out how to solve this, as I had no success with factory reset or flashing OTAs and factory images
Click to expand...
Click to collapse
I had the exact same problem as you. face unlock became unreliable after the Android 11 upgrade, so I deleted face data and tried to set up again. It keeps saying 'fit face into frame' no matter the angle or the lighting. Did a factory reset and no improvement. I have never rooted or unlocked the bootloader on this phone. I informed google support and they are sending me a replacement.
Just to share an experience with the community: After android 11 update I was having glitches with face unlock. (Totally stock, no root & all latest ota) This got worse until it wouldn't work at all. Deleting face & starting over didn't work as it just refused to even acknowledge trying to register anything. Then the auto brightness starting flicking up and down and finally half the screen disappeared under green flickering. A factory hard reset made no difference. I even did it twice but the welcome screen on rebooting was still covered in green flickering. Searching for a new phone reluctantly. I picked up my pixel 4xl again to see if I could think of a way of selling it for any purpose & it was fine! Set up & reinstalled a backup & everything including face unlock works perfectly like new. What was all that about!?
Can you describe full algorithm for noob, please?
Stiil don`t working
fezzy102 said:
I tried that and it's a no go. Looks like bootloader is the way for now.
Click to expand...
Click to collapse
I've done relocking bootloader, but it didn`t help, face unlock still not working, OC is stock, latest.
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
kingkong0821 said:
I dunno what's the situation of you guys
But let me share my experience
I was having lock screen lags in Android 11
So I flashed the previous Android 10 image
It broke the face unlock and still broken even after flashing the full Android 11 image with wipe
What I did was flashing back to Android 10 again
Then update to Android 11 through OTA
This also was the method in r beta to fix face unlock issues
Click to expand...
Click to collapse
This is a known problem, and so far Google has not fixed it. Unsure if they ever will.
Sent from my Pixel 4 XL using Tapatalk
Related
Hi guys,
First of all, sorry for my really bad use of the English language;
Second: I recently switched from a Nexus 6P to an E6553 (because...reasons), and I'm really feeling home with my new smartphone.
The only thing is driving me crazy is...the camera focus.
What's the problem? Simple: it doesn't work, I'm sure it's a software problem and I'll let you know why I think this.
Just after the Setup Wizard, the camera works, and works really really well (it shots awesome pics!). Focuses even little objects such as insects, without the littlest issue. An example is the first attachment: I shot that pic just after a factory reset.
But the problem comes when I restore my apps, my photos and then reboot the phone. Then, the focus literally DIES. No way to get it working, it just stucks. End.
The only way to get it working is...formatting the phone another time and then never reboot it again!
I tried a factory reset from setting, a software repair via Xperia Companion, I even tried to refash the stock ROM through Flashtool (which...simply stucks at "Writing data", and the only thing I can do is repairing the software with XC).
Nothing to do: the camera works flawlessly after a reset/repair/flash, but after a reboot it becomes unusable.
And focus isn't the only problem (as it was a little one ????) : opening the Video Mode in camera makes the device freeze, meanwhile using third party apps for the camera makes me see an huge amount of glitches. The strange thing is that everything works without issues until a reboot, so it's certainly a software bug, but I don't know related to what. And no, it's not an app or something I installed: focus doesn't works even when booting in Safe Mode or creating a new user from settings.
And no again, bootloader is not unlocked, it isn't even unlockable, so no DRM Keys fault.
What you suggest me to do? I really love that phone, but using it with this camera is just impossible.
Uh, last details: I'm on the latest firmware, 32.1.A.1.185, Customised IT (Italy). I tried to flash another firmware (CE1) but as I said before, it stucks on "Writing data".
Thanks in advance.
Today I'm going to send it in warranty for replace the camera. It will be back in a couple days, I'll let you know if the bug is solved.
I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.
Oveana said:
I have focus problem too.
E6533, .185
unlocked bootloader--->flashed rootable kernel--->TWRP--->root--->flashed drm
After all those steps bootloader is now locked. Everything works fine except rear camera focus.
Click to expand...
Click to collapse
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Thanks for your Solution. KEEP US UPDATED
ale29-09 said:
I managed to fix it! The bug doesn't appears if I skip the setup wizard and I log in my Google account in a second time. All is working well, and I performed a reset 3 days ago.
Yay!
Click to expand...
Click to collapse
Sorry, I did not understand what you did. Could you say that again with different words?
Oveana said:
Sorry, I did not understand what you did. Could you say that again with different words?
Click to expand...
Click to collapse
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.
ale29-09 said:
I skipped the setup wizard (initial configuration) at the startup after the factory reset, then I added my Google Account opening Play Store.
Click to expand...
Click to collapse
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.
Oveana said:
Thank you for your solution. But it did not work for me. Maybe because my situation is different from yours. I unlocked the bootloader.
Click to expand...
Click to collapse
Why you unlocked bootloader Man?
arokososoo said:
Why you unlocked bootloader Man?
Click to expand...
Click to collapse
For rooting
Oveana said:
For rooting
Click to expand...
Click to collapse
If you again lock bootloader+ Ta restore, then camera problem gonna stay as it is now I.e no focus?
Dear All,
I have a friend with Huawei P9 Plus with this Firmware VIE-L29C636B103, i don't know what is in his mind on that time but unfortunately after restarting the phone he forgot his PIN to unlocked the phone and the fingerprint was not working. As far as i know, the only solution is by Factory Reset the phone, but he did not want to loose his data. Is there any way to solve this problem?
Thank You
mardiatmo said:
Dear All,
I have a friend with Huawei P9 Plus with this Firmware VIE-L29C636B103, i don't know what is in his mind on that time but unfortunately after restarting the phone he forgot his PIN to unlocked the phone and the fingerprint was not working. As far as i know, the only solution is by Factory Reset the phone, but he did not want to loose his data. Is there any way to solve this problem?
Thank You
Click to expand...
Click to collapse
has his phone root and is there a custom recovery?
Fed2x said:
has his phone root and is there a custom recovery?
Click to expand...
Click to collapse
No still original without custom recovery. Can i use TWRP to backup first the data ?
The problem is that you not unlock and then root yet. You basically can't use TWRP. If unlock bootloader, the phone will be immediately wipe data.
mardiatmo said:
No still original without custom recovery. Can i use TWRP to backup first the data ?
Click to expand...
Click to collapse
mardiatmo said:
No still original without custom recovery. Can i use TWRP to backup first the data ?
Click to expand...
Click to collapse
He or you could've used it to delete ". key" -files through adb. But that is only useful to have access to the data. You can't set new fingerprints or delete any of them because he must know his forgotten password for it. So it would only be a temporary solution.
Unlocking the bootloader never erased my data. It couldn't cause of some failure appeared at let's say 30%. But I'm not certain that the failure appears also on his phone. Which leads to my suggested solution:
He should try to remember the password and include any typos(yes, typos. My pin was 85320 but it also happened that i typed two times the false pin. The outcome was 85350. Huawei's layout was kinda bull**** and vulnerable for that type of failures. At least to me.) As I know it must be a PIN, not a password. If that fails get rid of the data and make a factory reset.
Thank you all,
Today i connect the P9 Plus Phone USB to HiSuite in Windows 10, i just leave this around 5 minutes and suddenly it connected to HiSuite automatically. Now i'm still backing up the data pictures, etc. Still wondering why in windows 10 it can connected automatically than in windows 7 After backup finished i'm gonna factory reset the phone.
My mistake on comments on unlocking bootloader will erase date since I mixed up the process. Now I remembered that after unlock, if you proceed further to root the phone, the phone will have to erase the data immediately. No option for you to choose not to erase data during rooting process if not mistaken. That's why I dare not to root again the phone.
Fed2x said:
He or you could've used it to delete ". key" -files through adb. But that is only useful to have access to the data. You can't set new fingerprints or delete any of them because he must know his forgotten password for it. So it would only be a temporary solution.
Unlocking the bootloader never erased my data. It couldn't cause of some failure appeared at let's say 30%. But I'm not certain that the failure appears also on his phone. Which leads to my suggested solution:
He should try to remember the password and include any typos(yes, typos. My pin was 85320 but it also happened that i typed two times the false pin. The outcome was 85350. Huawei's layout was kinda bull**** and vulnerable for that type of failures. At least to me.) As I know it must be a PIN, not a password. If that fails get rid of the data and make a factory reset.
Click to expand...
Click to collapse
How to use adb ???
My Moto X4 XT1900-2 Fingerprint Sensor Not Working, Even It's Option is Missing From Setting, Anyone Having Same Issue ?????
Ritesh Mhatre said:
My Moto X4 XT1900-2 Fingerprint Sensor Not Working, Even It's Option is Missing From Setting, Anyone Having Same Issue ?????
Click to expand...
Click to collapse
Try factory reset
I do...but doesn't solved
Did you flash any ROM on it ? Maybe you tried to downgrade the device from Oreo ?
Today when I tried to find a solution to not installing OTA, I've flashed 7.1.1 as a downgrade. It failed, but after reboot my fingerprint sensor disappeared, too. Then after I reflashed Android 8 it appeared again.
emcom said:
Did you flash any ROM on it ? Maybe you tried to downgrade the device from Oreo ?
Today when I tried to find a solution to not installing OTA, I've flashed 7.1.1 as a downgrade. It failed, but after reboot my fingerprint sensor disappeared, too. Then after I reflashed Android 8 it appeared again.
Click to expand...
Click to collapse
It doesn't unlocked my bootloader ??????
Coz i doesn't want to void my warranty !!!!!
Ritesh Mhatre said:
It doesn't unlocked my bootloader ??????
Coz i doesn't want to void my warranty !!!!!
Click to expand...
Click to collapse
So, what were you doing with the phone ? Flashing it ? Any information ?
flashing will unlocked my bootloader or not ????
Can't you answer simple question ?
WHAT WERE YOU DOING WITH THE PHONE ?
Set a pin or password security and the option to unlock it with the fingerprint will appear again
MeltingSnowman said:
Set a pin or password security and the option to unlock it with the fingerprint will appear again
Click to expand...
Click to collapse
It doesn't appear
When you did a factory reset did you restore from backup afterwards or set it up as a new phone? If you set it up as a new phone and it still didn't work then I'd say you probably need to contact Motorola and ask about getting it repaired.
trwrt said:
When you did a factory reset did you restore from backup afterwards or set it up as a new phone? If you set it up as a new phone and it still didn't work then I'd say you probably need to contact Motorola and ask about getting it repaired.
Click to expand...
Click to collapse
Ohk..thank you
Bro i have the same problem
Yes i have same issue
Till yesterday fingerprint sensor was working absolutely fine, and then suddenly it stopped working, then after i tried restarting device but didn't solved. Anyone has the solution then please help me
+1, same problem
i do have the same problem, no fingerprint option in security and the senser is not reacting on anything.
had fingerprints registered and working, but after the first october update the problem occurs.
When i flash back to los 15.1 build from 2018-09-26 the fingerprint sensor works again, option to configure reapears and all already registered prints are there.
Karamelmar said:
i do have the same problem, no fingerprint option in security and the senser is not reacting on anything.
had fingerprints registered and working, but after the first october update the problem occurs.
When i flash back to los 15.1 build from 2018-09-26 the fingerprint sensor works again, option to configure reapears and all already registered prints are there.
Click to expand...
Click to collapse
Then you need to remove those fingerprints before flashing back to stock
bcrichster said:
Then you need to remove those fingerprints before flashing back to stock
Click to expand...
Click to collapse
My post was a little unclear, sorry. i am on los 15.1 and do have this issue on any build after 2018-09-26. i already opened up a regression on los jira bug/regression tracker (REGRESSION-2178), but since no one voted for it or seems to have this problem, i though it may be some step i took.
Anyway. in the meantime i tried to clear all fingerprints before flashing but it did not help
(i did not flash back to stock but to los)
I also did a complete factory reset, formatted data/ wiped everything and then did a fresh install of los 15.1 most recent build, but still got the problem.
I bet you still have a fingerprint file somewhere that needs removed..
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
I bet you still have a fingerprint file somewhere that needs removed..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
@bcrichster: Thanks for pointing me in the right direction...
i flashed back to los 15.1 (2018-09-26), removed the fingerprintes and pin, flashed to the most recent version of los 15.1 but it did not work.
flashed the build LOS 15.1 (2018-10-30), then the menu was there and the sensor works!
So my question: where are the fingerprint files on the x4 stored... read about fingerprints and searched on the device, but did not find them...
Is there a difference between Slot A/B regarding the fingerprints?
Thanks
I had the same issue when I first flashed RR room. Ended up flashing back to stock then going through the whole custom ROM setup again. Fixed the sensor and all the other little issues I was having (no headphone sound, etc). Not sure what the underlying issue was but for the sensor, left over files makes sense.
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.
koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems
Foreword: My time with Vivo has come to an end. After flashing a wrong devicecfg and accidentally rebooting my device it is now in a hard bricked state.
Vivo has locked down EDL, there is absolutely no way to flash or backup anything in EDL mode without the official Tools (namely Vivo AFTool 5.9.80).
Vivo India refers me to Vivo Germany - Vivo Germany has outsourced its customer support to bulgaria.
The people on the other side of the line know absolutely nothing about the technical aspect and refuse to put me through to anyone with any kind of knowhow.
Due to their anti consumer and anti repair attitudes I will not buy another Vivo phone.
With this out of the way: You might end up like me with a hard brick. Or without signal.
Even if this will not save you from a hard brick I can not stress this enough: Make a BACKUP! And backup your data. This will wipe your phone.
This process is IRREVERSIBLE unless you have a split ROM of the chinese Firmware or your own Backup.
THIS or BL UNLOCK will break your portrait mode. No more bokeh, neither in Origin OS nor FunTouch.
Do NOT flash fsg, modemst1 and modemst2. They are commented out in the COMMANDS file.
You do this at your own risk. As said before this might brick your device.
Unlock your Bootloader
Backup your Partitions
Download my Flash Folder and Extract it: Android File Host
Open 01COMMANDS.txt and read the instructions
Open a command shell in the same folder that you can find 01COMMANDS.txt in
Run the given commands in blocks or one after the other
If you do not have signal after flashing you might have to erase modemst1 and modemst2 partitions, so that they get replaced by the backup in fsg.
A magisk flashed boot.img and adb-modded recovery is included so you can flash it after booting up FunTouch once and backup all your partitions again.
Thanks again to @Pervokur for helping me along the way. There is definitely an easier method that involves less risky flash operations.
My phone died on the cross while I was trying to figure it out, so maybe someone else will pick up the torch.
I will not be able to offer any kind of support.
RIP @Killuminati91's Vivo, who died for the cause.
Sorry to hear that, man, you were so close to what looked like an easy switch between ROMs.
I know you said you were no developer but you are still a leap ahead of most of us here. Long do we miss the good old days where ROMs, kernels and pure innovation shortly followed our much-wanted phone when flashing a few ROMs a week was normal.
Thanks for all your help, perhaps one day there will be a way to recover your phone.
Many thanks, may I relock the bootloader when i finished change to Global rom?
amos0609 said:
Many thanks, may I relock the bootloader when i finished change to Global rom?
Click to expand...
Click to collapse
Same question
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
how did you relock the bootloader, does the portrait mode work again?
does any one change the origin os /ocean into funtouch?
version? how to relock after it can switch to funtouch?
by the way, I saw the post on the taiwan vivo phone of fb
the second hand goods, it wrote he change the origin os into funtouch
and he sell this service , it charge 2000 nt dollars in taiwan.
maybe someone can save your phone.
Killuminati91
I think the only problem that keeps the phone from being recognized as official FunTouch is dm-verity.
In theory both phone versions have the same exact hardware.
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
stevenkh168 said:
i'm fail in step 2 :RECREATE DYNAMIC PARTITIONS) & step 3 :FLASH DYNAMIC PARTITIONS)
Click to expand...
Click to collapse
Message?
silence360 said:
I thought you fixed your issue with I think wifi or your signal, and you were good to go, and you successfully swapped over to Funtouch?? Was there other issues that you encountered that you continued to mess with it and caused your phone to get bricked? Good job getting this far and sharing the info!
Click to expand...
Click to collapse
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Killuminati91 said:
Message?
I wanted to find a smoother solution for the dm-verity message and the constant "update to fix broken system prompts" by flash-disabling it. Noticed that portrait mode was not working anymore, so I wanted to return to OriginOS, check if it works and return to FunTouch with a more streamlined, simpler solution to write a guide. Signal was fixed but it sometimes would not connect for the first 10 minutes after a reboot.
When switching back to FunTouch I flashed boot, recovery, vendor_boot, and the vbmeta's while trying to figure out what exactly is needed to get the device recognized as IN. Was not working so I tried devcfg and accidentally rebooted before flashing more partitions. -> Bootloop without recovery / fastboot.
Click to expand...
Click to collapse
did you try using the OriginOS's camera app on FuntouchOS ? I find it when u use the front facing camera, the portrait mode still work. In the other hand, the back camera is not working in portrait mode. I follow your guide and using the FuntouchOS about 2 days. Everything works fine, except the portrait mode and the AOD. Cant use it anymore.
Oh I see, now that is weird that the portrait mode is not working. So even if you switch not all functionality has returned. Thanks for the explanation. Hopefully someone can continue your work, and find a solution for a seamless transition.
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
hope to see some good news from you sir.
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Killuminati91 said:
Yeah, returning to Origin did not fix portraits either, so flashing the cam apk itself wouldnt work. I am not sure what exactly is causing it, I just noticed it after flashing FunTouch. Maybe it is disabled by unlocking the BL or a hidden eFuse? Dont know if its possible to get it back.
Im in contact with someone in china, vivo service center remote flashing is my last straw to get this back to work but I doubt that they will do that. A cracked AFTool 5.9.80. would solve all of ours problems but we will not see that for at least half a year i think. I've been gone from android for a few years - all the hurdles surprised me, manufacturers locking down their bootloaders and EVEN edl is kinda disappointing.
Click to expand...
Click to collapse
Update us...
have you been able to solve it?
amos0609 said:
Great works I tried to relock and was successful, but the device Google Pay store CTS is not verified.
Click to expand...
Click to collapse
NHQ Thang said:
how did you relock the bootloader, does the portrait mode work again?
Click to expand...
Click to collapse
same question
adkana4310 said:
Update us...
have you been able to solve it?
Click to expand...
Click to collapse
If u asking me so no im still on the same cant flash
redwatch99 said:
hi i have som big problem with flashing x70 pro plus to funtouch , can some one help me with it ?
cant flash step 2 and 3
Click to expand...
Click to collapse
Someone who can help me solve it ?