Camera focus working ONLY after a factory reset/firmware repair! - Xperia Z4/Z3+ Q&A, Help & Troubleshooting

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?

Related

Fingerprint Sensor Replaced, how to re-calibrate?

My p10 was just got back from warranty claim for broken screen. When i turn it on, there was this menu asking to recalibrate fingerprint sensor because the sensor was just replaced (not inputting new fingerprint). It was unclear how i should do it at first, however after few attempts it was supposedly asking me to rotate the phone while the finger resting on top of the sensor.
Too bad, i think my first few failed attempts may have miscalibrated the whole sensor.
Anyone knows how to get back into that menu?
Allesa said:
My p10 was just got back from warranty claim for broken screen. When i turn it on, there was this menu asking to recalibrate fingerprint sensor because the sensor was just replaced (not inputting new fingerprint). It was unclear how i should do it at first, however after few attempts it was supposedly asking me to rotate the phone while the finger resting on top of the sensor.
Too bad, i think my first few failed attempts may have miscalibrated the whole sensor.
Anyone knows how to get back into that menu?
Click to expand...
Click to collapse
Remove the fingerprint in Settings and add a new one.
Sent from my LON-L29 using XDA Labs
Mostar088 said:
Remove the fingerprint in Settings and add a new one.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
that was the first thing i did.
well it is solved now. Solution is to re-flash full firmware. Factory reset wont do.
how did u reflashed it .. bcz I tried volume down+up+lock method but always it fails to updata
Allesa said:
that was the first thing i did.
well it is solved now. Solution is to re-flash full firmware. Factory reset wont do.
Click to expand...
Click to collapse
can u plz tell me how u reflashed it... bcz I have the same problem but my firmware always fails installing at 5%
kanishka1234 said:
can u plz tell me how u reflashed it... bcz I have the same problem but my firmware always fails installing at 5%
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page58
I replaced a broken display on a P10 VTR-L29 and the fingerprint button is not working, everything else is. At first I though the display is faulty, but now I have doubts since the fingerprint option on the menu is just not there. I re-flashed the same version of the firmware (B369) via TWRP and the problem persists. I may have to try a factory reset.
sky|ined said:
I replaced a broken display on a P10 VTR-L29 and the fingerprint button is not working, everything else is. At first I though the display is faulty, but now I have doubts since the fingerprint option on the menu is just not there. I re-flashed the same version of the firmware (B369) via TWRP and the problem persists. I may have to try a factory reset.
Click to expand...
Click to collapse
Fingerprint is not accidentally paired with PCB like in iPhone?
is there any solution for now? cause i cant unlock the bootloader any more
StarSix01 said:
is there any solution for now? cause i cant unlock the bootloader any more
Click to expand...
Click to collapse
So this is how it ends when noobs messing with phones they don´t understand.
-You can unlock bootloader by paying some bucks to DC phoenix.
When you have no fgingerprint sensor options enabled it points that:
- the fingerprint sensor is broken
- the fingerprint sensor is not conected right
Hi alll
I had the same problem after replacing my screen.
I used Quick tuneup, and since the fingerprint sensor work correctly.
DallasCZ said:
So this is how it ends when noobs messing with phones they don´t understand.
-You can unlock bootloader by paying some bucks to DC phoenix.
When you have no fgingerprint sensor options enabled it points that:
- the fingerprint sensor is broken
- the fingerprint sensor is not conected right
Click to expand...
Click to collapse
Who are You to call me a noob??
Ive got the phone from a friend and just asked for help.
Did i say, that there is no Option for fingerprint? NO there is one
StarSix01 said:
Who are You to call me a noob?
Ive got the phone from a friend and just asked for help.
Did i say, that there is no Option for fingerprint? NO there is one
Click to expand...
Click to collapse
Sorry bro, my fault, i thought you are the one who asked before you.
You didnt say anything about your problem just asked if there is a solution and that you cannot unlock bootloader. With this info no one is able to help you. But anyway:
1. method:
-Remove existing fingerprints
-do a factory reset
-add a new fingerprint (when finger not scaned properly try to push a little bit harder on the sensor and rotate the finger)
-After the new fingeprint is scaned it should work well
2. method:
-after you recieve OTA notification (every month) go to settings/system updates/ there are three dots in upper right corner and select "get the whole latest package". This will download the whole firmware and perform a factory reset low level and this should work (if simple factry reset didnt work for you).
if this methods don´t work i will suggest you to go to phone service.
DallasCZ said:
Sorry bro, my fault, i thought you are the one who asked before you.
You didnt say anything about your problem just asked if there is a solution and that you cannot unlock bootloader. With this info no one is able to help you. But anyway:
1. method:
-Remove existing fingerprints
-do a factory reset
-add a new fingerprint (when finger not scaned properly try to push a little bit harder on the sensor and rotate the finger)
-After the new fingeprint is scaned it should work well
2. method:
-after you recieve OTA notification (every month) go to settings/system updates/ there are three dots in upper right corner and select "get the whole latest package". This will download the whole firmware and perform a factory reset low level and this should work (if simple factry reset didnt work for you).
if this methods don´t work i will suggest you to go to phone service.
Click to expand...
Click to collapse
No problem Bro
I managed to download a filmware package with the filmware Finder (somehow it worked) do i have to use the dload method now?
spoolerbloque said:
Hi alll
I had the same problem after replacing my screen.
I used Quick tuneup, and since the fingerprint sensor work correctly.
Click to expand...
Click to collapse
thank you very very much its work for me

Mate 10 ALP-L09 front camera issues?

Hi there everyone, long story short, I have a unlocked/rooted Mate 10 yesterday I realize that the front camera bokeh feature completely broke my photos, they just keep "loading..." and in the gallery the pic is just a broken gray square... Anyone is having the same issue?
Will appreciate any help!
I've already tried:
Reset default settings
Phone factory reset
Thanks!
cause you rooted , need reset setting then reboot
hoangtu2410 said:
cause you rooted , need reset setting then reboot
Click to expand...
Click to collapse
Hi there, do you know how can I do that? any quick guide or steps?
I've tried to but I almost get bricked because of the oem relock
Thanks!
lavosgo said:
Hi there, do you know how can I do that? any quick guide or steps?
I've tried to but I almost get bricked because of the oem relock
Thanks!
Click to expand...
Click to collapse
systems > reset > reset all settings then reboot the phone , do not turn on artistic bokeh mode again
or you can upgrade fw to disable root . I found out that i dont really need root anymore
hoangtu2410 said:
systems > reset > reset all settings then reboot the phone , do not turn on artistic bokeh mode again
or you can upgrade fw to disable root . I found out that i dont really need root anymore
Click to expand...
Click to collapse
You should be able to just flash back stock RAMDISK.
Hello, I have the same issue, front cam just says loading when picture is taken. I am rooted as well. Were you able to resolve this?
I am on Mate 10 Pro
me too
yup me too, but with rear camera. Think .jpeg files are corrupted. Bought phone new from Vodafone 2 weeks ago. Not rooted. Did x2 full hard resets and it recurred. Vodafone did a "like for like" replacement on assumption it was due to faulty internal memory. (Its seems like the sort of thing that would happen if there was an SD care and the SD card was kaput). Hope prob doesnt come back. If does then suggests it wasnt a handset / hardware problem for me but rather a more general software issue ...

Face unlock trouble on a fresh android 11 install

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

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

			
				
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容?
您可能需要卸载它们并重新安装,看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题,或者这根本无法解决问题,请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题,无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

			
				
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.

How To Guide x70 Pro Plus Origin OS to FunTouch 36.9.3

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 ?

Categories

Resources