Android 11
10.0.10.HD63CB to 11.0.1.5.HD63CB
url: , payload: (size: 2763742131, metadata_size: 163455, metadata signature: , hash: B75BB0090A5EDA20DFC2ADD3A39F1609782F440C6916DD95FEBB3EFF07785C89
SHA1 597E476A4998CB26B6A61B6D57A9677EBC1EEFFE
February 2021 Security update
10.0.13.HD63CB to 11.0.1.1.HD63CB:
url: , payload: (size: 2751257860, metadata_size: 162370, metadata signature: , hash: C1603970CAAF4869F7BD2FBEF177C377A18984D40947B7F96F3B67D09D16744E)
Size 2.75GB SHA1 176630595d901676a111f951d7bff5e0aa6a6404
April 2021 Security update
11.0.1.1.HD63CB to 11.0.1.2.HD63CB
url: , payload: (size: 325611615, metadata_size: 594919, metadata signature: , hash: 49353DE7B9F9831148C78FC2F38EEC33CEB43126607A0ADF2EAE32A2BC006BBF)
Size 326MB SHA1 9e9f6e647af70b7be8f3f05580ffc320af603d33
June 2021 Security update
11.0.1.2.HD63CB to 11.0.1.3.HD63CB
url: , payload: (size: 214605343, metadata_size: 588720, metadata signature: , hash: 6FDBC3037553A76AF6AB0401558913A2F4D8897E0D83C10948459F5BE00EB741)
SHA1 8a8a8689be965d2cee98bc9b89606a156eef478e
August 2021 Security update
11.0.1.3.HD63CB to 11.0.1.4.HD63CB
url: , payload: (size: 106363136, metadata_size: 441012, metadata signature: , hash:
6143AA11441BE6A9DB246BDB370872B8879B560A52F94289225448E01E158B76)
SHA1 42622490acb227b2af72a2ed779664902cbe8f2d
October 2021 Security update
11.0.1.4.HD63CB to 11.0.1.5.HD63CB
url: , payload: (size: 97763397, metadata_size: 531922, metadata signature: , hash: 20C0BC7D9CBC92117368E8DBADEE9A7E251E04B67337A9697F36FFCC9F86C46D
SHA1 5DFD8A279B1205179EA5A2F477FE94D8BA492F4C
December 2021 Security update
11.0.1.5.HD63CB to 11.0.1.6.HD63CB
url: , payload: (size: 82469170, metadata_size: 368639, metadata signature: , hash: F47B9735E6BB0ACF9CFD9D62EA8558B07FDBAB6830D2A7FF43FF63A324CF17CC
SHA1 11e77affc3412357689b0ac1a57af0000748c874
February 2022 Security update
11.0.1.6.HD63CB to 11.0.1.7.HD63CB
url: , payload: (size: 93163747, metadata_size: 439227, metadata signature: , hash: F113AFFB50E86B37DF675D5689F55ECCA7131C9ABA597550E412E0AC6D502A66
SHA1 ddb3c95704b64d9573c07d3a8a1952819fd69dd8
April 2022 Security update
11.0.1.7.HD63CB to 11.0.1.8.HD63CB
url: , payload: (size: 88754173, metadata_size: 554010, metadata signature: , hash: 5A11D422AC4081B8F50780FDCEF97F74637A9E2B9DEC808DF5AA5890D6C0AE1D
SHA1 38e22c7e6126e13851e9ef1fe8b17246ca358c71
June 2022 Security update
11.0.1.8.HD63CB to 11.0.1.9.HD63CB
url: , payload: (size: 95790995, metadata_size: 446000, metadata signature: , hash: 1770D116AA16FBA1DFF9CC4B8AD68C2ED9565AB17D99C66F4A51032AC5A57501
SHA1 e9bc427e2da0f31f951d2e181ddee328c02b2d31
August 2022 Security update
11.0.1.9.HD63CB to 11.0.1.10.HD63CB
url: , payload: (size: 104399629, metadata_size: 405719, metadata signature: , hash: E84EDFE896F1F39D98F47E133353A15DCAFC967940186AAB5A5B7A43E4511198
SHA1 12140cf105cedd3d780bde75f4d1f4eb39f7a8dc
October 2022 Security update
11.0.1.10.HD63CB to 11.0.1.11.HD63CB
url: , payload: (size: 90963856, metadata_size: 520229, metadata signature: , hash: DCABB33EA9912B046180836F0A996BA9DFCE01D5FD8F7589702CA4F52E0DE02B
SHA1 cbeeb41f8dbe37f6c6dd1325b4d3461514a8c755
December 2022 Security update
11.0.1.11.HD63CB to 12
url: , payload: (size: 4083260429, metadata_size: 157030, metadata signature: , hash: DAF81C20C3101E1A31E883A9B05BD686A037EEDE5AC5EA6FD5384F7F69559E93
If you look at my post history you will se why i'm not happy with this update.
Every version after 10.0.13 is broken. I randomly am unable to place or receive calls. The phone simply states that network is unavailable.
I'm also unable to use my USB-C to USB-C and 3.5mm splitter to charge the phone and use the headphones at the same time. This issue was not present on 10.0.14 but was in 0.15
I was hoping that T-Mobile was holding the update back to fix these issues as I was using the global version before but it looks like it's just as broken on their release. I'm sick of this phone and of OnePlus. I'll be looking for a way to downgrade back to x.13 which has no issues, but now I'll have to wipe my phone. Great.
Delta105RUS said:
If you look at my post history you will se why i'm not happy with this update.
Every version after 10.0.13 is broken. I randomly am unable to place or receive calls. The phone simply states that network is unavailable.
I'm also unable to use my USB-C to USB-C and 3.5mm splitter to charge the phone and use the headphones at the same time. This issue was not present on 10.0.14 but was in 0.15
I was hoping that T-Mobile was holding the update back to fix these issues as I was using the global version before but it looks like it's just as broken on their release. I'm sick of this phone and of OnePlus. I'll be looking for a way to downgrade back to x.13 which has no issues, but now I'll have to wipe my phone. Great.
Click to expand...
Click to collapse
Maybe you have to flash the other images for the calls to work because I was on it and it works for me... I just flashed the europe firmware because all the custom ROMs use the firmware from EU but you need the flash all bat to do that...
[email protected] said:
Maybe you have to flash the other images for the calls to work because I was on it and it works for me... I just flashed the europe firmware because all the custom ROMs use the firmware from EU but you need the flash all bat to do that...
Click to expand...
Click to collapse
I guess I could try the EU version, but it works on the 10.0.13 global. And if custom ROMs are based on EU ROM, then I think the issue would persist, because the issue also happened on 2 custom roms I've tried.
I'm sorry... but that's not the case with me... I'm running a personal build of lineage Os now... and I had to flash EU firmware from T-Mobile firmware because mobile data wouldn't work but it's ok now... I'll upload it to drive later if you want to try it out (Los)
[email protected] said:
I'm sorry... but that's not the case with me... I'm running a personal build of lineage Os now... and I had to flash EU firmware from T-Mobile firmware because mobile data wouldn't work but it's ok now... I'll upload it to drive later if you want to try it out (Los)
Click to expand...
Click to collapse
You built los for op7t? Hallelujah !! Please share
HueyT said:
You built los for op7t? Hallelujah !! Please share
Click to expand...
Click to collapse
It's buggy right now... I have to rebuild it... everything was good but for some reason COD won't open up on the rom but I know what is wrong
Google Drive - Virus scan warning
drive.google.com
But the first one I built is good but the kernel was outdated..28 instead of 31
[email protected] said:
But the first one I built is good but the kernel was outdated..28 instead of 31
Click to expand...
Click to collapse
This deserve its own thread !!!
HueyT said:
This deserve its own thread !!!
Click to expand...
Click to collapse
I'm not going to do that because there's a Dev that is going to be getting the phone and doing Official Los so... I'll leave that up to him.
Luk's builds r unofficial also
HueyT said:
Luk's builds r unofficial also
Click to expand...
Click to collapse
Well I'm building something now... when it finishes I'll give you the link
HueyT said:
This deserve its own thread !!!
Click to expand...
Click to collapse
[email protected] said:
I'm not going to do that because there's a Dev that is going to be getting the phone and doing Official Los so... I'll leave that up to him.
Click to expand...
Click to collapse
this thread topic is the ota lets keep on topic please.
[email protected] said:
Well I'm building something now... when it finishes I'll give you the link
Click to expand...
Click to collapse
This works awesome. Thanks
cars1189 said:
this thread topic is the ota lets keep on topic please.
Click to expand...
Click to collapse
Oxygen updater app can give access to eu, usa, indian stock roms easily:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
HueyT said:
Oxygen updater app can give access to eu, usa, indian stock roms easily:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Click to expand...
Click to collapse
This topic is stock for tmobile otas updater app doesn't apply here.
You're asking for trouble to do partial OTA flashes, especially with locked bootloader--difficult to unbrick
cars1189 said:
This topic is stock for tmobile otas updater app doesn't apply here.
Click to expand...
Click to collapse
Sure it does as it's much safer to do whole rom stock clean flashes
HueyT said:
Sure it does as it's much safer to do whole rom stock clean flashes
Click to expand...
Click to collapse
No Oxygen Updater doesn't work for t-mobile stock. Nothing to do with safe or not the app is irrelevant here.
"
In the same way as OnePlus 6T and 7 Pro sold by T-Mobile, it is not possible to install any updates retrieved from another source than T-Mobile.
Therefore it is not possible to offer updates for this device in the app."
so again please stay on topic.
Related
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.
Preview Picures:
https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2
https://forum.xda-developers.com/showpost.php?p=78870686&postcount=436
https://forum.xda-developers.com/showpost.php?p=79450390&postcount=619
https://forum.xda-developers.com/showpost.php?p=79460850&postcount=624
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Known Bugs:
Camera is under development.
[TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion
Bugreport:
A bugreport needs logcat, dmesg and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@nasko_spasko
@laoli0913
@twistedddx
@dhacke thank your for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony
Source Code: https://github.com/SonyAosp
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-08
Created 2018-09-16
Last Updated 2020-10-23
Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with 7-zip or Linux.
GCAM (Need GAPPS, but improves the camera a lot):
I usually use the newest Arnova's GCAM
Installation:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG
News
05.01.2020
this rom is now officially end of life like the omnirom.
Future development happens only on android 10.0 with kernel 4.14.
Of course this doesn't automatically make this rom unusable.
Click to expand...
Click to collapse
27.10.2019
sonyaosp 9.0.0_r46
august security patch
newest sync with sodp code.
Fixed not working touch for the few xz2 (compact) users with tcm touch chip.
(i don't know why the tcm chip got rarely used in the xz2 & xz2 compact hardware).
Ps: The new security updates are only happening on android 10 and require backporting to 9 from developers who know what they are doing to avoid any new (security) bugs.
We sadly don't have this capacity.
Click to expand...
Click to collapse
07.09.2019
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
https://github.com/sonyxperiadev/bug_tracker/issues/351
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
apollo_v8.zip
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
28.08.2019
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast sonyaosp switches to q.)
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
08.08.2019
sonyaosp 9.0.0_r46
august security patch
new glove mode
Click to expand...
Click to collapse
12.07.2019
sonyaosp 9.0.0_r44
july security patch
Click to expand...
Click to collapse
16.06.2019
sonyaosp with june 2019 security patch level.
Click to expand...
Click to collapse
31.05.2019
sonyaosp with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
https://git.ix5.org/felix/dualsim-patcher/pulls/3
Click to expand...
Click to collapse
19.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
11.05.2019
next build will hopefully contain the open source chromium browser cherry-picked from omnirom.
(if i didn't it wrong, the builds are at
out/target/product/{devicename}/obj/apps/chromium_intermediates/
and
out/target/product/{devicename}/system/app/chromium/chromium.apk)
so we have at least one browser build in and this should also fix maybe happening webview bug.
Thank you @murrofx and @hingbong for your bugreports!
The next build is on hold (like omnirom and aosp twrp) until we get a new prebuild kernel (prebuild kernels usually ensure that the kernel is working and buildable).
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/le.um.2.3.2.r1.4
Click to expand...
Click to collapse
02.05.2019
i heard that oemv9 will support the hexagon snapdragon processor.
- longer battery life
- faster device
- real hdr plus for our tama camera
Click to expand...
Click to collapse
22.04.2019
oemv8 (camera) support!
Click to expand...
Click to collapse
22.04.2019
attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=77635765&postcount=2
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled.
Click to expand...
Click to collapse
12.04.2019
9.0.0_r35 april security update
much fixes
oemv7 support
you should be able to try aosp 10.0 q gsi's with it!
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
21.02.2019
updated the rom for the probably tomorrow released sony oem v6 with updated camera hal!
(beta release, has still a crash with exposure, they are not finished with their work. Don't expect stock like photos "now".)
Click to expand...
Click to collapse
10.02.2019
february 2019 patch level
switch from sony aosp to sonyaosp.
Sony aosp = sonyaosp + additional fixes (like exfat sdcard support)
sonyaosp = aosp + device support fixes for xperias
i excluded the gapps with a bit work and investigation!
Click to expand...
Click to collapse
17.01.2019
january 2019 patch level
Click to expand...
Click to collapse
09.01.2019
moved to android file host.
Added builds for every supported device.
Click to expand...
Click to collapse
22.12.2018
added the xz3 (akatsuki).
Camera still not feature complete.
Please search or report bugs in the bug tracker.
Twrp will follow.
Click to expand...
Click to collapse
29.11.2018
first android 9.0 build.
added the xz2c (apollo).
Should be stable enough for stable use.
Please search or report bugs in the bug tracker.
Click to expand...
Click to collapse
12.10.2018
new build with fixed bugs.
including the fixed display damaging bug.
May may maaaaaaaaay you get graphical/display issues, you should deactivate your device asap with (vol up + power)
Click to expand...
Click to collapse
24.09.2018
build "2018-09-14_15:00+2:00":
Switched back to oem vendor img for android 8.1.
The oem vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse
16.09.2018
first release of the unstable, bugfull build.
Click to expand...
Click to collapse
Deleted. Reason: wrong thread.
Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.
Haldi4803 said:
Anyone that has AOSP installed can do me a Favor and run a MicroSD Speed Test?
I.E Androbench and in Settings switch target partition to MicroSD folder.
Click to expand...
Click to collapse
The sdcard Support is still missing.
(Look at the bug list)
24.09.2018
Build "2018-09-14_15:00+2:00":
Switched back to OEM vendor img for Android 8.1.
The OEM vendor 9.0 img shouldn't be used.
Click to expand...
Click to collapse
https://github.com/sonyxperiadev/bug_tracker/issues/169#issuecomment-424278920
PLEASE DON'T FLASH TAMA WITH THE CURRENT KERNEL
My Akari's display got permanently damaged.
I repeat, DO NOT FLASH.
Click to expand...
Click to collapse
I planned a new build on thuesday with the new kernel fixes.
But now I will wait.
The AOSP 4.9 kernel is now stable enough to get prebuild by sony.
(Which is inside my TWRP builds)
Nice.
https://github.com/sonyxperiadev/vendor-sony-kernel/tree/aosp/LE.UM.2.3.2.r1.4
My next AOSP ROM will probably get nice fixes. (Should still be tested and confirmed).
But he still need to confirm if the hardware damaging bug got really fixed or only by a workaround.
https://github.com/sonyxperiadev/bug_tracker/issues/166#issuecomment-425406778
HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .
margee82 said:
HI every1 !
Does any1 know why I am unable to find any Xperia XZ2 rom in the web at all ?
I hate the feeling I can't use Gcam at all because of Cam2 API is not supported .
Click to expand...
Click to collapse
Do you mean Custom ROMs?
The XZ2 was introduced with a brand new kernel.
It took months make it compatible with AOSP to create custom ROMs and even since the compatibility stock update in September, the aosp support needs more work.
After that and my TWRP starts working, the custom creation will start.
Probably I make a new build with synced sources in 3 weeks.
Then the user github user kholk will be back from his 15 days vacation.
(He mentioned the display damage but and created the workaround).
Status Update!
https://github.com/sonyxperiadev/kernel/pull/1688#issuecomment-428714128
kholk said:
MSM8956 Loire stability not impacted by the upstream updates. @oshmoun never saw stability issues due to that.
Tone testing can be started since this platform is stable.
Tama testing will happen soon, after display issues get solved.
Display Issues = The Big Hardware Damaging Bug!
Yoshino, Nile on hold due to stability issues to be solved.
Click to expand...
Click to collapse
Display issues = The Big Hardware Damaging Bug!
It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.
MartinX3 said:
It seems that I will make a new AOSP Build this week.
The Sony Developers made a rampage in the XZ2 Bug List on Github and closed important bugs, including the display damaging bug.
Click to expand...
Click to collapse
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms
hary232 said:
Are you aware that sony released new binaries for 8.1 ?
im curious what the binary brings for 8.1 roms
Click to expand...
Click to collapse
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers
MartinX3 said:
Yeahr and switched to 8.1.0r47
That are the AOSP hardware drivers
Click to expand...
Click to collapse
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?
hary232 said:
cool. i assume you are planning to release a build soon then (after the build error gets fixed by sony, of course)?
Click to expand...
Click to collapse
Yes
You saw my reported build error?
MartinX3 said:
Yes
You saw my reported build error?
Click to expand...
Click to collapse
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.
hary232 said:
yes! i really look forward for DRS functionality.
i'm monitoring the github from time to time. still not pulling the trigger to unlock the bl tho.
At any case, thank you for your hard work so far.
Click to expand...
Click to collapse
Thank you
After storm released the DRMfix (after I gave him the ok) you can use your stock firmware like you had never unlocked the BL
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the OmniROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on OmniROM Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.
Preview Picures:
https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2
https://forum.xda-developers.com/showpost.php?p=78856492&postcount=4
https://forum.xda-developers.com/showpost.php?p=79450402&postcount=443
https://forum.xda-developers.com/showpost.php?p=79460796&postcount=456
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Known Bugs:
Camera is under development.
[TAMA] [AKATSUKI] [CRITICAL??] Speakers clipping and distortion
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
OmniROM Bugtracker -> If you think the problem is in OmniROM
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs logcat, dmesg and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@oshmoun for his device tree portings
@dhacke thank your for providing a download server
And the OmniROM developers!
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
OmniROM, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, oshmoun, OmniROM
Source Code: https://github.com/omnirom/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: OmniROM
Version Information
Status: No Longer Updated
Current Stable Version: 9
Stable Release Date: 2019-08-10
Created 2019-02-07
Last Updated 2020-10-23
Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with 7-zip or Linux.
GCAM (Need GAPPS, but improves the camera a lot):
I usually use the newest Arnova's GCAM
Installation:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
(Mandatory on dual sim devices) Dual Sim Patcher
(Optional) https://opengapps.org/ or MicroG
In case of touch issues on the XZ2 compact:
Download (try the v10 zip first, if it doesn't work try v9 or v8)
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(Mandatory on dual sim devices) Dual Sim Patcher
If your system apps did loose their permissions (sadly that happens sometime after flashing a boot.img again -> AOSP bug which is maybe fixed in 10.0)
fastboot flash userdata userdata.img (Flashing the boot.img may
(Optional) https://opengapps.org/ or MicroG
News
05.01.2020
i thought pushing a maintenance update would be a good idea.
Sadly it wasn't achievable.
I tried to simply rebuild the old sodp sync with the newest omnirom, also synced the newest sodp stuff wit the newest omnirom.
But that every time resulted into
1. Installing gapps on a fresh system let the device crash into twrp with the message "set_policy_failed:/data/cache/"
2. Upgrading from the previous version resulted into "no web views detected". The webview is needed for some apps to render their content. Without that they would simply crash.
Regardless if the gapps, aosp or bromite webview was installed, none was listed and the logcat throws errors.
3. The audio doesn't route anymore to a connected usb audio 3.5mm adapter.
4. There may be more bugs, but i am too frustrated to with the already occurring bugs and invested hours/days.
Lets look optimistically into the future of android 10.0, kernel 4.14 and which custom roms can be build on it.
Click to expand...
Click to collapse
12.10.2019
https://gerrit.omnirom.org/#/q/topic:asb_2019-09+(status:open+or+status:merged)
https://gerrit.omnirom.org/#/q/topic:asb_2019-10+(status:open+or+status:merged)
omnirom 9 may be deprecated, but it seems that they backport security fixes.
Soooo, we get still security updates.
On the other side i got insulted (called a stupid idiot), warned, kicked and banned at once for asking about the security commits and saying that the insulter has a low emphatic intelligence.
I look if i will continue distributing stuff for this toxic community administration.
Click to expand...
Click to collapse
04.10.2019
it's official announced by the omnirom boss.
Omnirom 9 reached end of life and is now deprecated.
Omnirom 10 for xz2, xz2c, xz3 will come after the sony aosp builds with q and kernel 4.14 are stable enough.
Click to expand...
Click to collapse
07.09.2019
dear xz2 compact owners with not working touch.
It seems that we fixed the problem
https://github.com/sonyxperiadev/bug_tracker/issues/351
the code needs to to get refactored and merged into sodp, before i can release new builds.
But anyway, i'm on vacation & studying for exams, so don't expect builds earlier than end of september/october.
To test it
apollo_v8.zip
Code:
fastboot flash boot boot.img
fastboot flash vendor vendor.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
28.08.2019
someone may have seen that in september comes a sodp switch to
1. Android 10 (queen cake)
2. Kernel 4.14 (using 4.9 at the moment)
i won't switch asap to the new stuff and wait until it proofs enough stability to act as a daily driver.
Maybe it is stable directly right release (i don't think it) or it may take ~1-5 months.
(and i don't know how fast omnirom switches to q.)
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
11.08.2019
omnirom 9.0.0_r47
august security patch
new glove mode
Click to expand...
Click to collapse
12.07.2019
omnirom 9.0.0_r44.
July security patch.
Click to expand...
Click to collapse
11.06.2019
omnirom 9.0.0_r40.
June security patch.
Click to expand...
Click to collapse
31.05.2019
omnirom with may 2019 security patch level.
Newer, faster, more stable, oemv9 support.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
There is also the twrp dual sim patcher. Without it the single sim firmware won't work on a dual sim phone.
That'll save bandwith and server storage.
I linked the patcher on the first page, but use my uploaded v4alpha patcher instead.
It contains my complete overhaul of the patcher and the current v3 in the xda thread doesn't work on tama.
I already made a pull request and the author just needs to merge my changes.
https://git.ix5.org/felix/dualsim-patcher/pulls/3
Click to expand...
Click to collapse
19.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
02.05.2019
i heard that oemv9 will support the hexagon snapdragon processor.
- longer battery life
- faster device
- real hdr plus for our tama camera
Click to expand...
Click to collapse
22.04.2019
oemv8 (camera) support!
Removed buildin twrp.
Twrp needs to get build as -eng, not as -userdebug.
And we got now a working "fastboot boot twrp.img".
Click to expand...
Click to collapse
22.04.2019
attached oemv8 images at the post
https://forum.xda-developers.com/showpost.php?p=78856251&postcount=2
it is only a current snapshot of the camera development.
Expect further improvements with the upcoming oem blobs.
Ps: Oemv8 compatible builds are getting compiled after i released the oemv8 sonyaosp builds.
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
02.04.2019
omnirom 9.0.0_35.
April security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.
Hopefully fixed ril crash with manually merged upstream code from sony aosp sodp.
Click to expand...
Click to collapse
31.03.2019
omnirom 9.0.0_34.
March security patch.
Needs oemv7 blobs.
Improved stability and fixed bugs.
Now with integrated twrp.
Click to expand...
Click to collapse
22.02.2019
updated the rom for the sony oem v6 with updated camera hal!
(beta release, has still a crash with exposure, they are not finished with their work. Don't expect stock like photos "now".)
Click to expand...
Click to collapse
10.02.2019
february security update release.
Click to expand...
Click to collapse
07.02.2019
finaly xda fixed their blocking website bug and i was able to create this new xdadev project.
First release from 01. February 2019
Click to expand...
Click to collapse
Screenshots
Screenshots
Always great devoted work from you!
You have a small typo in your post:
The stock firmware updates doesn't not update your "android"
Should read
The stock firmware updates doesn't just update your "android"
twistedddx said:
Always great devoted work from you!
You have a small typo in your post:
The stock firmware updates doesn't not update your "android"
Should read
The stock firmware updates doesn't just update your "android"
Click to expand...
Click to collapse
xD Thank you
Great job [emoji6]
How is battery life?
Any lag after a few days if use?
Envoyé de mon H8266 en utilisant Tapatalk
niaboc79 said:
Great job [emoji6]
How is battery life?
Any lag after a few days if use?
Envoyé de mon H8266 en utilisant Tapatalk
Click to expand...
Click to collapse
Thank you
The only thing I see so far is the missing camera.
And the phone uses a bit more energy I thing, but I need to test that.
Together with the sony team we did a great step.
Now we support the exFAT file system on sdcards.
(There still needs work to be done in the sepolicy, will take a bit before code gets merged for my next release build)
PS:
ext4 support for sdcards, too.
Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?
Haldi4803 said:
Hooo i see interactive governor in the screenshots?
AOSP does not use EAS or does only OMNI rom not use EAS?
Click to expand...
Click to collapse
erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.
Edit:
Interactive is used.
And there is no EAS.
Deleted
MartinX3 said:
erm, maybe the added EAS stuff last month. Hmm.
I asked some devs now.
Edit:
Interactive is used.
And there is no EAS.
Click to expand...
Click to collapse
So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?
Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.
xFirefly93 said:
So old HMP is used by Sony for their SD845 devices, or is this "workaround" only applied upon their official shared AOSP sources and blobs?
Could in that case explain the increased power consumption, becausr HMP is a leeching sucker compared to Energy Aware Scheduling / EAS.
Click to expand...
Click to collapse
I ask them if there are EAS plans.
Edit:
No plans, seems they don't like it.
Edit1:
Seems that with the other stuff in the kernel the EAS would lead into a battery drain.
And that the AOSP is battery optimized without it.
Ediit2:
They don't hate EAS.
It was just a decision at a time where other parameters lead to this decision.
Maybe they switch to EAS in the future.
Edit3:
EAM Energy Models are needed.
And because it's very hard to get one EAS may never get implemented.
@MartinX3
When do you plan to release the Omnirom build with the february 2019 patch?
dhacke said:
@MartinX3
When do you plan to release the Omnirom build with the february 2019 patch?
Click to expand...
Click to collapse
The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.
MartinX3 said:
The February patch level required a rebuild of my build cache.
It's at 20% since an hour.
I am sure I can upload the stuff this evening.
Click to expand...
Click to collapse
Thx for the info.
dhacke said:
Thx for the info.
Click to expand...
Click to collapse
You're welcome. Feel free to ask.
@MartinX3
Besides of the security patch are there any other fixes in the new upcoming build?
dhacke said:
@MartinX3
Besides of the security patch are there any other fixes in the new upcoming build?
Click to expand...
Click to collapse
It has a build in changelog app.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
-
Links
18. 20210419: april security patch: https://drive.google.com/file/d/1ngw-Ac6JN16L5ZF5NfiVOzgFhrSnO-GZ/view?usp=sharing
17. 20201220: december security patch: https://drive.google.com/file/d/1sSJTq3EmkrF4e-JFgCHNHrN2ArxZn7vO/view?usp=sharing
16. 20200815: august security patch: https://drive.google.com/file/d/1CLna2ZCjwn6excJ48zEORQRs6KEYfwPS/view?usp=sharing
15. 20200724: july security patch: https://drive.google.com/file/d/1nfyXJKb_X4bspfzCEP1PU8TDbvg8CDZf/view?usp=sharing
14. 20200614: june security patch: https://drive.google.com/file/d/1OytkLQnOP_KMzsD52STQWG5QAd-zz_Y4/view?usp=sharing
13. 20200523: may security patch: https://drive.google.com/file/d/1-fNVsac004wNSMspGgJlJaOwFj51MAnV/view?usp=sharing
12. 20200411: april security patch, kernel update: https://drive.google.com/file/d/1yjI9j4dZmOY34AwdGNKv24hcaBg6ObPN/view?usp=sharing
11. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1g4jjvW6u1hiJy2m81QKmyZ-gc1rmeTgB/view?usp=sharing
10. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1oxURZhtzFKu7MlI7VD1QQKwjavVJtBUJ/view?usp=sharing
9. 20191224: https://drive.google.com/file/d/1W0mQdKscN4qiaa6q3uUliTry5n6anPgz/view?usp=sharing
8. 20191215: fix internal speaker, bt calls: https://drive.google.com/file/d/1fXg0qVz7oARO9EkNZ04x8ZIsFejWfcDc/view?usp=sharing
7. 20191210: mobile data: https://drive.google.com/file/d/1fHycuBYogxuQOJuHG_pXHZdh0DnloPPc/view?usp=sharing
6. 20191116: november security patch: https://drive.google.com/file/d/1eexCgGG-vj0c6mEOboP56b4YzeK9WxOl/view?usp=sharing
5. 20191114: https://drive.google.com/file/d/1OuyEPQRMyxikHGjwHSke34cLintfOPnH/view?usp=sharing
4. 20191027: latest code, small cleanup, disable Codec2.0 components (long delay on start youtube) (thanks @followmsi): https://drive.google.com/file/d/1QYe1yi-q_pioLKVaR7EzdS7cqYnPjbs7/view?usp=sharing
3. 20191013: https://drive.google.com/file/d/1Q7DTLmy1HR7H_HJvEvWXyntpGUXpJXOD/view?usp=sharing
2. 20191007: https://drive.google.com/file/d/18SICwdnJqDJpytbCw0z3DgqBPf9_kXCU/view?usp=sharing
1. 20191006: https://drive.google.com/file/d/1NulGtfJV8Zq5F0JUPYwKW8d-AhhhOrLn/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Root
Install latest magisk (20.1+) from canary channel: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/lineageos
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
I'm glad to run a new version of android for note pro 12.2.
Of course we are still at the beginning, the system is at an early stage, there are not even official gapps.
But already a lot of stuff work.
It's great to see that it goes with Lineage 17 for the P905. Thanks a lot Valera1978
Valera1978 said:
I'm glad to run a new version of android for note pro 12.2.
Of course we are still at the beginning, the system is at an early stage, there are not even official gapps.
But already a lot of stuff work.
Click to expand...
Click to collapse
Thank you, Valera!
Really thank you Valera! I'm very happy to see this. I sue this tablet to take notes at university so I have to reporter that palm rejection doesn't work. I hope in the next builds. Keep up the good work and thank you again!
The issue mobil data means, it doesn't work at all?
Dirty install over LineageOS 16.0 did not work. Could boot, but no login possible.
Clean install did work. Got message "Your device has an internal fault. Please contact the manufacturer". But could acknowledge and login. Working using the GApps from the first link (BiTGApps).
Could not get Magisk (19.4) to work. Could flash but Magiskmanager shows not installed and no root.
mad0701 said:
The issue mobil data means, it doesn't work at all?
Click to expand...
Click to collapse
for now - no mobile data at all
pantau said:
Dirty install over LineageOS 16.0 did not work. Could boot, but no login possible.
Clean install did work. Got message "Your device has an internal fault. Please contact the manufacturer". But could acknowledge and login. Working using the GApps from the first link (BiTGApps).
Could not get Magisk (19.4) to work. Could flash but Magiskmanager shows not installed and no root.
Click to expand...
Click to collapse
Right now "Your device has an internal fault. Please contact the manufacturer" message present on all lineage 17 firmwaresю
Magisk workaround is ready, see first post.
Valera1978 said:
Right now "Your device has an internal fault. Please contact the manufacturer" message present on all lineage 17 firmwaresю
Magisk workaround is ready, see first post.
Click to expand...
Click to collapse
Magisk does work now. Thanks a lot!
Thanks so much Valera
Thanks so much Valera, you have been helping us keep our Note Pro alive.
The only point I see need for more attention would be with palm rejection, as this is essential for using s-pen.
Gratitude for your work Valera, God bless you.
Palm rejection fixed?
Does this version fix the palm rejection issue? The last version working I think was Lineage 14.0. I really would like to use the S-Pen again for note-taking.
mnemonic-de said:
Does this version fix the palm rejection issue? The last version working I think was Lineage 14.0. I really would like to use the S-Pen again for note-taking.
Click to expand...
Click to collapse
No one?
dannyt84 said:
No one?
Click to expand...
Click to collapse
You mean that you can lay your hand on the screen while writing with the pen ? I will try to test it once I get the rom working.
dannyt84 said:
No one?
Click to expand...
Click to collapse
No not working
Will this work for the P900 or is it only the P905? Since the only difference is a mobile radio (to my understanding) I don't see why I can't but I don't see it mentioned specifically so figured I'd ask.
Ist only for P905... Processor and other Hardware are different...
Did anyone get safetynet to pass with magisk 20 or canary channel ?
Although i can not enjoy the fruits of your labour cos i have the sm-p900 i was think maybe if its possible to change my motherboard from p900 to the p905 board. i found one on ebay. I have 4 of these tablets i have purchased over the years as i keep dropping them and crack the screen. If anyone knows more if swapping the boards will work please let us know as this could be another way of upgrading and using the big lovely screen with Android 10
Did anyone test if Edxposed is working? Which version? I tried with Beta YAHFA and Sandhook, but did not booting (automatically always Download Mode)...
LineageOS 16Lineage 16.0 - For Nexus 10 Manta
This is a continuation of followmsi's builds.
Disclaimer:
I am not responsible for your actions or consequences, directly or indirectly, related to the files and/or advice offered.
It is your choice to proceed.
Known issues:
- HWC (hardware composer) is partly broken. (Invisible icons, wallpaper, some overlays, preview screen in resent...)
- Camera does not work. (Broken HAL1 camera and unsupported HAL2 camera.)
- Encryption does not work. (Will result in a bootloop)
- NFC may not work correctly and may drain the battery. (You can disable it in the setting menu.)
Instructions:
Clean install:
1. Install TWRP (Custom Recovery)
2. Boot into TWRP and Format Data
3. Wipe all
4. Install ROM
- 4a. Install GApps (Optional)
- 4b. Install Magisk (Optional)
5. Reboot to system
Do not install the TWRP app.
Update install:
1. Boot into TWRP
2. Install ROM
3. Reboot to system
Do not install the TWRP app.
Download Links:
Nexus 10 MediaFire - Link
Nexus 10 SourceForge - Link
Nexus 10 GoogleDrive - Link
Other Links:
<ADD LATER>
Build Sources:
Kernel GitHub - Link
Build Manifest GitHub - Link
Credits:
LineageOS
@followmsi
<RESERVE>
Lineage-16.0 October 2020
- October 2020 Google security updates
Changes:
- Kernel Patch to prevent crash in Firefox and other apps. GitHub - Link
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20201011-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20201011-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
Cheers all.
thank you for continuing this rom.
Thank you for continuing this Nexus 10 ROM.
I've tried it, and had trouble changing the background.
Additionally, when I also tried GApps open_gapps-arm-9.0-full-20201015.zip, I had no Icons (only Icon names), but have not found time to determine if this this was related.
C-Base said:
Thank you for continuing this Nexus 10 ROM.
I've tried it, and had trouble changing the background.
Additionally, when I also tried GApps open_gapps-arm-9.0-full-20201015.zip, I had no Icons (only Icon names), but have not found time to determine if this this was related.
Click to expand...
Click to collapse
Sad to say it was and still is an issue.
Some users stated that switching to a different launcher helped.
Nova and Next were the ones mentioned if I remember correctly.
I added the known issues to the OP.
Cheers.
Lineage-16.0 November 2020
- November 2020 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20201107-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20201107-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
Cheers all.
Lineage-16.0 December 2020
- December 2020 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20201215-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20201215-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
Cheers all.
Lineage-16.0 January 2021
- January 2021 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20210123-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20210123-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
Cheers all.
Lineage-16.0 February 2021
- February 2021 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20210206-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20210206-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
lineage-16.0-20210206-UNOFFICIAL-manta.zip.sha256 MediaFire - Download
Cheers all.
Thank you for your work ipdev!!!
EDIT: May I ask why you decided to continue builds of lineage 16 when followmsi has moved on to lineageos 17.1?
@ipdev thank you for offering this version of Lineage with the security updates. I have a strange problem with purchased play apps using open G apps. Anything i have already bought I have to buy again. Is this a limitation of using Open G apps? Is there an alternative/fix? Im new to this whole thing!!
Thanks
Now resolved - i was using Pico!
bo0gietrain said:
Thank you for your work ipdev!!!
EDIT: May I ask why you decided to continue builds of lineage 16 when followmsi has moved on to lineageos 17.1?
Click to expand...
Click to collapse
Sorry for the extreme delay.
Save for a few issues, Lineage 16 runs quite well on manta.
The Lineage Team maintains the security updates.
Does not take that long to sync and build.
Normally takes longer to upload.
Originally, I was not sure if anyone would want l16 updates for manta.
Until the download count is zero or I can not build l16 anymore, I will run an update when Lineage updates the security.
A while back, I bought a second Nexus 10.
Paid a little more than I should have.
My second manta is still stock partition so, l17 will not fit.
Currently I run l16 without gapps on it.
Cheers.
graham_uk said:
@ipdev thank you for offering this version of Lineage with the security updates. I have a strange problem with purchased play apps using open G apps. Anything i have already bought I have to buy again. Is this a limitation of using Open G apps? Is there an alternative/fix? Im new to this whole thing!!
Thanks
Now resolved - i was using Pico!
Click to expand...
Click to collapse
Hi.
This will happen every now and then.
As you noticed, you waited long enough and Google will update PlayStore and straighten out.
It's a Google thing.
Cheers.
Lineage-16.0 March 2021
- March 2021 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20210307-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20210307-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
lineage-16.0-20210307-UNOFFICIAL-manta.zip.sha256 MediaFire - Download
Cheers all.
ipdev said:
Lineage-16.0 March 2021
- March 2021 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20210307-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20210307-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
lineage-16.0-20210307-UNOFFICIAL-manta.zip.sha256 MediaFire - Download
Cheers all.
Click to expand...
Click to collapse
Is it necessary intall also or alone the last two zip files, please?
tinaag said:
Is it necessary intall also or alone the last two zip files, please?
Click to expand...
Click to collapse
The md5sum and sha256sum are just to verify the zip file.
Both md5 and sha256 generate a hash value that is used as a checksum for a file.
md5 is older, sha256 is newer and more secure.
The files are just text files that include the hash value and the file name.
lineage-16.0-20210307-UNOFFICIAL-manta.zip.md5sum
aa8cb40245c9064ea6d4125a4016ef71 lineage-16.0-20210307-UNOFFICIAL-manta.zip
lineage-16.0-20210307-UNOFFICIAL-manta.zip.sha256
b57509450b267b6d217fa2bc01961e3e83cccfc4c82aa3334cc48dd4e77d2087 lineage-16.0-20210307-UNOFFICIAL-manta.zip
Example using sha256sum on linux.
Run sha256sum on the zip file to display the hash value.
Bash:
[[email protected] 20210307]$ sha256sum lineage-16.0-20210307-UNOFFICIAL-manta.zip
b57509450b267b6d217fa2bc01961e3e83cccfc4c82aa3334cc48dd4e77d2087 lineage-16.0-20210307-UNOFFICIAL-manta.zip
[[email protected] 20210307]$
Run sha256sum using a file that contains the hash value and file name.
Bash:
[[email protected] 20210307]$ sha256sum -c lineage-16.0-20210307-UNOFFICIAL-manta.zip.sha256
lineage-16.0-20210307-UNOFFICIAL-manta.zip: OK
[[email protected] 20210307]$
The md5sum and/or sha256sum are not needed to install the rom.
All the rom zips are full builds so, you can install any one as a clean install.
GApps might be needed depending on the apps you use.
Magisk is necessary if you need to pass SafetyNet.
Cheers.
PS.
My manta running lineage-16.0-20210307-UNOFFICIAL-manta only (No Magisk. No GApps.).
Netflix runs fine.
Lineage-16.0 April 2021
- April 2021 Google security updates
Changes:
- LineageOS 16.0 updates. Gerrit Review - Link
Direct Download:
lineage-16.0-20210412-UNOFFICIAL-manta.zip MediaFire - Download
lineage-16.0-20210412-UNOFFICIAL-manta.zip.md5sum MediaFire - Download
lineage-16.0-20210412-UNOFFICIAL-manta.zip.sha256 MediaFire - Download
Cheers all.
Your build is a lot faster than the Android 10 build! However I made the mistake to apply my own wallpaper, so now I got a black screen. The only way to get the default wallpaper back is to reflash?
Eagleman77 said:
Your build is a lot faster than the Android 10 build! However I made the mistake to apply my own wallpaper, so now I got a black screen. The only way to get the default wallpaper back is to reflash?
Click to expand...
Click to collapse
Agreed. On my 32 GB Nexus 10 this ROM is clearly faster than my previous LineageOS 14.1-20180611. Installing was a bit tricky because even Pico OpenGapps didn't fit on /system but resizing partitions solved that (following these instructions https://forum.xda-developers.com/t/nexus-10-gapps-fix-with-pie.4064613/). Now I have the disappearing icons but let's see what Nova Launcher does to that.
Hello
I would like to start a thread with all the stock and magisk patched Boot Images for the Pixel 6 Pro and it's updates.
I'll try to keep this up to date and always use the latest Magisk Stable for patching new images.
Download Google Drive:
Stable:
13.0.0 (TQ3A.230605.010, Jun 2023)
13.0.0 (TQ2A.230505.002, May 2023)
13.0.0 (TQ2A.230405.003.E1, Apr 2023)
13.0.0 (TQ2A.230305.008.E1, Mar 2023)
13.0.0 (TQ1A.230205.002, Feb 2023)
13.0.0 (TQ1A.230105.002, Jan 2023)
13.0.0 (TQ1A.221205.011, Dec 2022)
13.0.0 (TP1A.221105.002, Nov 2022)
13.0.0 (TP1A.221005.002, Oct 2022)
13.0.0 (TP1A.220905.004, Sep 2022)
13.0.0 (TP1A.220624.021, Aug 2022)
12.1.0 (SQ3A.220705.003, Jul 2022)
12.1.0 (SQ3A.220605.009.B1, Jun 2022)
12.1.0 (SP2A.220505.002, May 2022)
12.1.0 (SP2A.220405.004, Apr 2022)
12.1.0 (SP2A.220305.013.A3, Mar 2022)
12.0.0 (SQ1D.220205.004, Feb 2022)
12.0.0 (SQ1D.220205.003, Feb 2022)
raven - Google Drive
drive.google.com
Disclaimer:
I am not responsible for what you do with your device. I only upload and/or patch the provided boot images.
reserved
#2 just in case
Added 12.0.0 (SQ1D.220205.004, Feb 2022) Stock/Patched.
This is an awesome thread. I don't know why someone didn't start this earlier. Anyone have the 12L beta 3 stock and patched image?
Burt Squirtz said:
This is an awesome thread. I don't know why someone didn't start this earlier. Anyone have the 12L beta 3 stock and patched image?
Click to expand...
Click to collapse
Added 12L beta 3 s2b3.220205.007 🫡
Also added 13 Developer Preview tpp1.220114.016
Yooo mann. Will check this thread for the next update. It will save us a lot of time. Cheers
Burt Squirtz said:
This is an awesome thread. I don't know why someone didn't start this earlier. Anyone have the 12L beta 3 stock and patched image?
Click to expand...
Click to collapse
Because if its readily available, changes often, and is maintained by someone up stream. Some tend to leave it out. Safer with less sources to aquire something. Saves space when releasing. AND Caution If there is proprietary code in the files (there is). it can be come a whole thing to have to deal with in the future.
Haven't heard about google going after anyone like Nintendo does with their code so not a real issue, just technically, sorta, kind of, maybe, actually, for sure is not anyone else's code to distribute outside of the scope of the license.
Android 13 Developer Preview 1
Stock Kernel.
Magisk Patched Kernel . Has both Zygisk and MagiskHide
Thank you for trying to keep this up to date.
Please mind though, everyone, that using someone else's magisk patched boot images can result in problems. It's unlikely, but it has happened - @topjohnwu recommends to always patch the image yourself.
Morgrain said:
Thank you for trying to keep this up to date.
Please mind though, everyone, that using someone else's magisk patched boot images can result in problems. It's unlikely, but it has happened - @topjohnwu recommends to always patch the image yourself.
Click to expand...
Click to collapse
Additionally, you also won't be able to restore the stock boot image via Uninstall or update via the "Install to Inactive Slot" method in Magisk because there will be no stock boot image that is backed up by Magisk since you didn't patch the boot image on your own device.
Just something for people to keep in mind.
Morgrain said:
Thank you for trying to keep this up to date.
Please mind though, everyone, that using someone else's magisk patched boot images can result in problems. It's unlikely, but it has happened - @topjohnwu recommends to always patch the image yourself.
Click to expand...
Click to collapse
I agree.
My take: this thread really shouldn't even exist. Not just because of security though, but because it is utterly redundant.
ALL of the factory images (including boot.img) are available HERE: https://developers.google.com/android/images
And it is trivial to patch magisk to a boot.img using its internal function INSTALL --> Select and patch a file.
*** THE PATCH FUNCTION DOES NOT NEED TO BE PERFORMED ON THE SAME DEVICE!!!
Further, anybody with an ounce of security in mind really shouldn't be using the factory images (and all the built-in tracking) to begin with.
same fastboot cmd used on 13 for patched_magisk.img?
AndroidAddict420 said:
same fastboot cmd used on 13 for patched_magisk.img?
Click to expand...
Click to collapse
Same, latest magisk stable
There is a new way to flash patch_magisk.img :
1st : Patch boot.img
2nd : fastboot boot patched_magisk.img
3rd : Direct Install
AndroidAddict420 said:
There is a new way to flash patch_magisk.img :
1st : Patch boot.img
2nd : fastboot boot patched_magisk.img
3rd : Direct Install
Click to expand...
Click to collapse
That's what I did for months now
AndroidAddict420 said:
There is a new way to flash patch_magisk.img :
1st : Patch boot.img
2nd : fastboot boot patched_magisk.img
3rd : Direct Install
Click to expand...
Click to collapse
You can eliminate step 3 by running 'fastboot flash boot patched.img'
96carboard said:
You can eliminate step 3 by running 'fastboot flash boot patched.img'
Click to expand...
Click to collapse
Doing this could cause boot loop if using a custom kernel, best to boot using patched boot incase anything goes wrong. Reboot and phone should use default boot.img. if boot is fine then step 3
I can't figure out why I am not passing safety net but I am rooted. I followed the root steps from various threads and used the stock 12L bout img from this thread.... Patched it with Magisk..... And flashed that while rooting.
I feel like I'm missing a short step somewhere. Someone help please?
Lycidias said:
Hello
I would like to start a thread with all the stock and magisk patched Boot Images for the Pixel 6 Pro and it's updates.
I'll try to keep this up to date and always use the latest Magisk Stable for patching new images.
Download Google Drive:
Stable:
12.0.0 (SQ1D.220205.004, Feb 2022)
12.0.0 (SQ1D.220205.003, Feb 2022)
Beta:
s2b3.220205.007
Developer Preview:
tpp1.220114.016
raven - Google Drive
drive.google.com
Disclaimer:
I am not responsible for what you do with your device. I only upload and/or patch the provided boot images.
Click to expand...
Click to collapse
Great idea, thanks for this