Develop Bugs

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

[Kernel][Stock]MIUI-V3

===========================================
CAUTION:
===========================================
1) Needs an unlocked phone
2) This kernel is meant for MIUI Roms
3) I did not build this from source, i just edited the stock boot.img and packed it again
3) I am not responsible if your phone dies or the earth ends,...
4) its always better to install this via a "fastboot boot boot.img" command, if it doesn't work, you can just reboot & you will get back to your original setup!!
===========================================
FEATURES:
===========================================
1) Enabled fingerprint wakeup --> does not work on Dev roms
2) Set the Min GPU speed from 214Mhz to 133Mhz
3) Available for Dev(Experminental) & Global MIUI Roms
===========================================
Instructions(TWRP Method)
===========================================
-> download your zip file
-> flash it in TWRP recovery
Downloads
MIUI GLOBAL ROM
MIUI-V3-8.0.5.0.zip
MIUI-V3-8.0.2.0.zip
===========================================
Instructions(fastboot method)
===========================================
-> download the required boot.img
-> reboot phone into fastboot mode ( VOL DOWN + Power)
-> open command prompt where the boot.img is located and type
*replace the "boot.img" with the img file you downloaded
for permanent solution
Code:
fastboot flash boot boot.img
fastboot reboot
for temporary solution (reverts back to your previous boot.img once you reboot)
Code:
fastboot boot boot.img
fastboot reboot
Downloads
*Tested and working perfectly on the following global ROMs!
#you can test on other MIUI ROMs (China,dev etc) & give your feedback
MIUI GLOBAL ROM
MIUI-V3-8.0.5.0.img
MIUI-V3-8.0.2.0.img
MIUI GLOBAL DEV ROM
MIUI-V3-6.10.20.img -Experminental
MIUI Xiaomi.eu DEV ROM
MIUI-V3-xiaomi.eu-6.10.20.img -Experminental
PREVIOUS FILES
Code:
[B][U]MIUI GLOBAL ROM[/U][/B]
[URL="https://mega.nz/#!Co9SkZTT!JOlDZH8_q__e0__QSrnN-t2ET9626s4aQ5BRB_2Rnfk"]MIUI-V2-8.0.5.0.img[/URL]
[URL="https://mega.nz/#!HxUFgZiB!UpLbLIYvg5Wp7s8d_P7zFdvrljVVHerCrFcRUNsgYGo"]MIUI-V2-8.0.2.0.img[/URL]
[URL="https://mega.nz/#!X9MUUDbS!nnSMqbCpJSyyNMzOaMQOVjF5lBaVwpuoeD8RJZXS2I4"]MIUI-V1-8.0.5.0.img[/URL]
[URL="https://mega.nz/#!q9c13bpI!kV0lFh_GtpVq4jhAUPblwICfob7227mCVx5LR4fq4tc"]MIUI-V1-8.0.2.0.img[/URL]
[B][U]MIUI GLOBAL DEV ROM[/U][/B]
[URL="https://mega.nz/#!K58X2KrQ!Gbmeibs-vU3eQi3ITBbAhCu9KMyVLDuPsl5svSaFuXM"]MIUI-V2-6.10.20.img[/URL]
[B][U]MIUI Xiaomi.eu DEV ROM[/U][/B]
[URL="https://mega.nz/#!r1E2VChQ!FWdPHfbL2gbJ2QDv1y5afyH0RcCxGKnS-BJg5MaMb70"]MIUI-V2-xiaomi.eu-6.10.20.img[/URL]
===========================================
Changelog:
===========================================
Code:
[B][U]V3[/U][/B]
[LIST]
[*]Revert back to default stock GPU governor
[*]maintains the min GPU Speed to 133Mhz on stock governor
[/LIST]
[B][U]V2[/U][/B]
[LIST]
[*]enabled the GPU to go to minimum frequency(214Mhz to 133Mhz)
[*]set simple-ondemand governor for GPU
[*]added Dev ROM support
[/LIST]
[I]-----------------------------------------[/I]
[U][U]V1:[/U][/U]
[LIST]
[*]initial releease
[*]enabled fingerprint wakeup
[/LIST]
===========================================
Credits:
===========================================
bgcngm- for the amazing work he has done!!
*may be there is a better way to do this instead of boot.img, i dont know it

