Before to start flashing
This is an UNOFFICIAL version of CM12.1, so this means that have bugs that i hope to fix soon. So use it carefully at your own risk. The most important thing to say, after flash this ROM,is ....
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Installation Guideline
Install the lastest version of TWRP (it's in uploading state and have an important update in fstab file)
Power down your phone and go in recovery mode.
Copy the ROM file in your sdcard
Make a wipe data/factory reset
Install the zip you copied
Wipe cache
Reboot
What works
First Boot
Audio
RIL
SDCARD
Tethering
LEDS
Touchpad now works
Bluetooth (partial: pairing not works)
Some else i'm testing
Light and proximity sensors, Accelerometer, Gyroscope and Magnetic sensors
What not works
Camera
GPS
NFC
SMS
Anything else i will find and fix
Screenshots and Video
In the top of the pace, section Screenshots.
Download
M4 Aqua ProjectMarshmallow Official Site
Uploading in this moment. You will see a post on my site!
Installation
Be sure to have my TWRP installed on your device. If you don't have it go to my site and download it (see download section).
Download and copy the ROM and GAPPS in the root of your SD
Boot in TWRP
Wipe your data (wipe data/factory reset in TWRP)
Install the ROM (Install... in TWRP)
Install GAPPS (see more information in the following GAPPS Section)
Reboot
GAPPS
You can download your GAPPS here. Be sure to download the ARM64 version for 5.1. The pico version is the minimal one (save more space).
Bug Channel
Please report any bug and issues here!
http://projectmarshmallow.altervista.org/bug-channel/
Both the ROM and the new RECOVERY will be uploaded on my site. Stay in touch!
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Sony Xperia M4 Aqua
Contributors
tonystark88
Source Code: https://github.com/projectmarshmallow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
Version Information
Status: Alpha
Created 2015-12-12
Last Updated 2016-04-30
Thanks for the rom, but where is the download? All I see is the download page for TWRP
Still uploading. I will advice you when finishs. Anyway its a testing ROM...not for daily use.
Does this has any problem with battery draining more than the stock rom? because this problem existed in my old ? z1 and i can't find anything related to the camera, so am asking if is it working? and any chance of porting z4 camera framework so we can use superior auto in this rom? Thanks in advance
I think is a bit premature make these kind of discussions now. When i'll make this rome stable (now it's a test build, have some reboot problems probaby lrelated to thermanager config) we can face more problems. But don't worry, any problem/idea will be faced at right time.
Awesome! Thank for your work!
Thanks for excellent work! Hope some major bugs could be fixed asap [emoji481]
Sent from my E2312 using Tapatalk
put more SS please...
WiFi not working???About Sound too??
And This is Android M or Android LP???
CyanogenMod 12 is based on android 5.x so that means this rom is lollipop
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Great news. Thanks God for You.Good Luck and we will wait for results
Wysłane z mojego E2303 przy użyciu Tapatalka
tonystark88 said:
I'm waiting for the upload because the rom boot loops for a thermanager problem. Anyway i have fixed also sensors. I'm not able at this moment to offer more infos because rom boot loops. When i fix the thermanager config and rom will be stable i could be more detailed. I'm sure that RIL and 3g connection works. Wifi powers on but not reveal available Wi-Fi but i think is a configuration problem too.
Let me work guys, we are so close
Click to expand...
Click to collapse
If you can force enable adb and upload the rom I'm sure that we can send you logcats to find the problems. Also, could you upload the new TWRP that is mentioned in the OP?
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
boylush said:
@tonystark88
Hi, under GPL v2 license you are required to link a copy of the kernel you used, otherwise, would be in violation of the license. Thank you.
I have taken a look at your source, would it be possible if u rebuild it with Sony's Unified Kernel? Thanks!
Click to expand...
Click to collapse
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
tonystark88 said:
I'm not violating anything, i'm not reselling or forcing someone else. I don't understand all this pressure, you have all the informations you want now, you saw my sources. The kernel is the same published from sonyxperiadev. I have to fork it to my page to be in rule with GPLv2? I don't think, i think is useless.
If you want that i publish my sources (already unstable) on the first page, i don't see the problem, i will do it.
Also, i see this discussion only a waste of time that i subtract to my work.
Click to expand...
Click to collapse
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
It's the temp .config file generated when u build the kernel. I renamed it and used because differently from the asp defconfig is formatted well.
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
I see no problem here especially since Sony hasn't exactly released the kernel code. There is no reason to be so distrustful. Heck he hasn't even released the rom yet so what are you complaining about. Please don't take offense. He is just trying to further this community
boylush said:
It's not out of nothing, cos ur sources must be able to build. You changed one of the defconfigs to cyanogenmod_blablabla so you have to fork and make the changes on ur end as well. Hope u understand
Click to expand...
Click to collapse
Supports developers, do not lock their work
I don't understand this mentality of 'Let the dev work and do his thing' and saying that he should be given space to himself to work and build CM12 for The M4 Aqua. As it stands, you all don't know what Open Source Means. The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua. I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
I don't like these kinds of reasoning about me and about my work only because in two months other people aren't been able to boot nothing, also a recovery. This is the last time i will respond to you because this is a DEV topic, and here will be DEV things.
Furrydaus said:
The M4 Aqua is in a state where much dev work is needed and all you guys do is hamper the speed at which developers can build ROMs for you. Without Kernel Source code and all LOCAL modifications uploaded, other devs can't jump in and help out to build for the M4 Aqua.
Click to expand...
Click to collapse
I repeat this thing again, all my sources are public. Just see the first page of this topic. And also, all sources are open on sonyxperiadev and are a intellectual property of Sony. All the LOCAL modifications are on my github page, in the commit area. Just click and see.
Furrydaus said:
I work mainly in the Xperia SP Forums and when the Xperia SP got released, it barely had any source code given by SONY but now we're at CM13. CM13!!!! From a 2012 device to 2015 we have gotten CM13 while YOUR M4 Aqua is stuck at even building CM12! All the Xperia SP had going for it is the AMAZING DEV support with SO MUCH OPEN SOURCE CODE that we all learnt to share. We keep the credits individual to commits and we all gave credits which were due in every rom we built.
Click to expand...
Click to collapse
And i'm happy for the Sony XPERIA SP, this means people work together. In the case of Sony M4 Aqua i just saw topics that bumps out after i started to develop, also if only the recovery, for this device. No one sent me a message for say, "Tony let's work together".
Furrydaus said:
If I can't build the ROM with what you say uses the original sony kernel source code, then this ROM is violating GPL code. I will be back soon to test the results and see if it does indeed build and churns out the exact bugs reported. If you are unable to handle even a small request that Boylush has said and say that you're already stressed out due to ONE MEASLY request then there seems to be something wrong.
Click to expand...
Click to collapse
I'm not stressed, i feel great thanks And again no one ROM violates the GPL license. Simply because there isn't yet on the site and will not be until will complete boot correctly. And about the request, i responded yet. I have to repeat that i used the same kernel published by sonyxperiadev site WITHOUT MODIFICATIONS ?
Furrydaus said:
Those of you who have absolutely no developer experience I would advise you to refrain from trying to defend your individual parties and let this be easily settled by simple building on my end.
Click to expand...
Click to collapse
Probably in the ROMS world this sentence is true. But i'm a graduated ICT Engeneer and i worked in past in Android. Maybe i know a little bit of devel things, and i say "a little bit" because i know i can do it, and i not let you and others to offend me without know who i am.
CONCLUSION
Without me, the unexperienced, this device today has a working recovery and i hope for ALL THIS COMMUNITY a working CM12.1 . And i repeat again this thing: THE SOURCES ARE PUBLIC ON MY GITHUB AND ON THE SONYXPERIADEV GITHUB. I'm not blocking the work of anyone and i will be happy if someone else will make the rom work better and efficiently than mine. I will learn where i failed from the other devs commits, like i always did.
I hope is more clear my point of view now to avoid future noisy discussions.
Related
NEED HELP
Hello guys, I'm working on a generic tree for our beloved device Honor 7, but not getting enough success, so each and every of you are invited to help me create a new device tree for AOSP 5.1 ROM or CM 12.1, so that we can taste the Stock Android too.
The benefits of these ROMs are that the device will get more fast and stable as there will be minimum apps and bloatwares installed.
So, it is a humble request, that whosoever have any knowledge about creating a tree from scratch please help me.
I have created a skeleton of the tree but it is not a success too as there are many things we still have to consider.
@sminki and @kenshiwara, we will setup an organization on GitHub so everyone can contribute there only.
Hi,
It will be wonderfull to have CM on our honor7.
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
sminki said:
Sorry mate. You haven't seen my troubles over the last few weeks then
After my H7 'died', I got a warranty replacement phone, and unlocking was proving impossible, each day was bringing more frustration and anger so i've sold it!
That's it, i'm out of the "honor" business for good (hence the "unsupported" bit on the recovery and kernel threads), but as a parting "gift", here's a few things that may help "the cause".
Sorry, the length of this post got out of control! :silly:
device tree starting point:
https://github.com/TeamWin/android_device_huawei_p8 - it's similar enough, that with a little editing and boom, we had our recovery*
https://github.com/debbiche/android_device_huawei_p8 - another fuller "tree" (wip), again the p8 is similar enough to use as a base
https://github.com/Gibbon99/android_device_huawei_hwgemini - mediapad x2 - another kirin
if you're insane, you could get the dtb files (iirc - i got these from compiling the source) and decompile, but this contains EVERYTHING, theses files are huge, many hundred kb and would take days to get the info out you need (if there is any!)
cm
have a look at codeworkx H6 git, it's the closest device you'll find that has CM actually running on it, albeit CM11 (and abandoned!)
https://github.com/codeworkx/proprietary_vendor_huawei
https://github.com/codeworkx/android_device_huawei_h60-common
other things:
osm0sis' kitchen out of the many boot image unpack/repack tools, this worked the best with huawei boot/recovery images
* with this in mind, anyone running Linux can pull apart my recovery, fix the issues in default.prop, add extra partitions to fstab and repack it. then post it for everyone else to use.
with the sh!tty way fastboot is on these phones, and the way modem binaries get patched, you're going to have to look for a way to write these in recovery (scripted with dd i imagine) so that everyone can use without having the ballache that is B100,B121,B140 etc etc to get to a version that will work with your ROM. this for me is where it's all going to hurt! (and end with bricks!)
final thing - the kernel source is terrible, it is so far removed from AOSP that simple things that you could normally just drop in, like cpu governors won't work. unless you really know C++ and how to debug it's gonna be near stock (like mine funnily enough!)
Good luck chaps :good: it's gonna be a hell of a ride!
Click to expand...
Click to collapse
Thanks, this will help enough and I was not aware of your troubles
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Is there any whatsapp group of honor 7.I want to join it.
udayraj99 said:
Is there any whatsapp group of honor 7.I want to join it.
Click to expand...
Click to collapse
Stop spamming
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Mee too
omkarpranavxxx said:
Omg I think I will never receive a Custom ROM for PLK-UL00 as they didn't release source code for that and device tree is way far
Click to expand...
Click to collapse
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
asiekierka said:
I got a device tree working with CM12.1 and USB debugging, but Mali was a showstopper. Now I'm fighting with CM13 instead... Generally, the B313 ROM is far less hacky, but we lose the open source kernel for a while until they release one.
I will set up a GitHub tree with what I have when I get CM13 compiling again, however keep in mind that you need to patch the boot.img manually to use the closed-source B313 kernel until Huawei releases the source for that, which probably won't happen at the very least until it's fully in OTA. I'd love some help from someone who is more experienced, especially with the Mali drivers which are the worst of pains.
EDIT: I got CM13 compiling again. Let's hope for the best.
EDIT2: Mali works! Sadly, that currently depends on Huawei's libgui.so which brings in a huge chunk of Huawei's patched libraries - otherwise, it segfaults in strange places. Any ideas?
Click to expand...
Click to collapse
Hello, did any of the CM compiled fully to be a flashable zip? if yes, then have you flashed it and took logcat?
Nishadan said:
As an indian user evwn i feel i made wrong choice....should have gone for one plus x
Click to expand...
Click to collapse
Yup lesson learnt snapdragon or nothing frm now on
maybe you know
I post link - http://download-c.huawei.com/downlo...oadId=62086&version=204465&siteCode=worldwide
Honor 7 Open Source（PLK-L01_Android5_0_2_EMUI3_1_kernel_EN)
Any progress?
I hope I can do something,it is nice to see cm for honor 7.
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
cycovision said:
Since it has been a while that any Info came out of this thread I have to ask.. Is anyone still working the tree?
I normaly do not ask for etas but in this case it would be useful if the thread is abandoned that we could know the reasons and Problems so maybe someone else could join in with a different approach
Click to expand...
Click to collapse
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
DigiGoon said:
I'm a bit busy to continue my work on the tree, but after my exams I will continue to work on tree with Android 6.0 source. Hope it goes well.
Click to expand...
Click to collapse
good luck with your exams
Until then you can use this
New ROM for Honor 7 PLK-L01.
DigiGoon said:
Until then you can use this
New ROM for Honor 7 PLK-L01.
Click to expand...
Click to collapse
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
muhammad Shohayeb said:
Can we get a kitkat rom if your work with the device tree is done ? I really do miss kitkat[emoji20]
Sent from my PLK-TL01H using XDA-Developers mobile app
Click to expand...
Click to collapse
I will be developing AOSP 6.0, if others can give it a try then maybe we can get it.
Announcing Sailfish for the Sony Xperia Z3 Compact!
This is not Android!
This should be thought of as a development experiment. It may be useful if you are a developer and want to write/port apps the the Sailfish operating system. It is not an end-user product, however, if you wish to experiment and try something different then feel free!
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone.
Special thanks to:
rss351 and locusf for the collaborative effort in porting SailfishOS to the Z3 compact
Everyone from the SailfishOS team/community, sledges and mal- in particular.
All Cyanogenmod devs, since SailfishOS uses drivers from Cyanogenmod to talk with the phone's hardware
Known issues:
Bluetooth isn't turned on, cause i've put no effort in for that so far
Camera doesn't work, cause it's not hooked up to interface.
No recovery inside hybris bootimage (you need to flash manually to return to cm/use recovery)
Sensors dont work (auto-adjust brightness, etcetera)
The Jolla account/store functionality is not enabled. This is being worked on by Jolla. In the meantime: use openrepo's warehouse (see bottom of this post)
What works:
Booting, basic usage of the OS itself (browsing, etc)
Texting, calling, data over mobile network (2g and 3g tested, 4g should work but is untested)
Wifi (both 2,4 and 5 GHz)
Power management seems to work fine (not tested much though)
Looking around and getting a feel for SailfishOS
Using your phone to develop and debug SailfishOS apps.
Installation guide/checklist:
Insert default warranty void message here. Your warranty is now void
Make a backup (just to be sure)
Depending on what you need from your phone, this may not be a rom suitable for daily driving with. But installation is non-destructive to your existing rom, so if you're curious, give SailfishOS a try
I have not tested this on locked bootloaders, but since I needed to modify the kernel, I guess that you need an unlocked bootloader.
Note this is not an official Sailfish OS build, and the Xperia Z3c is not a Jolla phone, so please don't report bugs to Jolla. If you want to report a bug, this thread is perfectly fine for that.
BEWARE: this image is NOT optimized for security. The phone boots in development mode by default. There is a root shell on telnet port 2323. This is not secure and will give anyone who wants it remote access to your phone. When the port matures this will be fixed.
The Sailfish OS image does not provide recovery, and since the Xperia Z3c does not have a recovery partition, you need a bootimage with recovery on it to flash cm/stock/sailfishos upgrade. I highly recommend using Nut's Xperia files for this. Use the boot.img from your Cyanogenmod installation.
The Sailfish OS image is based on a recent version of Cyanogenmod 12.1, so update your Cyanogenmod installation while you are at it. Use cm-12.1-20160523-NIGHTLY-z3c.zip if you encounter issues with other versions. Using another rom is not guaranteed to work, even if this rom is based on Cyanogenmod.
You can find the required zip in this Mega folder: https://mega.nz/#F!ucoRnDjD!WAHNWgxLQX5SK1Vdu8MRWw
Use your favorite recovery (but not CM's recovery since that checks for signatures, which this image does not have) to flash the zip.
If you want to return to Cyanogenmod, extract boot.img from your cm-12 zip and flash that with fastboot. Alternatively you can restore a previous backup. There is no need to re-flash Cyanogenmod because it was not removed by installing SailfishOS. You can remove the /data/.stowaways/sailfishos/ folder afterwards to reclaim disk space.
FAQ
You can find a FAQ which mentions most common user questions for SailfishOS here: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 . It's mainly aimed to the Nexus 4 and 5, but it's fairly applicable for all other ports as well.
Contributing
If you think this is awesome, and want to help fix the issues currently open: come by in #sailfishos-porters on irc.freenode.net!
Sources
You can find all used source code (may not be up-to-date to the latest image, but all key components are there) here: https://github.com/xperiasailors/
Installing OpenRepos warehouse
OpenRepos warehouse is like what F-Droid is versus Google's Play store. An unofficial, community-driven repository of open source apps.
Go to settings->developer options and set a password. Then open a terminal or connect over ssh to your phone (ssh [email protected]_of_phone).
Download the latest version of the warehouse app from here: https://openrepos.net/content/basil/warehouse-sailfishos
When you are asked to terminate packagekit anywhere in the steps below, answer yes.
Code:
$ devel-su
# zypper rr adaptation0
# zypper in <location_of_rpm_you_downloaded>
After this Warehouse app will be in your app launcher.
Impressive work! :good:
Sent from my Sony Xperia Z3 Compact using XDA Labs
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
mrrflagg said:
Just having a go now.
Edit: just stayed on sony screen. Would it be because I came from SLiMM 1.8 ROM and not from a CM based ROM?
Click to expand...
Click to collapse
Probably, yes.
SailfishOS uses libhybris for hardware communication, which in turn uses the existing Cyanogenmod installation for drivers and proprietary blobs. But hybris is compiled against a certain Cyanogenmod version, so using other roms as a base might fail.
I've updated the TS and put the exact CM version I used in there, that should work fine.
There are any news? The project is in development?
Alexander3273 said:
There are any news? The project is in development?
Click to expand...
Click to collapse
No news, I don't spend much time on this port, every now and then I fiddle around with it an evening.
I'm currently trying to get AOSP based Sailfish port because Cyanogenmod for Z3c seems unmaintained, but progress is very slow.
Thank you for the info. Do you know when a version (sailfish port) comes out?
Hello! Thanks for your work. May i know the progress ?
it would be great to see a real "european" OS coming out of the dust...
i hate the thought that any company from the other side of the atlantic are wheels in the monster of patriot act...
@maikoool Any news about new build or something?
Yes, look here:
https://nokius.net/SFOS/scorpion/PreAlpha/
But still no Cam, no BT, No Sensors and No video playback
AFAIK is the 'scorpion' the Z3 Tablet compact, so not the Z3 compact. The base images will probably be the same.
I've recently rolled a build using AOSP 5.1 from the Sony Xperia developer pages, but my Z3c has developed an issue where the top and bottom of the screen don't function, so I cannot test properly.
Aries is device name, right? What's scorpion ?
kskarthik said:
Aries is device name, right? What's scorpion ?
Click to expand...
Click to collapse
Aries = Z3 compact, Scorpion = Z3 Tablet compact
I'm waiting eagerly to see SFOS on aries Do you know anything about our device support on jolla's list ?
CyanogenMod 13 for the Sony Xperia XA Dual Sim
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the F3112 and the F3116
Code:
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
@Deepflex for his P9000 github repository used as base for sources.
@zacharias.maladroit for his CM13 guide for Z5 and who have heavily inspired me for this guide
-The Sonyxperiadev team for releasing their kernel sources to the public.
-The entire CyanogenMod team.
-All Xda contributors for their guides and HowTo.
-The Google searchbar
Known Issues
-Camera not working
-Video not working
-No Sim
-Screen not wake up after screen off.
-No sound
-"Security" settings not working
-"More... " settings not working
-NFC not working
-GPS (not tested)
-Full brightness
-And probably more...
Guides/Instructions
For now I will not explain how to flash because my Rom is in very beta stage and I need help for debugging,
it mean it's not user friendly and only skilled users will know how to flash it,
As soon as the rom will be stable I will update this part of the guide.
I will just say it's like any other CM Rom flashing.
Downloads
CyanogenMod Recovery https://mega.nz/#!EoJXyK6R!ORe1tBtn2LhkFsOIs0grhOo_jFDsYKT1wJKGGBJhBsA
ROM
Initial release: https://mega.nz/#!gx50yZZL!i1qL_Ab9_LubJCmuYefnazW4ddn_r5Z-a-8FXmKTsDg
Questions and bug reporting
The following questions will be ignored
- Inappropriate questions
- Requests for other devices
-Forced orders, EX. : "PLS FIX!!!!!!"
-ETA's
-Often repeated questions or requests usually by the same user
-Requests that are out of CM
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
Source Code can be obtained from:
https://github.com/CyanogenMod
https://github.com/rrvuhpg
Kernel Source code can be obtained from: http://developer.sonymobile.com/downloads/xperia-open-source-archives/
I gladly accept any developers that are willing to contribute to this project! Please PM @rrvuhpg if you are interested in joining this project!
You can join my XA/Ultra channel on Telegram for dev questions: telegram.me/rrvuhpg_XA
ROM OS Version: 6.0.1 Marshmallow
ROM Firmware Required: 33.2.B.3.81 Recommended
Based On: CyanogenMod
Version Information
Status: Initial release
cool !! nice work.. if u can do the same on F3111 please !
first time i get sony and i use stock firmware ..with other brands i use custom rom
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
ObtuseFox said:
Nice! I've been waiting for this!
I'm learning C and JAVA myself, but guess it would take a long time before I can actually develop something!
Until then, I count on you! Thanks!
Click to expand...
Click to collapse
You know porting roms have nothing to make with pure developpment. More with analyse of codes and importations of libraries, etc... You won't really code a whole page
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Stersound said:
I am so happy to see this here
My old LG D295 just died and i pull the trigger for XA F3111 and i hope everything is going well with the port
Click to expand...
Click to collapse
It's on the good way, I'm waiting for my new computer to continue, my actual take 11 hours to build :silly: As soon as the "ril" (telephony features) will work I will release an update, for now I can enter pin code but sim stay locked
All other features are working or unstable, only NFC is not working. For XA single sim you will have to wait a little more.
Cyanogen means losing Bluetooth aptX.
saintsimon said:
Cyanogen means losing Bluetooth aptX.
Click to expand...
Click to collapse
Sir i believe this is not correct
Stersound said:
Sir i believe this is not correct
Click to expand...
Click to collapse
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Can we expect CM 14 ? instead?
are you going to build a rom like cm or aosp for the xa ultra?
sexxualization said:
are you going to build a rom like cm or aosp for the xa ultra?
Click to expand...
Click to collapse
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
rrvuhpg said:
Probably no, I don't have an unlocked Ultra to work on it. As long as we don't know why Ultra devices can brick when flashing with Flashtool it will stay with locked bootloader.
Click to expand...
Click to collapse
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
sexxualization said:
well i own an unlocked xa ultra with twrp recovery to help you try the rom out
Click to expand...
Click to collapse
Thank you for your help but I need the device in my hands for many reasons (dump, debugging, reverse engineering, ...).
As you know XA and Ultra are not intended to have custom roms and I have to make my own sources, it mean a lot of work. Ultra is not a simple copy/paste of the XA system
saintsimon said:
Well: aptX means licence fees. Does Cyanogen pay them?
I need facts, no beliefs. Cyanogen is not known for aptX support.
Or is there a file like "libbt-aptX-ARM-x.x.x.so" in the /system/lib/ folder? If not, your belief is unsubstantiated.
Click to expand...
Click to collapse
Apt-x is a feature supported in vanilla android already.
Then it's true you should have the loading library (which isn't all that secret btw) but for some reason, it's reported to work nevertheless on Xperia S.
Regardless, I don't see why you couldn't just include stock libbt-aptX-ARM-4.2.2.so in android_vendor/proprietary (or android_device/prebuilt, Idk)
EDIT: https://review.lineageos.org/#/c/158337
Is there any chance this ROM will work on the f3111?
jolpool said:
Is there any chance this ROM will work on the f3111?
Click to expand...
Click to collapse
I think this project is kind of dead already since were no activities happening.
Jhayzt said:
I think this project is kind of dead already since were no activities happening.
Click to expand...
Click to collapse
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
rrvuhpg said:
As you know CM is dead and Lineage OS just launched. Other thing, Nougat for XA and Ultra will come soon and I know that users will ask for Rom based on it. We can say CM13 project is dead but new Lineage OS project will come for XA
Click to expand...
Click to collapse
Really looking forward for lineage OS for XA.
Please update this rom asap. Really need your help, i hate this stock version. The touch screen is very annoying. I can't touch the edge of the screen. Please help us
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
The main purpose of this thread is to unify all the useful web links, mainly other XDA threads, that contribute to improve and expand the development, guides, discussions and all other useful sources of data related to our device.
"HOW DO I KNOW IF THIS IS MY DEVICE?"
The device we are talking about here is a Huawei Mediapad T1 10, which consists in at least 3 different variants:
- LTE variant (T1-A21L)
-WiFi variant (T1-A21W)
-LTE chinese variant (T1-A23L)
They are exactly the same device in terms of hardware and software (this one vary a little), the only difference is that one has SIM slot (T1-A21L) and the other one no (T1-A21W).
An important point to keep in mind is the codename of our device, which is a technical name all Android device have and which identify exclusively to the device. This is very usual in development threads such as ROMs and Recovery threads, so you might see it in the thread title.
The codename of our device is hwt1a21l
-Technical information of our device. Specs are from the LTE variant but it applies for the WiFi variant expect for the SIM slot: [url]http://m.huawei.com/ukmobile/consumer/tablets/detail/mediapad-t1-10-uk.htm[/URL]
If you still have doubts about this topic i suggest you to ask you doubts or check other people's doubts.
RULES:
1- Please only discussions related to our device (Huawei Mediapad T1 10 T1-A21L/T1-A21W). See previous paragraph to know if you own this device.
2- If you want to report an issue or any other subject related to an existing rom, recovery or other subjects try to keep the conversations in the respective thread of what you want to talk. It's not mandatory but it's a good way to keep conversations in the proper thread so other people can check it.
3- Try to keep clean and proper conversations when posting in this thread.
ROMS:
- EMUI 3.0 Light: [url]https://forum.xda-developers.com/huawei-mediapad/development/rom-emui-3-0-light-mediapad-t1-10-t3609602[/URL]
- CarbonROM KK (Unofficial): [url]https://forum.xda-developers.com/huawei-mediapad/development/rom-carbonrom-mediapad-t1-10-t3662497[/URL]
RECOVERIES:
- Philz Touch 6.59.0: link
- TWRP: link
ROOT:
- SuperSU for EMUI 3.0 (may be valid for other ROMs): link. Credits to @mann1
MODS/OTHER DEVELOPMENT RELATED TOPICS:
WIP.
STOCK FIRMWARE:
-EMUI 3.0 Stock ROM (V100R001C232B009CUSTC100D001 for T1-A21w & V100R001C100B013CUSTC100D001 for T1-A21L) : link
HOW TO UNLOCK THE BOOTLOADER:
WIP.
UNBRICK THE DEVICE:
WIP.
Created 18/05/2017
Last update 23/02/2018
reserved
Updated post with a new ROM (EMUI 3.0 Light).
For those who pricked their devices and and have stuck in boot loop after rooting or trying new custom recovery, they need the stock BOOT or RECOVERY images from here.
Thanks, I love this.
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
MIRACAST
Hola podría alguien decirme como puedo activar el miracast en mi tablet huawei t1-a21l .
mustang_ssc said:
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
Click to expand...
Click to collapse
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
emmanuelix said:
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
Click to expand...
Click to collapse
@mustang_scc
+1 to that. I have the stock rom with root access.
The tablet mainly sits and collects dust right now so I wouldnt mind using it for testing.
Let me know if I can help.
emmanuelix said:
Dear mustang_ssc, I don't know if you are still wondering about usefulness of uploading CarbonROM KitKat for th t1 10 ? There is an important interest from my side for more than 1 device.
If I can be of any help to avoid important workload to you, I ll be pleased to contribute.
Click to expand...
Click to collapse
Apexaddicted said:
@mustang_scc
+1 to that. I have the stock rom with root access.
The tablet mainly sits and collects dust right now so I wouldnt mind using it for testing.
Let me know if I can help.
Click to expand...
Click to collapse
Though the bug are not solved yet, I will probably open a thread for the rom this weekend so people interested like you can install it, test it or keep it on his tablet without mind the current bugs.
I will keep you informed
The CarbonROM KK is ready for testing purpouses, i need testers. @emmanuelix , @Apexaddicted , @PinkOstrich or anyone who owns the LTE variant who would like to test it, please send me a PM.
PD: sorry for the delay about this, i was quite short of time and also had to port it again because i realized i lost all the ROMs when i formated my hard drive disk.
Deleted:
Duplicated post.
Sorry but I only own the WiFi version.
Apexaddicted said:
Sorry but I only own the WiFi version.
Click to expand...
Click to collapse
Don't worry, i will open the thread and people with the WiFi variant will be able to download it. I want people with the LTE one to test it because i own the WiFi Varian as well.
Also a reminder for everyone:
Keep in mind that the rom still has some few critical bugs which you may not be happy to flash the rom. The main bugs are:
-Camera not working
-Notification led not working
-Weird bug with the Play Store which does not allow to use it unless, on my experience, you wait for about 1 day to be able to use it.
mustang_ssc said:
Don't worry, i will open the thread and people with the WiFi variant will be able to download it. I want people with the LTE one to test it because i own the WiFi Varian as well.
Also a reminder for everyone:
Keep in mind that the rom still has some few critical bugs which you may not be happy to flash the rom. The main bugs are:
-Camera not working
-Notification led not working
-Weird bug with the Play Store which does not allow to use it unless, on my experience, you wait for about 1 day to be able to use it.
Click to expand...
Click to collapse
Thank you @mustang_ssc. I only own the Wi-Fi version also, sorry !
I have finally posted the ROM (CarbonROM). As mentioned it has not been tested on the LTE variant, but it should work properly as the Wi-Fi one.
Link: https://forum.xda-developers.com/huawei-mediapad/development/rom-carbonrom-mediapad-t1-10-t3662497
mustang_ssc said:
I had my pc broken quite amount of time and i could not work on some roms that i was testing. I was planning to upload CarbonROM Kit Kat for our device, but unfortunately i see a lack of users activity for this device which makes me think that maybe it is not very relevant to create and upload the builds (which takes much more time than what it seems, and my time for this activities is quite limited).
If i see more interest for this then i could upload the rom, and maybe future ones.
Click to expand...
Click to collapse
I would definitely appreciate it!
hooligan333 said:
I would definitely appreciate it!
Click to expand...
Click to collapse
You have the link for the rom on the previous post.
Alright, have good and bad news, let's start with the good one:
I have a completely working 5.1.1 Android ROM (EMUI 3.1) from the T1-A23L which works on the LTE and Wi-Fi variants (T1-A21L & T1_A21W), big thanks to @tenderVeteran who sent me this ROM and informed me about it. This means we finally have Lollipop for our device and we have the possibility to port another Lollipop ones.
The bad new is that i need to make it flashable but for some reason it does not boot. I need some more time to figure out about a solution on this topic and i will publish it as soon as i get it booting.
Glad to hear about the progress! Cant wait to try it out. Please let us know if there is anything we can do to help.
Additionally...Ive been looking for ways to compile a custom kernel for the mediapad. Have you tried this yet?
Rob
Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5
These release notes cover Sailfish OS 4.4.0.72 for the following devices:
Sony Xperia 1 (J8110, J9110)
Sony Xperia 5 (J8210, J9210)
Intro
This port has been updated last to the latest release of Sailfish OS 4.4.0.72 in addition to that several adaptation bugs discovered in the testing of the first release have been fixed.
Also several documentation updates or buildinfrastructure changes have been made.
Updates to these project components are now tracking in the main bug tracking repository SailfishOS-SonyXperia/bugs/releases.
The highlights in this release are:
[prjconf] Fix pattern dependencies. Fixes SailfishOS-SonyXperia/bugs#55, fixes SailfishOS-SonyXperia/bugs#59
[patterns] Require ngfd >= 1.4 instead of ngfd-plugin-native-vibrator. Fixes SailfishOS-SonyXperia/bugs#69
[configs] Keep dual sim configs on J9210/Xperia 5, remove on J8110. Fixes SailfishOS-SonyXperia/bugs#51
[kickstart] Fix @DEVICES@ name for Xperia 5/J9210 in flash-on-windows. Resolves SailfishOS-SonyXperia/bugs#50
Thanks to all who have provided testing, reported bugs or have contributed otherwise.
FunctionalityThe devices have the same functionality level as the Xperia 10 II port made by Jolla,
except in areas such as VoLTE where public packages are missing or in relation to Sailfish X features which are (currently) unavailable.
Known issues
SailfishOS-SonyXperia/bugs#33
Because of a missing package inside the adaptation-common repository Windows binaries for flashing are missing inside the zip archive. To workaround that issue have added another zip file that includes these files as "droid-flashingtools.zip" to this release.
SailfishOS-SonyXperia/bugs#37
The launcher icons on the Xperia 1 are to small because there's no bigger graphics-theme size than 2.0.
ProjectThe Github project that contains this port and all other ports from this project can be found here:
Sailfish OS Community ports for Sony Xperia devices
Sailfish OS comunity ports for Sony Xperia devices - Sailfish OS Community ports for Sony Xperia devices
github.com
Project UpdatesAs explained above there’s now a separate changelog for project wide updates which can be found down below:
Release Project Update 02-12-2022 · SailfishOS-SonyXperia/bugs
Intro The changelog describes all the project wide changes, such as for example documentation updates or build infrastructure changes. In case an adaptation issue arose from wrong build configurati...
github.com
The changelog file about the project updates can be found down below:
project_changelog.md
About
The goal of this project is to port additional Sony devices on top of Jolla's existing adaptations while staying as close as possible to the existing ports and contributing back to the upstream where possible.
Most of the changes from Jolla ports are adopted in both directions since the issues that one port has usually apply to the sister device of the same generation (e.g. Xperia 10 II -> Xperia 1/5).
This is the reason why changes from Jolla’s port end up in the changelog for these port,
in many cases because they also affect the specific port but not always.
Where possible changes that were done for this port go back to the _Mer-Hybris_ repositories such as the kernel or droid repositories.
The project is open for anyone that wishes to port additional Sony devices to Sailfish OS. Feel free to suggest new features, provide bug reports or to contribute.
SourcesAny sources specific to this port can be found inside the project linked above. The device repositories are named after the devices board name for example in this case kumano.
All our sources are included inside the project linked above.
All other sources are taken unpatched from upstream which is either Sony-AOSP or SailfishOS/mer-hybris.
If changes are needed inside upstream repositories these are submitted to the upstream repositories.
This GPL includes components such as the kernel or libhybris.
On pressure of XDA I add the direct link to the kernel repository, however the exact ref used during build
can be found inside the droid-hal repository, which in the case of the Xperia 1 for example, droid-hal-kumano.
Sources for this board
https://github.com/mer-hybris/android_kernel_sony_msm/tree/hybris-sony-aosp/LA.UM.7.1.r1
https://github.com/SailfishOS-SonyXperia/droid-hal-sony-kumano
Report bugs
Bugs can be opened in the bug repository linked below:
GitHub - SailfishOS-SonyXperia/bugs: Empty repository that is used as a bugtracker
Empty repository that is used as a bugtracker. Contribute to SailfishOS-SonyXperia/bugs development by creating an account on GitHub.
github.com
Download
Release 4.4.0.72+git1 · SailfishOS-SonyXperia/droid-hal-version-sony-kumano
Sailfish OS 4.4.0.72 for Sony Xperia 1 and 5 These release notes cover Sailfish OS 4.4.0.72 for the following devices: Sony Xperia 1 (J8110, J9110) Sony Xperia 5 (J8210, J9210) Intro This port ha...
github.com
Flashing
To install Sailfish OS on your device please follow the install instructs in the flashing-readme.txt file included in the archive or read the offical flashing instructions for either the Xperia 10 II or Xperia 10 III:
Sailfish X Installation Instructions - Jolla
jolla.com
Just make sure to download the software binaries for your device instead of the ones mentioned in the instructions:
Software binaries for AOSP Android 10.0 – Kernel 4.14 – Kumano (latest) - Sony Developer World
developer.sony.com
Changeloghttps://github.com/SailfishOS-SonyX.../releases/download/4.4.0.72+git1/Changelog.md
Great job, thanks for making the port! Does it have Android app support? If it does I'll definitely give it a try, I saw on the SailfishOS official website that only the paid version can run Android apps...
Edit: I see why now, because of the very very long term support that you get, it's like 7 years of updates for a bit of money, that's pretty good.
just try to use on my device.
its first time for me using Sailfish OS.
but.
when i turn off the phone, and try to turn it on, it asks for the security code, after i enter the security code, it just loading in quite a long time,
then, simcard and wifi didnt works.
I can confirm, that neither data connection nor WiFi works.
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs:
https://jolla.zendesk.com/hc/en-us/articles/360013910599-Collecting-basic-logs-from-a-Sailfish-device
You can also try to flash the new images, I will add tomorrow.
I updated the release archives today:
Package ngfd as `CUSTOM_’ FFMemless vibration effects require newer version than packaged in SailfishOS 4.4.0.
Fix issue in ssu-vendor-data package that made the address of the adaptation repository invalid. [BUG] address of adaptation repo is invalid #49
I've installed Sailfish and its working fine. But i dont find access to install android apps. Is there a way to install APKs?
Thaodan said:
Without any data such as logs I can't help you. Please create a bug in the bugtracker.
Please also make sure that you flash the version that matches your device.
Please follow this article to fetch logs.
You can also try to flash the new images, I will add tomorrow.
Click to expand...
Click to collapse
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
P.S.: Yes, I've tried it 4 times (went back to the latest Sony fw), and the last time I've flashed the latest Sony fw even on slot a and b before flashing Sailfish OS again (the latest [1.06] for the Xperia 5 Dual Sim variant), but unfortunately every time with the aforementioned result...
Klaus N. said:
First of all, many thanks for your reply - very appreciated!
Yes, I've downloaded and flashed the appropriate version (J9210, Xperia 5, DualSim). As I've bought this device as a new one about 2 years ago, I've used it that time, and it worked. The bootloader was already opened; it was rooted, because of some rooting apps.
Click to expand...
Click to collapse
Did you download the version for the J9210? Please check the file name of the archive.
Klaus N. said:
Therefore, it was not necessary to check, if data connection, wifi, gps, camera and so on works, because it worked.
I flashed sailfish os (with the latest software binaries, Android 10, Kernel 4.14 - as in the op described [the extracted .img I've placed in the same folder as your firmware, of course]) via Linux Mint.
Click to expand...
Click to collapse
Extracted the .img? You should extract the .zip archive, then run ./flash.sh to flash Sailfish OS to the device.
Klaus N. said:
The device boots up flawlessly, the screen is responding without any problem, and also the intro worked.
But I can't activate wifi. I can push the button, and it responses, but it don't activates wifi. Also, my sim card won't be recognized, therefore there's no chance to enter the sim pin.
So there's a few questions:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
Sorry I forgot to post the link, please look again.
Klaus N. said:
Or is it necessary to buy a Yolla licence? No problem, I would pay for it, but the Xperia 5 isn't listed yet on your homepage...
Thanks in advance for your kind reply!
Click to expand...
Click to collapse
Not you don't need to buy a license, the device isn't support by Sailfish X (it is not available so far for community ports).
Klaus N. said:
You write "please follow this article to fetch logs", but without a link... I guess, it's not like fetching logs in android? So would you please tell me, how I can do that, to provide you the log?
Click to expand...
Click to collapse
@Thaodan
Thanks for providing the link!
Here's the basic-logs-2022-09-24-1031.tar from my device.
Thank's in advance!
In addition, the answers (sorry, almost forgot) to your questions:
Yes, I've downloaded the Sailfish_OS-Sailfish-SonyXperia-4.4.0.68-j9210-1.0.0.6.zip and the software binaries provided in your op.
I've only extracted the zip, but not the .img, ofc. Then I put the Software Binaries.img into the same folder as the firmware and run ./flash.sh
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Klaus N. said:
@Thaodan
As there's one month left in the meanwhile, I only wanted to ask, if there's some progress regarding the J9210!? Is this the wanted logs, do you need some other, or has this project stopped?
Click to expand...
Click to collapse
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Thaodan said:
I checked and didn't found anything obvious in your logs. I didn't had time to check your device further before my vacation.
I didn't mention it here but please open a bug report, a forum or specificly this forum thread isn't the best place to talk about issues.
My J9210 runs fine.
Click to expand...
Click to collapse
First of all, thank you very much for your reply!
Ok, so I'll give it one more try: I will set it up with the latest Sony stock fw, put my sim-card into it and test/use everything - as described...
I'll report back!
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Thaodan said:
I just checked my test phone everything works so far.
Please check if it doesn't work that you flash the latest stock version that is close to this one: 55.0.A.11.25.
Click to expand...
Click to collapse
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
@Thaodan
One further question: Have you installed Sailfish OS via Windows or Linux? I did it with Linux Mint...
Klaus N. said:
The Xperia 5 firmware I've flashed is the J9210_Customized EU_55.2.A.4.332-R13C one. I'll flash it again and give SF OS another try. Perhaps it failed because my Xperia 5 was rooted and debloated; I also had AFWall+, the Xposed framework and XPrivacyLUA installed. I don't know...
Right after flashing the aforementioned fw I will test GPS, mobile data, wifi and so on, and will keep everything turned on before flashing SF OS - maybe it will work?
Click to expand...
Click to collapse
have you tried?
I want to try it again, but it's a shame if it's without a simcard or wifi.
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Klaus N. said:
Well, now I've flashed the J9210_Customized EU_55.2.A.4.332-R13C fw, played around with data connection, wifi, bluetooth, camera, and everything worked.
Then I tried to install SF OS via Windows 10 64 bit, but there must be a mistake inside the script. I definitely own a Xperia 5 dual-sim (J9210)!!!!!!! But: Please have a look into the attached pic...
Then I tried to flash SF OS running Linux Mint (latest stable release); the flash ran through without any error, but again: No WiFi, no data connection.
I'm about to give up!!!
One note:
I've flashed so many devices, mostly LineageOS, but also Ubuntu Touch, and never had any problem like that - unfortunately, it's annoying...
Click to expand...
Click to collapse
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Thaodan said:
Isually use Linux to flash but also should have checked the Windows flash script.
Please edit the batch script you called and replace j9210 with J9210.
I just fixed the issue but for now just change the flash script for Windows:
[BUG] Device is invalid in windows flashing script for Xperia 5/j9210 · Issue #50 · SailfishOS-SonyXperia/bugs
The @[email protected] in the kickstart script is written as j9210 but it should be J9210.
github.com
Click to expand...
Click to collapse
Thank you very much for the response - and your efforts, ofc!
Finally: It works
I had not to flash the latest firmware (doesn't work), but a rollback to the J9210_Customized EU_1320-0801_55.1.A.9.52_R10B fw before flashing Sailfish OS did the trick!