Related
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
android4.4 cannot open
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Click to expand...
Click to collapse
awesome thankx
我是一个卒 said:
android4.4 cannot open
Click to expand...
Click to collapse
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
BytesReverser said:
did you read OP's post properly ?
There is no GUI or anything, just enable and restart and you're all set.
Click to expand...
Click to collapse
sorry,my english is poor
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
berezker said:
I've been trying to find a fix ever since i got this phone and your module fixed it with no hassle
Thank you very much
Can i have your permission to share this on Mi A1 forums and xiaomi subreddit?
Click to expand...
Click to collapse
Sure thing. If I can ask you to please link to this post and not share the APK.
madmack said:
Sure thing. If I can ask you to please link to this post and not share the APK.
Click to expand...
Click to collapse
No problem
Thank you again so much
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Amornik said:
Hi!
Are you actively working on this still? and did you get around to testing it on a oneplus of any kind? I got the 5T, this does nothing on it sadly, and i'm desperate for a fix
thanks!
Click to expand...
Click to collapse
I can't say I'm "working on it still" but whenever I have a need for it, I update it. I actually have the pixel 2 xl running latest oreo 8.1 and needed the added 5 GHz access points at work to have higher speeds (780 MBps beats 54 Mbps any day!)
Works fine here. Just make sure your xposed is working fine and that this module is loaded correctly. Reboot, profit. should work on all 8.1 ROMs given that I'm only modifying a simple framework method which should exist in all variants out there.
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Amornik said:
Hi,
thanks for the reply!
I have installed the latest Xposed, and your module (downloaded from there, not the file here) & rebooted. nothing happens. I do not see my 5GHZ when it's on the 148 and up band. When I switch it to the lower bands (38 and up) works just fine. this is driving me insane. Any chance you could help me out ?
In another post, someone offered me to replace a file, and that seemed to work for a bit, but now it has also stopped working
Link: https://forum.xda-developers.com/oneplus-5t/help/wifi-region-5ghz-question-5t-t3776003#post76220330
Thanks! appreciate any and all help.
Edit: Actually it would help to understand what it is exactly your addon is changing ? since the above file does have something that seems relevant. is this the same value being changed?
Click to expand...
Click to collapse
Maybe use my file here instead? Not sure what's on the xposed modules repo.
madmack said:
Maybe use my file here instead? Not sure what's on the xposed modules repo.
Click to expand...
Click to collapse
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Works fine on my xiaomi a1 !!! thx so much!!
madmack said:
I wrote this for myself but here it is in case anyone is also interested.
Google sets the wifi country code to whatever is in your sim card. If the country does not have a corresponding list of enabled 5GHz frequencies, then a lot of these frequencies get disabled. This mod simply sets the country code to US. There is no GUI or anything, just enable and restart and you're all set. Android marshmallow only. I tested it on my S7 edge and it's working fine.
Enjoy.
Edit: Added OREO 8.1 version. Testing working on Pixel 2 XL.
Click to expand...
Click to collapse
cleberjb said:
Works fine on my xiaomi a1 !!! thx so much!!
Click to expand...
Click to collapse
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Amornik said:
It would be great if you could specify which version of Android (8.0, 8.1) and which ROM (or stock).
thanks!
Click to expand...
Click to collapse
Sorry my inconvenience. Works on Android 8.0 stock.
Amornik said:
Hi,
Thanks for the reply! I thought I had mentioned I already tried it, did not change anything.
Maybe if you told me which file this is editing and which value is being changed, I might be able to debug and see if it's actually changing the value it needs to.
Click to expand...
Click to collapse
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
madmack said:
Sure, editing method setCountryCode in com.android.server.wifi.WifiServiceImpl
Setting the parameter to US manually.
Click to expand...
Click to collapse
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Amornik said:
Cool, thanks!
Just as a follow up..
1. is this com.android.server.wifi.wifiserviceimpl a file (.jar?)or db file?
2. where is it located?
3. does your fix change it every time on reboot? or is it a one time change? (meaning, does the phone update this from the SIM occasionally?)
thanks again!
Click to expand...
Click to collapse
no man, it's a framework class that xposed can tap into and change the behavior. Take a look at the source code of Android AOSP for that class. it's not a simple file in /system that you modify. It is changed every time this method is invoked, it's how xposed works.
Lol, just goes to show how much I know about how rhis works, which is nothing
Its working with the update to 8.1 btw.
Thanks for all your work and patience!
Hi,
I will release here my updated "boot.img" files for the Xperia XA Ultra Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Follow the guide from @Yooooomi to flash new firmware on your Ultra to avoid bugs and brick: https://forum.xda-developers.com/xa-ultra/how-to/flashing-xa-ultra-flashtool-t3551319
Releases:
12/28/2016: From 36.0.B.2.109 kernel sources and Ramdisk from 36.0.B.2.109 firmware.
https://mega.nz/#!cxI3SJaC!o-aqc2gUZufDJefKaxGRxRhekEq32B1bIDB3ROxyd7Y
04/01/2017: From 36.0.B.2.146 kernel sources and Ramdisk from 36.0.B.2.146 firmware.
https://mega.nz/#!VhwRQLqR!rOqEFWeOC3IQKl4aDw7P_v0U2wmZtBPXk_MSDJMEy9k
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
twhhhco said:
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
Click to expand...
Click to collapse
Hi, it's not a Rom just a boot.img for unlocked bootloaders with stock kernel built from Sony open source archive.
36.2.B.2.109 boot should fix the front camera not focusing after root.
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
klengjaua said:
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
Click to expand...
Click to collapse
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
rrvuhpg said:
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
Click to expand...
Click to collapse
These are the fixes you mentioned?
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
rrvuhpg said:
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
Click to expand...
Click to collapse
I will do it with f3213
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Nrsoto said:
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Click to expand...
Click to collapse
Here's step by step what I did, I hope it will work for your device too:
1. Go to xperifirm and download the 36.0.A.1.111 firmware (service unit exchange)
2. Create a bundle on the flashtool within the firmware folder
3. Flash it
4. Happy rooting!
There is however something I have to mention about this fw: you'll probably not receive any system updates
IF U ARE A SNAPCHAT USER install Snapchat before messing the system up with xposed
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Talal Tango said:
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Click to expand...
Click to collapse
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
sexxualization said:
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
Click to expand...
Click to collapse
I've had this issue on all firmwares up until the one i mentioned. And yeah i didn't even use my external usage yet, so it seems that im having a different issues although we both got dark images. I would try different firmwares but I dont know what sony did to make the battery much better on the recent firmware. I'll try messing around till I find the culprit.
Thanks.
Buggy with f3216...please fix
Help Downgrading to .111
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Pandawa3 said:
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Click to expand...
Click to collapse
By deleting root, I assume you tried to delete the root app not root access itself.
You have to go back to stock rom, install snapchat, log in, root your phone and never log out.
szucsi1996 said:
Buggy with f3216...please fix
Click to expand...
Click to collapse
Hi, how is it buggy? I would like to root my f3216, thx.
Aphex33 said:
Hi, how is it buggy? I would like to root my f3216, thx.
Click to expand...
Click to collapse
i think, don't do it!
edit: Brightness adjustment not working, ui very buggy, etc.
Xperia XZ1 G8341 Vanilla AOSP ROM
This is my first ROM and its fully Vanilla. I Just followed this Build guide without any modifications whatsoever.
The future goal is to build a stable Rom with mostly FOSS Software, stability and useful tools/settings.
Bugs/missing functions i discovered so far:
- Camera Not working always and -> Lens Distortion. Although RAW should be possible.
- Sony Bootlogo has some Artifacts
- No automatic APN setting
- No NFC 25.05 working
- No 90/120Hz mode (or does it?)
- No Display Colour Calibration
- Low Singlethread Geekbench Score (836) and (6060 Multicore) [Governors and schedulers not optimized]
Fingerprint Sensor is working and it takes some time to find Network (not sure if bug or normal).
I hope to find usable answers to those problems + ideas and hope, to receive enough feedback to improve as much as possible.
Just Flash all files (boot, recovery [or any working TWRP], system,vendor, userdata and the OEM Binaries [
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img] and you should be good to go.
XZ1 Single Sim(25.05.19)
XZ1 Dual Sim
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_yoshino.img
120Hz Mode
Obviously I am not responsible for bricked devices or anything that this could be related to.
XDA:DevDB Information
RumiRom, ROM for the Sony Xperia XZ1
Contributors
celeron1
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: Stock AOSP Userdebug
Version Information
Status: Testing
Created 2019-05-25
Last Updated 2019-05-30
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
marios199546 said:
Don't use V8 binaries, V9 are out
https://developer.sony.com/file/dow...-for-aosp-pie-android-9-0-kernel-4-9-yoshino/
Worse perfomance is expected because of lack of qti perf framework
Click to expand...
Click to collapse
Neat!
Im gonna try these. Thanks a lot.
I would marry if you turn 60fps to 90-120-144 omg plz plz
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
There is little to nothing about this I could find for the xz1 except one oreo based rom. I have to compile the kernel for it and find out if 60+ hz is really working and how to succesfully implement a toggle option for it. Since im new at this it might take some time without help but its something I want to impliment.
The Xz1s Display obviously is really underperforming in non Sony roms without the "Bravia engine" (colour apperence) imo compared to other open roms. I tried the Bravia magisk module but could not see any difference (also did not checked what it should do at system level).
So if someone has more knowledge feel free to share
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
*Update 29.05. I Fixed Wifi for the 120Hz version. link in first post
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
What about the version for two SIM cards?
Model G8342.
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Riskypedia said:
Your rom works perfect on my phone, thanks dev.
Btw, doesn't it support Treble? I cannot boot any of the GSI roms on the forum...
Click to expand...
Click to collapse
It should support Treble.
Maybe you also need to flash "Disable DM Verity" and "Magisk" after
Can be used on G8342 ? ?
Sent from my Sony Xperia XZ1 using XDA Labs
celeron1 said:
I compiled a Kernel from here and modified:
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-base-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar-sde.dtsi
arch/arm64/boot/dts/qcom/dsi-panel-somc-poplar.dtsi
(changed 60hz to 90/120hz).
How can I check if the Panel really is working under those frequencies and if other steps are needed?
When compiling I got an Error with drivers/staging/wlan-qc/qcacld-3.0 -> so i removed them from drivers/staging/Kconfig (So apparently no Wifi).
These are the Kernels (boot):
90Hz
120Hz
Camera seems to work without problems (also Raw) so I guess there is something wrong with the precompiled Sony Kernel.
Also the Sony bootlogo is not present (no artifakts??)
And again. Flash at own risk.
Click to expand...
Click to collapse
Can i use this kernel with stock sony rom? (Existenz patched btw...)
ΒΕΓΑ said:
Can i use this kernel with stock sony rom? (Existenz patched btw...)
Click to expand...
Click to collapse
The Kernel is for AOSP (Linux kernel 4.9) so normally it shouldnt work with the Stock Firmware but i dont know if it works with the patched Existenz rom.
therma.cpp said:
What about the version for two SIM cards?
Model G8342.
Click to expand...
Click to collapse
Its for the single Sim.
Im not satisfied with the current State but I can build a dual sim version as well. (Building on hdd due to small SSD so it might take a while)
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
sinkoo1979 said:
Screen is not responsive (SOV36). Any suggestions?
update: not the rom. tried to flash different rom and same result.
Click to expand...
Click to collapse
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
celeron1 said:
Does it respond different while charging?
Is the screen properly clean?
Try flashing the last stock rom > same result?
If not try flashing any gsi > result?
Then full cfw flash + sw binary.
And do factory resets before flashing.
Hoping for the best. Not sure how and if the SOV36 model differs from the rest
Click to expand...
Click to collapse
no
yes
no
did not work
works with stock
sinkoo1979 said:
no
yes
no
did not work
works with stock
Click to expand...
Click to collapse
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
celeron1 said:
Dis you try one of these GSIs and did you flash the SW-Binaries after?
How "non responsive" is it? Laggy/Not at all/Ghost touches etc.?
Since this is off-Topic i will delete this message after you read it. You shuld open a new Thread where the Problem could be discussed.:good:
Click to expand...
Click to collapse
Nothing at all
sinkoo1979 said:
Nothing at all
Click to expand...
Click to collapse
Try flashing a oreo based stock rom.(or if you only tried oreo then pie), then flash gsi etc
ΒΕΓΑ said:
I would marry if you turn 60fps to 90-120-144 omg plz plz
Click to expand...
Click to collapse
don't you think it would be the least manner to put some pics of your ass when you come around with "marrying-for-asking"? XD :silly::silly:
Below are Stock kernels with DT2W added. The kernels have been extracted from 47.2.A.11.228 firmware.
The kernels are SElinux enforcing (same as stock). They are in no way custom, all i have done is add the dtb from Iovf's .107 kernel to allow double tap 2 wake.
Some people have reported the DT2W feature requires a solid tap, and sometimes may not wake the screen instantly.
This is out of my hands, and capabilities, to do anything about.
Installation:
On stock .228 firmware:
Flash the kernel for your device in TWRP
Flash whatever Magisk.zip you prefer, and reboot. Once rebooted, install the magisk module below (DT2W_Magisk Module) and reboot.
(If you want permissive selinux, also install the Permissive module in Magisk at the same time).
eXistenZ users:
The kernels are also compatible. Same install steps apply (flash kernel, flash magisk, reboot)
If.you want to keep SElinux set to enforcing, use the DT2W_Magisk Module.
If you are using something to set SElinux to permissive for fonts (or whatever reason), you dont need the DT2W Magisk Module, only the Permissive module.
Also attached are the TWRP flashable stock .228 kernels.
Thanks to @iovf for the original kernels I pinched parts from.
Thanks to @shoey63 for the DT2W Magisk Module.
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Did you flash magisk after kernel?
theflanker said:
Stuck on Sony boot logo. I use the last eXistenz rom on last firmware .228
Click to expand...
Click to collapse
Which kernel? Single or dual?
kojak1989 said:
Did you flash magisk after kernel?
Click to expand...
Click to collapse
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Beetle84 said:
Which kernel? Single or dual?
Click to expand...
Click to collapse
Single
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
Did tou do it with clean install ? If yes then you must do it with 18.1 and let eXistenZ boot once and for me iovf kernel make freezes.
theflanker said:
Yes of course, 20.0 version. Maybe I have to try 18.1. I will try and tell you.
Single
Click to expand...
Click to collapse
I use v20 on the XZP with no drama, can you try the dual sim kernel and let me know? There is no harm in using a dual kernel on a single sim phone. Thanks.
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
Myself5 said:
I roughly remember looking into this decades ago and the conclusion was that either the XZP/XZ1 kernel is super ****ed (beyond repair) or they have some sort of hardware issue causing the situations. When you used DT2W and combined it with using the power button in a specific order the touchscreen wouldn't work anymore until you turn the screen off/on again using the power button.
Click to expand...
Click to collapse
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Generic123. said:
I tried these kernels, and it seems really inconsistent and finicky. However, I think I found the reason why there are so many issues with double tap to wake on the XZ1; a developer looked into implementing tap to wake and had this to say:
@Beetle84, do you know anyone who could look into this? It would be nice to see if this was a really bad software limitation, or just a hardware limitation.
Click to expand...
Click to collapse
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Generic123. said:
Is there any way you could contact iovf to ask him/her? Maybe we could see if the method you mentioned for the XZP might be able to get dt2w to work on the XZ1.
Click to expand...
Click to collapse
Will do
Beetle84 said:
Will do
Click to expand...
Click to collapse
Many thanks my dude.
I'm bit courious, as there has been only one person has mentioned what rom and firmware they are using, but for those that are using the the existenz rom have you tried going into the rom display settings and flipping on the dt2w switch to see if it helps..
see pic..
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
theflanker said:
I tried to reflash everything with Magisk 18.1 but I have the same error.
But doesn't it work for me?
Click to expand...
Click to collapse
No idea mate, single and dual are confirmed working. Try flashing the stock kernel, magisk and reboot
Then try the dt2w kernel, magisk and reboot.
Beetle84 said:
I think its the xz1 panel derf alot said somewhere in his LOS thread... xzp works flawlessly with dt2w, despite the above quote.
On another note, whih kernel did you try, the single or dual?
Click to expand...
Click to collapse
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
Generic123. said:
Does that mean the XZ1 does not have the appropiate hardware for it? It's a shame if that's the case.
I used the single sim kernel, on existenz pie with the magisk module.
Click to expand...
Click to collapse
See above.
Beetle84 said:
I believe its hardware. For the xzp, the dt2w code was ported (by a different dev than iovf) from the xperia x to the xzp kernel. Im not sure if it will get any better ever. Im not positive how iovf did it.
Thanks for letting me know about which kernel you flashed, someone above bootlooped using the single sim kernel, no idea why. Its kinda hard to test myself without the xz1... A few guys tested before i uploaded them here, so I don't know what happened for him/her.
Click to expand...
Click to collapse
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Myself5 said:
IIRC the Xperia XZ Premium got shipped with multiple touchscreens.
I can assure you mine is doing that, and I can provide you multiple other instances where it happened. I've been trying to use my XZP as a DD for around 2 months and had that issue nearly daily when DT2W was enabled. (Mind you, that was shortly after release though, so it's been a while).
See above.
There is nothing that was "ported". Both devices have the code for Doubletap to wake in the kernel. It's a single matter of replacing a "false" with "true". None of that is standard code btw, so isn't it interesting that Sony put effort into adding Doubletap to wake just to disable it then?
P.S: Why are you building Dual and Single SIM variants of the kernel?
Click to expand...
Click to collapse
Thanks for the clarification. Would it be possible for us to determine what our touchscreen manufacturers are? In your case, tap to wake is pretty glitchy. But, in @Beetle84's case, he appears to have little/no issues. It would be nice to see if different touchscreen manufacturers are at play here.
kernel - stock ready for root
Boot.img For Xperia 5 J8210 and J9210 variants.
J8210/J9210
DOWNLOAD:
STOCK
J8270
DOWNLOAD:
STOCK
For root you need install magisk manager and patch boot.img via magisk .
Next step is easy : Install drivers and use flashtool or fastboot to flash patched boot.img .
Good luck .
FLASHING:
For flash you need :
1.Unlocked bootloader (warranty to be not void)
2.ADB i FASTBOOT
3.Drivers for your device (try to install drivers from flashtool. Win10 users must disable drivers signing.)
If you like my work , please press Thanks
If you want to buy me a coffee for my work you can use PayPal Thanks
https://paypal.me/marek10747
My Facebook group :
Facebook support group , for all devices !!
This kernel I do for xperia 5 only
This kernel is from flashtool , I only unpack it manually without use flashtool , because flashtool don't support unpacking this files now .
XDA:DevDB Information
XPERIA 5 - KERNEL, Kernel for the Sony Xperia 5
Contributors
MAREK10747
Kernel Special Features:
Version Information
Status: Stable
For: J8210,J9210
Base: 55.0.A.11.25
Created 2019-11-12
Last Updated 2019-11-12
Thanks.
However, I won't root my device. I've had Sony devices since 2012 and it'll be the 1st device that I won't root.
Unfortunately, since XZ2, we have no DRM patch and cannot have hope to have it...
I don't want to lose DRM protected stuff (such as camera denoising...).
Thank you, might give this a go. Have you tested on an Xperia 5?
Sent from my Sony J8210 using XDA Labs
Until the Xperia 5 doesnt received anymore os updates I will give this a go. Does it contain the drm keys?
That was stock boot without patches , drm etc. You can flash it via fastboot .
nreuge said:
Thanks.
However, I won't root my device. I've had Sony devices since 2012 and it'll be the 1st device that I won't root.
Unfortunately, since XZ2, we have no DRM patch and cannot have hope to have it...
I don't want to lose DRM protected stuff (such as camera denoising...).
Click to expand...
Click to collapse
Looks like You totally missed the DRM Patches which are around since 2017... There is nothing not working anymore. Even AOSP can take Denoised Pictures OOTB. Besides that has SONY Changed a lot around the Camera with the Xperia 1 & 5. I mean... 3 Lenses? We are good to go. My Xperia 5 will be in My Hands tomorrow and i will not wait a Single Minute to unlock its Bootloader :angel:
Miustone said:
Looks like You totally missed the DRM Patches which are around since 2017... There is nothing not working anymore. Even AOSP can take Denoised Pictures OOTB. Besides that has SONY Changed a lot around the Camera with the Xperia 1 & 5. I mean... 3 Lenses? We are good to go. My Xperia 5 will be in My Hands tomorrow and i will not wait a Single Minute to unlock its Bootloader :angel:
Click to expand...
Click to collapse
a bit off-topic
@Miustone could you run "Camera2 API Probe" before/after unlocking and post screenshots of the results for comparision, please. I would like to know which DRM camera stuff still works afterwards without ta-backup/restore
blue-spiderfire said:
a bit off-topic
@Miustone could you run "Camera2 API Probe" before/after unlocking and post screenshots of the results for comparision, please. I would like to know which DRM camera stuff still works afterwards without ta-backup/restore
Click to expand...
Click to collapse
Sure. Will do that over the Weekend...
Miustone said:
Looks like You totally missed the DRM Patches which are around since 2017... There is nothing not working anymore. Even AOSP can take Denoised Pictures OOTB. Besides that has SONY Changed a lot around the Camera with the Xperia 1 & 5. I mean... 3 Lenses? We are good to go. My Xperia 5 will be in My Hands tomorrow and i will not wait a Single Minute to unlock its Bootloader :angel:
Click to expand...
Click to collapse
Ha ha!! Excuse me but find us a DRM patch for xperia XZ2, XZ3 and 1. You won't find because it does not exist.
Beside my Xperia 5, I've my good old rooted XZ2: its denoising in low light conditions is not good at all, it was much better when it was not rooted. Why? Because some Sony camera stuff is DRM protected.
Now, you can do anything with your device, I don't care...
PS: the only existing "patch" for XZ2 only prevents black view in camera on Pie (it was a real patch on Oreo... but this is a long story, I won't tell it here).
What sin file did you extract from and what tool did you use to extract it? Thanks
EDIT: @MAREK10747 sorry, read in your post that you extracted manually because Flashtool doesn't work with these files yet. I've uploaded what I believe is the US' Xperia 5 (J8270) boot image. If you have a moment would you mind extracting this one so we can root?
https://drive.google.com/drive/folders/1DLNDojeqr-Pmq0Xu6F5Nr_0I16b1uTd2?usp=sharing
orrorin said:
What sin file did you extract from and what tool did you use to extract it? Thanks
EDIT: @MAREK10747 sorry, read in your post that you extracted manually because Flashtool doesn't work with these files yet. I've uploaded what I believe is the US' Xperia 5 (J8270) boot image. If you have a moment would you mind extracting this one so we can root?
https://drive.google.com/drive/folders/1DLNDojeqr-Pmq0Xu6F5Nr_0I16b1uTd2?usp=sharing
Click to expand...
Click to collapse
I can try to help you . Soon I download this file and extract , to next sunday i'm busy .
@orrorin https://mega.nz/#!YQcgBaZa!Vm4Nu-CMHtCD27V-SK14-6mjAiJwEwgFvW5xIprJWHI
Get your boot
MAREK10747 said:
@orrorin https://mega.nz/#!YQcgBaZa!Vm4Nu-CMHtCD27V-SK14-6mjAiJwEwgFvW5xIprJWHI
Get your boot
Click to expand...
Click to collapse
THANK YOU!!!
EDIT: This totally worked, rooted with Magisk with no TWRP and (so far) working fine
orrorin said:
THANK YOU!!!
EDIT: This totally worked, rooted with Magisk with no TWRP and (so far) working fine
Click to expand...
Click to collapse
No problem If you you can press thanks in my thread and/or give me one U.S dolar donate
MAREK10747 said:
@orrorin https://mega.nz/#!YQcgBaZa!Vm4Nu-CMHtCD27V-SK14-6mjAiJwEwgFvW5xIprJWHI
Get your boot
Click to expand...
Click to collapse
@orrorin
TWRP`? :crying:
Edit: Oh, so You just flashed a Magisk edited Kernel Image for Root?
@MAREK10747 any chance that You can do the Job? https://forum.xda-developers.com/xperia-5/how-to/twrp-xperia-5-t4015077
---------- Post added at 20:06 ---------- Previous post was at 20:05 ----------
[/COLOR @MAREK10747 any chance that You can do the Job? https://forum.xda-developers.com/xperia-5/how-to/twrp-xperia-5-t4015077
I don't have this device . Chance is little . After broke of XA1 I bought meizu m6t and I have meizu device . If you motivate me via paypal I can try to make twrp without this device physically .
Miustone said:
@MAREK10747 any chance that You can do the Job? https://forum.xda-developers.com/xperia-5/how-to/twrp-xperia-5-t4015077
---------- Post added at 20:06 ---------- Previous post was at 20:05 ----------
[/COLOR @MAREK10747 any chance that You can do the Job? https://forum.xda-developers.com/xperia-5/how-to/twrp-xperia-5-t4015077
Click to expand...
Click to collapse
Actually you can try to flash twrp from lenovo , but I don't test it . http://www.mediafire.com/file/89uw6vpivyd1q91/recovery-TWRP-3.3.0-0524-LENOVO_Z5PRO_GT-CN-wzsx150.img/file Possibly this twrp boot correct and to be work if no say me about this .
If this recovery boot , you can make backup of system boot and other partitions and give me here . I try to do mod for system and boot .
Hi!
Sorry if this is a stupid question, I'm a complete beginner at these things and never rooted anything in my life so... Please be gentle I'm looking to root my Xperia 5 j9210 version because I'm told that's what I need to do in order to regain the ability to record calls which was lost to me due to the Android Pie update. However, I feel lost in the terminology and I'm really unsure about what I actually need and what I don't need... I read somewhere I need a custom rom, someone said Stock works fine, either way I can find neither stock nor custom roms for the device in question despite my best efforts... I did however find this, but a Kernel is not a rom as far as I understand so I don't really know where that leaves me... Would anyone mind explaining to me what this is, if it will help me achieve what I need (root acess so I can record calls) and if so how do I use it? I'm talking like, explain this as if I was a caveman and then maybe I might get it somewhere down the line... xD
I'm imagining a lot of people would just go "You have no idea what you're doing, this is not for you, please stop", but I am genuinely trying to learn about these things so... If you don't mind, please help this humble beginner understand the basics
Any and all help is much appreciated!
Cheers
Miustone said:
@orrorin
TWRP`? :crying:
Edit: Oh, so You just flashed a Magisk edited Kernel Image for Root?
Click to expand...
Click to collapse
I totally agree!
@MAREK10747
Sorry in advance for my ignorance:
But at least, a minimum of knowledge of Android and Magisk assumed, the people will know what to do. Before at least there's a working TWRP for this device, I won't buy it and will stay with a supported XZ2/XZ3 device.
Well, it's a new device, and I surely don't want to criticize you; it will help people who already got this device and can't wait to root :good:
MAREK10747 said:
... If you motivate me via paypal I can try to make twrp without this device physically...
Click to expand...
Click to collapse
Sorry again, but this isn't the correct order. It has to be: Someone offers a product and another one is willing to pay for it and/or support it, but not: "Send me some money via PayPal to motivate me and I will see what I can do". It's like to buy a pig in a poke!
On the other hand, I don't know, if this goes conform with the xda rules...