Is ok for MIUI 8.1 (6.10.20) ? The beta dev version

GalaxyS4_Lollipop said:
Is ok for MIUI 8.1 (6.10.20) ? The beta dev version
Click to expand...
Click to collapse
You can always try this!!!
Code:
fastboot boot boot.img
If it doest work, just reboot and your back to normal!!!

*may be there is a better way to do this instead of boot.img, i dont know it
Click to expand...
Click to collapse
I take it this is achieved with a ramdisk modification that allows for
Code:
fpc_fpc1020/enable_wakeup 1
on init.target.rc?
I *think* you might get away with a flashable zip that implements this:
Code:
echo 1 > /sys/devices/soc/soc\:fpc_fpc1020/enable_wakeup
in the /etc/init.d userinit file then sets the permissions (chmod o+x?)
Not 100% sure though!

chiragkrishna said:
You can always try this!!!
Code:
fastboot boot boot.img
If it doest work, just reboot and your back to normal!!!
Click to expand...
Click to collapse
Bootloop with global devs rom 6.10.20...
Could you please mention the changes you have done bro?
So that I can edit and make them in our own modified boot.img?
It will be so thankful

ravinder0003 said:
Bootloop with global devs rom 6.10.20...
Could you please mention the changes you have done bro?
So that I can edit and make them in our own modified boot.img?
It will be so thankful
Click to expand...
Click to collapse
Sure, extract boot.img & add this
or give me the boot.img file, i will mod it and upload it,...

chiragkrishna said:
Sure, extract boot.img & add this
or give me the boot.img file, i will mod it and upload it,...
Click to expand...
Click to collapse
thanks a lot bro...

chiragkrishna said:
Sure, extract boot.img & add this
or give me the boot.img file, i will mod it and upload it,...
Click to expand...
Click to collapse
this is the boot.img from latest stock dev rom aka 6.10.20
I tried to unpack and repack but stuck at MI Logo...
thx bro

added few new things
Set the Min GPU speed from 214Mhz to 133Mhz
GPU->simple-ondemand governor
Made a dev version

Harrynowl said:
Not 100% sure though!
Click to expand...
Click to collapse
stock rom doesn't support it

chiragkrishna said:
added few new things
Set the Min GPU speed from 214Mhz to 133Mhz
GPU->simple-ondemand governor
Made a dev version
Click to expand...
Click to collapse
Thanks, I'm going to try it on Xiaomi.eu ROM, which is China Dev based and report it.
Edit: not working

Can i flash it with terminal? I dont have pc right now so.. Any way to flash it without pc?

Hey does this unlock 32gb to full speeds

Yarraque said:
Can i flash it with terminal? I dont have pc right now so.. Any way to flash it without pc?
Click to expand...
Click to collapse
no you cant, you can wait for few minutes,.. creating a flash-able zips
gowtham300 said:
Hey does this unlock 32gb to full speeds
Click to expand...
Click to collapse
it does not,..
----------------------
update: added twrp zip files,... flash them in recovery

Yarraque said:
Can i flash it with terminal? I dont have pc right now so.. Any way to flash it without pc?
Click to expand...
Click to collapse
You can flash .img via Flashify.

marcoly said:
You can flash .img via Flashify.
Click to expand...
Click to collapse
I've uploaded the recover zip files!!!

chiragkrishna said:
I've uploaded the recover zip files!!!
Click to expand...
Click to collapse
And? This is just another possibility. He can flash zip via TWRP or flash img via Flashify.

marcoly said:
And? This is just another possibility. He can flash zip via TWRP or flash img via Flashify.
Click to expand...
Click to collapse
thanks, even i didn't knew that,...

