Related
Hello, I am trying to build an AOSP 6.0 ROM. I downloaded the source, built the image, flashed, with corresponding vendor image (MMB29P) and it boots. However, the BT doesn't work at all. Is there something I'm missing, I've tried different orders of flashing, different vendor images, etc. I thought the vendor image was supposed to reduce complexity, but I'm sort of stuck. Do I need to somehow "extract" the files from the vendor image and add them to the build structure, or something else? I appeal to the makers of many ROMs!
I have exact same problem. I have tried building AOSP MMB29V and MTC19T and tried booting with vendor images from corresponding factory binaries. Bluetooth just doesn't turn on if I use system.img built from AOSP. It works fine with system.img from factory binaries. This is with Nexus 5X.
If anyone has a solution or a suggestion, please reply...
_gps_ said:
I have exact same problem. I have tried building AOSP MMB29V and MTC19T and tried booting with vendor images from corresponding factory binaries. Bluetooth just doesn't turn on if I use system.img built from AOSP. It works fine with system.img from factory binaries. This is with Nexus 5X.
If anyone has a solution or a suggestion, please reply...
Click to expand...
Click to collapse
You need to add the proprietary vendor files to /system as well, just like on older Nexuses. I know Google claimed all non-free files are in /vendor, but that is actually not true at all.
jisoo said:
You need to add the proprietary vendor files to /system as well, just like on older Nexuses. I know Google claimed all non-free files are in /vendor, but that is actually not true at all.
Click to expand...
Click to collapse
Thanks for reply Jisoo
Can you please guide me which files to copy to AOSP build tree? Did you mean I need to copy files to /vendor during build, or to /system?
If you meant /vendor, till Lollipop, vendor images *nexus binaries* were copied to <aosp-root>/vendor. But there are no nexus binaries for Nexus 5X, that could be copied to /vendor (at least not on https://developers.google.com/android/nexus/drivers). Should I extract from vendor.img?
Or if you meant /system, please guide which files. any pointers would be helpful. I dont think this is mentioned on any aosp official sites.
_gps_ said:
Thanks for reply Jisoo
Can you please guide me which files to copy to AOSP build tree? Did you mean I need to copy files to /vendor during build, or to /system?
If you meant /vendor, till Lollipop, vendor images *nexus binaries* were copied to <aosp-root>/vendor. But there are no nexus binaries for Nexus 5X, that could be copied to /vendor (at least not on https://developers.google.com/android/nexus/drivers). Should I extract from vendor.img?
Or if you meant /system, please guide which files. any pointers would be helpful. I dont think this is mentioned on any aosp official sites.
Click to expand...
Click to collapse
So there's 2 locations for non-free files in the new Nexus devices.
1. /vendor partition, which you would typically update with the vendor.img images direct from Google
2. non-free files in the /system partition, very similar to what you had in the older Nexus devices (and what are used in all non-Nexus CM-devices, for instance)
You can get these files from a few repos on github, like TheMuppets or PureNexus. If you prefer to extract the files themselves from a factory image, it's still useful to check what should be included by looking at the makefiles in these repos.
You'll also need to add the non-free files to your device tree somehow. The easy way (by pulling the whole non-free repo and including the makefiles from there) would mean including the following line in your device tree makefile (using bullhead as an example):
Code:
+$(call inherit-product-if-exists, vendor/lge/bullhead/device-vendor.mk)
Hello,
Does anyonw understand how we should extract the driver files from this link:
https://developers.google.com/android/nexus/drivers
I see 2 links for each devices:
1. "google's vendor"
2. list of devices (camera, gps...)
Do we need to run the *.sh file for both ? Does the *.sh file will download all the required driver files ?
What are actually these driver files ? Is it the HAL .so files ?
Thank you,
Ranchu
Hello xda forums,
After a lot of experimentation I have been able to get TWRP working with /data decryption support (compatible with stock Sony ROM encryption) using LineageOS 14.1 sources. It is able to mount encrypted stock Sony ROM /data and install Magisk on it.
Credits / Special Thanks:
- LineageOS and @Quarx, @Olivier, @cdesai, Myself5, kali-, banmeifyouwant for android device ivy source tree (which I forked)
- @nailyk for help and ideas from effort on Sony Z3
- AndroPlus Kernel for providing ideas on things to try.
- @Captain_Throwback for help with hw crypto.
Warning:
Do not enable "Encrypt my phone" if you are running Magisk already on stock ROM! Encryption will hang because android will not be able to unmount /data to encrypt it and you will be forced to reboot and then you will be forced to wipe /data. If you plan to use Magisk, first uninstall it completely from recovery, THEN encrypt your phone, THEN install Magisk and whatever modules you want.
Developed on Sony E6533 (Z3+ Dual) but should work on both variants due to the efforts of @Quarx in unifying the device tree. Built from LineageOS 14.1 android ivy device tree.
How to install:
- Power off completely, then hold volume up key, then plug in USB to PC. If done correctly the front LED will light up BLUE.
- Make sure fastboot drivers are installed. If you have generic android drivers, you can install driver "Android bootloader interface" manually for the "S1Boot" entry in device manager on windows when phone is in fastboot mode.
- Download attachment and unzip it to get the img file.
- fastboot flash FOTAKernel recovery.img
How to enter:
- Power off completely.
- Hold volume down key, then push power also.
- Do not release volume down and power until sony logo appears.
- It will enter recovery flashed in FOTAKernel partition.
Help wanted:
- Testing all scenarios on encrypted /data such as backup / restore.
- Charging LED does not work (I don't know the changes needed to make it work in recovery).
Known issues:
- Battery charge indicator only updates once every minute but charging is working fine.
- Reboot to bootloader from within TWRP doesn't work (seems to be Sony bootloader issue, will remove in next build) (use power off, then hold vol. up + plug in usb instead).
- Reboot to recovery from within TWRP doesn't always work (sony bootloader issue, fixed by updating to sony nougat bootloader). (use power off, then hold vol. down + power until sony logo instead).
- "Hotbooting" (ie: fastboot boot recovery.img) this recovery does not work. Phone will hang on Sony logo and heat up and require hard power off using power off button inside side flap (or press Power + Vol Up + Vol Down simultaneously for 3 seconds).
Source:
Device tree: https://github.com/rwasef1830/android_device_sony_ivy/tree/cm-14.1-twrp
TWRP: https://github.com/omnirom/android_bootable_recovery/ (cherry pick https://gerrit.omnirom.org/#/c/22096/ thanks to @Captain_Throwback)
Changelog
2017-02-27:
- Initial release
2017-02-28:
- Embed minimum crypto blobs directly in recovery, now it is completely independent from /system and /firmware. Commented out /firmware from fstab to prevent accidental damage by users.
- Removed accidentally left debug messages in firmware_class.c in previous release.
2017-02-28-02:
- Moved qseecomd binary and libs outside /system to avoid becoming affected by mounting /system.
- Enable qualcomm hardware encryption engine (thanks to @nailyk and @Captain_Throwback for help).
- Use busybox instead of toolbox/toybox to avoid problems with scripts due to missing functions.
2018-03-04-01:
- Sync'd to latest ivy / kitakami sources.
- Updated to latest TWRP on android-7.1 branch.
Developer notes
- Encryption depends on binary blobs in phone "modem" partition: keymaste.* and kmota.* (shipped with firmware FTF). These blobs have now been embedded in the recovery image itself, so recovery runs completely standalone.
- Also needed are cmnlib.* files from /system/etc/firmware but they are embedded in this recovery image to allow crypto to work completely independently of /system.
- Sony firmware package can be flashed with @Androxyde flashtool.
Future ideas
- Generalize the changes needed for TWRP to make it compatible with Kitakami in general (z5 / z5 premium) and make the tree cleaner. If any devs want to help, please reply, I'm a noob myself at this
- Implement charging LED.
Updated 2017-02-28.
Now trying to get cryptfs hw encryption working!
Please!!! Help me....
I'm with boot loop in twrp, how to solve this? I have Dual version on stock ROM V278
EverCH said:
I'm with boot loop in twrp, how to solve this? I have Dual version on stock ROM V278
Click to expand...
Click to collapse
What does boot loop in twrp mean ? If you mean you are unable to reboot from TWRP to system, just go to reboot in menu and power off and then power on. It will go to system.
If you mean something else, please provide more details.
I do this, but when I try to restart the system, it goes back to the twrp, even if it turns off the phone and calls again, it starts directly in twrp, it does not start the OS, it stays in loop in recovery.
EverCH said:
I do this, but when I try to restart the system, it goes back to the twrp, even if it turns off the phone and calls again, it starts directly in twrp, it does not start the OS, it stays in loop in recovery.
Click to expand...
Click to collapse
Unplug phone. From inside TWRP go to reboot menu, and choose power off. Wait for few seconds after screen turn off, then power on using power button only.
Otherwise, try to go in fastboot mode again by doing vol. up + plug in, and then from console do fastboot reboot.
Work great on dual version:victory:
DiscMan55 said:
Unplug phone. From inside TWRP go to reboot menu, and choose power off. Wait for few seconds after screen turn off, then power on using power button only.
Otherwise, try to go in fastboot mode again by doing vol. up + plug in, and then from console do fastboot reboot.
Click to expand...
Click to collapse
I just did this however I got the same result, it never starts the OS, even turning it off for a few minutes when connecting it enters the twrp, remembering that I am with ROM 32.3.A.0.376 dual version
EverCH said:
I just did this however I got the same result, it never starts the OS, even turning it off for a few minutes when connecting it enters the twrp, remembering that I am with ROM 32.3.A.0.376 dual version
Click to expand...
Click to collapse
At this point, I don't know what can be wrong. I would try to reflash with sony flashtool all partitions (except userdata), then flash twrp again from fastboot. Maybe that will reset it.
To anyone familiar with BoardConfig.mk syntax:
I am trying to get TARGET_HW_DISK_ENCRYPTION working. There is a problem with TWRP, it expects libcryptfs_hw.so to be found in $(TARGET_OUT_VENDOR_SHARED_LIBRARIES)/libcryptfs_hw.so but in sony tree, libcryptfs for qualcomm comes from default LineageOS qcom opensource cryptfs driver (which delegates to libQSEEComAPI.so which is pulled from blobs) in https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/
In the Android.mk in that driver https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/blob/cm-14.1/Android.mk LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 are not defined, so libcryptfs_hw.so gets built to default /lib and /lib64 location, so it is not found by TWRP (https://github.com/omnirom/android_bootable_recovery/blob/android-7.1/prebuilt/Android.mk#L172) .
Is there a way in my device BoardConfig.mk where I can make ninja understand to build libcryptfs_hw.so like normal and then have it copy it to where TWRP expects it before building TWRP ?
I'm trying to have my tree "just work" without having to fork the lineage os repo just to add 2 lines. If I add:
Code:
# in vendor/qcom/opensource/cryptfs_hw/Android.mk
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64
It builds and works successfully, but I don't want this ugly hack.
DiscMan55 said:
To anyone familiar with BoardConfig.mk syntax:
I am trying to get TARGET_HW_DISK_ENCRYPTION working. There is a problem with TWRP, it expects libcryptfs_hw.so to be found in $(TARGET_OUT_VENDOR_SHARED_LIBRARIES)/libcryptfs_hw.so but in sony tree, libcryptfs for qualcomm comes from default LineageOS qcom opensource cryptfs driver (which delegates to libQSEEComAPI.so which is pulled from blobs) in https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/
In the Android.mk in that driver https://github.com/LineageOS/android_vendor_qcom_opensource_cryptfs_hw/blob/cm-14.1/Android.mk LOCAL_MODULE_PATH_32 and LOCAL_MODULE_PATH_64 are not defined, so libcryptfs_hw.so gets built to default /lib and /lib64 location, so it is not found by TWRP (https://github.com/omnirom/android_bootable_recovery/blob/android-7.1/prebuilt/Android.mk#L172) .
Is there a way in my device BoardConfig.mk where I can make ninja understand to build libcryptfs_hw.so like normal and then have it copy it to where TWRP expects it before building TWRP ?
I'm trying to have my tree "just work" without having to fork the lineage os repo just to add 2 lines. If I add:
Code:
# in vendor/qcom/opensource/cryptfs_hw/Android.mk
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64
It builds and works successfully, but I don't want this ugly hack.
Click to expand...
Click to collapse
Weird way to include it into twrp. Is it the same into 6.0 branch or does they use dependencies system?
You can try to replace with something like:
Code:
ifneq ($(strip $(TARGET_ARCH)),arm64)
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
else
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64
endif
but I think a better way would be to change the include into twrp.
nailyk said:
Weird way to include it into twrp. Is it the same into 6.0 branch or does they use dependencies system?
You can try to replace with something like:
Code:
ifneq ($(strip $(TARGET_ARCH)),arm64)
LOCAL_MODULE_PATH_32 := $(TARGET_OUT_VENDOR)/lib
else
LOCAL_MODULE_PATH_64 := $(TARGET_OUT_VENDOR)/lib64
endif
but I think a better way would be to change the include into twrp.
Click to expand...
Click to collapse
When I modify vendor/qcom/opensource/cryptfs_hw/Android.mk as I quoted, ninja picks up that it is dependency, and it compiles libcryptfs_hw first, and then copies to where TWRP wants, but I can't make it understand to "alias" or build it manually in its default location and then put it where ninja wants to be still recognized as dependency.
I don't want to hack qcom source because I want my same BoardConfig to work for LineageOS build as well as TWRP (I want to make 100% compatible encryption in LineageOS 14.1 with stock sony rom with best performance and lowest battery with hw crypto).
DiscMan55 said:
When I modify vendor/qcom/opensource/cryptfs_hw/Android.mk as I quoted, ninja picks up that it is dependency, and it compiles libcryptfs_hw first, and then copies to where TWRP wants, but I can't make it understand to "alias" or build it manually in its default location and then put it where ninja wants to be still recognized as dependency.
I don't want to hack qcom source because I want my same BoardConfig to work for LineageOS build as well as TWRP (I want to make 100% compatible encryption in LineageOS 14.1 with stock sony rom with best performance and lowest battery with hw crypto).
Click to expand...
Click to collapse
Does TARGET_RECOVERY_DEVICE_MODULES := libcryptfs_hw get the module be built at the right location?
(it should be something like LOCAL_DEPENDENCIES += TARGET_RECOVERY_DEVICE_MODULES into twrp makefiles but can't find it again. I hope they don't remove it...)
I know they get encryption working because pixel is encrypted and afaik it is qcom arm 64 too.
nailyk said:
Does TARGET_RECOVERY_DEVICE_MODULES := libcryptfs_hw get the module be built at the right location?
(it should be something like LOCAL_DEPENDENCIES += TARGET_RECOVERY_DEVICE_MODULES into twrp makefiles but can't find it again. I hope they don't remove it...)
I know they get encryption working because pixel is encrypted and afaik it is qcom arm 64 too.
Click to expand...
Click to collapse
Nope, it gets built but at the default location (which is wrong for twrp) as the normal behavior for android.mk without explicit local_module_path.
Now I am only stuck on how to just copy it to /vendor/ before TWRP builds (how to say that in BoardConfig.mk)
Here's the relevant part of my BoardConfig.mk:
Code:
TARGET_HW_DISK_ENCRYPTION := true
TARGET_CRYPTFS_HW_PATH := vendor/qcom/opensource/cryptfs_hw
TARGET_SWV8_DISK_ENCRYPTION := true
TARGET_RECOVERY_DEVICE_MODULES := libcryptfs_hw
# latest attempt, doesn't work, still complains file is missing
PRODUCT_COPY_FILES += ${TARGET_OUT_SHARED_LIBRARIES}/libcryptfs_hw.so:$(TARGET_OUT_VENDOR_SHARED_LIBRARIES)/libcryptfs_hw.so
Cherry-pick this: https://gerrit.omnirom.org/22096
DiscMan55 said:
Nope, it gets built but at the default location (which is wrong for twrp) as the normal behavior for android.mk without explicit local_module_path.
Now I am only stuck on how to just copy it to /vendor/ before TWRP builds (how to say that in BoardConfig.mk)
I tried PRODUCT_COPY_FILES but it didn't work
Click to expand...
Click to collapse
Product copy_files on Lineage is parsed only at bacon time. The only way is to create a dummy target like:
Code:
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
LOCAL_SRC_FILE := out/target/product/device/xxx/yyy/zzz/libcryptfs_hw.so
LOCAL_MODULE := libcryptfs_hw64
LOCAL_MODULE_PATH := $(TARGET_RECOVERY_ROOT_OUT)/lib64/
LOCAL_POST_INSTALL_CMD += \
ln -sfT libcryptfs_hw64.so $(TARGET_RECOVERY_ROOT_OUT)/lib64/libcryptfs_hw.so;
include $(BUILD_PREBUILT)
Or to put it as prebuilt into device/sony/ivy/recovery/root/lib64/ (symlink doesn't get copied, that was my problem )
Maybe you should try the twrp IRC chan, probably somebody had already solved this.
Haha Captain is here your are in good hands now
nailyk said:
Product copy_files on Lineage is parsed only at bacon time. The only way is to create a dummy target like:
Or to put it as prebuilt into device/sony/ivy/recovery/root/lib64/ (symlink doesn't get copied, that was my problem )
Maybe you should try the twrp IRC chan, probably somebody had already solved this.
Click to expand...
Click to collapse
You missed my post .
LineageOS 15.1 (Beta v1.01) originally for Moto E5 Play (james) working on Moto E5 (Nora)
Very Important!!!!
I've just found the way to boot sucessfully LOS 15.1 on nora_row, the ROM was originally made by @MotoJunkie01, so I'm not taking this ROM as mine, I've mentioned that I'm not a dev, I just love to share what I found, I hope this won't cause any problem and it will be useful for you guys.
Previously I've shared how to root Moto E5 (Nora) because there wasn't any specific info for that variant, TWRP and Root Guide was only for Play/Plus, and then after some attemps, I finally found a way to use TWRP and how to flash LOS 15.1
Disclaimer
I'm not responsible for any dead SD cards/phones
If your phone turns into a nuclear bomb
If your dog/cat complain about you
Advertisment
The ROM is working almost fine but "Keep in mind that I have XT1944-2" also it is a beta ROM and if my previous guide of root didn't work properly, you shouldn't try to install it, because it may result on a brick or something else, as always is mentioned, try by your own risk.
BUGS
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
You tell me
Requirements
1. The most important and obviously, unlocked bootloader, a computer, and just basic knowldge
2. Stock ROM zip, in case of something is wrong and because you'll need to extract boot.img, here are the links and a guide to recover your phone in case of brick: https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
3. TWRP recovery. You can get it here: https://forum.xda-developers.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323
4. You may wonder how to install TWRP, I must admit that it's not possible on Nora (causes brick) but searching here in XDA I've found that you can boot into TWRP without installing and also if you make a backup it will work in case of emergency
5. Platform tools folder that contains fastboot and adb drivers (your boot.img must be extracted here): https://www.dropbox.com/s/c3c8rev5e40gy5b/platform-tools-latest-windows.zip?dl=0
6. Remember to put the ROM and Gapps on your SD:
ROM: https://drive.google.com/open?id=1F2rC7zIZPqod3vMC1t22uhNYMQbf56K6
Gapps: https://drive.google.com/drive/folders/1rHf5XIs7XK3kWFFLekjrK0ub_bKnSlUI
Instructions
1. First of all boot into bootloader or fastboot (power & volume down) and connect your phone to your PC
2. At this point it is supposed that you have downloaded platform tools folder and all necessary zips (stock ROM, LOS, gapps), then inside the folder press Shift+Right Click, and select "open CMD window here" for Windows 7, on Windows 8 and up just click "Archive", then when CMD it's open, type: fastboot boot twrp_james.img Your phone automatically will reboot into TWRP.
3. The recovery will delay 1 or 2 minutes to start and it will ask us for our key to decrypt data. Just press cancel, because we don't have that key, and that option is not working and swipe to allow modifications. Don't mount anything, what it is already mounted is fine, only you can mount SD Card, in case that is not mounted, if you don't have a SD Card you wouldn't be able to make a backup
4. Go to backup section, and choose SD Card to put your backup there, remember that the Backup couldn't be saved on Internal Storage because the ROM will wipe Internal Storage and System, then if you choose all the partitions nothing wrong would happen, but if you are not pretty sure, just skip data and cache
5. The time that TWRP will took to backup depends on the things that you have on your system (Ignore red letters that show some errors)
6. Then go to Wipe section and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting and then go to reboot section and choose bootloader because remember that TWRP is not installed and we nned to reboot the recovery, then use again CMD to boot into TWRP
7. Then we are again on TWRP, then press Install, select SD Card and look for the ROM zip and Gapps and swipe to flash, it's very fast the installation, wait until it finish and reboot your device into bootloader, It will be with red letters, but don't be affraid.
8. Another important thing, that ROM, contains boot.img from Moto E5 Play, that's what I told you, that you will need to use boot.img from stock ROM, then go to Platform Tools Folder and again open CMD (Shift+Left Click for W7) and type: fastboot flash boot boot.img Wait until it finish and type fastboot reboot
9. And that's all, first boot will delay, be patience. Additionally I couldn't find a way to skip force encrypt, so the phone will be encrypted and it will reboot, sometimes if you reboot the ROM it would reboot again, it's normal, As this ROM it's unnofficial it will show tha your device is uncertified but you can hide that notifications and use your phone normally.
Magisk, Xposed and Substratum work, but choose carefully what are you going to install because some modules will cause problems or a bootloop, if you need some help write your comments and experiences. YouTube for some reason open but didn't shows anything.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to @Deivid_21 for sharing working gapps
Thanks to the entire LineageOS team;
This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.
MotoJunkie01 said:
This is great news. Slowly but surely, development for the entire Moto E5 series is growing. Great work on this OP.
Click to expand...
Click to collapse
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one
Fersho said:
Yeah thank you, but I was unable to find a no verity kernel for E5, Play and Plus have got it, but this one not, then thanks for sharing a LOS 15.1 it's cool just the only bug was the camera but because of that encryption the ROM became laggy, I wish I could have a good computer to compile but well it seems to hard, anyway i hope more coming ROMS because it's sad that LOS 16 it's already released and we hardly have got just one but it's appreciated the time and effort for this one
Click to expand...
Click to collapse
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.
MotoJunkie01 said:
Yeah that's my dilemma as well. I have neither the time nor regular access to a high quality machine to compile. I have a port for Lineage 16.0 for the E5 Play which boots and functions somewhat. When I can smooth some things out and get it a bit more stable, I'll post it as well.
You should post a no-verity kernel for the E5 for others to use. It would be appreciated I'm sure.
Click to expand...
Click to collapse
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel
Fersho said:
For real? I would really love to test Pie, pls upload it, then I'm trying to post a no-verity kernel but then how am I going to extract the necessary things? I had seen a tutorial to unpack boot.img but then I don't know how to disable dm vrity or where are the files located on Moto E5 Play/Plus kernel
Click to expand...
Click to collapse
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.
MotoJunkie01 said:
Here is an easier method -- install the stock boot image on your device using either fastboot or TWRP. Then, in TWRP, install this boot image patch script -- https://drive.google.com/file/d/1oLrNL3OYhwlCCLOtLdQEQM4tGsIucsPQ/view?usp=drivesdk
It will unpack, patch, repack and flash the modified boot image back to your boot partition, disabling dm-verity. Then use TWRP to make a backup of your /boot partition. Using a file manager, rename the backup from boot.emmc.win to boot.img and you're done. You'll then have a no-verity kernel in boot.img format. The file can then be installed by other members using fastboot or TWRP.
Once you're done, you can simply use TWRP to reinstall or restore your previous ROM configuration.
Click to expand...
Click to collapse
It doesn't works, also using zip on LOS/Stock it doesn't boot
Fersho said:
It doesn't works, also using zip on LOS/Stock it doesn't boot
Click to expand...
Click to collapse
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.
MotoJunkie01 said:
I will patch a boot image to disabled dm-verity for the Moto E5. I'll post soon as I get some free time.
Click to expand...
Click to collapse
Thanks, but finally I removed encryption, but men, it was very hard for me and it took me like 3 or 4 hours, but well the procedure is a llitle bit confusing, and I couldn't create a boot.img just ported the ones already shared for Play/Plus and seemed to work "fine", If I got some time I would make another tutorial but I guess that it will be long
Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.
MotoJunkie01 said:
Here is a no-verity kernel for the xt1944-2 Moto E5
From Build No. OPP27.91-25
https://drive.google.com/file/d/1NcyuFRgvvRiS5MT5Jxl3uS3XHCnULBMc/view?usp=drivesdk
In case anybody needs it.
Click to expand...
Click to collapse
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?
Fersho said:
Thank You, Do you believe that I don't have XT1944-2 I have XT1944-4 I notice that when I've seen something in settings, then It's only flash the kernel and that's all?
Click to expand...
Click to collapse
I'll do a no-verity for xt1944-1 also. In fact, I'll try and cover all variants for which I have firmware access. You can try to boot the kernel for xt1944-2 prior to flashing it, by using:
fastboot boot no-verity_xt1944-2.boot.img
If it boots, you should be safe in flashing it to your /boot partition. In any event, I'll post some no-verity kernels for the Moto E5 variants.
so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait
SeerePetrova said:
so if i have the xt1944-3 can I use this tutorial? and what twrp recovery should I use..? or should i just wait
Click to expand...
Click to collapse
Well I've only tested on XT1944-2/4 you should try by your own risk, then for TWRP use the one that is made for Moto E5 Play, then boot into TWRP using fastboot boot "twrp-james.img" don't try to install because it wont work
Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
01-04 06:43:08.824 F/libc (622): CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found
01-04 06:43:08.825 F/libc (622): Fatal signal 6 (SIGABRT), code -6 in tid 622 (motorola.hardwa), pid 622 (motorola.hardwa)
01-04 06:43:09.162 F/DEBUG (712): pid: 622, tid: 622, name: motorola.hardwa >>> /vendor/bin/hw/[email protected] <<<
01-04 06:43:09.162 F/DEBUG (712): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-04 06:43:09.180 F/DEBUG (712): Abort message: 'CANNOT LINK EXECUTABLE "/vendor/bin/hw/[email protected]": library "[email protected]" not found'
Click to expand...
Click to collapse
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.
weakNPCdotCom said:
Any plans to get the remaining hardware working? I tried flashing factory Vendor image from the XT1921-1 retail firmware for the hell of it to see if that might change anything with the camera and flash, but it didn't. LOS logs a crash.
I might not have been looking in the right place but the imgtuner file name in /vendor/lib/hw is: [email protected]
If I had any idea how to fix this I would try.
Click to expand...
Click to collapse
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.
MotoJunkie01 said:
I was hoping the camera commits had been added to the GitHub repositories by now, but they have not as of this date. A manual fix can likely be accomplished by replacing the camlibs in the Lineage build with the camlibs from the stock build. Unfortunately, due to my work schedule, I don't get a lot of spare time for development, but if anybody wants to try, simply copying/replacing the camlibs from stock to Lineage should fix the camera.
Click to expand...
Click to collapse
Im new to the android rom/firmware file structure. just want to make sure I understand. are you referring to the .so camera libraries in vendor/lib? or do you mean the actual /core/java/android/hardware framework files in the source?
Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy
tbirdguy said:
Res Remix system-180818-arm-aonly-gapps.img
camera works good... flash too
apparently i still have force encrypt though and the phone can definitely get laggy
Click to expand...
Click to collapse
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches, anyway I couldn't find a way to fix that lag, even using apps like L Speed
Fersho said:
That's right, camera and flashlight are working on RR OS GSI Official, but that lag is horrible, well it's only while scrolling and system ui, but the rest of the apps are working fine, to disable encryption you must flash no verity kernel that it's attached on previous commentaries and also to edit fstab.qcom then you'll skip encryption, but it doesn't affect on performance because even you skipped encryption the device still laggy, also on Pie is the same, but some extra bugs like graphic glitches
Click to expand...
Click to collapse
Just FYI the no verity kernel results in a bootloop on the TMO XT1921-3
"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon
I tried this is working,nice tool.
Thanks dev.
Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
hey there! wonderful tool to have. Thank u so much
Not working in my laptop say a software need a to update
Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?
ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it
How to flash it's says this...
Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?
KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.
Can you please upload Oreo December update stock and patched boot image. TIA
Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.
My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained
its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed
The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!
Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals
Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????
built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.
ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.