Related
Presenting the latest development version of the TeamWin Recovery Project's touch recovery for the HTC Wildfire S. TeamWin Touch Recovery now has official builds available through TeamWin and GooManager for the Marvel. With any luck MarvelC support will soon follow. Please visit the TWRP and TeamWin pages for more information.
Compiled for and tested on the original GSM Marvel. Always awaiting more testing from CDMA Marvel users. This software is provided without support or warranty: use it at your own risk.
Known Issues:
Fails on a handful of new GSM Marvel devices with updated/incompatible hardware, locking at the initial HTC splash screen.
Change Log:
XX:XX XX/8/2012 - Initial release of TWRP v2.2.2.0: Upstream code changes resolve the issues with formatting SD-EXT and partitioning the SD-Card. Includes the initial release of a revised 320x480 default theme with cleaner action pages, slightly larger buttons and more spacious checklists. First stable, full-featured and issue free release of TWRP for the HTC Wildfire S. Previous buggy versions have been removed from the revision history and can no longer be downloaded.
17:35 19/08/2012 PDT - Second release of TWRP v2.2.1.5: Issues with offmode charging resolved thanks to kalaker.
23:32 17/08/2012 PDT - Initial release of TWRP v2.2.1.5: Upstream code includes changes that resolve issues with the system rebooting during backup operations.
03:00 06/08/2012 PDT - Initial release of TWRP v2.2.1.4: Upstream code includes a handful of nice little bug fixes including a resolution for the mount issues.
23:05 05/08/2012 PDT - Minor aesthetic tweaks to the new theme.
02:29 05/08/2012 PDT - Third release of TWRP v2.2.1: Includes a carefully scaled v2.2 theme enabling the latest release's advanced features.
22:59 28/07/2012 PDT - Second release of TWRP v2.2.1: Corrected a glitch in my build environment that could have lead to issues and then forked it for dedicated platform builds. First dedicated MarvelC build.
23:58 27/07/2012 PDT - Initial release of TWRP v2.2.1: Compiled from the most recent code provided by: TWRP, Cryptomilk and the CyanogenMod ICS-Release branch.
22:55 09/07/2012 PDT - Maintenance release of TWRP v2.1.8: Reconfigured and shrank the kernel in order to utilize a less aggressive form of compression than LZMA. Switched from the CyanogenMod ICS branch to ICS-Release.
12:35 09/07/2012 PDT - Initial release of TWRP v2.1.8: Built using the ICS branchs of the CyanogenMod and Cryptomilk Marvel sources. Oversized image required LZMA compression.
To Do:
Build flashable .ZIP
Download Links:
TWRP for GSM HTC Wildfire S (Marvel) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 34f201ec8c8b0f0d2eae64c88ac3d888
TWRP for CDMA HTC Wildfire S (MarvelC) v2.2.2.0 (Preview Release) - Image - Mirror
MD5: 7c4d137a37098900ff3b2a9412ee8994
This is not the place for support.
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! THIS IS!
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. Please limit all discussion in this thread to development issues. I've started you off with some installation instructions as that was the first issue. I will update and check in as necessary. Enjoy!
You need to have the HTC drivers installed.
Then in cmd type:
fastboot flash recovery recovery.img.
Place the img file in the same folder as the adb files, so you won't have to specify a path.
Good luck,
Awesome work btw. :laugh:
WoefulDerelict said:
I apologize in advance for what may seem abusive but, as it has been laid down here in the RULES and I CLEARLY stated there would be ABSOLUTELY NO SUPPORT in my original post, it stands to reason that I'm decently covered.
THIS IS NOT THE PLACE FOR YOUR QUESTIONS! Ignorance and stupidity will not be tolerated.
In my infinite generosity I've created a place where users can get answers to frequently asked questions and seek support from one another. As an added bonus it will save you from my wrath. I've started you off with some installation instructions as that was the first issue. Enjoy!
Click to expand...
Click to collapse
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
He means he wont be answering any questions in this thread.............he created another thread for discussion in the general section
Semantics...
Red5 said:
If you're not going to support this, then this dosent belong in the Dev section... it can go in the General section or Apps section. Only Supported work belongs in the Dev section.
Click to expand...
Click to collapse
I believe the issue here is entirely one of semantics. In my lexicon support encompasses the magical realm of end-user hand holding. In no way do I feel it is necessary or reasonable to expect a user manual with warm and fuzzy walk-troughs of every possible thing you could want to do and some friendly advice with a hug every time the user has a problem with their FREE software. I certainly don't plan to offer any of the above.
I do; however, plan on maintaining my work. I'm quite interested in information that would allow me to improve the image or resolve a reproducible issue. I also have no qualms discussing the work with other developers, providing updates as the code base evolves, accepting proper issue reports or feature suggestions. I'd simply prefer to avoid getting bogged down by questions that could easily be answered by visiting the project's home page or querying Google. I find it quite counter productive to wade through user prattle when I'm trying to fix an issue or collaborate with another developer.
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
I'm not sure what you're asking.
marchelius said:
Hello.
Is this recovery version work on Marvel with black CWM Recovery effect (new graphics hardware) ??
Click to expand...
Click to collapse
This should be compatible with any HTC Marvel based Wildfire S. I believe they are all based on the same SOC. The kernel should have support for all MSM7227 based graphics hardware.
WoefulDerelict said:
This should be compatible with any HTC Marvel based Wildfire S...
Click to expand...
Click to collapse
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Works perfectly on my phone. Mine is the A510e.
The joys of platform fragmentation.
marchelius said:
Should be, but it isn't. After flash, my phone stuck on white screen with green HTC logo after attempt to enter in recovery...
Click to expand...
Click to collapse
SomeDudeOnTheNet said:
Works perfectly on my phone. Mine is the A510e.
Click to expand...
Click to collapse
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
WoefulDerelict said:
I suppose the plus side is that I have some confirmation that the software works on other A501e devices. If you're going to report something as not working could you at least go to the trouble of including your device's identifying information? A510b/e, SPL and Radio versions would be a great start.
Click to expand...
Click to collapse
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Main branch broken with CM9 on Marvel since updating to 2.2 code.
TWRP updated their main branch to v2.2 today. While I was hoping for the resolution of current issues their changes break my build with CM9. I'm stepping through the changes presently to see if I reason out what changed between 2.2 and 2.1.8 to cause the issue and correct the it. Stay tuned for more updates.
More please...
marchelius said:
OK.
HTC A510e
Android 2.3.5
EQDKP v4.7
Kernel 2.6.35.10-ga66971c
47.23e.35.3038H_7.57.39.10M
S-ON, unlocked via HTCDev
Click to expand...
Click to collapse
Could I get the HBOOT, MICROP and Radio version from your SPL? Hold the volume rocker and power button down while turning on the device to access the bootloader for that information.
IF these Frankenstein devices exist I'm going to need a profile of the revised hardware in order to correct the issue along with some proud owners to test fixes as I don't have access to one. The Marvel I was given is based off the original hardware profile and TWRP2.1.8 works fine when built with CM9 and the cryptomilk.org MSM7227 kernel. I'll do what I can to fix it but, I'm currently trying to resolve build issues with the new 2.2 release. I'm hoping this new code base along with a revised kernel will resolve many of the current issues.
It's ALIVE!
The problem is it's behaving like I brought it to life with a couple bolts of lightning. To say that it has issues would be overly kind but, it boots and I can navigate around. I'm currently trying to track down all the shorts making 2.2 twitch. Stay tuned.
Fresh revision.
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
WoefulDerelict said:
Finally managed a clean build from the latest source. I'd love for some brave MarvelC users to give it a test before building a flashable .ZIP for the general public.
Click to expand...
Click to collapse
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Yea, I knew that.
eoghan2t7 said:
Thanks but theres a few issues
1. Theme isn't updated
2. On-screen keyboard wont work due to current theme
3 l. Swipe to start backups/restoring wont work due the theme.
More or less this is just like the previous twrp until themes are resized etc
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
WoefulDerelict said:
This was already noted in the original post as the last entry under the known issues header. I maintain this for a reason. Thankfully the themes are XML based and updating it shouldn't be ridiculously difficult. Once I've gotten the issue list stable and nailed down where they are all rooted I'll see what I can do to tackle this and the formatting errors as they seem to be the largest TWRP specific issues I could correct. I wager the XML theme business will be relatively quick and painless.
Click to expand...
Click to collapse
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
eoghan2t7 said:
Yeah the themes are XML based but the image editing will be the worst part
Sent from my Wildfire S A510e using Tapatalk 2
Click to expand...
Click to collapse
I'm trying to imagine that being easy. I'm not totally inept in Adobe or AutoCad products so I'm sure I can toss together something in a week or so. Depends on how much the real job needs my time and brain meats.
Below are a list of all known YU Yureka (Plus) OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - tomato
Current firmware: Android 5.1.1, Build LMY49J, Cyanogen OS version 12.1-YOG4PAS8A4
YOG4PAS8A4 from YOG4PAS3JM - http://builds.cyngn.com/incremental/tomato/cm-tomato-04864afef4-to-5242dd42b2-signed.zip
YOG4PAS6ZA from YOG4PAS3JM - http://builds.cyngn.com/incremental/tomato/cm-tomato-04864afef4-to-f758a6e288-signed.zip (pulled out)
YOG4PAS3JM from YNG1TAS34J - http://builds.cyngn.com/incremental/tomato/cm-tomato-c991cd279d-to-04864afef4-signed.zip
YOG4PAS3JM from YNG1TAS1K0 - http://builds.cyngn.com/incremental/tomato/cm-tomato-00b2e333e8-to-04864afef4-signed.zip
YNG1TAS34J from YNG1TAS1K0 - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-00b2e333e8-to-c991cd279d-signed.zip
YNG1TAS1K0 from YNG1TAS0W0 - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-56deeca328-to-00b2e333e8-signed.zip
YNG1TAS0W0 (Lollipop 5.0.2) - http://builds.cyngn.com/cyanogen-os...deeca328/cm-12.0-YNG1TAS0W0-tomato-signed.zip
XNPH08P from XNPH05Q - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-9828f8e9cc-to-b06a7190f5-signed.zip *
XNPH05Q from XNPH52O - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip
* XNPH08P is a beta update & as reported by the users, it breaks Proximity sensor. Flash at your own risk!
Mirrors
http://forum.xda-developers.com/yureka/general/yu-yureka-mirrors-official-cyanogen-t3107684
SPECIAL THANKS
@oldblue910
@salilrane
@oldblue910 for maintaining similar threads for various Nexus & GPE devices.
HASH (MD5)
Every AndroidFileHost mirror link consists of corresponding MD5 hash; please compare them after download.
INSTALLATION GUIDE
As long as your system is stock, flash (using ADB sideload or from SD card) in stock recovery. Always re-flash the SuperSU zip immediately following to re-gain root access. Bootloader status isn't checked while updating.
Thanks Titokhan...
Thanks for the link. Is there a change list location for this update with from Yureka or cyanogen?
Just updated...
Titokhan said:
Below are a list of all known YU Yureka OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - tomato
Current firmware: Android 4.4.4, Build KTU84Q, Cyanogen OS version 11.0-XNPH05Q
XNPH05Q from XNPH52O - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip (Mirror by @salilrane)
SPECIAL THANKS
@oldblue910
@salilrane
Click to expand...
Click to collapse
Mine is rooted.... And pls tell me how to install @Titokhan
Ashok sha said:
Mine is rooted.... And pls tell me how to install @Titokhan
Click to expand...
Click to collapse
I flashed it on rooted yureka and then wiped dalvik and cache. Then flashed super su and it worked.
Mine was rooted so again flashed the stock firmware and then installed the ota manually.
Titokhan said:
Below are a list of all known YU Yureka OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - tomato
Current firmware: Android 4.4.4, Build KTU84Q, Cyanogen OS version 11.0-XNPH05Q
XNPH05Q from XNPH52O - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip (Mirror by @salilrane)
SPECIAL THANKS
@oldblue910
@salilrane
Click to expand...
Click to collapse
after flashing update will the bootloader be locked
skumar9296 said:
after flashing update will the bootloader be locked
Click to expand...
Click to collapse
Nope; bootloader status is unchanged.
Titokhan said:
Below are a list of all known YU Yureka OTA updates. Each time there is a new OTA update, the links will be posted here as they become available. If you get an OTA notification that we don't have a link for, please pull the filename out of logcat for us before applying the OTA and post it here. Once you post it, I'll update this post and mirror the file, in case CyanogenMod pulls it down in the future.
OTA Updates - tomato
Current firmware: Android 4.4.4, Build KTU84Q, Cyanogen OS version 11.0-XNPH05Q
XNPH05Q from XNPH52O - http://builds.cyngn.com/fota/incremental/tomato/cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip (Mirror by @salilrane)
SPECIAL THANKS
@oldblue910
@salilrane
Click to expand...
Click to collapse
Rooted users will not get ota in mobile?
skumar9296 said:
Rooted users will not get ota in mobile?
Click to expand...
Click to collapse
There shouldn't be any issue as @salilrane has got the OTA though he is rooted.
P.S No need to quote the first post again & again.
First post updated; now includes XNPH08P from XNPH05Q.
Any ota download link for the latest released ota?
Titokhan said:
First post updated; now includes XNPH08P from XNPH05Q.
Click to expand...
Click to collapse
changelog?
@Titokhan someone in yu forums said that this update has been rolled back due some issues is it true??
Did anyone got this update via OTA, if yes then please post a screen shot of the same
how to update this ota?
please any one tell me the process..
hope any one reply:crying:
@die2mrw007
Check the first post carefully.
@skumar9296
No official changelog is provided.
@jadega
Yah, its kind of a beta update. As you know, the thread is dedicated for collecting all OTAs, whether it is beta or final.
@Rakesh251
Read this post carefully.
titokhan said:
@die2mrw007
check the first post carefully.
@skumar9296
no official changelog is provided.
@jadega
yah, its kind of a beta update. As you know, the thread is dedicated for collecting all otas, whether it is beta or final.
@rakesh251
read this post carefully.
Click to expand...
Click to collapse
did not understand how to update ota if i am on stock ota
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
Can anyone add our device to the supported devices list ? This would be very helpful, especially since we have a large internal space, for testing out new ROMs...
Here is how to add support to any device :
https://forum.xda-developers.com/android/development/guide-dualboot-patcher-unsupported-t3647056
I wanted to try it, but I am using my phone on a daily basis and don't have an alternate VoLTE phone... Also I am a bit inexperienced in development... :crying:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
sachinm said:
Tried given steps..
1st latest version not worked when clicked on ROM, failed.
I tried bit old version say 9.3 build 179.. Clicking rom worked.
Then followed all steps but not seen X01BD device while patching zip.
This much i did.. Will check other ways.
Note: we need to check other or older version of dbp
Click to expand...
Click to collapse
Thanks for trying
Did you follow the official method ? Which recovery are you using ? TWRP or PBRP ?
Yes
I have tried it finally... Both unofficial method as well as official..
1) Unofficial method does not seem to work, because the app crashes when we click on the ROMs section... This happens for all snapshots from 9.3.0.r340 onwards... I tried the snapshot before this one i.e. 9.3.0.r327 and there were no crashes. I continued with the unofficial method, flashed PATCH.zip, gave root permissions etc but this method did not work...
2) I tried the official method. I forked the project on Github, made the neccessary changes to the asus.yml file and created a pull request.
Here : https://github.com/chenxiaolong/DualBootPatcher/pull/1380
Now we wait for the changes to be merged with the main repo ... Then test the new release...
I didn't have enough bandwidth, otherwise would have built the apk from source myself... Still there is time ... I'll try to see if I can build the apk ....
Hey guys ... Can anyone please help in building this apk ?
Here is my repository which I forked from the official :
https://github.com/Tyakrish/DualBootPatcher
Just fork from my link and build the apk using the steps described here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-from-source
And here :
https://github.com/chenxiaolong/DualBootPatcher/wiki/Building-DualBootPatcher-using-docker-images
Any update on DBP
sachinm said:
Any update on DBP
Click to expand...
Click to collapse
Unfortunately no... @chenxiaolong has not yet merged the commits with the main repo
There are a lot of commits still waiting...
You can check the status of the commit here:
https://github.com/chenxiaolong/DualBootPatcher/pull/1380
I dont currently have a build environment set up... Otherwise I would have built an unofficial version to test on our device...
Update: The mega link is temporarily down, I have plans and more details coming soon
Hi all,
Here we have some Build 16212 cabs for MSM8974 Lumia's!
For those who don't know already, Build 16212 was accidently released on 1st June 2017 in 3 Branches (rs_iot, rs_xbox and rs_devices) but these cause bootloops and caused *all users to reflash back.
*Some users got the update working on a 735 and Elite X3
THIS IS ONE OF THE ACCIDENTALLY RELEASES UPDATES THAT CAUSED BOOTLOOPS, So only try this if you are wanting to dig into it for testing
If you want to test make sure:
- Unlocked Bootloader
- Date set to at least 1/6/2017
- Expect bootloops
- Cabs are ONLY for MSM8974 devices
Mega Link:
File on MEGA
mega.nz
If you or anyone you know has any other 16212 Cabs, please please share!
lol, didnt expect you here. I hope some glimmer of hope appears out of nowhere.
burd said:
lol, didnt expect you here. I hope some glimmer of hope appears out of nowhere.
Click to expand...
Click to collapse
I'm everywhere yeah hopefully good comes of this!
Empyreal96 said:
Hi all,
Here we have some Build 16212 cabs for MSM8974 Lumia's!
For those who don't know already, Build 16212 was accidently released on 1st June 2017 in 3 Branches (rs_iot, rs_xbox and rs_devices) but these cause bootloops and caused *all users to reflash back.
*Some users got the update working on a 735 and Elite X3
THIS IS ONE OF THE ACCIDENTALLY RELEASES UPDATES THAT CAUSED BOOTLOOPS, So only try this if you are wanting to dig into it for testing
If you want to test make sure:
- Unlocked Bootloader
- Date set to at least 1/6/2017
- Expect bootloops
- Cabs are ONLY for MSM8974 devices
Mega Link:
File on MEGA
mega.nz
If you or anyone you know has any other 16212 Cabs, please please share!
Click to expand...
Click to collapse
Sir/Madam, this Google Drive file seems to be invalid. Can you send it again? We are very interested in the Win10M update after version 1709.
John12138 said:
Sir/Madam, this Google Drive file seems to be invalid. Can you send it again? We are very interested in the Win10M update after version 1709.
Click to expand...
Click to collapse
Yeah the drive link is down sorry, but for good reason! I'll be sharing in a few weeks when I have free time with an actually guide on installing and booting the build
This build linked here has no shell/start, so pretty useless as-is.. but stay tuned!
Empyreal96 said:
Yeah the drive link is down sorry, but for good reason! I'll be sharing in a few weeks when I have free time with an actually guide on installing and booting the build
This build linked here has no shell/start, so pretty useless as-is.. but stay tuned!
Click to expand...
Click to collapse
Thanks for your hard work, I look forward to your new sharing link.
Will this work on the 950 XL? Also, is this dead?