encore27 said:
Thanks, I'm going to try it on Xiaomi.eu ROM, which is China Dev based and report it.
Click to expand...
Click to collapse
have you tested it ? if you did , can you specify which version ? Thank you

harrez said:
have you tested it ? if you did , can you specify which version ? Thank you
Click to expand...
Click to collapse
you can use the following to test yourself
Code:
fastboot boot boot.img
its not permanent, for example the phone does not boot up, just hold the power button for few seconds and your phone will reboot to your previous state....
only this command is permanent
Code:
fastboot flash boot boot.img

[AOKP][PROJECT_TREBLE][8.1.0][a/b devices only][4/2/18]

This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that

First!
Sent from my Pixel 2 XL using Tapatalk

slothdabski said:
First!
Click to expand...
Click to collapse
Crap missed it..

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
does google camera work with hdr+? do you get unlimited photo storage?

sixohtew said:
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://androidfilehost.com/?w=files&flid=261339
commands:
$: fastboot flash system_a system.img
(for pixel devices= $: fastboot flash vbmeta_a vbmeta.img)
then boot into twrp and wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps but no root, im working on that
Click to expand...
Click to collapse
We should all be here not everyone can do what you do..

I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.

cdnsnOw said:
We should all be here not everyone can do what you do..
Click to expand...
Click to collapse
What I meant was if you don't know how to use fastboot, you probably shouldn't be messing with your phone because you used the wrong code and bricked it..no offense

What is the difference flashing with TWRP and fastboot method?

So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.

gforceriders said:
So far no luck getting it to boot. This is what I did.
fastboot flash system_a system.img
fastboot flash vbmeta_a vbmeta.img
then boot into twrp and wipe data and reboot
Going to update to the leatest April image and try again.
Click to expand...
Click to collapse
Maybe after flashing vbmeta reboot bootloader then load up twrp

cdnsnOw said:
What is the difference flashing with TWRP and fastboot method?
Click to expand...
Click to collapse
This is a system.img and needs to be flashed to the system which requires fastboot..in twrp you MUST make sure you're flashing to the system_a partition

sixohtew said:
Maybe after flashing vbmeta reboot bootloader then load up twrp
Click to expand...
Click to collapse
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.

abduleo77 said:
I can't get twrp to load after flashing.....it just hangs at the start up screen. Any suggestions? I went back to stock and flashed over that.
Click to expand...
Click to collapse
Try booting twrp right after the vbmeta.img

gforceriders said:
Yeah did that still no luck getting it to boot. Can't even switch to slot A without getting an error after fastbooting the images.
Click to expand...
Click to collapse
Which device? Pixel 2 xl?

sixohtew said:
Which device? Pixel 2 xl?
Click to expand...
Click to collapse
Yep, the pixel 2 XL.

gforceriders said:
Yep, the pixel 2 XL.
Click to expand...
Click to collapse
Did you come from another rom or were you stock? This boots just fine for me

sixohtew said:
Did you come from another rom or were you stock? This boots just fine for me
Click to expand...
Click to collapse
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.

gforceriders said:
Yes, came from another rom and when that didn't work I went back to stock and still wouldn't boot.
Click to expand...
Click to collapse
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?

sixohtew said:
Does it bootloop? Or boot back to the bootloader? If it boot loops are you seeing the aokp boot animation? Could you possibly get a logcat?
Click to expand...
Click to collapse
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.

gforceriders said:
It bootloops. No aokp boot animation. I will try and use the bootloop fix script and flash full stock and test again here shortly.
Click to expand...
Click to collapse
Yeah if you tried to flash it over another rom instead of stock, issues could arise..I'll put a script together that will flash stock with the new system.img and add the vbmeta.img to it so it flashes all the necessary files

[Android 10.0] AOSP for Xperia XZ2 [2019.10.01]

