Database Develop

ROM: Sony AOSP 8.1 (H3113) (unofficial)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sony AOSP project​
Disclaimer
I'm not liable for anything YOU do to YOUR device, YOU are doing it and it's YOUR device.
What is it?
It's a project developed and maintained by Sony Xperia Developers team.
You can get more informations here: https://developer.sony.com/develop/open-devices/
Can I build it by myself?
Sure, just follow these instructions and have patience!
What works and what doesn't?
According to this official page, almost everything seems to be fine.
How can I flash it?
Follow these steps:
Unlock the bootloader (this will erase your data and will void warranty): https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Setup fastboot on your PC (there are many guides for this step)
Download and unpack the zip archive
Open a shell into the folder containing unpacked files
Run these commands:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (it’s not necessary to flash userdata every time)
Download and unpack the corresponding vendor image from here: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open a shell into the folder containing unpacked image
Run this command:
fastboot flash oem SW_binaries_for_Xperia_xxxxx.img (where "xxxxx" varies depending on the file)
(optional) In case you want to flash GApps, Magisk or other mods, you can use TWRP: https://forum.xda-developers.com/xa2-ultra/development/recovery-twrp-3-2-1-0-touch-recovery-t3774193
Reboot the device and enjoy!
Download link
You can get the builds from my AFH folder: https://androidfilehost.com/?w=files&flid=269497.
I haven't done any change to Sony's source code, these are vanilla builds.
Credits
All credits go to Sony and Google.
XDA:DevDB Information
Sony AOSP, ROM for the Sony XA2 Ultra
Contributors
axxx007xxxz
Source Code: https://github.com/sonyxperiadev
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-05-08
Last Updated 2018-05-08

Reserved
NOTE: I'm in no way associated with Sony, these are unofficial builds and are made for pesonal usage.
Also, these builds are untested so I can't assure they're going to work!

Reserved 2
Post reserved for future usage.

Reserved 3
Post reserved for future usage.

Reserved 4
Post reserved for future usage.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r20
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 81032020581dd636ab9d7f8414609bad07332288
Last commit of sonyxperiadev/kernel: 1df958f2943c6c5cae31018e42d2f42e8a55c4b3
Last commit of sonyxperiadev/device-sony-nile: c775da101d57377979cdcb79b1ba1b5bbd3739a4
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=818222786056029296.

It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).

Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying. And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it.
Click to expand...
Click to collapse
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.

roirraW "edor" ehT said:
I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.

Casserole said:
I haven't flashed any magisks at the moment, so I don't think the problem are caused by it. But thanks anyway for the reply.
Click to expand...
Click to collapse
You're welcome! I'm not suggesting that you flashing Magisk or anything is the cause of this on this ROM, it's just related to changes in Android 8.1 and that it doesn't really necessarily mean there's something wrong. I'm sure there are ways around it, but since I'm not a developer and I don't know what triggers it, I don't know.

Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?

tombassi said:
cool down dude !! XDA is not the correct please for these bad words. if you don't know what you are doing that is not the Developer fault and if you need no bugs stay with the stock ROM.
Click to expand...
Click to collapse
Thanks! With "almost everything seems to be fine", I meant that most of the main parts (should) work.
Camera is a known problem on Sony devices due to DRM keys getting erased on bootloader unlock.
Casserole said:
It always says "There's an internal problem with your device" after booting up. It's kinda annoying.
And it also does not accept my Samsung microSD card formatted on stock ROM and wants me to format it. I'm backing it up, and will try to format it later.
Fingerprint aslo does not work, but I'm fine with that at the moment.
If someone needs to know, I have H4113 (dual-sim variant of regular XA2).
Click to expand...
Click to collapse
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Code:
persist.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,1
then reboot the phone and test.
These come directly from H4113 makefile, I can't assure you everything will be fine after this, but you can give it a try.
As per the fingerprint, it's currently broken on all variants, I'm sorry.
mirco_pa said:
Is fingerprint scanner not working for everyone or it is not working only for those with a fingerprint scanner made by a a different hardware maker?
Click to expand...
Click to collapse
Sony website reports it as currently not working on AOSP, I'm sorry.

