Develop Bugs

[FIX] FED-Patcher v7 (ForceEncrypt Disable Patcher)

Hello everybody,
I created a tool for the nexus 9 that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 9 (aka flounder) it's the CPU's task. Even though the nexus 9's CPU has 2 pretty fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 9)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.

Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.

itlnstln said:
Thanks for creating this! In theory, would this work for the Nexus 6 as well? It would seem like it's a similar process.
Click to expand...
Click to collapse
Hey there,
yes, it would probably work because the process itself is pretty generic. The only real difference between devices is the device-path for the boot-partition as well as the path(s) for the fstab-file(s) inside the boot.img. Nothing that cannot be done - but I don't have a device for testing. If you feel adventurous I can do a nexus6 (shamu) version for you for testing. I will double check so it should not eff up your device .
EDIT: Not to forget, the nexus 9 is a 64bit device. mkbootimg as well as unmkbootimg are compiled for 64bit. I have to rebuild those two programs for 32bit to make them work for 32bit devices.

If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.

itlnstln said:
If you have time for a N6 build, that would be great. If not, it's not a big deal since there seems to be more support for that device.
Click to expand...
Click to collapse
Well, it's pretty much done. Do you want to test a version that does not actually flash anything but do everything else - just to see if it works correctly?

Absolutely!

itlnstln said:
Absolutely!
Click to expand...
Click to collapse
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!

gladiac said:
Alright, here you go!
If no error occurs there will be the already modified boot.img file in your temp-directory of your nexus 6. You can send me this file to be completely sure that everything went according to plan. Here is the adb-command:
Code:
adb pull /tmp/fed_patcher/boot-new.img
If all goes well I will upload the new version with nexus 6 (shamu) support tomorrow.
Good night!
Click to expand...
Click to collapse
Thanks! It seemed to work OK. Here's the boot image.

itlnstln said:
Thanks! It seemed to work OK. Here's the boot image.
Click to expand...
Click to collapse
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy

gladiac said:
Thanks for your help! I just updated the flashable ZIP in the first post. Enjoy
Click to expand...
Click to collapse
You're the best! Thanks!

I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9

madbat99 said:
I noticed in op it says "4 pretty fast cores". This puppy only has 2 cores. Just throwing it out there for readers that don't know. I'm sure it was just a minor oversight.
Sent from my Nexus 9
Click to expand...
Click to collapse
Hi,
you are right, thanks. I just fixed the text in the op.

Hey everybody,
I will enable support for the Nexus 9 LTE (flounder_lte) this afternoon in FED-Pather v3. If you want other devices to be supported please tell me. Is there a list of android devices that have forced encryption?

So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?

femmyade2001 said:
So this works great, leaving device unencrypted. But anyone having issues with apps crashing? Most especially Google Play Services?
Click to expand...
Click to collapse
This problem is new to me. My patch only modifies the boot-image so that it does not enforce encryption. It is merely a flag in fstab that gets changed and should not have anything to do with crashing apps. Anyway, do you have a logcat?

Hey everybody,
v3 is here with HTC Nexus 9 LTE (flounder_lte) support!
Enjoy

I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi, sorry to hear that. I will have a look into the boot.img that gets shipped with LMY48M. Not sure what is going on here.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Alright - unmkbootimg fails because the boot.img that google ships has 256 Bytes of extra data (it is probably signed or something) at the beginning. If you strip that off it works correctly:
Code:
dd if=boot.img of=boot-stripped.img bs=256 skip=1
Well, this was unexpected. But nothing that cannot be dealt with. I will make my flashable ZIP search for the offset of the boot.img-signature inside the dumped boot.img and strip of the preceding data. The rest of the process should work as usual.

itlnstln said:
I'm getting an error with my N9 (WiFi). When I try flashing in TWRP, it throws this error:
! Unpacking failed
=> unmkbootimg return value: 0
E: Error executing updater binary in zip...
All I did was go into fastboot, flash the updated image for LMY48M, then go into TWRP to flash the fix. I even went back into fastboot to try re-flashing the boot.img.
Click to expand...
Click to collapse
Hi @itlnstln,
I just made a new version which should do the trick. I tested the new functionality to the best of my knowledge. If the script fails for some reason it wont flash anything - so the probability for actual damage is very low. Do you feel adventurous xD?
Please tell me if it worked for you or not.