AOSP 10.0 For XZ2​Based on Sony Open Devices​I am not responsible for bricked devices, dead SD cards.​Special Thanks: @local__hero
请中文用户遵守XDA规则，使用双语留言​For English Users
Required files:
Kernel 4.9:
Code:
Read me at first
SODP will support AOSP 10.0 officially on kernel 4.14.
This build is based on kernel 4.9(The same as Pie).
kernel-4.9-based: Download Link With: )SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_tama.img
How to flash:
You must flash full package before flashing Update
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash dtbo dtbo.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash oem <PATH of OEM>
fastboot erase userdata
How to flash Gapps：
1. Flash AOSP 9.0 by Martin X3. Never boot after flashing it.
2. Flash TWRP for SODP 9.0 by Martin X3.
Code:
fastboot flash boot TWRP.img
3. Power on and boot into TWRP.
4. Copy System.img, vendor.img, boot.img into phone. Flash them to their partitions.
5. Reboot to fastboot.
6. Flash vbmeta.img and dtbo.img
Don't forget to flash oem file.
Update and known BUG:
Flash Full-V20191001 before flashing this update.
Update-V20191001:
Update
1. Hotspot fixed.
Bug
1. Camera lag.
Full-V20191001:
Update
1. USB fixed.
2. Go back to HMP.
3. Audio fixed.
4. Upgrade to Android 10.0.0 R3.
Bug
1. Hotspot is broken.
2. Camera lag.
Update-V20190924:
Flash Full-V20190923 before flashing this update.
Update
1. EAS support, performance improve.
2. PreRoot boot.img.
Bug
1. Audio.
2. Hotspot is broken.
3. Camera lag.
Full-V20190923:
Bug
1. USB is broken.
2. Hotspot is broken.
3. Camera lag.
-----------------------------------------------------U--U------------------------------------------------------------------------------
中文教程
所需文件如下：
基于4.9内核的版本:
Code:
请详阅：
SODP 会在4.14内核上支持Android 10.0，这是一个基于4.9内核，使用和9.0相同驱动的体验版本
基于4.9内核的刷机包 下载地址 搭配后面这个版本的OEM文件使用SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_tama.img
怎么刷机：Fastboot模式下根据下面的命令刷入
刷Update升级包之前必须刷入前一个最近的Full包
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash dtbo dtbo.img
fastboot flash vendor vendor.img
fastboot flash vbmeta vbmeta.img
fastboot flash oem <PATH of OEM>
fastboot erase userdata
谷歌套件: 自己找10.0能用的，找到了这样刷：
1. 刷马丁AOSP 9.0，不要启动。
2. 将马丁为SODP 9.0 制作的Twrp刷入Boot分区。
3. 开机启动进入Twrp。
4. 拷贝10.0的System.img，boot.img，vendor.img进入内置储存，然后刷入对应分区。
5. 刷Gapps和Magisk。
6. 关机进入fastboot模式，刷dtbo以及vbmeta文件。
别忘了OEM文件
已知问题和修复内容:
看英文的，这都看不懂了快回去找你们英语老师补习。
--------------------------------------------------------------------U-U----------------------------------------------------------------
XDA:DevDB Information
Treble, ROM for the Sony Xperia XZ2
Source Codes
Link
Contributors
Sjll
ROM OS Version: 10.0
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
国内用户可以通过附件的支付宝捐助我
Version Information
Status: Testing
Created 2019-09-24
Last Updated 2019-10-01

Hi
Are gapps baked in? I had trouble booting twrp and would like to have a build with gapps build in if possible, so I can directly flash to my device
Best regards

good job，but any bug？

NoMercyWWE said:
Hi
Are gapps baked in? I had trouble booting twrp and would like to have a build with gapps build in if possible, so I can directly flash to my device
Best regards
Click to expand...
Click to collapse
No gapps included. Twrp doesn't works.
tainhao said:
good job，but any bug？
Click to expand...
Click to collapse
Speaker audio quality is not good.

Now i'm really enticed to unlock Bootloader ^^
But if TWRP doesn't work and you can't install GAPPS that kinda sucks.
Would it theoretically be possible to manually modify system.img and inject gapps? or is that signed ?