axxx007xxxz said:
The SD card problem could be related to your phone being dual SIM: as the title says, these builds are for H3113 (single SIM variant).
You can try to set dual SIM properties in build.prop (you can do it with an app like this or a text editor if you have root access, otherwise I think it's doable through TWRP too):
Click to expand...
Click to collapse
I think SD card problem was related to something else, because it started working after reformatting.
But there were also problems with SIM card, it worked on first boot, but after removing and inserting it again device shown that there were no signal, so your solution may be helpful in this situation. I can't test it due to limited amount of time, though.

New build
Build informations:
Build type: userdebug
Android revision: android-8.1.0_r26
CAF revision: LA.UM.6.4.r1
Last commit of sonyxperiadev/local_manifests: 1c992d7f3f2ef8d0b53397e23227e10489e40bec
Last commit of sonyxperiadev/kernel: ab6fd5b1a4126cfdd4391eefe8eba17eb6626781
Last commit of sonyxperiadev/device-sony-nile: 7d57c76da9ce47849429347e77e013781e63db2f
Last commit of sonyxperiadev/device-sony-pioneer: 5b804c4aa86ca13653d2d692120437fa76f61ae9.
Download link: https://androidfilehost.com/?fid=890278863836285554.

Can you build one for H4113? You shood have files for it too

Thanks axxx007xxxz for sharing these builds! They helped me recover Android on my completely wiped h3113 pioneer. Both the 8.0 and 8.1 build work for me. Downloading them to my PC was the hardest part, for some reason the download often fails.
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Thank you!
roirraW "edor" ehT said:
Just information: I have the H3223 not H3213, and haven't tried to flash this, but on the Google Pixel (8.1) with at least some custom kernels and some versions of Magisk, the same "There's an internal problem with your device" when you boot up, but other than possibly having your phone screen on longer than it should, there are no actual problems on the Pixel. Could be for the same reason(s), whatever those reasons are. I'm not positive but I think that more recent versions of Magisk might not cause that message anymore. I use an old version of Magisk, but in my case the Pixel custom kernel I use causes that, too.
Click to expand...
Click to collapse
I get the same error message right after booting, also without root. It's annoying, but I guess I can live with it.
P.S. As I'm a new user, I cannot use links yet. Please use these footnotes instead:
*: https[colon]//developer[dot]sony[dot]com/develop/open-devices/downloads/software-binaries
**: https[colon]//developer[dot]sony[dot]com/develop/open-devices/guides/aosp-build-instructions/build-aosp-nougat-8-1-oreo-4-4/#tutorial-step-6

1. parts of android which are closed source, graphics driver for example. you won't see them.
2. eng should give you more debugging options, like working adb logcat without enabling developer options which is sometimes needed while you're porting android to new device and there's just black screen on the phone for example. correct me if i'm wrong.
3. flashing worked through twrp for me but i had to build unsingned zip.
regarding the internal problem message, just ignore it.

davidhozic said:
Can you build one for H4113? You shood have files for it too
Click to expand...
Click to collapse
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Nonstop decay said:
Downloading them to my PC was the hardest part, for some reason the download often fails.
Click to expand...
Click to collapse
Unfortunately, Android File Host is problematic sometime.
Nonstop decay said:
I still have a couple of questions about these Sony AOSP builds that maybe you can answer:
1. Do you know what the Sony software binaries* do? I have flashed them on my device a couple of times, but I don't see anything added.
2. What is the difference between build type "userdebug" and "eng"?
3. If I use this build, how would you recommed I update it? Is the only way to flash in fastboot? (Like step 6 in Sony's guide**?)
Click to expand...
Click to collapse
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.

axxx007xxxz said:
I can make a H4113 build if you want to test it though.
Click to expand...
Click to collapse
Just wondering aside from not being supported in Sony's open device program what exactly is needed to get the H3223 from getting AOSP 8.1 built for it? I can't imagine the kernel being much different on the H3223 from any of the other XA2 Ultra single sim models, right?

axxx007xxxz said:
Checking H4113 makefile, I don't see big differences except for a few properties: https://github.com/sonyxperiadev/device-sony-pioneer/blob/master/aosp_h4113.mk#L18-L22; you can try to set them (you can use an app like this) and check if you can get dual SIM to work.
I can make a H4113 build if you want to test it though.
Unfortunately, Android File Host is problematic sometime.
Basically, what @frantisheq said.
I think you can flash IMG files through TWRP too if you extract the ZIP into your phone's memory.
Click to expand...
Click to collapse
Yes plese make a build for H4413, i get so many random errors and every time i fix an error there appears another. And is the build for this model supposed to work with h4113? Aren't the boot images incompatible?

[OFFICIAL] [NIGHTLIES] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 16.0 thread for the Motorola Moto Z2 Force, codename nash.
Join our Moto Z2 Force Development Discord server!
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
Camera Mods don't work
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work.
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Ultrasonic Proximity Sensor doesn't work -- No support present in the OSS Audio HAL. If it was written in, it wouldn't be used by anything in Lineage, as the normal proximity sensor works fine.
Notes:
Official Lineage OS builds for nash ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll only find support for these in the Discord linked above.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 16.0, ROM for the Moto Z2 Force
Contributors
npjohnson, erfanoabdi, invisiblek
Source Code: https://github.com/LineageOS/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo Firmware
Based On: LineageOS
Version Information
Status: Nightly
Created 2019-03-03
Last Updated 2020-01-12

Reserved

Reserved

Thank you， ota ：）

How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras

7bob said:
How to get root on LOS 16?
There's no official root binary for LOS 16: https://download.lineageos.org/extras
Click to expand...
Click to collapse
Check again.

Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?

zidemizar said:
Just finished installing Lineage 16 on my moto z2 force, I cannot find the option for locking the screen by using the fingerprint that came originally with the phone. Is this feature available on lineage 16?
Click to expand...
Click to collapse
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.

npjohnson said:
Check again.
Click to expand...
Click to collapse
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?

7bob said:
Thanks, now I see it.
Is there something I have to consider when updating a Z2 Force from 15.1 to 16? Or can I just follow the general update guidelines?
Click to expand...
Click to collapse
Just follow general guidelines. We already had testers and upgrading from 15.1 to 16.0 didn't cause any issues. Obviously, if you do run into an issue, it is suggested to clean flash first to see if it was a borked update

npjohnson said:
Yes. If you aren't seeing it, I'd suspect you're using an unsupported addon, or your hardware is failing.
It shows up/works fine here.
Click to expand...
Click to collapse
Do you have a screenshot showing that it shows under screenlock settings?
Also what gaaps did you use when installing, I used the reccomended mindthegaaps and it kept giving me errors related to pixel apks.

link if image does not work
https://imgur.com/a/1eoVcgk
This is what shows under my screenlock setting, I do not have the setting that allows me to lock the phone using the fingerprint reader, this is from a fresh Lineage 15.1 installation with mindthegaaps, nothing else is installed on it. Had the same issue with lineage 16

Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.

Now I have installed los 16 and it was instructive for me. Learning by doing. After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP? I'm on slot b now and on system_a is nothing. If I want update later, I have to do just flash the zip over TWRP and then reboot it and then maybe flash gapps again, because it's the first update on slot_a? Hope that's works because the encoding problem. Don't have the key.

AmazerG said:
Am I able to install Lineage 16 on Sprint Moto Z2 Force? I will get the phone next week, so I don't know if it's nash or what? Thanks.
Click to expand...
Click to collapse
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
allrightlite said:
After I have get working TWPR on both slots, data area of los 16 was suddenly encoded and requires a passwort for it on TWRP start to use it. So backup of intern data fails. Ok so far, we have two slots and that's anyway the backup. But how will work the update process? Just over the updater-function in settings/system or over TWRP?.
Click to expand...
Click to collapse
Remove your fingerprint and screen lock method prior to entering TWRP. If you came from a stock ROM you must format data before flashing LOS. Updates can be done automatically with the updater, or manually thru recovery. The latter requires more time with no added benefits. Also encryption is enabled with custom ROMs.

So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done

I have tries at this moment to update over the lineage updater in settings and it's stopping with installation error. After try to reboot to TWRP it's endet up in reboots. But LOS16 stats normally again after press power button a little bit. Now I try again to update. Presumably it isn't working again. I think I will reflash twrp first and try then over this to update. Good idea or what's going wrong on my phone?
I must do new install. All broken. Holy crap. Hope this time I get it working.

7bob said:
So I was able to successfully update from 15.1 to 16.0. Here's what I did:
Backup my data
Boot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, wipe System partition, then start sideload
Code:
adb sideload lineage-16.0-20190305-nightly-nash-signed.zip
reboot into bootloader
Code:
fastboot boot twrp-3.2.3-2-nash.img
In TWRP, start sideload
Code:
adb sideload MindTheGapps-9.0.0-arm64-20190216_211116.zip
Code:
adb sideload addonsu-16.0-arm64-signed.zip
reboot
done
Click to expand...
Click to collapse
what are the steps to update from firmware 8.0 to LineageOS 15.1 or 16, please
unlock bootloader, twrp, magisk (no problem),
My phone locks the boot loader again when I try to install a custom ROM
my firmware (TWRP, magisk)
RETAIL/NASH_RETAIL_8.0.0_OPXS27.109-34-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
in any way I thank you :good:

Ok, I have found out how get it working. Updater app not working here, always installation error after end of update process. Don't know why. So now I have a way found out, which seems to be working every update. Go to TWRP, flash los16 new zip and, this is very important (understand it very late xD) don't forget to flash twrp installer zip directly after los 16, because otherwise on the other slot is the stock recovery again. So, after this boot to the other slot with twrp directly from your phone and flash gapps every time, every update. Here I forgot it and nothing of the play store and co. was working anymore. Android Framework ID was away, too. Is there an easier way to update over TWRP or do I have to do so? And what happend to, backup wasn't possible to restore, maybe cause thought encoding?
The new update process with A/B is not easy to understand directly But the rom is a beast, very very good. Why I update and switch to los16? That's easy, because the bluetooth bugs on stock oreo was terrible (and no 8.1-batterie icon ) and lags on few drm videos and here and there. Speed of the UFS-flash going slower and slower, no its 3 times faster again. This phone works really great with LOS16. Very good work! It's not easy to understand all, but I will get it in my brain
Edit: There is another point, which could be interesting. Netflix shows error on start up (15001) and this even though safety net is passed. Hm.. Have downloaded from play store. Maybe older version does do this job, don't know.

Ace42 said:
Sure. It works on TMO and SPR, just no VZ and ATT for obvious reasons. Nash is the internal name for the Z2.
Click to expand...
Click to collapse
Is there anything different between Sprint Z2 force and Tmo ones in terms of hardware such as lack some band or what?

[ROM][UNOFFICIAL][jd2019][9 Pie] LineageOS 16.0 for the Lenovo Z5s L78071

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 Pie, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Known issues: (as of May 19, 2020)
- FM Radio app doesn't work; It actually works, just once every two attempts: If it crashes the first time, select close app, clear apps from background and try again; I'll find a definite fix soon;
- Wi-Fi signal strength doesn't show on status bar, only in the wireless screen;
- Fingerprint reader doesn't work;
- SELinux is currently set to permissive;
Instructions:
- This is a FULL ROM build, meaning your BOOT, DTBO, SYSTEM and VENDOR partitions will be overwritten. Backup first!
- You need firmware version 11.x.y (preferably 11.3.169 - recovery encryption only tested with that version), any will do. 10.5 will not work
- Download TWRP from the files section, fastboot flash it (if you don't have custom recovery yet)
- Download patched vbmeta.img
- Download the latest build
- (Optional) Download Gapps (arm64 9.0, any flavor) and Magisk
- Boot to recovery (whichever you have), flash the new recovery
- Reboot to recovery, now your data is decrypted, flash vbmeta, latest build, magisk and gapps
- Format DATA completely to start from scratch since encryption is different
- Reboot
Downloads:
Builds: https://sourceforge.net/projects/lineageos-lenovo-z5s/files/
Source code:
LineageOS: https://github.com/LineageOS
Kernel and Device Tree: https://github.com/jacoghi
Reporting Bugs:
DO NOT Report bugs if you're not following the instructions!
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.

Changelog:
May 19, 2020:
- Initital release, everything working except for FM and fingerprint reader;
- Kernel is completely overhauled and updated to LA.UM.7.8.r1-08500-SDM710.0;
- Audio drivers are stock 11.3.169 (we don't have the sources);
- Wifi is open-source, with MAC randomization currently being tested;
- Call recording already works;
- BT Audio works for calls and everything else, HD codecs being optimized;
- Wifi Display works perfectly on my cheap chinese Android TV Box. Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
- Camera2API is active, RAW pictures are also enabled;
- Build will automatically encrypt your device, I had to fool Lenovo's BS keymaster to make it work, so it has to be enabled;
- As of now, I don't care if your apps work or not, that's not my problem, just let me know about hardware issues;

jacoghi said:
Please test with a Chromecast / Google Cast / SmartTVs, since I don't have any of those;
Click to expand...
Click to collapse
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!

carlshark said:
I can confirm that this works.
It's great to have a ROM that works and doesn't have audio problems or auto brightness issues compared to GSIs. I've been using this for two days without any problems aside from the bugs already mentioned. I am holding off on using Magisk like I normally do so as not to introduce complications.
Overall, a great first effort. Thank you very much!
Click to expand...
Click to collapse
Thanks for confirming that to me, great to know. Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd? And you can use magisk without any issues, I'm using it here right now, no problems.

jacoghi said:
Would you happen to have any of those fancy hi Def Bluetooth headphones so we can test aptx and aptxhd?
Click to expand...
Click to collapse
No, sorry. If that changes, I will let you know
I can imagine most of the users that are here are currently using a GSI. The stock 11.3.169 from here can actually be installed via TWRP. Flashing it would revert to stock recovery so users need to reinstall the TWRP recovery image during the same session. That's how I ensured that I was running an 11.x firmware after using all those GSIs from 4PDA. Hopefully this helps others to revert to stock so they can use your LOS build.

Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download

And what is apparently massive news for us, our phone will get an Android 10 official update, meaning we'll be able to boot lineage 17.1 with the updated audio drivers (in theory). Anybody in China or who knows how to trick their system and able to get ahold of these files?
https://club.lenovo.com.cn/thread-5849244-1-1.html

jacoghi said:
Some more good news, we now have a TWRP that decrypts data even from this updated Lineage 16 build. It actually should work for any ROM flashed atop firmware 11.3.169. That's the one I'm using and probably the majority of people who wanna stick to "the latest and greatest" speech, so here we go, now we can enable OTAs without any issues and flash anything. This recovery can decrypt any data regardless of password type, so you can use PATTERN, PIN, or whatever, it will work, I tested them all.
https://sourceforge.net/projects/lineageos-lenovo-z5s/files/twrp-3310-jd2019-recovery.img/download
Click to expand...
Click to collapse
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.

carlshark said:
Hi, I used your recovery to try and create a full backup of your ROM before I go back to stock. I encounter an error when it tries to backup the system partition - the backup fails. When I tried to install the Full OTA ROM from Lenovo, it also fails. I flashed the other TWRP and both the backup and install worked.
I'm going back to stock to get the 11.5 update available only if the phone has a locked bootloader.
Click to expand...
Click to collapse
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man

jacoghi said:
Hey man, thanks for the report. I just rebooted to recovery and backed up the system partition without a hitch, so no clue what happened with you. Regarding the Lenovo Ota it probably doesn't work since they use different manifests from the ones I'm using with lineage. Nevertheless I'll make it universal now that I know about it. Let me know if you can get 11.5 and we can make a dump of all partitions. Thanks man
Click to expand...
Click to collapse
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo

carlshark said:
The only thing I can think about was that I was trying to save to a microSD instead of internal storage.
Anyhow, I'm back on LOS. I went back to stock, relocked the bootloader, got the update notification but the downloaded update fails on install. I "read" in the Chinese forums that access to 11.5 is some sort of closed beta; some users also encounter failed updates.
@wzsx150 published a new TWRP based on Android 10, probably with the partition file info of 11.5. It doesn't work for me when I flashed it on top of 11.3 (Android 9). Thought it might help you further.
Click to expand...
Click to collapse
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.

jacoghi said:
That's why it failed, system partition is 5.1 GB, your sdcard is probably formatted in FAT32 which DOESN'T ALLOW files over 4GB, that's a filesystem limitation.
Click to expand...
Click to collapse
Oh, right, I totally forgot all about that. Should have tried enabling compression or saving to internal storage.
I'll wait for somebody getting us 11.5 firmware files and release a new twrp for Android 10, (partitions won't change and AFAIK, wsx's twrp doesn't decrypt and is full of extra non open source stuff) and Lineage 17.1, until then makes little sense to me update this knowing it won't last long anyways.
Click to expand...
Click to collapse
I've found a 4PDA post regarding updating to 11.5 and reposted the good stuff here. Hope it helps. Thanks for your good work!
---------- Post added at 06:38 AM ---------- Previous post was at 06:35 AM ----------
seisa said:
hey man could you please help out, was trying to revert to the stock rom but getting a blank screen after i'm done and it shows lenovo
Click to expand...
Click to collapse
I know this is the wrong thread to answer this, but we can't really help you out without some more details. Were you trying to install through recovery? Through QFIL?
From the looks of it, sounds like you have a bootloop. Try doing QFIL again and unlocking bootloader, or the other way around - sometimes it works for me that way.

I have Z5s 6GB/128GB model, sold as Global Version & Global ROM.
It does have EU LTE bands, so it probably is somewhat "global".
The downside: I am at 10.5 version with no updates available. Seller also told that there are no updates.
Two questions:
1. Is it absolutely necessary to have 11.3+ to install this LineageOS ROM? What is blocking installation if I have 10.5? Can I brick it?
-- EDIT: I will answer myself: Yes it is needed. LineageOS did not flash over 10.5 and gave an error. That was validation error before flashing, so no harm done.
2. Is it safe to install Chinese ROM on this device? Is it possible to loose something in the process? Like LTE bands or something else important?
-- EDIT: Seems to be ok.
I really want to install LineageOS or some other google free AOSP ROM. But I do not want to loose important features or brick it in the process.
Thanks.
EDIT: I installed Arrow OS GSI at the moment over 10.5 and it seems to work. But still looking forward to get pure LineageOS installed.

I have one problem that is hardware related:
Microphone level is quite low compared to my previous phone and people are complaining about low volume when I call.
Is there any way to add more gain? I tried to search but did not find easy and straightforward answer. Most solutions refer to methods/files that do not exist on this ROM.
What I found was complaint that there is still no way to easily manage audio stuff in android...
Mic Test (lauresprojects.com.mictest) app confirms that recording levels are considerably lower in both direct sound and communication mode when comparing to my other phone.
Otherwise seems to working quite nicely. Thanks for your good work.

I can't use face unlock with this ROM.

Is there still some active development at this project?
Is there some active development at this project?

[ROM][UNOFFICIAL] LineageOS 17.1 for Xperia 10 II [Stock-based]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock Android 10 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
6.This ROM works fo both dual and single models.
Downloads Links
LineageOS 17.1:
Unofficial-build: Link
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 10.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Download Lineage Recovery: AFH
3. Put your device into fastboot by volume up key.
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
5. Enter fastbootd:
Code:
fastboot reboot fastboot
6. Flash LineageOS:
Code:
fastboot flash:raw boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
7. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
Gapps:
After flashed images in fastbootd, choose Enter recovery - Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Dolby Atmos:
Install magisk
1. Install Q-10__Dolby_Digital_Plus_v.7.3-_MMT-Ex_-20200519 from repey6.
2. Install Audio_Modification_Library-v4.0 from Magisk repo
3. Install sepolicy to permissive
4. Turn off AudioFX and reboot
Enjoy Dolby! All files I provide a mirror on AFH, you could downlaod from here.
Never flash oem from SODP!!
If you flashed oem and meet any issues, I could only say you are a hanhan.
Root access:
Flash Magisk in recovery.
Twrp:
See this: Link
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Luk1337
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-17.1 for Xperia 10 II, ROM for the Sony Xperia 10 II
Contributors
Sjll
Source Code:
GitHub - sjllls/android_kernel_sony_sm6125
Contribute to sjllls/android_kernel_sony_sm6125 development by creating an account on GitHub.
github.com
GitHub - sjllls/android_device_sony_pdx201
Contribute to sjllls/android_device_sony_pdx201 development by creating an account on GitHub.
github.com
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-11-26
Last Updated 2020-11-30

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Not tested
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Res

hi, this might be a stupid question, but what part of this is from the stock firmware? i mean lineage OS is a complete ROM with its own kernel system etc. what is the benefit of combining it with stock? better HW compatibility? and does this affect OTA updates?

bamdadkhan said:
hi, this might be a stupid question, but what part of this is from the stock firmware? i mean lineage OS is a complete ROM with its own kernel system etc. what is the benefit of combining it with stock? better HW compatibility? and does this affect OTA updates?
Click to expand...
Click to collapse
this might be a stupid question
Click to expand...
Click to collapse
Not at all, good question.
what is the benefit of combining it with stock?...
Click to expand...
Click to collapse
Better user experience and better battery time than SODP lineageOS. Test it yourself please.
does this affect OTA updates?
Click to expand...
Click to collapse
If you mean stock FW update. This is LIneageOS, not stock FW, we will provide OTA once we get LineageOS official support.
what part of this is from the stock firmware?
Click to expand...
Click to collapse
Some stock blobs and some kernel drivers, but System is LineageOS. There is no difference with other phones.
i mean lineage OS is a complete ROM with its own kernel system etc
Click to expand...
Click to collapse
As above, system is LineageOS, blobs and kernel drivers are provided by Sony. This is the same as other phones supported by LineageOS.

thanks for the detailed answer. sounds really awesome. too bad i'm on mac os and it's really hard to flash the stock FW here. i'm going to try tomorrow, though. : )

Sjll said:
If you mean stock FW update. This is LIneageOS, not stock FW, we will provide OTA once we get LineageOS official support.
Click to expand...
Click to collapse
You're planning official certification by LineageOS down the line?
Any reason not to flash the OEM binaries, by the way? What's the recourse for fixing that and installing this if one's already flashed the SODP firmware?

You're planning official certification by LineageOS down the line?
Click to expand...
Click to collapse
Yup.
Any reason not to flash the OEM binaries, by the way? What's the recourse for fixing that and installing this if one's already flashed the SODP firmware?
Click to expand...
Click to collapse
Go back to official Android 10 firmware, and boot it.

is there any way to do this without installing the whole stock firmware? i understand that you cannot distribute parts of it due to some legal crap, but if i have the extracted files from the .ftf can i just use fastboot to flash those?
i'm asking because after 2 hours of headaches (installing mono for xperifirm, flashtool not recognising my firmware files, doing the whole thing again in a VM in virtualbox but failing on the USB being constantly disconnected etc.) it's obvious that doing this on OS X is damn near impossible - and i don't have access to a windows machine currently.

bamdadkhan said:
is there any way to do this without installing the whole stock firmware? i understand that you cannot distribute parts of it due to some legal crap, but if i have the extracted files from the .ftf can i just use fastboot to flash those?
i'm asking because after 2 hours of headaches (installing mono for xperifirm, flashtool not recognising my firmware files, doing the whole thing again in a VM in virtualbox but failing on the USB being constantly disconnected etc.) it's obvious that doing this on OS X is damn near impossible - and i don't have access to a windows machine currently.
Click to expand...
Click to collapse
Newflasher:
1. Download firmware with XperiaFirm.
2. Flash it with newflasher.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Or fastboot:
1. 1. Download firmware with XperiaFirm.
2. Convert two sin files should named super_XXXXX.sin and oem_XXXX.sin with unsin.
https://forum.xda-developers.com/crossdevice-dev/sony/tool-unsin-sin-v3-unpacker-t3128106
3. After you get two .ext4 files, flash them via fastboot.
Code:
fastboot flash super super_xxxxxx.ext4
fastboot flash oem oem_xxxxxxxx.ext4

well i tried everything..
- spun up a VM with vagrant and copied over the .sin files, did an unsin but the super one only produced an .img not a .ext4. tried flashing that but it want't happy.
- so i tried flashtool's sin editor but that complained about this version of sin being too new.
- then i found some (bad) info in the net about using an *older* version of flashtool for this. of course that didn't work either.
even though i'm really interested in this (especially since the other lineage ROM has major bugs), i had to give up.

You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?

bmo2718 said:
You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
I've got the XQ-AU52 and can confirm this runs fine on it. I don't use two sims though, so can't confirm whether or not that happens to work.

dreDREb13 said:
I've got the XQ-AU52 and can confirm this runs fine on it. I don't use two sims though, so can't confirm whether or not that happens to work.
Click to expand...
Click to collapse
Don't plan on using two SIMS either, but in the thread for the other rom it was specifically stated that it only works for one variant.
Anyway, thanks for the reply, I will try it.

Hi @Sjll, do you think that this commit will help activating L1 for Xperia 10 II and possible another mark II devices?
Luk added that on Xperia XA2 and enabled widevine L1 for it

I have some questions
1)Will you add suport of Google Camera?
2) Does Google Pay work? and will it work in future? A heard something like that Google want start check Safenet with hardware solutions
Stock ROM doesn't has Level3 and RAW Capture

1) Read first post, there is the answer
2) If Safetynet pass CTS, will work Google Pay. About the future, if Google decides to check hardware, there is no way to pass CTS, so no Google Pay. The developer of Magisk has a twit about that explaining.