{LineageOS 14.1} Update failing

I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian

bwgreen9 said:
I am running lineageos-nightly-20170706 on my OnePlus 3 - I've tried to update it using both lineageos-nightly-20170803 and lineageos-nightly-20170810 - both give the same error when TWRP tries to install the file:
assert failed: op3.verify_modem('2017-06-27 21:43:31== "1"
updater process ended with ERROR: 7
Error installing zip file '/data/data/org.lineageos.updater/app_updates/lineage-14.1-20170810-nightly-oneplus3-signed.zip'
I did a full wipe and flash installing this, but I don't want to lose all the config work I've done if I don't have to - so I wanted to try updating this time. Am I doing something wrong or missing something? I download it, then choose Install - it reboots the pphone to TWRP (3.0.4-1), I click Install, then Up a Level so I can find the file in /data/data/org.lineagos.updater/app_updates, select the zip file, and swipe to install it.
Thanks,
Brian
Click to expand...
Click to collapse
Firmware...

I am not an android expert - what do I need, and how do I apply it?

bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
Well, your firmware is outdated, you need to update it.
This should help you out:
http://lmgtfy.com/?iie=1&q=Oneplus+3+modem+firmware+xda

bwgreen9 said:
I am not an android expert - what do I need, and how do I apply it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628
I flashed this one in recovery 4.1.6 Firmware + Modem, and then i flashed the full zip of the lineage update.

Question How to install gapps after installing GSI rom?

I have installed Lineage 18.1 GSI and trying to install gapps. I have rooted and using franko to flash opengapps pico and get an error 70 that there is not enough space on /system. What is the way to get this done? Thanks in advance!

I would like to know that as well.
Tried to flash via stock recovery but that aborted because signature verification failed.
Apps like Flashify, Flash Gordon, Flashfire or Rashr didn't work either.
With MagiskGapps-basic-module from wacko1805 the playservice framework always crashed.
I think the easiest and best way would be to flash opengapps via TWRP.
@ada12 seems to have a TWRP build that still has some bugs, but can be used to flash unsigned zip files.
Maybe he can share this with us.

I feel like this should not be a collasal effort, but it has become one. I have spent the whole day trying to figure it out. I want to use Lineage OS 18.1 with gapps from Andyyan, not any other rom.

psychofaktory said:
I think the easiest and best way would be to flash opengapps via TWRP.
Click to expand...
Click to collapse
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.

Thanks @wirespot
The hint with the linked script to create a custom Magisk module on the preferred OpenGapps bundle was worth gold!

Now I have another problem that comes from installing the OpenGapps via Magisk.
For passing SafetyNet I have to add com.google.android.gms and com.google.android.gms.unstable to the deny list.
But when restarting Magisk all modules are reloaded. So also the OpenGapps module.
As a result, the adjustments to the deny list for the Google Play services are discarded again with every restart and the SafetyNet check fails.
How can I prevent that the two entries are no longer removed from the deny list?
Or how can I ensure that the entries are automatically added to the deny list on restart?
Edit:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?

wirespot said:
I suspect that Magisk should be able to do whatever TWRP is doing (which is just putting some files in certain places, for the most part). Have you tried to find a Magisk module with OpenGapps? Or you can try making your own (but be warned that lzip is not available by default on any Android or Linux).
Edit: nevermind, I see you found a LiteGapps Magisk module.
Click to expand...
Click to collapse
Yes, but there is an issue with litegapps, the google contacts sync is broken unfortunately...

psychofaktory said:
It seems that this is what Magisk intended and com.google.android.gms and ...gms.unstable are automatically added to the deny list.
But now I have the question, how can I pass the SafetyNet test?
Click to expand...
Click to collapse
The deny list only lets you pass Basic check. To also pass CTS you need the USNF module (Universal SafetyNet Fix) and possibly other modules too. More details in this thread (check the end of the post), but try with just deny list and USNF first.

Neither the basic integrity check, nor cts profile match are passed.
Besides the denial list, I tried the modules "Shamiko", "Universal SafetyNet Fix" and "MagiskHide Props Config".
With the latter I have also tried various combinations, unfortunately unsuccessful in each case.
It looks like the deny-list does not work.
I suspect here also a connection with the message together that Magisk displays with each call:
Code:
An "su" command that does no belong to Magisk is detected. Please remove the other unsupported su
I have already been able to disable Phh-su with these commands:
Code:
adb shell
phh-su
mount -o remount,rw /
mount -o remount,rw /system
remount
mount -o remount,rw /
mount -o remount,rw /system
/system/bin/phh-securize.sh system.img
But the message in Magisk still appears.

Yeah passing SafetyNet with a custom ROM may be tricky. Didgeridoohan has a few more tips on their website you can try.

OK, I am already a big step closer to the solution.
After installing Magisk regularly, I first installed the Franco Kernel Manager.
Through this I was then able to flash UnSu.zip, which completely removed phh-su.
This also removed the message "An "su" command that does no belong to Magisk is detected" from Magisk.
Magisk had to be set up again afterwards, since it was also cleaned up by the UnSu script.
YASNAC now already showed "Basic integrity -> Pass".
But now I have not found a way to pass the CTS-profile match.
Does anyone here know what settings to set via MagiskHideProps Config?
And could someone send me the fingerprint of the stock rom (62.0.A.9.11)?
Code:
getprop ro.build.fingerprint

After some tests I discovered a big disadvantage with the variant to flash OpenGapps via Magisk.
Push notifications do not seem to work.
I use too many services that rely on Google Push notifications, so I can't do without them.
Compared to the "normal" variant of flashing OpenGapps via recovery before the first boot, the Magisk variant seems to be missing important dependencies and permissions that are only set during the first boot of the rom.
Therefore, the only useful variant is to flash GApps via recovery.
I really hope that we will soon have the possibility to flash unsigned zip files here!

Another approach:
Opengapps-zip files cannot be flashed via the stock recovery because it fails signature verfication.
The GSI roms can be flashed via the stock recovery. So they seem to be signed correctly.
Would it be possible to sign the Opengapps-Zip files with the same signature keys as the GSI-Roms to be able to flash them via the stock recovery?

Aren't GSI ROMs flashed through fastboot? Since they're partition images not zip installers like OpenGapps.

Of course. You are right.

Would it be possible to merge a GAPPS zip file into a GSI image and then flash the image with fastboot?

Question Trying to install APK from APKMirror, getting "The parser did not find any certificates in the .apk"

Hi everyone,
I'm using LineageOS with a OnePlus 9 Pro.
I'm trying to install the OnePlus camera app downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/
When I try to install it with the built-in installer, it just says "App not installed."
If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"
What is the reason for this, or how can I fix this?
Thanks!

Is that. Apk file?

Hi @warangekar!
Yep, it's an .apk file downloaded from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-6-2-117-android-apk-download/, it's com.oneplus.camera_6.2.117-26211918_minAPI29(arm64-v8a)(nodpi)_apkmirror.com.apk
(This is the version for which the Notes say "Extracted from OnePlus 9 Pro", that's why I chose this one. But afterwards I tried a couple more different versions of the same app, and I got the same error message for all of them when tried to install.)

It's extension is exactly. apk something like .xapk, .apks

@warangekar It's exactly .apk

Download Mirror Apk installer and try to install it with it

@warangekar I did, as I wrote in my first message:
>If I try installing it with the APKMirror installer, it displays the error message "The parser did not find any certificates in the .apk"

May be that Apk file is corrupt

If that file is not corrupted then you should try following,
This error is thrown by adb when we use it to install the application on a device/emulator. There are a few things you can try to isolate and resolve the issue.
Try on a different device/emulator. If this works, it is most probably an issue with the device configuration - check that USB debugging is enabled in Developer options.
Try killing the adb process. The CLI will start a fresh one on the next run.
Try to cleanup the configuration and artifacts directories - rm -rf node_module hooks platforms. Then run the application again.
Try installing Android SDK Tools version 28.0.3 and Android SDK 28
If the issue persists, you can run the project with tns run android --log trace > out.txt command and send us the out.txt file that will contain the full output log of the NativeScript CLI.

As the page says :
- "Note: Sideloading this APK may not work, so you may need root to install. Click here for more info.
For some reason, some manufacturers sometimes forget to sign some system APKs with APK Signature Scheme v2, while indicating that these APKs are indeed v2-signed. These APKs are usually signed with only APK Signature Scheme v1 (jar signature), so we can still confirm the signature is valid, but Android will refuse to sideload them due to the missing v2 signature."
So most probably signing it will do the trick.
I signed it with a debug key, see if it work.
EDIT: tested and working on android 11

Okay

You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.

ekin_strops said:
You can't install the APK on non-OOS ROMs. It needs to be ported (modified) in order to work on non-stock ROMs. And no, there is no ported version of it.
Click to expand...
Click to collapse
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core

Oneplus# said:
What? Is not true at all, I tried this apk and I've successfully installed it on a Samsung....android 11 stock wiith one ui core
Click to expand...
Click to collapse
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm

ekin_strops said:
I'm talking about OnePlus phones, try checking next time in what Sub-Forum you're in.
Oh, wait, and it must be fun having a non-functional camera installed into your phone. khm khm
Click to expand...
Click to collapse
- First, he have a one plus 9 pro and lineage.
- Second your answer say that it can't be installed on non oos-rom ... so not right.
- Third Maybe will be not good, maybe on some phone will crash but the apk definitely install itself because it was only missing a signature.
- And last I'm not using it, I've installed only to be sure that the apk install itself.
So "You can't install the APK on non-OOS ROMs." Is not right, it can be installed.

Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

Hello,
After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.
Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working
- because of lzgmc's and JayanthKandula's hard work, needed changes were reduced to minimum
Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
Changelog:
05.2023
- small kernel updates
- small performance and ui tweaks
04.2023
- use updated drivers from the most recent version of MIUI Global 14.0.4.0
- use current 4.19 kernel instead of old one
- performance and ui tweaks
Images:
PE - Alioth - Google Drive
drive.google.com
Sources:
https://gitlab.com/lukasz1992-pe/
Instruction:
- you have to flash 05.2023 full image first, if you were on different image
For every next incremental update:
- allow system to boot after flashing
- then reboot to recovery
- flash incremental update
FAQ:
Q: Do you have the device?
A: Yes, I use my ROM on my device
Q: How to report bugs?
A: Write about them here
Q: I do not trust your builds
A: No problem, build image yourself from source or just do not use this rom
Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.
Q: Why automatic updates are not working?
A: Because alioth is not officially supported, I support it unoficially. Maybe I add updates to my repo.
Q: Why do you publish incremental updates
A: They take less space on my Google Drive and are easier to flash
Q: I want to install 05.2023 (and newer) images directly
A: Flash 04.2023 version first, then install incremental updates one by one (as described in description above)
Q: Incremental update does not work
A: Make sure you are on the correct image, follow the order and allow to boot system after each flash (do not try to flash >1 image without reboot)
Q: Is this a vendor-boot ROM?
A: No
Q: Is there any guarantee?
A: xD

You accidentally used the Question-tag for this thread

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:
Code:
Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.
Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?

lukasz_m said:
Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?
Please also confirm you do not have magisk etc.?
Click to expand...
Click to collapse
Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh
I also don't have magisk or anything like that installed.

[DELETED]

Okay, released a new, fixed update - I tested it, it should work

I flashed the new update and its been working fine, thanks for you work!

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

lukasz_m said:
Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.
Click to expand...
Click to collapse
Ah great, thought I was asking a stupid question
Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

Update - 2023.05 image was reuploaded

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?
And thx for keeping this device updated, really appreciate what you're doing here.

hi, yes - you can do it

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance
My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL
Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
reboot to recovery and try again

lukasz_m said:
mount /dev/block/by-name/metadata /metadata
rm -rf /metadata/ota*
Click to expand...
Click to collapse
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.

ciottaciotta said:
Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.
I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device
Than what I have to do ?
thanks in advance for your time.
Click to expand...
Click to collapse
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

blonderulez said:
First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above
Click to expand...
Click to collapse
OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"
When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

Does this work?
Code:
mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*