Sadly it didn't work. First time it just got stuck after 'sending 'unlock' (5KB)' command. A few other tries using different USB 2.0 ports I got this again:
target didn't report max-download-size
sending 'unlock' (5 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
Looks like there is a newer TWRP avaialble for Z5S. Probably everyone knows about but I haven't seem it mentioned here so just in case someone has missed it:
Sure. TWRP 3.3.2b for Lenovo Z5S Android 10:Hi! I certainly didn't know about this. Can you mirror this somewhere please? Thanks
Are you sure you used the option "format data" in TWRP ? It should erase everything, and fix these kind of issues with security and encryption.So it doesn't look like it's specifically Havoc related. The fingerprint doesn't work on Lineage either. I must have flashed my phone like 20 times with different rom versions including full data wipes, dirty flashes, etc. The fingerprint only works on Pixel every time, no issues. It almost seems as if some security / data encryption settings are ROM independent, they are not being completely wiped when reinstalling the ROMs and are linked to the first ROM installed. It doesn't make much sense to me but cannot come up with any other explanation. Also when I dirty flashed Havoc over Pixel after setting my fingerprint there, I could still see the fingerprint set up in Havoc but it didn't work and I couldn't add another one.
And also I am being asked to input the password in TWRP every time on the start-up to encrypt the data. I am not sure what password it needs as the PIN setup inside the ROM doesn't work. Confused.
EDIT: I've just restored the stock ROM using TWRP (the scanner works perfectly here as expected), reinstalled TWRP as the recovery went back to stock, wiped everything, installed Havoc, Open Gapps and Magisk and after rebooting.... the fingerprint still doesn't work.
EDIT: Just installed some Android Testing Tool and when trying to test Fingerprint it gives me an error message saying "Your Android device does not have this feature, or this feature may be using by other apps". On another app (Device Info) it doesn't pass the hardware test. It doesn't even start it actually, as if the scanner wasn't present on the device.
Would you have any idea how to enable the scanner? Do you think flashing a stock ROM with Qfil and reinstalling everything from the scratch might solve the problem? I personally doubt it but since no one else is having issues with the fingerprint I thought it might work for some weird reason.
Yes, 100%. - format data, followed by wipe of dalvik, data, cache and system before IMG flash. Even tried format data, reboot recovery so it doesn't ask for the decryption password followed by wipe and install - no joy. Dirty install on top of Pixel was a no-go either. Installed fine but the fingerprint still wasn't working. Thought it might have worked since fingerprint is fine in Pixel.Are you sure you used the option "format data" in TWRP ? It should erase everything, and fix these kind of issues with security and encryption.
Tried to flash the latest stock using QFIL (probably won't make any difference but I thought I'd give it a go to make sure) but getting some error messages:Remarks :
- use the latest QFIL instead : https://qfiltool.com/qfil-tool-v2-0-2-3
- if it's still not working (FireHorse file not found, for example), install latest QPST https://qpsttool.com/qpst-tool-v2-7-480 and try again
- if your phone is not recognized in bootloader mode, follow this instructions https://forum.xda-developers.com/attachment.php?attachmentid=2480396&d=1388281089 (found here https://forum.xda-developers.com/showthread.php?t=2588979)
Some fixes :
Tried to flash the latest stock using QFIL (probably won't make any difference but I thought I'd give it a go to make sure) but getting some error messages:
2020-06-07 12:57:01.686 12:57:01: ERROR: function: sahara_rx_data:277 Unable to read packet header. Only read 0 bytes.
2020-06-07 12:57:01.688 12:57:01: ERROR: function: sahara_main:983 Sahara protocol error
2020-06-07 12:57:01.689 12:57:01: ERROR: function: main:320 Uploading Image using Sahara protocol failed
2020-06-07 12:57:01.691 Download Fail:Sahara Fail:QSaharaServer Failrocess fail
2020-06-07 12:57:01.693 Finish Download
Any ideas? Cheers.
Sure. TWRP 3.3.2b for Lenovo Z5S Android 10:
The link is for the compressed file that should have all the files included. I haven't tested it yet so proceed with caution. The original information can be found by clicking here. It's in Chinese so most likely you need to use Google Translate.
Do you know how to disable encryption on Havoc or Pixel? This seems to be missing from the settings on both. Cheers.
And still no matter what I cannot access my main encrypted data partition in TWRP since it's asking for a password but doesn't recognise the one set in the system (either in Havoc or Pixel). And I still can't find a way to disable the encryption altogether which I don't need anyway.
The same here. I've tried it with no luck. I was about to post that it doesn't work. It actually does say it's for Android 10. However since we are using Android 10 GSI ROMs I completely didn't register that it means the underlying OS.I usually just use the IMG file inside. However it's not usable with the current Android 9.0 based ZUI - probably this is for ZUI 11.5 based on Android 10 which is in closed beta. I tried flashing it and it just looped back to the bootloader/fastboot menu.
Thanks a lot! Will give it a go and see what happens.Theere is an option in the Advanced menu of wzsx's TWRP - "RM Forceencrypt". Have tried this on another phone with the same features, it should remove dm-verity and forced encryption. Haven't tried this on the Z5s though.
---------- Post added at 10:23 AM ---------- Previous post was at 10:02 AM ----------
In my experience, wzsx's TWRP doesn't play well with encryption. You can try @jacoghi's TWRP here (Thread).
Dang. I got the same error when trying to flash Lineage by jacoghi. Maybe my firmware being older than 11.1 is the reason I am having issues with the fingerprint sensor.You have a firmware older than 11.1 installed on your phone. You can remove that assert by unzipping the package, going to meta-inf, com, google, android and editing the updater script, just delete
assert(jd2019.verify_trustzone("TZ.XF.5.0.2-00076") == "1"); from it and rezip evertyhing.
Dang. I got the same error when trying to flash Lineage by jacoghi. Maybe my firmware being older than 11.1 is the reason I am having issues with the fingerprint sensor.
Looks like I should probably flash the latest stock ROM after all. I thought I could avoid that as knowing my luck I will end up bricking the phone. Well... If I can even get it flashed in the first place.
Thanks man. Understood. That makes sense. For some reason I thought that might be related. I remember when I was on my ZUK Z2 Pro we had to flash certain firmware version to have full radio support for example. Otherwise there were some issues. But those were not generic ROMs so I guess that's where the difference lies. It's still kinda weird that the fingerprint works in Pixel only not other ROMs (tested Havoc and Lineage).The fact you might have firmware older than 11.1 doesn't affect your fingerprint reader usage, that has to do with the services the rom is initializing since all of these system roms are generic. If you flash my rom or firmware older than 11.1 following that workaround, you won't notice any difference, that only affects drm which has to do with Netflix (but I later found out our device is not certified anyways, so I'll remove that in the future...). Keep in mind my rom is a full rom, so you cannot flash a generic system image on top of it (actually, I never tested doing so, it MIGHT work, lol) if you wanna change down the road, in that case you'll have to reflash a full stock image and then flash the generic system.
For some reason this version of Gcam crashes on my phone running Pixel GSI. Immediately after installation I got some "lib" error message when starting the app. Couldn't see exactly what it was as it would pop up for a split second and crash. After rebooting the error message is gone, the camera starts but crashes as soon as it loads. Is there any other working Gcam for the Z5S you could recommend?Camera App: Install Gcam_6.2.030_Advanced_V2.2.190716.1800-Final.apk from https://www.celsoazevedo.com/files/a...ev-arnova8G2/.
Using adb:0. Download the firmware files to your smartphone.
1. Enter the recovery menu. To do this, turn off the smartphone and simultaneously hold down the power button and volume +.
2. In the recovery menu, select the item Cleaning -> Selective cleaning. Check the boxes on Dalvik / ART Cache , System , Data and Cache . Swipe the slider to the right. Return to the main recovery menu.
3. In the main recovery menu, select Installation -> Install Img. Select firmware file XX.img. For system section firmware, select System Image, and for boot - Boot. Swipe the slider to the right. Go to the main recovery menu. Select Reboot -> System.
This procedure is new for all smartphones, so don't be afraid to ask questions if something went wrong.
0. Install the USB, ADB and Qualcomm drivers on the PC. Reboot the computer and connect the smartphone to the PC. Download files for firmware on PC.
1. In the folder where the files (.img) were saved, press SHIFT and the right mouse button from scratch. In the context menu, select PowerShell or CMD (activate command console).
2. Enter the commands one by one
fastboot flash system XX.img
fastboot erase userdata
PS In some cases, it will be necessary to flash vendor and / or boot:
fastboot flash vendor XX.img
fastboot flash boot XX.img