Hmm, I got this:
Code:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2 (773764 KB)...
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
Edit:
All good now, I didnt boot correctly in fastbootd mode.

bamdadkhan said:
well i tried everything..
- spun up a VM with vagrant and copied over the .sin files, did an unsin but the super one only produced an .img not a .ext4. tried flashing that but it want't happy.
- so i tried flashtool's sin editor but that complained about this version of sin being too new.
- then i found some (bad) info in the net about using an *older* version of flashtool for this. of course that didn't work either.
even though i'm really interested in this (especially since the other lineage ROM has major bugs), i had to give up.
Click to expand...
Click to collapse
usin is enough for you to unpack these sin file, you could flash these files unpacked by it. .ext4 is only an example,.
If you want to go back to stock, you need to reloack your device, then repair it with Xperia Companion.
bmo2718 said:
You didn't mention it in your description but in the download link it says this is for XQ-AU51 (single SIM). Will it still work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
SS/DSDS configs stored in vendor partition. So it's depend on your stock FW version.
Meloferz said:
Hi @Sjll, do you think that this commit will help activating L1 for Xperia 10 II and possible another mark II devices?
Luk added that on Xperia XA2 and enabled widevine L1 for it
Click to expand...
Click to collapse
We are using stock vendor blobs, so these files are never missing, you could only get L3 level on unlocked status.
adem_blackv said:
I have some questions
1)Will you add suport of Google Camera?
2) Does Google Pay work? and will it work in future? A heard something like that Google want start check Safenet with hardware solutions
Stock ROM doesn't has Level3 and RAW Capture
Click to expand...
Click to collapse
Gcam is really nice, but as you said, Xperia 10 II doesn't support RAW support, if I have time, I will try to port camera hal from SODP, which support RAW.
Meloferz said:
1) Read first post, there is the answer
2) If Safetynet pass CTS, will work Google Pay. About the future, if Google decides to check hardware, there is no way to pass CTS, so no Google Pay. The developer of Magisk has a twit about that explaining.
Click to expand...
Click to collapse
Sorry, GMS is not avaliable in China. You could try to pass Saftynet with some Magisk modules. I don't know much about it.