Haldi4803 said:
Now i'm really enticed to unlock Bootloader ^^
But if TWRP doesn't work and you can't install GAPPS that kinda sucks.
Would it theoretically be possible to manually modify system.img and inject gapps? or is that signed ?
Click to expand...
Click to collapse
You could wait for the TWRP for 10.0 or use com.excean.gspace
-------------------------------------------------Update------------------------
Update the way to flash Gapps.
@Haldi4803 @NoMercyWWE
-------------------------------------------------Update------------------------
I made some mistake.

just finished the flash, but when this phone connected to my laptop there was no link mode pumped out or on the navigation bar, and I didn't find anything that can help me link the phone.
---------- Post added at 07:04 AM ---------- Previous post was at 06:54 AM ----------
monshoal said:
just finished the flash, but when this phone connected to my laptop there was no link mode pumped out or on the navigation bar, and I didn't find anything that can help me link the phone.
Click to expand...
Click to collapse
sorry, it's the USB's fault. so far no problem encountered

Wonder if the 4.14kernel based build is stable
and does camera and TF slot work properly?
(总之就是4.14的能不能用捏，4.9以前装着bug略多，毕竟刷一次太费时间了，不稳就等养肥）

The Kernel v4.14 already got rooted or not ?
4.14内核版是否已root?
Does GCam work on AOSP v10 ?
谷歌相机能用吗？

monshoal said:
just finished the flash, but when this phone connected to my laptop there was no link mode pumped out or on the navigation bar, and I didn't find anything that can help me link the phone.
---------- Post added at 07:04 AM ---------- Previous post was at 06:54 AM ----------
sorry, it's the USB's fault. so far no problem encountered
Click to expand...
Click to collapse
USB fixed.
asz_kt said:
Wonder if the 4.14kernel based build is stable
and does camera and TF slot work properly?
(总之就是4.14的能不能用捏，4.9以前装着bug略多，毕竟刷一次太费时间了，不稳就等养肥）
Click to expand...
Click to collapse
MDLB said:
The Kernel v4.14 already got rooted or not ?
4.14内核版是否已root?
Does GCam work on AOSP v10 ?
谷歌相机能用吗？
Click to expand...
Click to collapse
Kernel 4.9 version is almost stable. 4.14 version is still working in progress.
You can use Magisk app to build a prerooted kernel.
Gcam works on AOSP, but you need to choose a suitable edition.
4.9内核的版本基本上没啥问题了，等twrp 10刷Gapps，不然你就用谷歌空间。4.14还要继续等，现在只能启动到adb，卡Sony，后续基本上会修复。
Root用Magisk app就能够做一个预先root过的boot.img，然后刷一下就好。
Gcam一直可用，不过你需要找一个适合Android 10的版本，不然会闪退。

Is there a schedule for the 4.14kernel version? or is there a bug list?
Camera lagging is just unbearable and i guess it comes with the 4.9kernel?

asz_kt said:
Is there a schedule for the 4.14kernel version? or is there a bug list?
Camera lagging is just unbearable and i guess it comes with the 4.9kernel?
Click to expand...
Click to collapse
https://forum.xda-developers.com/xperia-xz2/development/unstable-sonyaosp-10-0r1-t3975009
This reflects the current state
Will release new versions with OEM version and android monthly security patch.

Question Vendor_boot question

What does happen if I flash a standard recovery after flashing a vendor_boot rom?

skiangel said:
What does happen if I flash a standard recovery after flashing a vendor_boot rom?
Click to expand...
Click to collapse
Why would you want to do that? A bootloop is the likely outcome.

DarthJabba9 said:
Why would you want to do that? A bootloop is the likely outcome.
Click to expand...
Click to collapse
If i want to switch to a standard rom what i do?
I'm new to all this a/b partitioning and vendor_boot things

skiangel said:
If i want to switch to a standard rom what i do?
I'm new to all this a/b partitioning and vendor_boot things
Click to expand...
Click to collapse
You can simply flash the standard ROM with your vendor_boot recovery, and then flash the standard recovery afterwards.