DISCLAIMER: I own Xperia X10, Xperia J, Xperia Tipo, Xperia S and Xperia V, releases of all other phones are not personally tested by me. But since the kernel is the same in FXP/KXP ROMs I presume they would not harm your device in any way
Huge props go to all TeamWIn people like Dees_Troy and bigbiff and everyone else for developing this awesome recovery and lots of thanks to FreeXperia Team (FXP, Kali-, codeworkx, bin4ry,) for maintaining device configs for Xperias
This recovery is embedded into the ramdisk of a normal AOKP 4.1.2 bootimage. The kernels are same as the latest AOKP released by KXP team. These kernels should work with FXP's CM10, and other ROM's based of it (KXP ROM, Pac-man, officialCM10 etc). These kernels will not work on stock/cm7/cm9/blah/blah/any other ROM.
INSTRUCTIONS :
1. Download the zip file for your device (twrp2.4.3-xxxxx.zip)
2. Extract the boot.img from zip on your PC, and copy the whole zip file on device's SDcard.
3. Fastboot the kernel using the terminal command
Code:
fastboot flash boot boot.img
4. To enter recovery, when LED is pink press {vol up for 2012 models} or {vol down for 2011 models}
5. Flash zip that you kept in sdcard from recovery (wifi/OTG/etc will not work without proper modules flashed).
6. Enjoy
DOWNLOADS:
Mirror1 |or| Mirror2
download according to your device name in this list
Code:
[LIST]
[*]anzu Arc/ArcS
[*]aoba ION
[*]coconut Live with WALKMAN
[*]haida Neo V
[*]hallon Neo
[*]hayabusa TX
[*]hikari Acro S
[*]jlo J
[*]iyokan Pro
[*]mango MiniPro
[*]mesona Miro
[*]mint T
[*]nozomi S/SL
[*]satsuma Active
[*]smultron Mini
[*]tapioca Tipo
[*]tsubasa V
[*]urushi Ray
[*]zeus Play
[*]zeusc Play CDMA
[/LIST]
CHANGELOG :
All official changes to TWRP is found on http://teamw.in
Code:
=============twrp 2.4.3
code updated to oficial twrp 2.4.3.0
new device J, Tipo, Miro supported
=============twrp2.4
code updated to official twrp 2.4.1.0
fixed "/boot not found" error on 2011 phones
=============twrp 2.3
official twrp 2.3 sources
first release
=======================================================================================
for advanced users/devs/modders/porters
=======================================================================================
SOURCES:
The kernels present inside the bootimages are compiled from these sources
https://github.com/KangXperiaProject/android_kernel_sony_msm7x27a (for Tipo, J, Miro)
https://github.com/KangXperiaProject/android_kernel_sony_msm8x60 (for S,Ion,AcroS, T, V, TX)
https://github.com/KangXperiaProject/android_kernel_semc_msm7x30 (for all 2011 model phones)
The device configs are found on
https://github.com/KangXperiaProject/android_device_semc_<yourdevicename> (for all 2011 model phones)
https://github.com/KangXperiaProject/android_device_sony_<yourdevicename> (for all 2012 model phones)
you can also see our merged commits to see the precise patch we applied on each repository to be able to build TWRP
http://smartdev.com.pl:8080/#/q/status:merged,n,z
BUILD FROM SOURCE
To build TWRP for your Xperia,
1. merge the patch to enable TWRP on your own device tree (for eg. http://smartdev.com.pl:8080/#/c/239/ for Xperia T)
2. replace /bootable/recovery folder with TWRP (as mentioned here http://forum.xda-developers.com/showthread.php?t=2069242)
3. If your build folder is not from CM, switch to CM's build folder (i.e the android_build repo)
4. lunch ; mka bootimage;
PORT TO STOCK/ICS/YOU-FAVOURITE-KERNEL
A boot.img consists of the kernel image and the ramdisk (additionally and optionally RPM.bin and commandline). If you want to use TWRP for some other kernel, you have to do this
1. decompile this boot.img (for 2011 models it's a true boot.img, for 2012 models, it's actually a kernel.elf file renamed to boot.img, so you have to decompile accourdingly. you can use my kernel kitchen to do the same)
2. replace the kernel zImage with the one from the kernel you want to port to
3. replace /sbin/ramdisk.cpio with the "UNCOMPRESSED" ramdisk of the kernel you want to port this to. (usually ramdisk is compressed with gzip i.e. ramdisk.cpio.gz. you need to uncompressed ramdisk image i.e. ramdisk.cpio)
4. do not touch anyother thing
5. pack it up into a boot.img (for 2011) or kernel.elf (for 2012) and fastboot it
============================================================================================
BUGS AND SUPPORT
If you have any problem with this please please please post only on this thread, not on any other thread or not on PM.
Please send me the recovery log wherever possible, and also kmsg/dmesg if you can.
If you need assistance porting TWRP to your kernel, or building from source[only for Xperia phones that I have provided builds for], then also you can post here.
You have a lot of devices, LOL
Great Job, this is really awesome.
I am going to try this
Sent from my ST15i using xda app-developers app
hey man
I am unable to open the links of patches.
the link says connection refused.
I want to compile TWRP in PAC kernel
EDIT:
Must be my broadband problem. I am able to open your gerrit using my 3g net
Sorry
Known problems:
Backup/restore .android_secure (apps move to sdcard) does not work
Reboot to recovery from TWRP does not work
Executing terminal commands from TWRP does not work
Hardware keyboard does not work
Backspace of software keyboard does not work
USB mount
(compiled today / tested on mango)
good,, will you update to latest twrp 2.6?
Agnostic-kernel - filesystem independent kernel flasher
WARNING!
Please, make a backup or be prepared to roll back to a working state somehow. You are using this tool on your own responsibility. You have been warned!
If anything goes wrong, flashing another kernel that was working for you before should return your device to a working state.
Repository on GitHub
This is a recovery tool primarily made for kernel/ROM developers, but anyone is welcome to use it, provided he knows what to do. It was made to enable kernel developers to have a single .zip with the kernel which will work on all partition layouts like All-F2FS, Data-F2FS and All-EXT4 (the standard layout).
It takes a boot.img, unpacks it during the installation, finds out what partition layout is used on the device, changes the fstab in the ramdisk accordingly, repacks the boot.img and flashes it.
Instructions for kernel/ROM developers/flashaholics who wish to incorporate this tool:
Make sure your kernel is compiled with F2FS drivers.
Download agnostic-kernel-template.zip
Replace the boot.img-placeholder in the .zip with your boot.img.
OPTIONAL: change the fstab in fstab/ folder to specify any mount options you wish to use. Make sure you include a line for each partition and filesystem combination you want to use.
OPTIONAL: change the updater-script to print any additional messages or make modifications to the kernel after flashing.
Instructions for users who wish to try this tool:
Choose one of the prepacked kernels you wish to install and download it.
Install it via recovery.
Instructions for people who wish to port it to other devices:
Change the asserts in updater-script to check for your device name.
Change the fstab in the fstab/ folder. Make sure you include a line for each partition and filesystem combination you want to use.
Change the FSTAB variable in tools/repack-and-flash.sh to contain the name of your fstab file.
Change the BOOT_PARTITION variable to contain the path to your /boot partition device.
Currently supported partition layouts:
/system on EXT4 or F2FS
/cache on EXT4 or F2FS
/data on EXT4 or F2FS
Filesystem changes are supported only on these partitions because the Nexus 7 doesn't have any other EXT4 partitions by default.
If you want to add support for some other device specific layout (F2FS formatted SD card comes to mind, for example), feel free to do so or contact me, but it may require some changes to your recovery too.
Tested on:
Kernels
3.2.5-XPerience by @TeamMex
LegoKernel / SlimKernel by @legolas93
franco.Kernel by @franciscofranco and modified by @HTCDreamOn
linux-tegra-nv-3.1-grouper by @HTCDreamOn
M-Kernel by @Metallice
Recoveries
CWM Recovery 6.0.4.3 by ClockworkMod
TWRP by @legolas93[/MENTION]
MultiROM recovery by @@Tasssadar
ROMs
ROM shouldn't matter, I tested on various 4.4 / 5.0 ROMs and even without a ROM and it always worked.
Downloads
Pre-packed kernels:
Kernel from SlimROM by @legolas93
3.2.5-XPerience-19 by @TeamMex
Empty template for devs:
agnostic-kernel-template.zipYou can download other kernels using agnostic-kernel in their respective threads.
Credits:
Android Image Kitchen - @osm0sis - this wouldn't be possible without him
F2FS Recovery - @legolas93
Kernels on which I tested - @TeamMex & @legolas93 & @franciscofranco & @HTCDreamOn & @Metallice
Recovery magic - @Chainfire & @_that
Answers to a lot of my problems - forum.xda-developers.com community
Some nice ideas - @Metallice
Partition layout checking, scripting - @frantisek.nesveda
If you wish to incorporate or modify this tool, please, mention me somewhere, thanks
Changelog:
13th November 2014
This is a highly recommended update for all developers using agnostic-kernel.
Now completely ROM independent
Updated Android Kitchen to version 1.6 - thanks, @osm0sis!
Fixed an issue with Android Kitchen binaries using /system/bin/linker which was not always available.
First I did an ugly hack to solve the issue...
and then I found out that the updated Android Kitchen binaries are statically linked now and the ugly hack was not needed anymore.
Changes to the way fstab is generated - now it uses only one file and deletes unneeded lines from it - inspired by @Metallice
Added more error-checking
Some other small fixes and improvements
Tested on a lot of recoveries and partition layouts.
13th May 2014
Fixed an issue with the zip which could arise when /system was not mounted before the install.
Tested on a lot of recoveries and partition layouts.
12th May 2014
Initial release.
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
aosp said:
Add settings to enable/disable f2fs forcing mode so we can switch on …
…the fly. Force will force all wipe/format calls to use f2fs or ext4 depending on the selection. Also added code to ensure settings are re-written back to internal sd after a super wipe. Also removed fstab code to determine the mode since we now have a setting for it
http://goo.gl/NTamfl
Add code to analyze the fstab to determine whether we are in f2fs mod…
…e or ext4 mode
http://goo.gl/MJXQpE
Click to expand...
Click to collapse
If I'm not mistaken, this is a code in a custom recovery that enables the user to select if he wants to format his partitions as F2FS or EXT4, similar to what the MultiROM recovery does after yesterday's update?
If so, I don't see the connection that your code has with my tool... My tool is a template for a recovery zip, in which kernel devs can place their boot.img, and when the user installs that zip with the boot.img, the script in that zip will check for which partitions does the user have formatted as F2FS and modify the fstab in the boot.img accordingly.
Updated all the zips with a bugfix. The Android Image Kitchen would not start on CWM when /system was not mounted, because it tried to use sh in /system/bin instead of /sbin.
Also, I tested the zips on more partition layouts and recoveries, and verified that it works right both on CWM and TWRP and on ALL-F2FS, Data-F2FS and ALL-EXT4.
awesome work
How do we convert if we only have a zimage and no boot.img
Sent from my Nexus 7 using Tapatalk
chaostrodamis said:
How do we convert if we only have a zimage and no boot.img
Click to expand...
Click to collapse
The changes are all done to the ramdisk, so you can't do them without one, at least not with this method.
But, if you look how @sgt. meow does it in his Oxydo kernel, perhaps that is the way you could use. He unpacks the ramdisk from the currently installed kernel and then packs it with his zImage to a boot.img which he then flashes. This requires that the user first flashes another kernel with f2fs working, and then flashes your kernel.
Perhaps it would be easier if you packed your kernel with some ramdisk and then used it.
An updated version of agnostic-kernel is available in the OP. See post #2 for changelog.
Both the template zip and the two prepacked kernels are updated.
This is a highly reccomended update for all kernel developers, as it fixes compatibility issues with some ROMs (AOSP Lollipop, for example).
I've also published sources to my working folder on GitHub, if anyone is interested. There's nothing really important there, though.
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
RoryB said:
Thanks for the post in my thread. I've been trying to figure out how to edit the line in the file and kept running into roadblocks. I'll definitely take a peek. The other thing I am planning to do is pull the boot image from the phone instead of having it in the zip file.
Click to expand...
Click to collapse
You're welcome. And you could perhaps try pulling the boot.img with dd, something like this:
Code:
dd if=$BOOT_PARTITION of=/tmp/agnostic-kernel/boot.img
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Link for this this "Tech Karan (for his similar guide)"?
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
nsfnd said:
Link for this this "Tech Karan (for his similar guide)"?
Click to expand...
Click to collapse
You are right, sorry for forgetting this link. I have just edited the first post
nsfnd said:
I was able to install it mate thanks.
Working fine, very smooth.
Mi Login doesnt work tho, which i dont mind.
Click to expand...
Click to collapse
Yes, I have found this bug, too. This happens because there is the same one on Poco F1 (base rom).
Also, there are some missing applications, which can be installed as normal .apk files from APKMirror:
-> Mi Browser
-> Mi Cleaner
-> Mi Scanner
They made an Android 12, MIUI 13 version for Poco F1.
I tried to do the same technic explained above for that.
But Jancox Tools failed to extract with errors.
(imgextractor.py and ext4.py, NameError: name 'xattr' is not defined)
Link for the rom.
PocoOs Stable Channel (Official)
╭━┳━┳━┳━╮╭━┳━━╮ ┃╋┃┃┃╭┫┃┃┃┃┃━━┫ ┃╭┫┃┃╰┫┃┃┃┃┣━━┃ ╰╯╰━┻━┻━╯╰━┻━━╯ MIUI 13.0.4 EU rom Based on Android 12, Code name:Ignition🔥 ======================= Maintained by @facerracer4u ======================= About PocoOs: PocoOs comes with all poco standards We do not include harmful mods, and we...
t.me
Maybe you want to check it out.
Unfortunately, we have to make a compatible vendor.img for Mi 8. Otherwise, every MIUI 13 (Android 12) ROM cannot be booted (the existing vendor files are compatible with Android 11 MIUI ROM's). I will try to port /vendor, but I am not promising anything
At least, there is a compatible kernel (No Gravity v3.x.x)
Edit: NoGravityKernel does not support /system_ext (so for most MIUI S ROM's it is not compatible)
OK, ιt's been a long time since my last post, but I have found a bootable Android 12 version of MIUI 13, but I have not managed to fix the common bugs from Pocophone F1:
<!> audio
<!> camera
<!> slow motion while watching videos (due to the audio bug)
Also, this ROM does not have NFC support (Poco F1 does not come with)
In order to install it, I have flashed:
-> the ROM (by deleting the first line in /META-INF/com/google/android/updater-script
-> permissiver v5
-> dfe (disable forced encryption)
-> XDKernel-2.6
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Advanced Gears said:
Camera is now fixed, after replacing some vendor files (there is no need to chmod):
Code:
vendor/etc/camera/age_gender_bg
vendor/etc/camera/beauty_ui9_intelligent_params.config
vendor/etc/camera/camxoverridesettings.txt
vendor/etc/camera/crown_156_128.bin
vendor/etc/camera/dualcamera.png
vendor/etc/camera/eyelineblush.cng
vendor/etc/camera/face_goodly_208_180
vendor/etc/camera/face_ravishing_238_224
vendor/etc/camera/face_splendid_274_200
vendor/etc/camera/female_bg.png
vendor/etc/camera/female_icon.png
vendor/etc/camera/hdr_ui9_params.config
vendor/etc/camera/lf_facerank_model.bin
vendor/etc/camera/male_bg.png
vendor/etc/camera/male_icon.png
vendor/etc/camera/Miui-Light.ttf
vendor/etc/camera/MIUI_Time.ttf
vendor/etc/camera/people_gender.dat
vendor/etc/camera/score_bg.png
vendor/etc/camera/score_icon.png
vendor/etc/camera/sdm_ys_32p_120_21_5_perturb50.bin
vendor/etc/camera/watermark_font_2300_3199.dat
vendor/lib/camera/com.qti.sensor.imx363.so
vendor/lib/camera/com.qti.sensor.ov7251.so
vendor/lib/camera/com.qti.sensor.s5k3m3.so
vendor/lib/camera/com.qti.sensor.s5k3t1.so
vendor/lib/camera/com.qti.sensormodule.imx333.bin
vendor/lib/camera/com.qti.sensormodule.imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx333.bin
vendor/lib/camera/com.qti.sensormodule.liteon_imx363.bin
vendor/lib/camera/com.qti.sensormodule.liteon_s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.ov7251.bin
vendor/lib/camera/com.qti.sensormodule.s5k3m3sn03.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1.bin
vendor/lib/camera/com.qti.sensormodule.s5k3t1_qtech.bin
vendor/lib/camera/com.qti.tuned.default.bin
vendor/lib/camera/com.qti.tuned.liteon_imx363.bin
vendor/lib/camera/com.qti.tuned.liteon_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.qtech_s5k3t1.bin
vendor/lib/camera/com.qti.tuned.semco_imx363.bin
vendor/lib/camera/com.qti.tuned.semco_s5k3m3.bin
vendor/lib/camera/com.qti.tuned.sunny_ov7251.bin
vendor/lib/camera/com.qti.tuned.sunny_s5k3t1.bin
vendor/lib/camera/components/com.arcsoft.node.capturebokeh.so
vendor/lib/camera/components/com.arcsoft.node.capturefusion.so
vendor/lib/camera/components/com.arcsoft.node.hdr.so
vendor/lib/camera/components/com.arcsoft.node.hdrchecker.so
vendor/lib/camera/components/com.arcsoft.node.realtimebokeh.so
vendor/lib/camera/components/com.arcsoft.node.skinbeautifier.so
vendor/lib/camera/components/com.arcsoft.node.smoothtransition.so
vendor/lib/camera/components/com.arcsoft.node.superlowlight.so
vendor/lib/camera/components/com.mi.node.aiadd.so
vendor/lib/camera/components/com.mi.node.aiasd.so
vendor/lib/camera/components/com.qti.eisv2.so
vendor/lib/camera/components/com.qti.eisv3.so
vendor/lib/camera/components/com.qti.hvx.addconstant.so
vendor/lib/camera/components/com.qti.hvx.binning.so
vendor/lib/camera/components/com.qti.node.dummyrtb.so
vendor/lib/camera/components/com.qti.node.dummysat.so
vendor/lib/camera/components/com.qti.node.eisv2.so
vendor/lib/camera/components/com.qti.node.eisv3.so
vendor/lib/camera/components/com.qti.node.gpu.so
vendor/lib/camera/components/com.qti.node.memcpy.so
vendor/lib/camera/components/com.qti.node.photosolid.so
vendor/lib/camera/components/com.qti.node.remosaic.so
vendor/lib/camera/components/com.qti.node.sr.so
vendor/lib/camera/components/com.qti.node.swregistration.so
vendor/lib/camera/components/com.qti.node.watermark.so
vendor/lib/camera/components/com.qti.node.xiaomigenderage.so
vendor/lib/camera/components/com.qti.stats.aec.so
vendor/lib/camera/components/com.qti.stats.aecwrapper.so
vendor/lib/camera/components/com.qti.stats.af.so
vendor/lib/camera/components/com.qti.stats.afd.so
vendor/lib/camera/components/com.qti.stats.asd.so
vendor/lib/camera/components/com.qti.stats.awb.so
vendor/lib/camera/components/com.qti.stats.awbwrapper.so
vendor/lib/camera/components/com.qti.stats.pdlib.so
vendor/lib/camera/components/com.qti.stats.pdlibsony.so
vendor/lib/camera/components/com.qti.stats.pdlibwrapper.so
vendor/lib/camera/components/com.vidhance.node.eis.so
vendor/lib/camera/components/com.xiaomi.node.mibokeh.so
vendor/lib/camera/components/etc/GpuKernelRepo.pb
vendor/lib/camera/components/etc/model_back.dlc
vendor/lib/camera/components/etc/model_front.dlc
vendor/lib/camera/components/etc/morpho_lowlight4.0.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high.xml
vendor/lib/camera/components/etc/morpho_lowlight4.0_adrc_high_1.xml
vendor/lib/camera/fdconfigpreview.bin
vendor/lib/camera/fdconfigpreviewlite.bin
vendor/lib/camera/fdconfigvideo.bin
vendor/lib/camera/fdconfigvideolite.bin
vendor/lib/hw/camera.qcom.so
vendor/lib/hw/com.qti.chi.override.so
vendor/lib/libarcsoft_beautyshot.so
vendor/lib/libarcsoft_dualcam_image_optical_zoom.so
vendor/lib/libarcsoft_dualcam_refocus.so
vendor/lib/libarcsoft_dualcam_refocus_front.so
vendor/lib/libarcsoft_dualcam_refocus_rear_t.so
vendor/lib/libarcsoft_dualcam_refocus_rear_w.so
vendor/lib/libarcsoft_dualcam_video_optical_zoom.so
vendor/lib/libarcsoft_high_dynamic_range.so
vendor/lib/libarcsoft_low_light_hdr.so
vendor/lib/libarcsoft_portrait_lighting.so
vendor/lib/libarcsoft_portrait_lighting_c.so
vendor/lib/libarcsoft_supernight.so
vendor/lib/libc++_shared.so
vendor/lib/libcamera_dirty.so
vendor/lib/libcamera_scene.so
vendor/lib/libcamxfdalgov7.so
vendor/lib/libcamxfdengine.so
vendor/lib/libcamxstatscore.so
vendor/lib/libcamxtintlessalgo.so
vendor/lib/libcom.qti.chinodeutils.so
vendor/lib/libFaceGrade.so
vendor/lib/libft2vendor.so
vendor/lib/libHalSuperSensorServer.so
vendor/lib/libmibokeh_845.so
vendor/lib/libmmcamera_faceproc.so
vendor/lib/libmmcamera_faceproc2.so
vendor/lib/libmpbase.so
vendor/lib/libnanopb.so
vendor/lib/libremosaic_daemon.so
vendor/lib/libSNPE.so
vendor/lib/libSuperSensor.so
vendor/lib/libSuperSensorCPU.so
vendor/lib/libswregistrationalgo.so
vendor/lib/libsymphony-cpu.so
vendor/lib/libsymphonypower.so
vendor/lib/libtonemapalgo.so
vendor/lib/libvidhance.so
vendor/lib/libXMFD_AgeGender.so
vendor/lib/lib_denoiser3.so
vendor/lib/mibokeh_845_opencl.bin
vendor/lib64/libcamxfdalgov7.so
vendor/lib64/libcamxfdengine.so
vendor/lib64/libcamxstatscore.so
vendor/lib64/libnanopb.so
vendor/lib64/libremosaiclib.so
vendor/lib64/libremosaic_daemon.so
vendor/firmware/bu64748gwz.prog
vendor/firmware/CAMERA_ICP.elf
vendor/firmware/dipper_ois.coeff
vendor/firmware/dipper_ois.prog
vendor/firmware/dipper_ois_liteon.coeff
vendor/firmware/dipper_ois_liteon.prog
Click to expand...
Click to collapse
Well done, That's great!!!
Hoping to see a fully working android 12 and MIUI 13 soon on our MI8
So, after replacing some audio policy files from /vendor/etc, the sound comes out normally. However, I still have bugs such as slow videos and silent sounds coming as media when earphones are not connected. Are there some files at /vendor/etc to be replaced? I haven't found anything else, yet
(Also, I haven't looked for the required files for NFC support)
OK, now it's ported with no bugs.
Missing features: NFC support (Due to my inexperience, I cannot make bootable system and vendor .img files by using image kitchens and it's more difficult to set the correct permissions to files in the /bin folders from recovery)
The files to be changed are mentioned in this uploaded .txt file
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Thanks for sharing your progress, its exciting indeed.
Is it possible for you in the future to share a simpler way for us non advanced users to easily upgrade to MIUI 13, e.g through recovery zip from TWRP.
Because I don't own these ROM's, please check some Telegram channels. The file name of this one (with the mentioned changes) may remind you something
Advanced Gears said:
Hello guys,
After a little research, I have successfully ported MIUI 13 (v22.2.17) to Mi 8. I do not have any permissions to share the changed files as a rom, so I am writing this guide. I hope it will help
TO BEGIN WITH, WE NEED TO DOWNLOAD THE FOLLOWING FILES:
1) MIUI 13.0.10 for Mi 8
2) POCO OS for Pocophone F1 (choose the latest)
3) A custom kernel (personally, I prefer No Gravity Kernel v2.4.1)
4) An image extractor you prefer (Brotli Extractor, Jancox Tool, etc.)
AND HERE WE START:
--> Firstly, we extract the 2nd zip file using the image extractor (4) [vendor patch]
--> While waiting, we extract the same zip (the 2nd one) with a common extractor (such as WinRAR) and take system.img and boot.img [base "system" and "boot"]
--> Then, we extract the 1st zip and take vendor.new.dat.br, vendor.patch.dat, and vendor.transfer.list and META-INF and we navigate to META-INF/com/google/android and edit updater-script replacing the following lines: [base "vendor"]
Code:
ui_print("Patching vendor image unconditionally...");
show_progress(0.500000, 0);
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
set_progress(1.000000);
When done, we add the above vendor files and META-INF folder to (another) archive
--> When the extraction with the image extractor (4) finishes, we navigate to vendor and copy the following folders [vendor patch continue]:
* overlay
* etc/selinux
IN THE END WE HAVE...
> To flash system.img as image ["base system" step]
> To flash the .zip archive which only contains the vendor files (and, obviously, "META-INF") ["base vendor" step]
> To mount "/vendor", to delete the folders "overlay" and "etc/selinux" and, then, to replace these from the ["vendor patch continue" step]
> To flash the extracted boot.img ["base boot" step]
> (And, finally,) to flash the custom kernel (3), which makes the rom bootable.
Due to deodex, the whole boot should be finished in approximately 4 minutes
MISSING FEATURES:
> No NFC support
> No multilingual rom (but there are also some MIUI R roms here)
SPECIAL THANKS TO:
> romKTpro (for POCO OS)
> UOTAN (for vendor files)
> Tech Karan (for his similar guide)
> and to all the other developers who made the required and useful tools and mods
Click to expand...
Click to collapse
Hello, is this manual suitable for mi mix 3?
Advanced Gears said:
Hello, again. Because the previous guides were time-consuming, I have made a patch which replaces all the required files. Unfortunately, I have not managed to add NFC support.
Instructions:
We flash system.img, vendor.img, cust.img (system_ext.img), boot.img, DFE, XD/Etude kernel
We mount /vendor
We flash the patch
Click to expand...
Click to collapse
Hello I am new to this, but I already have an unlocked bootloader.
Can you please confirm :-
1. Which tool I need to use to flash the ROM .img files, Xiaomi Flash Tool?
2. Which latest MIUI 13 ROM is most suitable, POCO OS •13.0.12.0 EU [ IGNITION 4.0 ].zip?
3. Which beryllium2dipper-patch.zip patch I need to use for the Mi 8?
4. Only bug is NFC right? Will audio, camera, safetynet, banking apps, xiaomi account and cloud work?
Edit:
I am not sure if the steps are correct and which beryllium2dipper-patch.zip patch file I should use
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Advanced Gears said:
To begin with, the steps are not difficult. we have to flash the following files:
--> system.img, cust.img (system_ext), vendor.img (the patched one), boot.img
as images from a recovery which supports cust images, such as OrangeFox.
--> DFE (disable forced encryption), the latest stable patch, permissiver and XD kernel as .zip files
--> base.apk is Mi Video if someone wants to install the provided version and not this from Play Store, APKmirror etc..
(?)> If the ROM is not bootable, we have to make sure the previous ROM was not encrypted or /data is formatted.
(?)> And, of course, we also need to have the latest firmware from Xiaomi (Global/China)
Moreover, the bugs are the same: NFC, perhaps AOD (some developers have removed it on Poco, on Ignition 2.0 there is AOD support) and Dual GPS (but normal GPS works normally). Only these.
When it comes to Ignition 4.0, both are nice. Personally, I would choose the first version of Ignition 4.0 (not the reuploaded one), which is probably more stable.
Last but not least, it is likely that these ROM's can be ported to other devices, such as Mi Mix 3 (similar device), in case a suitable kernel is found and the correct proprietary files are replaced (usually, by testing).
Click to expand...
Click to collapse
Thanks for the explanation, I have flashed successfully with minor tweaks.
To resume:-
Prerequisites:
1. MIUI13 Android 12 firmware (POCO OS IGNITION 2.0) feels more responsive
2. Phone ROM with unlocked bootloader and OrangeFox recovery.
3. Phone ROM must be on latest Official ROM (Global/China)
4. Phone ROM must not encypted or /data formatted
Boot to OrangeFox recovery:
1. Flash .img files; system.img, cust.img (system_ext), vendor.img, boot.img (POCO OS IGNITION 2.0)
2. Flash .zip files; DFE (disable forced encryption), latest stable beryllium2dipper-patch, permissive and XD kernel
3. Reboot phone to system and enjoy
Edit:
I have reverted back to my old ROM (xiaomi.eu MIUI12.5} as I feel its more polished and optimised but its nice to see Android 12 with MIUI13 fully working ported to the Mi 8.
This is two version ,rec and boot , of TWRP
I flash it yesterday it working flawless.
Cool
tze_vitamin said:
This is two version ,rec and boot , of TWRP
I flash it yesterday it working flawless.
Click to expand...
Click to collapse
May I ask your phones version, A12 or A13?
A13... I just unpack REC folder and in my old recovery flash new .img a13 recovery, reboot to recovery choose flash current recovery and that's it
Im on A12 using this twrp. Its fine, but system is RO, dont know how to make it RW.
Edit: already RW.
May I ask what is the difference between the two files?
I flashed the recovery image and it is fully working. I am not sure what the boot image is for
Is this recovery the same as this one?
Recovery for Xiaomi devices - Browse /diting at SourceForge.net
List of relevant recovery in one place
sourceforge.net
I will only flash it once the stable miui14 for Diting is available.
Really need the camera to work properly
I.m.Tuga said:
Is this recovery the same as this one?
Recovery for Xiaomi devices - Browse /diting at SourceForge.net
List of relevant recovery in one place
sourceforge.net
I will only flash it once the stable miui14 for Diting is available.
Really need the camera to work properly
Click to expand...
Click to collapse
It will work when global Rom got update. It will be during this month
update:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
update:
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Update A12/A13
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Update A12/A13
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
NOSS8 said:
Update A12/A13
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/diting/
Click to expand...
Click to collapse
Is this for
fastboot flash recovery_ab *.img
or
fastboot boot *.img
Thanks
dagoban said:
Is this for
fastboot flash recovery_ab *.img
or
fastboot boot *.img
Thanks
Click to expand...
Click to collapse
For your device only the REC version is posted on this site.
fastboot flash recovery_ab *.img
After installation use
fastboot reboot recovery
Update
Recovery for Xiaomi devices - Browse /diting at SourceForge.net
List of relevant recovery in one place
sourceforge.net
Im on xiaomi.eu 13.0.10.0SLFCNXM stable room A12, using this twrp (v7.5). Its fine for backup and restore, but system is RO, dont know how to make it RW.
Help please
lmt399 said:
Im on xiaomi.eu 13.0.10.0SLFCNXM stable room A12, using this twrp (v7.5). Its fine for backup and restore, but system is RO, dont know how to make it RW.
Help please
Click to expand...
Click to collapse
A/B partitions +Android restrictions.
You can try this kind of script (good luck).
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
NOSS8 said:
A/B partitions +Android restrictions.
You can try this kind of script (good luck).
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I'll try
Update 7.7
2.71 GB folder on MEGA
32 files and 13 subfolders
mega.nz