Sjll said:
We are using stock vendor blobs, so these files are never missing, you could only get L3 level on unlocked status.
Click to expand...
Click to collapse
I know that we get L3 for widevine after unlocking bootloader, I just point you with that commit if could help to activate L1 for the Xperia 10 II with LOS, because Luk (Xperia XA2 series maintainer for LOS) could activate L1 for it with bootloader unlocked and using Lineage OS

After everyth
Meloferz said:
I know that we get L3 for widevine after unlocking bootloader, I just point you with that commit if could help to activate L1 for the Xperia 10 II with LOS, because Luk (Xperia XA2 series maintainer for LOS) could activate L1 for it with bootloader unlocked and using Lineage OS
Click to expand...
Click to collapse
I guess this is because nile platform has L1 after unlocked on Pie on stock. But we only have L3 on stock.
https://review.lineageos.org/c/LineageOS/android_device_sony_nile-common/+/269526

Question Vivo X Fold: OEM unlock seems to be there, root anyone?

I don't have the Vivo X Fold — am interested in getting it.
From what I've been reading there seems to be OEM unlock present in the settings…
Anyone rooted somehow? I haven't used a Vivo device yet — just Samsung, so with the restrictive Chinese approach assume there'd be no full firmware downloads, whereby Magisk patching tse boot would be easy. Or am I wrong?

