Related
Hi have been trying to get a TP-WN722N to run on my i9505 rooted and cwm recovery
TP-WN722N chipset = atheros ar9271
needs ath9k_htc driver
and htc_9271.fw
has anyone got a module i can insmod?
Am new to android as of 2 days ago so am still learning how to do everything. Bricked about 3 times.
Am trying to connect this usb wifi adapter to get monitor mode and injection. for aircrack/reaver
(maxters - aircrack-suite-for-galaxy-note-2)
or a link to a newbie tutorial to build kernel source supporting ath9k drivers?
Anyway will donate $15 to anyone that can get me running (is this allowed?)
cheers
Will still donate if somebody can help
compile kernel
Am about to compile kernel from source and build modules.
Will post after if it is successful and anyone is interested?
Will try do ath9k and rtl8187 drivers.
success
Success. Had problems with compiling on ubuntu 13.04. Then couldn't insmod the compiled modules due to dependencies for the mac80211 module so I ended up just compiling wanams adam kernel with the required modules built in and bang no more problems. Copied firmware to folder.
Tp link tl-wn722n wifi adapter running in monitor mode. Aircrack and reaver working with no problems. No -1 channel issue. hasn't cause any other problems with the phones built in wifi or anythng else.
Hope someone may find this useful. Will upload when i can post links if anyone wants it. But would be better to compile yourself
P.s. i am using this for easy pentesting on networks which i have permission. Not intended for illegal purposes.
This is awesome! Great work, i would love you to update the files as i am pretty new to linux...
DipSprayArc said:
Success. Had problems with compiling on ubuntu 13.04. Then couldn't insmod the compiled modules due to dependencies for the mac80211 module so I ended up just compiling wanams adam kernel with the required modules built in and bang no more problems. Copied firmware to folder.
Tp link tl-wn722n wifi adapter running in monitor mode. Aircrack and reaver working with no problems. No -1 channel issue. hasn't cause any other problems with the phones built in wifi or anythng else.
Hope someone may find this useful. Will upload when i can post links if anyone wants it. But would be better to compile yourself
P.s. i am using this for easy pentesting on networks which i have permission. Not intended for illegal purposes.
Click to expand...
Click to collapse
So you placed all of the modules and everything into a kernel and flashed it? May you please post a link in a drop box or something, to the working kernel with the modules in it?
Sorry for the huge bump
DipSprayArc said:
Success. Had problems with compiling on ubuntu 13.04. Then couldn't insmod the compiled modules due to dependencies for the mac80211 module so I ended up just compiling wanams adam kernel with the required modules built in and bang no more problems. Copied firmware to folder.
Tp link tl-wn722n wifi adapter running in monitor mode. Aircrack and reaver working with no problems. No -1 channel issue. hasn't cause any other problems with the phones built in wifi or anythng else.
Hope someone may find this useful. Will upload when i can post links if anyone wants it. But would be better to compile yourself
P.s. i am using this for easy pentesting on networks which i have permission. Not intended for illegal purposes.
Click to expand...
Click to collapse
Hi there. Decided to stop lurking and finally made an account. Also, I realize this is an incredible bump, but it's the only thread I could find on the subject.
I managed to compile the latest release of the CM11 kernel (same as my S4 is running) with ath9k and mac80211 support baked in (not modular), but my AR9271 is still b0rked. It shows up in lsusb, so it's working, but not functioning. I've tried like, everything....... except giving it extra power. Did you need to do that? AFAIK it only draws about 200-300 mA at most, and the S4 is more than capable of that ._.
Does anyone know if there's something special needed to get the adapter working apart from plugging it in? I'm losing sleep D:
help
ThePromisedLAN said:
Hi there. Decided to stop lurking and finally made an account. Also, I realize this is an incredible bump, but it's the only thread I could find on the subject.
I managed to compile the latest release of the CM11 kernel (same as my S4 is running) with ath9k and mac80211 support baked in (not modular), but my AR9271 is still b0rked. It shows up in lsusb, so it's working, but not functioning. I've tried like, everything....... except giving it extra power. Did you need to do that? AFAIK it only draws about 200-300 mA at most, and the S4 is more than capable of that ._.
Does anyone know if there's something special needed to get the adapter working apart from plugging it in? I'm losing sleep D:
Click to expand...
Click to collapse
Hey i can help you and you can help me..
i try to compiling those drivers too but i have some problem.. btw if you send me your kernel boot.img i can flash and tell u if you need extra power cause i have a cable that give extra power.. please contact me
would like this driver in the cm11 kernel would be fantastic so i can go downstairs outside and still hit my ap with my phone since i dont use data.
Hi sailors out there
When I'm going to read through the available sailfish threads the question about how to set up multirom & sailfish have been asked many times. So I thought I'm writing this little guide. I describe the procedure along the nexus 4 mako. But it have to be very similar on other devices like nexus 5 for example. The important parts that differs from mako are the kernel and modem image you've to use. I will describe the easiest way in my opinion. Experienced users have more capabilities to reach the goal. I will not describe how to install twrp recovery and unlock bootloader. Both are prequesites. Please use xda search or google to get this. But this little guide want's to be simple as possible. So let's begin .
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Beginning:
First we have to detect you're actual setup and where you want to go. Because nexus 4 is up to date I think the most common goal is to run android 4.4 as primary and sailfish os as secondary. Atm I have only paranoidandroid 4.4 on my device and will show you how to get everything working.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Requirements / Download following parts:
kernel aosp: http://d-h.st/A99
kernel cm: http://d-h.st/CCn
aosp = android open source rom. Ask in you're rom thread what version you're on with the rom
cm = cyanogen mod rom. Ask in you're rom thread what version you're on with the rom
Modem for nexus4 in version 0.84: http://d-h.st/cIJ
or
through an app in play store: https://play.google.com/store/apps/details?id=com.bpear.makomodem&hl=de
sailfishOS ea4: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
cm 10.1.3: http://get.cm/get/aWH
Multirom manager in play store: https://play.google.com/store/apps/details?id=com.tassadar.multirommgr&hl=de
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Before we're going on check up the following
1. All zip's you've downloaded have to be transferred on the device
2. Apps from play store are installed
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Installation process
Reboot in twrp recovery
Flash the new kernel
Flash the modem 0.84 in twrp. Or via the modem flasher from playstore. It's you're decision.
Boot back into android
Proof the functionality in android withe the new modem and kernel. Wlan working? Bluetooth? NFC?
Open mutlirom manager. Follow the installation steps.
After some time you'll be back in android. You have now the right modem, kernel and and a twrp multirom version on you're device
After this. Please reboot back into twrp recovery
There select the advanced button.
Then the multirom button
Select add rom and mark up the entry sailfish os
Press next.
Now you can choose two zip files to flash
zip1: Select the cm10.1.3 zip file
zip2: Select the sailfish EA4 zip file
Installation process is beginning.
After this select reboot
You automatically went into multirom where you can cancel the automatic boot process for the primary rom. Then you can select which rom you want to start.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And the most important thing is to read: http://forum.xda-developers.com/jolla-sailfish/general/qa-sailfish-n4-thread-devices-t2727330 for further question before you ask. I have described there many things to start with sailfish. If you find this useful think about to press the thanks button.
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
anttimonty said:
I'm a bit confused why do you insist on updating the modem? I checked my modem version and it is newer so I imagine there is no need to update. Also why use such an old version ov CM?
Just asking because I did all according to your instructions except I used newer CM build and didn't update my modem firmware as it was already newer. But for some reason Sailfish wont boot. It just hangs showing Google at start.
Click to expand...
Click to collapse
lol. and you ask why it won't work? It gave reasons for the instructions. Also look in the linked q&a thread at the bottom of first post. And here for you the relaese notes. Hope things becomes clear now. enjoy
Release Notes:
This release is based on SailfishOS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of alpha quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Click to expand...
Click to collapse
Also I stated in first post why I only described the way I've did
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
anttimonty said:
Ahh ok nevermind got it working once I used the older CM image. Wifi seems not to be working but I guess that is because I didn't downgrade my modem firmware. I guess I'll wait for a more stable builde or better yet buy a Jolla phone. Just like having the nexus 4 as I can test bunch of operating systems on it.
Click to expand...
Click to collapse
yes. that's a great benefit of this device Do you like sailfish?
With modem version 0.84 you have all parts working in sailfish and android
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
anttimonty said:
Ok thanks for the hint. I used to be one of the early adopters of Jolla, but couldn't use it as my daily phone so I sold it, but now that the OS has matured I think I maybe swithing back. Even though I still think Nokia N9 had far better UI experience. If only some would port N9 UI to Sailfish
Click to expand...
Click to collapse
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
v3ng3anc32002 said:
I feel the same, don't know why, but i just loved the N9 and the way the OS worked. I am not saying that sailfish is bad or something, but there Are somethings missing ...
Click to expand...
Click to collapse
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
mudnightoil said:
They've practically done nothing since pre-release to improve and refine the UI, and so many incredibly basic features are missing (voicemail notifications, global copy and paste etc). The pulley menus are ropey and the active covers feature hasn't really been made use of much. They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
I'm not a fan of Android and I can't see myself ever using WP or iOS, but the lack of progress and their production priorities are a bit dispiriting. I'm hoping that they're holding a lot of big and waited for improvements for update 1.1 (October).
Anyway, I'll keep it as my main phone for a bit longer, despite the fact that I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Works nicely on my n4. Looking for getting gapps to run....
mudnightoil said:
They seem to be mainly concentrating on the Jolla Launcher for Android, which will definitely make them higher profile ... but if all their software engineers and UX guys are working on that instead of Sailfish itself, then it seems like cutting off their nose to spite their face.
Click to expand...
Click to collapse
This is just wrong
mudnightoil said:
I have a Z3C coming early next week. Hope to see a decent Sailfish port for it soon.
Click to expand...
Click to collapse
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
paulle said:
hope the same for the z1c, but don't how is the chance to see this port (soon or later).
Click to expand...
Click to collapse
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
iuno said:
This is just wrong
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
thank you for information, followed your links to look at. It seems there for the z1c is a lot of remaining, we will need patience.
iuno said:
I bought a z1c after my N9 broke and I totally regret it. But I'll go on and try using it with Sailfish one day
I tried using the hadk but like some other devices, there are gpu-problems with the z1c (see https://wiki.merproject.org/wiki/Adaptations/libhybris/gpu).
Keep an eye on IRC logs and on the status matrix in mer wiki
sorry for off-topic
Click to expand...
Click to collapse
Don't think I'll regret getting the Z3C, from a hardware perspective ... held one the other day, as a friend had been gifted one by Sony. It's absolutely superb. Granted, I despise Android .. but for when the Jolla ****s itself / runs out of battery / when GPS or a camera is needed / roaming / skype /outdoor use, I can suffer it until there's a Sailfish port.
Hopefully as work is already under way for the One Plus One, the identical SoC used in the Z3 & Z3C won't be too much additional work.
For all the moaning and groaning about Mediatek, I'm guessing the simplest and best port of Sailfish will probably be for the Meizu MX4, as there'll be an Ubuntu ROM for it, and libhybris is used by Ubuntu Phone ...
Also, hopefully future iterations of the HADK will smooth out some of the problems porters are facing.
mudnightoil said:
Don't think I'll regret getting the Z3C, from a hardware perspective
Click to expand...
Click to collapse
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
iuno said:
it's the same for me...
The SoC in your z3c and 1+1 is actually the same as in z1c, I guess – 8974 vs 8974ac – only higher clocked.
You should not suppose that mediatek SoCs will be easier in general just because of is one working device. Jolla runs a Snapdragon and it works perfectly, most of the devices sailfish is currently ported to run snapdragons – with very different results.
Click to expand...
Click to collapse
I wasn't saying Mediatek in general will be easier (though it's possible), but any device with an official Ubuntu ROM certainly will (should) be - Meizu MX4 (Mediatek) is the first of those.
P.S. The Z3C is fantastic ... though unfortunately in black as opposed to the red I ordered (it's being swapped tomorrow).
Thank you very much for these instructions. i have one question though. In order to download CM 10.1.3, it says to click that link which takes you to download CM installer app. Ive used that app before and as far as I kmow, it doesnt let you choose which version of CM you want to install, instead it just sets you up to install the newest CM 11. I downloaded 10.1.3 from their site. Either way, no big deal.
Also, which kernel do I download to install? Aosp or CM?
Thank you
Still up to date
Hi,
are these steps still up to date or should we follow a different set up guide to install the latest sailfish OS on the Nexus 4? Because most, if not all, the links on the first page end up 404...
Bluetooth sync from Jolla to Nexus 4
Flashed my Nexus 4 with the factory 4.2.2 from google with radio .48 and then flashed cm-10.1-20131003-SNAPSHOT-TREATFORCOOPER-mako-signed.zip because that seemed to be the 10.1.3 mentioned in the guides to end up flashing the latest sfos from this guide http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823.
I didn't try calling, it has 3G network working and wifi is working but I can't seem to get the contacts from my Jolla phone using the Bluetooth sync from the settings.
Anybody has some advice on this?
Just had a good look at the wiki of devices on the mer website and found out the bluetooth is not yet working on the Nexus 4...
Works perfectly on my oneplus one
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
dylanbos1996 said:
Hello guys, i just have a (few) question(s)
So, last week i installed Google Edition Andriod Kitkat 4.4.4 on my galaxy S4 I9505.
This rom is till now, still amazing, fast and better than touchwiz in any way. But i can't seem to find on the internet how and which version of xposed framework i need to install, since it is per model (i think?) which model do i choose?
since i have a Galay S4 but my rom is not from a galaxy S4, i get confused which one i have to install.
Some links to downloads would be great!
Thanks in advance
Dylan
Click to expand...
Click to collapse
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Thank You!
MAX 404 said:
Hi mate
Basically it works in any android 4.0 + base rom device see from one of his threads
For which devices/ROMs does it work?
I develop the Xposed framework based on the AOSP sources. I'm personally using CM10.2 on an I9100 (Samsung Galaxy S2, bought in Germany). Basically, it should work on any phone which with a ROM based on Android 4.0 or later and an ARM or x86 processor (this is the processor architecture, almost all smart phones and tablets have either of those). Exceptions might be ROMs which are different from the original Android code in some very internal, central code parts (which don't need to be touched for most theming and enhancement modifications). But this is related to the ROM, not the phone itself.
The modules target higher-level code, so they are more likely to be incompatible with your ROM. Basically, the question is whether the methods and resources which the module modifies are similar on your ROM and on the developer's ROM. Let's say a module needs to modify the result of a certain method call. For this, it needs to specify the exact name and parameters that identify that method. If the in your ROM, an additional parameter has been added, the module can't find the method anymore and won't work. If the method can still be found, it will probably work (unless the rest of the app/ROM has changed too much).
There is not definite answer whether it will work. Just try it (of course, making a nandroid backup before is never a bad idea). If it doesn't work, just disable the module. You might want to inform the module developer (not me!) about this fact and provide details (e.g. a logcat and/or the content of /data/data/de.robv.android.xposed.installer/log/debug.log).
Try with latest 2.6.1
http://forum.xda-developers.com/xposed/xposed-faq-issues-t2735540
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
dylanbos1996 said:
Thank you so much for your help. I think it is pretty clear for me now.
Dylan
Click to expand...
Click to collapse
Any time mate.
Hi Z2a users I see that Sony never released 23.5.A.1.291 for Z2a, but on the source of this compilation is possible to build the kernel for Z2a, so I think is possible for Z2a users install Existenz 5.6.5 with some modifications, so if you have a Z2a and you are interested, write on this thread
If somebody wants, I can share the info
I have a Xperia Z2a D6563 and I am currently using EliteKernel with the eXistenZ, when you install the ROM, and flash the Kernel, the camera breaks, but I created some kind of fix using the Cyberian Z2 camera mod (I used this because I am not a developer but I barely know some stuff) and at this moment I have everything working on the Z2a except the front camera, I didn't know how to fix that but if somebody wants to know how I installed and set all, you can ask for it and I will create a post, it really worths it.
Hey z2a user here how can i help?
Physick26 said:
Hey z2a user here how can i help?
Click to expand...
Click to collapse
ok thank you, first I need that you have UB (unlocked bootloader), because I will give you a custom kernel, the reason, Sony released source for 23.5.A.1.291 for Z2a but never released 23.5.A.1.291 for Z2a so as Z2 and Z2a are really similar in theory we can put the Z2 firmware on Z2a just changing the kernel, so if we archieve this the Z2a users could use Existenz 5.6.5. Please contact me on telegram @ShadowElite22
ShadowElite said:
Hi Z2a users I see that Sony never released 23.5.A.1.291 for Z2a, but on the source of this compilation is possible to build the kernel for Z2a, so I think is possible for Z2a users install Existenz 5.6.5 with some modifications, so if you have a Z2a and you are interested, write on this thread
Click to expand...
Click to collapse
So, your kernel update is coming in nearly future? Good to hear that Dev :good:
EugenStanis said:
So, your kernel update is coming in nearly future? Good to hear that Dev :good:
Click to expand...
Click to collapse
Update status, my tester succesfully booted on Existenz v5.6.5, just camera don't work for now, but it will solved later, also I need that you send me the stock build.prop of Z2a, thanks.
I am so expecting the new kernel for z2a...
may I know when will it be released?
yatin_abc said:
I am so expecting the new kernel for z2a...
may I know when will it be released?
Click to expand...
Click to collapse
Well I have a problem, I lost all of my work (kernel and other stuff) because my PC first have a Windows 10 partition and the aubuntu partition, the windows 10 one was damaged and I must format my pc for fix it, I made a backup with Clonezilla of the Ubuntu partition (the one that have all of my work) but the backup wasn't done correctly, and I can't restore it (it seems that it have missing files) so I lost all of my works and I will to start again, the only good thing is that my kernel work is on github so the kernel isn't lost, but all of my other projects are lost, I will to start again this projects soon (first I need to pass some final exams of this semester of university) thanks for your wait I know that is a long wait.
flash z2 firmware to z2a
i need help regarding flashing different firmware, since z2 and z2a are almost the same in specs
i'm wondering if ever i could flash d6503/d6502 (z2) firmware to my d6563 (z2a), would the software or programs be compatible?
i really want to try the nougat update of z2 to my z2a..
hope someone could answer me, i cant really find any information about someone trying this..
thanks in advance.
nice day.
ps:
ShadowElite
also been waiting for your z2a 23.5.a.0.291 firmware
i hope i could also try that next time, because my battery drains really fast.
Cocolocoponcho said:
I have a Xperia Z2a D6563 and I am currently using EliteKernel with the eXistenZ, when you install the ROM, and flash the Kernel, the camera breaks, but I created some kind of fix using the Cyberian Z2 camera mod (I used this because I am not a developer but I barely know some stuff) and at this moment I have everything working on the Z2a except the front camera, I didn't know how to fix that but if somebody wants to know how I installed and set all, you can ask for it and I will create a post, it really worths it.
Click to expand...
Click to collapse
wow thats soundawsome！
can you make rr for z2a？:silly:
Hi. This script enables dualsim support on any custom rom for Xperia XZ (Kagura).
reserved 1
reserved 2
reserved3
It seems your file doesn't work with Android Pie AOSP. Any clue to fix it ?
ulysse132 said:
It seems your file doesn't work with Android Pie AOSP. Any clue to fix it ?
Click to expand...
Click to collapse
My bad, maybe u downloaded first file, i fixed and updated it as far as i noticed that i have typo in code. (It doesnt hurted your phone, but it doesnt enabled dualsim support too).
But it should work now on AOSP Pie (specially MotexT's one), this patcher was specially made for this rom. And it was tested with positive results.
gouster3 said:
Hi. This script enables dualsim support on any custom rom for Xperia XZ (Kagura).
Click to expand...
Click to collapse
Hi this doesn't work on pie.
Im using MotexTs AOSP pie and after flashing it doesn't work at all but rather gives an error message "your device has an internal problem please contact your manufacturer"
Any fix for this?
Uploaded an updated version that works with the new property "persist.vendor.radio" instead of "persist.radio".
https://sx.ix5.org/files/builds/kagura/misc/F8332_dualsim-vendor.zip
Updated dual-SIM patcher for all Sony devices moved here: Universal Sony DualSIM patcher
Updated DualSIM patcher should now work with Android 10, see the linked topic in previous post.