The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
------
I made a script to remove the system_ext partition in boot.img: entr0pia/XPatch: Remove the system_ext Partition ... You can try to patch the boot.img by yourself.
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Hey man great work! wanted to tell u that version 58.1.A.5.55 is out, maybe whenever u r free u could release the new boot.img for it? ty for ur work.
Haithamraid said:
Hey man great work! wanted to tell u that version 58.1.A.5.55 is out, maybe whenever u r free u could release the new boot.img for it? ty for ur work.
Click to expand...
Click to collapse
I Don't think this is needed anymore. Magisk had some changes in the meantime, which could put out working Images now...
Not sure about this but I would wonder if it isn't fixed already (Pixel Devices also had issues).
Miustone said:
I Don't think this is needed anymore. Magisk had some changes in the meantime, which could put out working Images now...
Not sure about this but I would wonder if it isn't fixed already (Pixel Devices also had issues).
Click to expand...
Click to collapse
i tried the latest canary version to patch the boot file and it still bootloops, if it is possible to create the latest one it would be lovely, until magisk sort their stuff out
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Hello, I've flashed your image but safetynet verification fails Also some apps are randomly crashing and idk what to do
robi101012981 said:
Hello, I've flashed your image but safetynet verification fails Also some apps are randomly crashing and idk what to do
Click to expand...
Click to collapse
Have you enabled MgaiskHide?
fengmubai said:
Have you enabled MgaiskHide?
Click to expand...
Click to collapse
Of course, otherwise I couldn't use banking apps such as Revolut
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Wow you are an absolute legend, was tearing my hair out as to why my 5 II kept bootlooping and this totally fixed it
robi101012981 said:
Hello, I've flashed your image but safetynet verification fails Also some apps are randomly crashing and idk what to do
Click to expand...
Click to collapse
https://twitter.com/i/web/status/1382563209995964418
The API key for safetynet verification is/was down, use another app from the play store and you will see that you still can pass safetynet
Goon Squad said:
Wow you are an absolute legend, was tearing my hair out as to why my 5 II kept bootlooping and this totally fixed it
https://twitter.com/i/web/status/1382563209995964418
The API key for safetynet verification is/was down, use another app from the play store and you will see that you still can pass safetynet
Click to expand...
Click to collapse
Thanks, but meanwhile I've sold my device cause it's a bad one.
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Update to HK_58.1.A.5.55
Hello,
The fixed boot image patched with magisk 22.1 for Xperia 5II (XQ-AS52_Customized EEA_58.1.A.5.159) is shared there on my drive.
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Update to HK_58.1.A.5.159
fengmubai said:
Update to HK_58.1.A.5.159
Click to expand...
Click to collapse
I can't seem to get your HK_58.1.A.5.159 to work like the previous versions did. I even tried patching the file myself but it doesn't work on my AS72 HK device. Is there any particular magisk version you're using? I tried 23.0, 22.0 and 22.1 but none of them worked and I bootlooped every time
Goon Squad said:
I can't seem to get your HK_58.1.A.5.159 to work like the previous versions did. I even tried patching the file myself but it doesn't work on my AS72 HK device. Is there any particular magisk version you're using? I tried 23.0, 22.0 and 22.1 but none of them worked and I bootlooped every time
Click to expand...
Click to collapse
22.1, and you can update it after boot into system. However, it works correctly on my device.
This worked perfectly! Thank you so much for this!
Update to HK_58.1.A.5.222A
fengmubai said:
The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive.
If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it.I have only patched the image for AS72, Customized HK and it works on my device. If you use other devices/ROMs, follow the solution and try youself.
Click to expand...
Click to collapse
Update to HK_58.1.A.5.280, automatically patched factory boot.img by the script: XPatch. You can try to patch the boot.img with the script by yourself.
Hello,
The fixed boot image patched with magisk 23 for Xperia 5II (XQ-AS52_Customized_EEA_58.1.A.5.330) is shared there on my Google Drive.
Update to HK_58.1.A.5.330
We've been tracking kernel updates and repacked + Magisk-patched versions in this thread since Jan. I suggest posting your work there so that it's all in one place.
Related
Orginal post:
https://www.google.pl/amp/s/forum.x...lopment/experimental-phh-treble-t3709659/amp/
Downolad Version V10:
With gapps and Su:
https://androidfilehost.com/?fid=746010030569954763
Without gapps and Su
https://androidfilehost.com/?fid=673956719939820512
Installation:
- First, you MUST be running a stock Android 8.0 ROM.
- Obviously, unlock your bootloader
- Download the correct system.img variant (see list of devices above, and dowload links below)
- Flash the system.img
- Do a Factory reset
- Reboot
What nor working?
- Broken camera because DRM KEY...
But all probably work pretty good!
For Xperia XZ1 and XZ1 COMPACT FLASH ONLY A version!!
Changeleog
v10: (2018-02/18)
- Android 8.1 !
- Includes versioned vndk, so devices running both 8.1 and 8.0 should work.
i heard google camera hdr+ working on android 8.1. is it working? What about battery efficiency?
Idk i not test this because my phone go to repair. I think camera not work on all apk. Because drm key broken but i don't know on 100%.
ok I will try it
eggimong said:
ok I will try it
Click to expand...
Click to collapse
Give screen plz. I will add on #1 post. And thank u!
i stuck on bootloop..
i flashed the file include su and gapps on 47.1.A.12.75. it stuck at sony boot logo then i flashed nosu and it stuck at boot animation
then i downgraded xz1 on 47.1.A.8.49 and flashed both but same result
i am not good at english :/
eggimong said:
i heard google camera hdr+ working on android 8.1. is it working? What about battery efficiency?
Click to expand...
Click to collapse
Maybe off topic but in Xperia XZ, Google camera hdr mod work fine without DRM keys in AOSP rom. I guess should work the same for XZ1
snake218 said:
Maybe off topic but in Xperia XZ, Google camera hdr mod work fine without DRM keys in AOSP rom. I guess should work the same for XZ1
Click to expand...
Click to collapse
you're right I installed aosp 8.1 (https://forum.xda-developers.com/xperia-xz1/how-to/aosp-8-1-t3750951)because project treble cause bootloop. it works hdr+!
eggimong said:
you're right i installed aosp 8.1 (https://forum.xda-developers.com/xperia-xz1/how-to/aosp-8-1-t3750951)because project treble cause bootloop. It works hdr+!
Click to expand...
Click to collapse
but their are limitation from sony like back cemra is set to 17 mp and iso set to 800 only they are in kernel i am working on it i am now learning kernel patching i have not done before lets hope for best
You can use TWRP brush into it？
V11 released
who can test that version?
I'll give it a shot
Download link?
N1ghtr08d said:
Download link?
Click to expand...
Click to collapse
Can be found in the original post from the treble forums.
Here is the post:
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Good luck, let us know.
Redcalibur said:
Can be found in the original post from the treble forums.
Here is the post:
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
Good luck, let us know.
Click to expand...
Click to collapse
Complete waste of time. I tried several different ways to flash this ROM but it's just not compatible with the XZ1 8341. Now i have to flash back to stock and the restore my TWRP backup.
Incompatible ROMs should NOT be posted on these forums unless they have been tested at the very least by the OP.
N1ghtr08d said:
Complete waste of time. I tried several different ways to flash this ROM but it's just not compatible with the XZ1 8341. Now i have to flash back to stock and the restore my TWRP backup.
Incompatible ROMs should NOT be posted on these forums unless they have been tested at the very least by the OP.
Click to expand...
Click to collapse
Hey, I'm asking this just to be sure that we can consider the rom incompatible for our device.
You used the rom that said A-only, right? Since the thread states that the XZ1 only supports build A-only. If so, we could try mentioning the issues you experienced in the original thread.
Thank you for your time.
Edit: I've just seen your posts in the original thread. Sorry for the quote.
No it's ok, I don't mind helping, it's just frustrating. I flashed the A only nosu vanilla version, then booted into TWRP and performed a factory reset and when I rebooted into system the phone just hangs on the Sony boot screen for ages then reboots and does the same thing again and again.
I had the same experience with all A-only versions.
N1ghtr08d said:
No it's ok, I don't mind helping, it's just frustrating. I flashed the A only nosu vanilla version, then booted into TWRP and performed a factory reset and when I rebooted into system the phone just hangs on the Sony boot screen for ages then reboots and does the same thing again and again.
Click to expand...
Click to collapse
try this version, for me on xz1c it loads to the inscription of "xperia", and it hangs https://drive.google.com/open?id=118pwXm2UK95AaYTvIfDAiWDBk-rUBh6Q
Infinite restart animation………………cnm?
I am trying to install magisk instead of supersu on my stock .154.
I flashed magisk v. 16 in twrp but I ended in a bootloop.
Am I missing something??
Supersu are working fine, but i would like to try magisk.
Thanks in advance:good:
torben5247 said:
I am trying to install magisk instead of supersu on my stock .154.
I flashed magisk v. 16 in twrp but I ended in a bootloop.
Am I missing something??
Supersu are working fine, but i would like to try magisk.
Thanks in advance:good:
Click to expand...
Click to collapse
Are there really no one that could give me some help installing magisk instead of supersu?
torben5247 said:
I am trying to install magisk instead of supersu on my stock .154.
I flashed magisk v. 16 in twrp but I ended in a bootloop.
Am I missing something??
Supersu are working fine, but i would like to try magisk.
Thanks in advance:good:
Click to expand...
Click to collapse
You need to patch the kernel using rootkernel or use a custom kernel.
Deleted
QWERTYsystems said:
You need to patch the kernel using rootkernel or use a custom kernel.
Click to expand...
Click to collapse
Finally got it working.
I had to flash boot.img moded using rootkernel.
The boot.img i had was moded using ta poc tool and that was causing the boot loop.
So magisk is working now!
Thanks for the reply.:good:
torben5247 said:
Finally got it working.
I had to flash boot.img moded using rootkernel.
The boot.img i had was moded using ta poc tool and that was causing the boot loop.
So magisk is working now!
Thanks for the reply.:good:
Click to expand...
Click to collapse
Hi i'm glad that you solve it @torben5247
But, can you provide me working link for those boot image or kernel? Because I need to use it too but still didnt find any clue how it works.
I'm really want to use banking apps with root permission so Magisk is my savior
Defforest said:
Hi i'm glad that you solve it @torben5247
But, can you provide me working link for those boot image or kernel? Because I need to use it too but still didnt find any clue how it works.
I'm really want to use banking apps with root permission so Magisk is my savior
Click to expand...
Click to collapse
Root kernel is a tool. The link is to the root kernel thread. All instructions are available in the thread.
Link:
https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
any help for step install magisk in Z5 Compact 7.1 N E5823 ?
Hello people
As we all know we had some issue that we can't use magisk v16.3
but get stuck forever with magisk v14.5...
But no now not anymore, we can use finally Magisk v16.3 ^^
It's a flashable kernel for fw 41.3.A.2.107.
Note:
This work on eXistenZ v5.0.0
Sony stock roms
Make always a back up before flash
Leave a feedback
.. Install instructions ..
1) Flash the kernel.
https://mega.nz/#!mpByDbbS!Gi1wHiGWihcN2G8AUColWatlNtcirJAbAllXQJnOnEE
2) Flash magisk.
https://mega.nz/#!WxAkSQTD!2NzFRxRYeXZ1NvVpC3ydqMiFhudLQtIr8Y2QyNVHg20
3) Flash SElinux manager and select permissive mode.
https://mega.nz/#!jsACgBAB!J58SSny5WBaKtbuD1QmCCq4sFLfhQJ-z0JucNMQiCPQ
4) Wipe cache and dalvik
5) Reboot
... Credits ...
Niaboc79, Serajr & Jitz975
. Proof .
Res
Pandemic said:
Res
Click to expand...
Click to collapse
Before root your machine has backup TA?
hoaiphong1 said:
Before root your machine has backup TA?
Click to expand...
Click to collapse
Always for in case due your drm keys because you can root only with unlocked bl.
It works on stock
Great happy to hear i will update the thread tonight
I just realized that /data/magisk folder is missing and i can't install modules. But with magisk 16.0 everything is OK
Zheka2015 said:
I just realized that /data/magisk folder is missing and i can't install modules. But with magisk 16.0 everything is OK
Click to expand...
Click to collapse
No issues here mate maybe you need to enable internet and re open magisk again because you need to install any module in magisk itself under downloads/modules.
no one have belong by this i guess, i should never buy XZs, this topic is indeed dead as they say !! really dissapointed and this kernel works also on dual, but thankfull people are hard to find
Pandemic said:
Always for in case due your drm keys because you can root only with unlocked bl.
Click to expand...
Click to collapse
hello, there isnt a way to root with locked bootloader?
-__-
No !
Hi,
I assume the rootkernel includes DRM fix as well to get back all xperia features?
CressKH said:
Hi,
I assume the rootkernel includes DRM fix as well to get back all xperia features?
Click to expand...
Click to collapse
No but update this weekend
Thanks for the hardwork.
Another question, since we can't backup TA partition on XZs which was released on Nougat, is there any feature that is lost permanently even with DRM fix?
I've finally figured this out!
This is a scientific breakthrough! Not really... lol
So, I've managed to make SafetyNet pass using a "custom" Magisk build.
I grabbed it from here and so far I've flashed this build and it coaxed SafetyNet into passing. On one treble ROM, ToxycOS, it completely made SafetyNet pass, both ctsProfile and basicIntegrity. On RR official though, it only made basicIntegrity pass. However, that's completely better than nothing at all!
This is how I got SafetyNet to pass completely, it only works if basicIntegrity is passing while ctsProfile if failing.
•Magisk builds: https://github.com/ianmacd/MagiskBuilds
•Magisk I flashed that got SafetyNet to pass: https://github.com/ianmacd/MagiskBuilds/blob/master/Magisk-v16.5-20180621-ianmacd.zip
•Guide to get SafetyNet to pass: https://github.com/phhusson/treble_experimentations/issues/116
Thanks to @topjohnwu for making Magisk possible
Big thanks to @ianmacd for making these Magisk builds
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
yo you can always change the device's fingerprint in order to make safetynet pass using a magisk module
crayonicle said:
Why did I post this?
I posted this because Magisk 16.6 kept on bootlooping for me, no matter what I did. I'm pretty sure it patches the kernel instead of the ramdisk so it causes a bootloop, again, not 100% sure what it's doing, but either way, it's bootlooping for me. These builds *hopefully* don't bootloop. I flashed 16.5 and it's working great.
Click to expand...
Click to collapse
Which version on 16.5 did you use i meant the build date
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
It works on BDN-L34
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
IonDEfeso said:
I passed the test successfully following this guide.
I used a Huawei Mate SE (BND-L34) running phusson's [AOSP 8.1 - Phh-Treble] v22. Then downloaded iammacd'smagisk build that the op provided and zip flashed it through TWRP. Then logged on android and uninstalled the magisk manager app (which was an older version) and then downloaded the newest one available and installed it as an apk. After that I opened the app and went to "downloads" and looked for MagiskHide Props, installed the module and rebooted phone. Then as the op did, I followed cawilliamson's instructions on how to set up MagiskHide Props the only difference being that I set up the fingerprint using Huawei mate 9 since Honor 7x were not listed.
I was running and failing at different points the SafetyNet test until I completed the process. Thats it, thanks to crayonicle for research and compiling such great information and to the other people that made it possible. :good:
Click to expand...
Click to collapse
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
chrisaw said:
Thanks to everyone but the guy who actually discovered and documented this? Hmph!
Click to expand...
Click to collapse
I got his permission to post this on Telegram.
Don't worry.
krlosoul said:
adb debug working?
huawei p8 lite 2017
phh treble rom gsi vanilla v22
Click to expand...
Click to collapse
It seems to be. You can always try and test it yourself.
Ashley david said:
Which version on 16.5 did you use i meant the build date
Click to expand...
Click to collapse
2018-6-21
BTW ive just updated to the "MagiskManager-v16.8-2018071902" which is ianmacd's lastest build posted and (first of all isnt bootlooping) and is also passing all of the SafetyNet tests. Also installed the lastest version of the Magisk Manager app 5.8.3 (129) successfully. Not sure if is helpful to report that but since it boot-looped me when I tried to update it last time, so now I consider it an achievement lol. I first uninstalled magisk manager through android uninstall (not the magisk uninstall, which unroots you and delete modules) then installed the new version manually.
-----------------------------------------------------------------------
mcc2005 said:
Have an Mate 9. What can I do for now? The Magisk-v16.5-20180621-ianmacd.zip dosen´t work for me. It´s bootloped!
Click to expand...
Click to collapse
I am no expert but what ROM are you running? I used to have RRO v6 and the boot loping happened to me when I updated magisk to lastest version through the app. Try flashing the older magisk you had before?
If not I think you will have to go back to stock which is what I had to do when that happened to me. I used a stock oreo zip rom for my device (BND-L34) and this guide now since you have the MATE 9 I dont know what the procedures and files needed for that one.
Using a BDN-L34 (Mate SE)
Back to report that I successfully flashed [8.1.0][TREBLE] Pixel Experience [AOSP][r36][2018/07/14] by jhenrique09 (8.1.0-20180714-0200-OFFICIAL) and sucessfully installed the last Magisk version (and app) and passed all the tests (even better it help me bypass the "google uncertified device" messages i was getting). To pass the SafetyNet I downloaded the MagiskHide on the Magisk app "Downloads" then ran a terminal emulator with the following commands.
Code:
su
props
Then only needed to set the fingerprint by doing:
1 > F > * > ** > Y > Y (This last option will make the device reboot, needed to pass SafetyNet, but you can reboot later by writing N)
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
IonDEfeso said:
*Note that you need to select your phones brand in the options given there.
**Select your phone model (or any other model with the same fingerprint reader or compatibility, guess you can try out different models and check if any works, at your own risk though, I dont know if there could be grave repercussions.)
Click to expand...
Click to collapse
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
crayonicle said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
Yeah I selected honor 9 for my Mate SE, I just mentioned that since I dont know how serious would it be the implications of selecting a totally different model for another phone but yeah just didn't wanted to tell people to select whatever and then suddenly their fingerprint isn't working or something like that haha. Btw i used the same guide you provided the first time i did everything he pointed but then realized that only the first step was enough so only did that.
steven360 said:
You dont exactly need to select your device model. I followed this guide using an Honor 7x. Worked well.
Click to expand...
Click to collapse
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
HourlongTuna5 said:
I did it on a Moto G5 with the latest Viper OS Oreo release, it doesn't work, can you help me please?
Click to expand...
Click to collapse
I'm afraid that this fix might be for Huawei only (no proof yet), maybe perhaps you can try with a similar moto phone?
Based on https://developer.sony.com/develop/...osp-build-instructions/build-aosp-android-12l
No changes. Completely Vanilla for now. Use https://developer.sony.com/develop/open-devices/downloads/software-binaries/ Kumano for Xperia 5
Download: https://sites.google.com/view/miustone/DIOS
Magisk GApps: https://sourceforge.net/projects/litegapps/files/litegapps/arm64/32/lite/
Magisk MicroG: https://github.com/nift4/microg_installer_revived
You may want to patch the boot.img with Magisk before flashing...
Cameras arent working yet see: https://github.com/sonyxperiadev/bug_tracker/issues/770
ALSO LOOKING FOR D!OS TESTERS AND DEVS TO JOIN MY NEW OS... PM ME!
CAUTION! THIS DOES WIPE ALL YOUR DATA!
Instructions:
Extract the Zip File to Your Fastboot Destination
Extract the Xperia Binaries Image to Your Fastboot Destination
Rename the Xperia Binaries Image to oem.img
Double Click the AOSXP-FLASH-XXX.bat File. Enjoy the Magic
Hello, there are screen shots
simple aosp, camera not working, no google apps, mtp, wi-fi not working
qwerta12 said:
simple aosp, camera not working, no google apps, mtp, wi-fi not working
Click to expand...
Click to collapse
"No changes. Completely Vanilla for now."
Working on including GApps and fixing the Issues rn... More coming soon!
TWRP and LOS coming afterwards...
Optimized some Things. New Builds comming today...
Miustone said:
Optimized some Things. New Builds comming today...
Click to expand...
Click to collapse
I'm waiting, I'll flash it as soon as you post it
qwerta12 said:
I'm waiting, I'll flash it as soon as you post it
Click to expand...
Click to collapse
I ran into some issues last night. Solved all of the issues but i have bootloops with OpenGApps included :/ Need to put more time into that...
Miustone said:
I ran into some issues last night. Solved all of the issues but i have bootloops with OpenGApps included :/ Need to put more time into that...
Click to expand...
Click to collapse
I think you can try to enable NikGapps or FlameGapps, maybe this is the problem
qwerta12 said:
I think you can try to enable NikGapps or FlameGapps, maybe this is the problem
Click to expand...
Click to collapse
I was always an OpenGApps user but seems like they don't put that much effort into it still... Think ill go with BiTGApps. Ill check Your mnetioned ones too. Thx
Miustone said:
I was always an OpenGApps user but seems like they don't put that much effort into it still... Think ill go with BiTGApps. Ill check Your mnetioned ones too. Thx
Click to expand...
Click to collapse
Good luck to you, is it working out?
qwerta12 said:
Good luck to you, is it working out?
Click to expand...
Click to collapse
Thanks! I have actually issues after trying to fix Wifi... Think ill start off with TWRP for now and AOSP after that. So we can flash external GApps (or not if wanted). Only Problem is that we have to use a Recovery inside the Kernel Image on 2019 Xperias. Means i have to choose a Kernel. Since we dont get Updates anymore would i bet on the AOSP Kernel since it is what we want to use anyways... Ill ask out the SODP Devs about some Help with that. Xperias from 2020+ can just grab a Recovery Image without the need to choose a Kernel with it. They also use Dynamic Partitions which is different from our 2019 Xperia A/B Static Partitions...
Lot of work to do but think it will go fast with some help
Miustone said:
Thanks! I have actually issues after trying to fix Wifi... Think ill start off with TWRP for now and AOSP after that. So we can flash external GApps (or not if wanted). Only Problem is that we have to use a Recovery inside the Kernel Image on 2019 Xperias. Means i have to choose a Kernel. Since we dont get Updates anymore would i bet on the AOSP Kernel since it is what we want to use anyways... Ill ask out the SODP Devs about some Help with that. Xperias from 2020+ can just grab a Recovery Image without the need to choose a Kernel with it. They also use Dynamic Partitions which is different from our 2019 Xperia A/B Static Partitions...
Lot of work to do but think it will go fast with some help
Click to expand...
Click to collapse
it's very good, I think everything will work out
if you want i could help as a tester
WiFi Fix is Merged
[9.12.r1] base_sm8150: Enable QCACLD WLAN by bartcubbins · Pull Request #116 · sonyxperiadev/kernel-defconfig
Enable Qualcomm Atheros CLD WLAN driver. Signed-off-by: Pavel Dubrova [email protected]
github.com
I'll do a resync with April Security Patch and all Apps removed. I'll make TWRP based on it so we can flash GApps and Magisk stuff...
New Build uploading. No Apps included so consider using Magisk Micro G if You want to use it as daily for now.
It's android-12.1.0_r4 so 12L April Security Patch. Wifi should work now. For Camera Please try GCam by BSG or Open Camera. TWRP Comes soon...
Releases · nift4/microg_installer_revived
Install microG GmsCore, GsfProxy, FakeStore (or Play Store if you want so) and MapsV1 to /system/ - nift4/microg_installer_revived
github.com
Miustone said:
New Build uploading. No Apps included so consider using Magisk Micro G if You want to use it as daily for now.
It's android-12.1.0_r4 so 12L April Security Patch. Wifi should work now. For Camera Please try GCam by BSG or Open Camera. TWRP Comes soon...
Releases · nift4/microg_installer_revived
Install microG GmsCore, GsfProxy, FakeStore (or Play Store if you want so) and MapsV1 to /system/ - nift4/microg_installer_revived
github.com
Click to expand...
Click to collapse
Is it possible to embed a stock camera application into the firmware? in such a rom it would be very useful
qwerta12 said:
Is it possible to embed a stock camera application into the firmware? in such a rom it would be very useful
Click to expand...
Click to collapse
Like that... https://github.com/GrapheneOS/Camera/releases ?
Upload went wrong. Restarted. Sorry! Kernel need to be redone for the Wifi fix so it is still broken on the actual upload. Ill work on that...
Miustone said:
Like that... https://github.com/GrapheneOS/Camera/releases ?
Upload went wrong. Restarted. Sorry! Kernel need to be redone for the Wifi fix so it is still broken on the actual upload. Ill work on that...
Click to expand...
Click to collapse
friend, it's okay, everything is fine, it will still work out by drawing
but about the camera, yet I was talking about adding a camera from the Sony stock firmware...
is there dual-sim support working?
Miustone said:
"No changes. Completely Vanilla for now."
Working on including GApps and fixing the Issues rn... More coming soon!
TWRP and LOS coming afterwards...
Click to expand...
Click to collapse
PLeeasssse, leave the Gapps optional, as they could be installed afterwards anyway! This leaves the choice to go for MicroG .
qwerta12 said:
friend, it's okay, everything is fine, it will still work out by drawing
but about the camera, yet I was talking about adding a camera from the Sony stock firmware...
Click to expand...
Click to collapse
I am keeping focus on excluding all the Stock stuff. There will be no Stock Camera or other Stock Apps. But GCam Support and an own Camera App based on the new CameraX stuff are the Goal...
Ermann123 said:
is there dual-sim support working?
Click to expand...
Click to collapse
Yes
Ermann123 said:
PLeeasssse, leave the Gapps optional, as they could be installed afterwards anyway! This leaves the choice to go for MicroG .
Click to expand...
Click to collapse
I will keep that in Mind!