I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.

AndroPlus said:
I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Click to expand...
Click to collapse
Many thanks! :0)
Is there a way to buy such a device online? Do you know any seller who will check and guarantee this?

白い熊 said:
Many thanks! :0)
Is there a way to buy such a device online? Do you know any seller who will check and guarantee this?
Click to expand...
Click to collapse
I don't know, you should ask seller to see if they can do it...

AndroPlus said:
I unlocked bootloader and rooted, I usee DSU Loader and dd command to extract boot.img from the device. (search it)
Click to expand...
Click to collapse
I'm searching fro DSU loader info — never used it before — and reading up on it. Thanks for the pointer.
Just for more details if I may:
— dd boot partition — understood; Looking now for how to via DSU loader.
— Then you patch via Magisk Manager I assume, right?
— How do you then flash back to phone? DSU loader again? Or is that where it's “magic ” comes in, it creates a virtual partitIon somewhere, placed modified boot there and you boot off of it?
— If the above is the case, do you boot modified via some boot combo?
— If it isn't the case, could you briefly describe?
Many thanks. :O)

> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?

robsmith11 said:
> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?
Click to expand...
Click to collapse
That's usually the case…

白い熊 said:
That's usually the case…
Click to expand...
Click to collapse
Even on phones that can be officially unlocked like Google Pixels?
That sucks. I only have experience using root with 3rd party roms, so didn't realize that.

白い熊 said:
I'm searching fro DSU loader info — never used it before — and reading up on it. Thanks for the pointer.
Just for more details if I may:
— dd boot partition — understood; Looking now for how to via DSU loader.
— Then you patch via Magisk Manager I assume, right?
— How do you then flash back to phone? DSU loader again? Or is that where it's “magic ” comes in, it creates a virtual partitIon somewhere, placed modified boot there and you boot off of it?
— If the above is the case, do you boot modified via some boot combo?
— If it isn't the case, could you briefly describe?
Many thanks. :O)
Click to expand...
Click to collapse
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
1. Download AOSP GSI (system-squeak-arm64-ab-vanilla.img.xz) from Phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
2. Once you prepared DSU, reboot from notification to boot into DSU's image
3. Connect USB cable
4. Run these commands in command prompt or powershell:
adb shell
su
dd if=/dev/block/by-name/boot of=/data/local/tmp/boot.img
chown shell.shell /data/local/tmp/boot.img
5. Exit adb shell and run this command to pull boot.img:
adb pull /data/local/tmp/boot.img
6. Patch boot.img with Magisk app
Installation
The Magic Mask for Android
topjohnwu.github.io
7. Reboot into bootloader and run:
fastboot flash boot magisk_patched_[random].img
robsmith11 said:
> Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Does that mean after you unlock, you won't be able to install any Android updates or security patches (and remain unlocked)?
Click to expand...
Click to collapse
No, you can get OTA update even after unlocking and remain unlocked.
First attempt will fail but then updater app downloads full zip automatically.

AndroPlus said:
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
Click to expand...
Click to collapse
Many thanks for the details.
I'm trying to find a pre-end-of-April device seller online now… :O)
BTW — is there a clean reflash or something option to rescue Vivo devices — if you brick it after root? Just factory reset from Recovery would do I guess.
Reason being — sometimes you're too eager to do somethIng and end up in a bootloop — happens to me from time to time - and I guess here the risk would be significant having to freeze all the China bloatware…
I would think there is Recovvery reset — but best to ask, I've never seen a Vivo device…

白い熊 said:
Many thanks for the details.
I'm trying to find a pre-end-of-April device seller online now… :O)
BTW — is there a clean reflash or something option to rescue Vivo devices — if you brick it after root? Just factory reset from Recovery would do I guess.
Reason being — sometimes you're too eager to do somethIng and end up in a bootloop — happens to me from time to time - and I guess here the risk would be significant having to freeze all the China bloatware…
I would think there is Recovvery reset — but best to ask, I've never seen a Vivo device…
Click to expand...
Click to collapse
Yes, factory reset from recovery or flash correct partition from fastboot (in case you flashed wrong/corrupted image).
There's EDL mode too, but I don't know if it can be used.
PD2145F_EX_A_3.11.8_vivo_qcom_LA.UM.9.14.r1-12600-LAHAINA-sm7325-sm8350_split_GsmMafia.Com.rar
drive.google.com

AndroPlus said:
Yes, factory reset from recovery or flash correct partition from fastboot (in case you flashed wrong/corrupted image).
There's EDL mode too, but I don't know if it can be used.
PD2145F_EX_A_3.11.8_vivo_qcom_LA.UM.9.14.r1-12600-LAHAINA-sm7325-sm8350_split_GsmMafia.Com.rar
drive.google.com
Click to expand...
Click to collapse
edl can't be used, needs authorization from vivo

AndroPlus said:
Note that the device must be before 2022-04-30 compile time to unlock bootloader, latest firmware blocks unlocking.
Click to expand...
Click to collapse
I'm communicating with some Chinese sellers on ebay - it's all shady in a regular way :O) - is the compile time printed somewhere on tthe box outside?
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
They're all saying - we can't break the seal and check, since then it's a used phone - logical. But also: don't worry it'll be OK - which usually means it won't… :O)

白い熊 said:
I'm communicating with some Chinese sellers on ebay - it's all shady in a regular way :O) - is the compile time printed somewhere on tthe box outside?
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
They're all saying - we can't break the seal and check, since then it's a used phone - logical. But also: don't worry it'll be OK - which usually means it won't… :O)
Click to expand...
Click to collapse
There's "生产日期" (Manufactured date) on the back of the box, and if it's 2022-04 it should have firmware with compile time before 2022-04-30.

白い熊 said:
Or is there manufacture time there? And go by that? Could you tell me exactly where on the box - or, if possible, share a pic?
Click to expand...
Click to collapse
My phone's manufactured date is 2022-06-27, and compile time is 2022-04-21.
I didn't install any updates yet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

KestL said:
My phone's manufactured date is 2022-06-27, and compile time is 2022-04-21.
I didn't install any updates yet.
View attachment 5676893 View attachment 5676895
Click to expand...
Click to collapse
Yeah - the problem is, there's no way to check compile time unless you go into Settings and for this you have to unseal the box — so they don't want to do this with an unused phone…

Hi guys, i read all you wrote and Im very interested in unlocking Vivo X note, but i have updated it (a few days ago), one thing i dont understand is what would possibly happen if i unllock the bootloader. Im very interested in doing it to flash any gsi and at least get wearOs working. Sorry, i know its not the phone, but i dont know where to ask

The X Note and the X Fold share the same underlying Origina OS Ocean operating system. Each has slightly different versions of the firmware, with the latter being 'tweaked' for use with the tablet style screen. With both phones the exploit that existed that allowed unlocking of the bootloader was patched by June's security update. If you have updated your X Note recently then you can't unlock your bootloader. There are currently no "downgrade" firmware packages available via the Vivo downgrade application. If Vivo makes these available then you could downgrade to May's firmware and use the exploit described in the X70 Pro forum to unlock and then you could flash with Magisk and do whatever you need to do. You can't at present.

frcraig said:
The X Note and the X Fold share the same underlying Origina OS Ocean operating system. Each has slightly different versions of the firmware, with the latter being 'tweaked' for use with the tablet style screen. With both phones the exploit that existed that allowed unlocking of the bootloader was patched by June's security update. If you have updated your X Note recently then you can't unlock your bootloader. There are currently no "downgrade" firmware packages available via the Vivo downgrade application. If Vivo makes these available then you could downgrade to May's firmware and use the exploit described in the X70 Pro forum to unlock and then you could flash with Magisk and do whatever you need to do. You can't at present.
Click to expand...
Click to collapse
Thanks man a lot.
So the only thing i can do is wait.

AndroPlus said:
Maybe it's easier to use DSU Sideloader app.
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
The step to root is:
1. Download AOSP GSI (system-squeak-arm64-ab-vanilla.img.xz) from Phhusson
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
2. Once you prepared DSU, reboot from notification to boot into DSU's image
3. Connect USB cable
4. Run these commands in command prompt or powershell:
adb shell
su
dd if=/dev/block/by-name/boot of=/data/local/tmp/boot.img
chown shell.shell /data/local/tmp/boot.img
5. Exit adb shell and run this command to pull boot.img:
adb pull /data/local/tmp/boot.img
6. Patch boot.img with Magisk app
Installation
The Magic Mask for Android
topjohnwu.github.io
7. Reboot into bootloader and run:
fastboot flash boot magisk_patched_[random].img
No, you can get OTA update even after unlocking and remain unlocked.
First attempt will fail but then updater app downloads full zip automatically.
Click to expand...
Click to collapse
Do you need unlock bootloader at first?