Database Develop

[Q] Moto X 2014 & Cisco AP

I have a Moto X (2014). I need to use it in various locations with Cisco APs. The problem I'm having is that after entering a network pass code, the network transitions directly to saved and never actually connects.
Logs on the phone show:
"WPA: CCMP is used, but EAPOL-Key descriptor version (3) is not 2"
The access points aren't mine to control or I'd patch them.
My desire is to disable pmf in /data/misc/wifi/wpa_supplicant.conf, but every time I toggle wifi the file seems to get regenerated with pmf=1 instead of the desired pmf=0.
Any thoughts? Or ideas when we might see a fix ala:
Code:
diff --git a/src/rsn_supp/wpa.c b/src/rsn_supp/wpa.c
index d95c1bd..f8825d2 100644
--- a/src/rsn_supp/wpa.c
+++ b/src/rsn_supp/wpa.c
@@ -1756,6 +1756,9 @@ int wpa_sm_rx_eapol(struct wpa_sm *sm, const u8 *src_addr,
wpa_msg(sm->ctx->msg_ctx, MSG_INFO,
"WPA: Backwards compatibility: allow invalid "
"version for non-CCMP group keys");
+ } else if (ver == WPA_KEY_INFO_TYPE_AES_128_CMAC) {
+ wpa_msg(sm->ctx->msg_ctx, MSG_INFO,
+ "WPA: Interoperability workaround: allow incorrect (should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor version to be used");
} else
goto out;
} else if (sm->pairwise_cipher == WPA_CIPHER_GCMP &&
The patch above isn't mine but I'm not yet 'old enough' to post links to external things. Just FYI, I didn't fix the C code, I just hacked up the overlay conf below.

[solved] PMF workaround for Moto X (2014)
Every single time I go to ask a question it's too soon.
If you have this phone and you're trying to connect to a CISCO AP that you either can't or won't update, here's a work around that should get you online.
Requirements
* Rooted
* Basic ADB use
* Basic linux commands
Code:
adb shell
su
cp /system/etc/wifi/wpa_supplicant_overlay.conf /sdcard/
On your computer
Code:
adb pull /sdcard/wpa_supplicant_overlay.conf .
perl -i -pe 's/pfm=1/pfm=0/' wpa_suplicant_overlay.conf
adb push wpa_supplicant_overlay.conf /sdcard/
Turn off wifi
Back on your phone.....
Code:
adb shell
su
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system
cp /sdcard/wpa_supplicant_overlay.conf /system/etc/wifi/wpa_supplicant_overlay.conf
sync
Reboot. Once your phone reboots, turn on wifi and you should be able to join if you were having the same problem I was with a few APs.
I'd like to thank /etc/init.qcom.wifi.sh for pointing me in the right direction.
NOTE:
This hack is a dirty, dirty hack. It completely disables pmf which is a fairly nice part of 802.11w
It hasn't reached mass adoption yet, but it's a shame I needed to disable this. A more pragmatic fix would be to fix the wifi driver to fall back as the patch in my first post does.

Awesome conversation I'm having with myself, but hey somebody might use this...
I wrote a stupid app so I could toggle the hack I did on/off for when I'm not using a crippled wifi AP. It's fugly but it works. The apk is at https://neverlight.com/MotoXWifiHack.apk

If you'd rather get the source and build it yourself, and I wouldn't blame you, I put it up here:
https://github.com/jstelzer/MotoWifiHack

Bell, Telus, Koodo and Freedom Mobile Volte and Vowifi Calling Working *Update Android 11 Require Root*

Finally
I can confirm it worked on my Oneplus 7 Pro both Volte and Vowifi calling it also can work on oneplus 6, and 6T since I don't have a device so I can't test it.
some people are unable to activated so this method require additional step for them.
Install QPST: https://mega.nz/file/zQt3ESDA#dd69iA2r9xZaYwWvYrCvVHl-OmjucIWI4ETFBTO5bM8 (This tool only work on Oneplus 6,6t, 7 series. Oneplus has blocked this tool on oneplus 5 series)
Next steps:
find PDC tool from installed QPST and open
select device from drop-down menu, if it is empty, you will have to reinstall/choose another driver
now right-click on overseas commerical ds and select Deactivated - Sub0
now right-click on Commerical-TMO and select SetSelectedConfig - Sub0
and now button Activate
Restart your phone than apply following step:
Oneplus Usb driver (Dont install it if you already installed this before)
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
After unzipping pixel3.zip you need to go to: Pixel3\mcfg_sw\generic\Pixel\NA\Freedom\VoLTE and copy mcfg_sw.mbn file to folder where you will have your EfsTools saved. It will ask you to overwrite one that is in that folder. Press yes.
Now follow these steps:
This method doesn't required root.
0. Make sure that you just enabled the VoWiFi and VoLTE in your carrier first !!!
1. Download and install the oneplus LogKit and Engineering mode apk:
3. Type *#800# --> oneplus Logkit --> Function Switch --> enable VoLTE and VoWifi switch
4. Open Settings --> WiFi & Intenet --> SIM & netwok --> enable VoLTE and VoWifi switch
5. Connect your phone to PC
6. Type *#801# in Phone app and enable Full-port switch (if your computer unable to recognize COM PORT try installing qualcomm driver: https://mega.nz/file/jV9ByarL#lbryKSC6uk9D-GTErtJ0SHyVOfWKA2TIl-psXmhj4YU)
7. Download and unzip the EfsTools with config files includes. (Make sure copy mcfg_sw.mbn file from pixel3.zip freedom folder replace the file if already exit.)
8. Open CMD as Administrator on the PC, navigate to the folder where you extract the files (eg. cd c:\EfsTools-0.10-modded-1.2-win32)
9. Now execute the following commands:
EfsTools.exe efsInfo
If your Freedom sim in Slot 1 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -v
If your Freedom sim in Slot 2 use this command:
1. EfsTools.exe writeFile -i mcfg_autoselect_by_uim -o /nv/item_files/mcfg/mcfg_autoselect_by_uim -s 1
2. EfsTools.exe uploadDirectory -i mcfg_sw.mbn -o / -s 1
Thats it. Commands with "1" on at the end are for the second SIM card.
You must register here in order to wifi calling work: https://vowifi.authenticateme.ca/
Credit goes to @popos1 and @astracd. Original Post: https://forums.oneplus.com/threads/freedom-mobile-wifi-calling-working.1284987/
You need These file:
Pixel 3 mbn file:
https://forum.xda-developers.com/showpost.php?p=78563337&postcount=4 (Recommend for oneplus 6 series)
Pixel 4 mbn file:
https://forum.xda-developers.com/pixel-4/help/mbn-files-pixel-4-request-t4050247 (Recommend for Oneplus 7 series)
Thanks for @asasanc
Oneplus logkit:
https://mega.nz/file/rZlADYzD#Pg8vLZI4tZ16VXe-v-JfPLCiCab9fTTWwFcPBI04oho
Efstool:
https://mega.nz/file/fQcnQAZT#i0dRA6PvsuK4_PmLHPVXSwhOZroSsR6P1CuUDHwHW8g
Enigneering Mode apk:
https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/
Join Telegram group:
https://t.me/joinchat/QOPwqkqivRqnI4YIW2bojA
Edit:
Alot of people have confirm this method working on Oneplus 6,6t, 7,7 pro, 7t, and 8. For some people VoLTE works right away but for some it take few day to provision as per freedom it could take somewhere 72-120 HR to provision.
Edit 2:
Pixel 2 mbn for oneplus 5. This is recommended for Oneplus 5 only.
https://mega.nz/file/HUsHVYqS#n7pDP-mEMIY5MXffqViAVoqPgF_Au3hzzm6s5dgBZu0
Update: 3/25/2021
This new method requires Root on Android 11.​Please note Engineering won't work on Android 11. you need to follow the following steps to open the ports.
you need Adb tool Platform-tool.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
1. Extract the Folder
2. Open the Platform Tool folder then hold the Shift key and right-click on empty space to open the Command Prompt in the same folder.
3. Then Type "ADB shell"
4. Then type "su" (This will ask root access on your phone)
5. Then type this command to open the port.
"setprop sys.usb.config diag,serial_cdev,rmnet,adb"
Then you have will access to EFStool and PDC tool to Flash mbn file using the above method

can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.

It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
does this trick only work on stock roms, or would it work on a custom rom as well?

What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...

omvir said:
can any other users confirm this is working? I wonder if this will allow the oneplus to connect to band 13 then as well? Because freedom was keeping band 13 for phones compatible with VOLTE on their network.
Click to expand...
Click to collapse
Yes it does connect to band 13.

CrazedBoredom said:
What do you mean by Step 0?
Edit: Did some Googling and found that you have to enable it on a webpage. Use this link to do so: https://vowifi.authenticateme.ca
I can't seem to get past the command: EfsTools.exe efsInfo
Keep getting the follow: Critical Error. The Operation has timed out.
And yes I am in an elevated command prompt.
Checking device manager shows me that when I have Serial and Full-port Switch ON, I have three devices (CDev Serial, OnePlus, OnePlus) that there are no drivers installed for. Not sure where to get these as searching automatically for an updated driver returns nothing...
Click to expand...
Click to collapse
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI

nabbasi said:
here you can download this oneplus driver . but can get this driver as well when you connect your phone to computer.
https://mega.nz/file/GYkxjByK#M6CZA9c9JQaX27j3dLzXRjBrclSVSB9cJs00B5BXdAI
Click to expand...
Click to collapse
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\

This is awesome news. Thanks for sharing brother!

CrazedBoredom said:
I've installed the one from my phone and still no dice. Still no drivers for the three devices. =\
Click to expand...
Click to collapse
.
Did you run CMD as administrator if not try with that.

nabbasi said:
.
Did you run CMD as administrator if not try with that.
Click to expand...
Click to collapse
Yep, no dice.

astracd said:
It works for me - wifi calling on OnePlus 6T McLaren. But not volte. I'm unsure if there is volte in my area. My wife have s9 bought from freedom and it doesn't switch to volte (wifi calling works)
Click to expand...
Click to collapse
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.

darkknight200 said:
I have op6t and am trying to do this but i am stuck on step 6 (6. Type *#801# in Phone app and enable Serial and Full-port switch).
everytime i try to do that , nothing happens. I am rooted on stock oxygen 10.3.5 if that matters.
Click to expand...
Click to collapse
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app

astracd said:
I have google dialer. So each time I run codes need to disable it and enable OP dialer as default dialer. So that could be one of reasons that doesn't work for you.
Second reason that it can be
You also need to get dialer that works as latest version doesn't work. I will try to find a post where they had dialer that works. I believe it was in one of OP5 topics for enabling the volte/vowifi.
Third reason
You would need to install engineering mode
I will try to attach the app
Click to expand...
Click to collapse
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.

darkknight200 said:
ya i managed to install the engineering mode apk from https://www.apkmirror.com/apk/onepl...-0-171117173719-25c8842-android-apk-download/ and can dial in the op dialer fine now.
when i try to enable serial it crashes but full port switch is able to turn on though.
Click to expand...
Click to collapse
Full port is enough. You don't need serial. :good:

astracd said:
Full port is enough. You don't need serial. :good:
Click to expand...
Click to collapse
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.

darkknight200 said:
ok now i am trying the commands in full admin but i keep getting the error message in the screenshot attatched
edit also when I have the serial port enabled, i chekd device manager and it gave me this in the 2nd screenshot. In normal mode without serial port enable, my phone shows up as normal function phone storage device.
Click to expand...
Click to collapse
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?

astracd said:
Did you open CMD as administrator?
And when you connect phone to laptop did laptop made connection sound ?
Click to expand...
Click to collapse
Yes to both

Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.

astracd said:
Other things I can think of right now change charging to drive for your usb connection.
Sometimes windows acting weird when the addresses are long. C:\xxxxxxxxx
I had saved mine in C:\efstools
I renamed folder didn't use full name
I don't think this will help, but worth to try. I will think more about it.
Click to expand...
Click to collapse
stil no luck with renaming them and using different state from charging to file transfer mode

[HELP] Lg v40 Verizon Diag Port Mode issue.

Hi I am using LG v40 Version on Hovac 3.8 Custom Rom (Android 10) , rooted with Magisk. I Am trying to Put phone to Diag mode to get it recognized by Qfil to repair its imei. I have tried Services code method , Adb command method as well as terminal command method but my cell is not being recognized as Diag 901d port. Any leads?

Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?

FLAmbuRNE1 said:
Basically in the same boat here.
I have the bootloader unlocked, rooted through magisk, adb and fastboot working fine. I've tried the usual adb commands:
su
setprop sys.usb.config diag,adb
and it does nothing. I've lost count of the amount of dialer codes I've tried. Drivers are installed correctly (EDL mode is recognised just fine).
Any idea about this or does this phone just *not have a diag mode?
(For reference, setprop sys.usb.config mtp,adb does a disconnect then reconnect sound so everything works right.)
Found the problem. The phone *does actually go into diag mode after adb command. It just doesn't say it has and neither does device manager show 901D ports for QFIL. You can backup/restore QCN on QFIL once you've done the adb command; just choose the regular COM port (you'll have to tick show NonQDLoader/Diag Port option in QFIL).
Do tell me if you managed to restore your IMEI. I'm stuck on either 0 or null depending on what I do. Restoring QCN seems to have no effect (through QFIL). Through QPST, I keep getting "invalid command from phone error." Any ideas?
Click to expand...
Click to collapse
only verizon roms doesnt have imei write protection (idk about A10 but for Pie its working)
if you imei on v40 already null you can try this guide
but use v40 verizon rom
on verizon rom for diag mode enable try this hidden menu code ##7764726405 and hit the call button type service code 000000

All guides seem to point towards the device being called HB-USB Diag 901D in the device manager.
I feel like this is a critical step towards being able to write protected NV items.
Trying to connect to the phone using QXDM tools does not work since the phone isn't recognized as being in Diag mode.
I've tried soooo many ways at this point but don't want to give up just yet.
Let me know if anyone has any luck in getting V40 to correctly connect in Diag mode - or prove to me that diag mode is achieved with the hidden menu (I don't see it working for me - guide me in case I'm misunderstanding something).
FLAmbuRNE1 - I stand corrected - via experimentation.
I was not seeing any ports change in Device Manager or any other application after issuing the
Code:
setprop sys.usb.config diag,adb
command as a super user or after enabling the diag port from the hidden menu.
QFIL's QCN Backup+Restore functionality kinda indicated that these commands do indeed make a difference. When QFIL Restoring QCN on my phone I noticed that QFIL was unable to reset the phone after sending data to the phone - unless I had done both of the above steps. As soon as I did, it would be able to restart my phone and verify that restore was completed.
I have some additional experiments on the way to try and figure out the exact memory locations in
Code:
modemst1, modemst2 & fsg
to modify and flash in order to restore my original IMEI. Fingers crossed...
I'll circle back here with what I find, or don't find. If I don't follow up, anyone interested, message me.

setprop sys.usb.config diag,adb
not work
C:\adb>adb shell
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
flashlmdd:/ $ su
flashlmdd:/ # setprop sys.usb.config diag,adb
flashlmdd:/ #

[ROM][A5/7 2017] Ubuntu Touch (ubports)

Ubuntu Touch (ubports) for the Galaxy A5/7 2017​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
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!
Source code:​Device tree: https://github.com/Exynos7880-Linux/samsung-exynos7880
Kernel: https://github.com/Exynos7880-Linux/android_kernel_samsung_universal7880
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:​Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:​
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera fixed in V3
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that Fixed in V3
MTP Fixed in V3
Untested:​
NFC
Miracast
A7, drivers have been fixed but no real world testing has been done
???
What works:​
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:​Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:​You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:​
Spoiler: Using SSH and logcat
How to use SSH:​SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:​Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:​If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:​Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:​

Download links:
ROM:
V1: https://mega.nz/file/aSgghJQR#hqsJgoWGMb_io4z4bbzRAXV3jDOJ8JDO0mrIL8fUQRs
V2: https://drive.google.com/file/d/1YIxs8EfYvSTt5Y3tTuAVux4RqxsZkGJf/view?usp=sharing
fix: https://drive.google.com/file/d/16hRYtE4oPRDJ4MU4QrRWHYsk_mTRLl09/view?usp=sharing
V3:
Camera and video recording fixed, and a battery drain issue was also fixed
A5: https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20221216.zip
A7: https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20221216.zip
Separate boot partition (only use if you know what you're doing)
A5 V1: https://mega.nz/file/ElRlASjA#qrzBFkZPC_BhEAPcZhfenVBLMYrqv9yvfFpVUnD9-2M
A7 V1: https://mega.nz/file/IkwSWAJT#9aLfme3LcatYTy-qwCcyd42PlJEx6m_-aRbzeKCvgvY

The camera on waydroid is not working. i don't know how to fix it. Camera app isn't installed and i cannot access it. I really want Ubuntu touch and a small camera functionallity for school to installations lessons

Is this stable?

Waydroid is not working. For some reason it crashes.
Also keyboard functions are a bit buggy.
I was trying to go online trough the browser and I made a typo.
After that I was not able to use the keyboard anymore.
I will keep following this threath because it is fun!

Are there new updates coming?

kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017​View attachment 5615835​
Code:
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!
Source code:​Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:​Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:​
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:​
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:​
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:​Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:​You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:​
Spoiler: Using SSH and logcat
How to use SSH:​SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:​Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:​If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:​Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:​View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017​View attachment 5615835​
Code:
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!
Source code:​Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:​Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:​
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:​
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:​
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:​Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:​You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:​
Spoiler: Using SSH and logcat
How to use SSH:​SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:​Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:​If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:​Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:​View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
This rom looks cool as f*ck. Can't wait to install it

kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017​View attachment 5615835​
Code:
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!
Source code:​Device tree: https://github.com/aymanrgab/samsung-exynos7880
Kernel: https://github.com/aymanrgab/android_kernel_samsung_axy17lte
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:​Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:​
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that
Face buttons (other than the home button)
MTP
Untested:​
NFC
Miracast
GPS
A7, drivers have been fixed but no real world testing has been done
???
What works:​
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:​Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:​You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:​
Spoiler: Using SSH and logcat
How to use SSH:​SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:​Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:​If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:​Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:​View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
Man Ubuntu on this brick it works pretty good even i should say better than i expected but of course there are some hiccups like fingerprint dosent work but these are small things. Also one question if its just halium patched kernel and boot can I try booting newer version of Ubuntu Touch GSi?
Great work.

First of all, excellent job! I have tried to port this device myself but thanks to the mess that was the kernel provided by lineage os devs, I wasn't able to. But also, I have an A7 2017 (SM-A720F) so I'm willing to test things out if you want.
Here are my initial feedbacks:
Both SIMs work (They are detected correctly)
Wifi works
Bluetooth works
Camera unsurprisingly doesn't work (Haven't tested the waydroid version)
Touch inputs work (test_input shows the same libis error as on github)
Back and recents buttons don't work but I'm guessing that's to be expected
Volume and power buttons work
The vibrators work (at least when receiving a call)
Mobile data maybe works? (It shows an "L" and I don't know what that means, I also don't have any data to test the connection)
Gyroscope (Auto-rotation) works
Also in dmesg -w on my computer, the device shows up as SM-A520F. But that should be an easy fix for the boot.img and it's something major either.

Arashk2006 said:
First of all, excellent job! I have tried to port this device myself but thanks to the mess that was the kernel provided by lineage os devs, I wasn't able to. But also, I have an A7 2017 (SM-A720F) so I'm willing to test things out if you want.
Here are my initial feedbacks:
Both SIMs work (They are detected correctly)
Wifi works
Bluetooth works
Camera unsurprisingly doesn't work (Haven't tested the waydroid version)
Touch inputs work (test_input shows the same libis error as on github)
Back and recents buttons don't work but I'm guessing that's to be expected
Volume and power buttons work
The vibrators work (at least when receiving a call)
Mobile data maybe works? (It shows an "L" and I don't know what that means, I also don't have any data to test the connection)
Gyroscope (Auto-rotation) works
Also in dmesg -w on my computer, the device shows up as SM-A520F. But that should be an easy fix for the boot.img and it's something major either.
Click to expand...
Click to collapse
Thanks for your feedback,
test_input has an upstream issue
also, camera is hard to debug it works on waydroid use github version https://github.com/aymanrgab/samsung-exynos7880/releases/tag/v2.1
L means LTE and it's work yeah
fell free to contribute https://github.com/Exynos7880-Linux/samsung-exynos7880

kquote03 said:
then flash fix.zip.
Click to expand...
Click to collapse
This no longer required.

kquote03 said:
sudo waydroid container start
and in a separate terminal run waydroid session start
Click to expand...
Click to collapse
These steps are no longer needed after reboot, start waydroid from launcher.

kquote03 said:
Ubuntu Touch (ubports) for the Galaxy A5/7 2017​View attachment 5615835​
Code:
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!
Source code:​Device tree: https://github.com/Exynos7880-Linux/samsung-exynos7880
Kernel: https://github.com/Exynos7880-Linux/android_kernel_samsung_universal7880
Ubports project management: https://github.com/Halium/projectmanagement/issues/294
Installation:​Just flash the ZIP through TWRP, then flash fix.zip.
Spoiler: Old method (for V1)
VERY IMPORTANT: Install the riseTreble re-partition script, this will modify your phone's partition table to include a Vendor partition. Please read the entire post before doing anything. Make sure that you're able to mount Vendor in TWRP before proceeding, if you can't then wipe the partitions listed in the riseTreble post.
After riseTreble re-partition script is done (you will know it's done when you can mount Vendor partition in TWRP), flash the zip found in the replies.
TWRP may wrongly warn that an OS is not installed, this is normal
What doesn't work:​
Camera (Mysteriously works in Waydroid) The user cannot give permission to the camera fixed in V3
Random reboots on sleep (workaround: keep an app active using UT Tweak Tool) FIXED in V2
You may have to enter the SSID of WiFi networks manually. Also, disconnecting may no longer give the option to reconnect, a reboot fixes that Fixed in V3
MTP Fixed in V3
Untested:​
NFC
Miracast
A7, drivers have been fixed but no real world testing has been done
???
What works:​
Essentials (display, charging, volume keys, etc)
Bluetooth
Fingerprint
Wi-Fi
Calling/Data
SD card slot
Waydroid:​Waydroid is a compatibility layer for Android on Linux. To install it, open up a terminal and run the following commands
sudo -s Run all following commands as root
(optional) mount -o rw,remount / This will mount your root partition as RW to use apt, this ROM however has an RW root partition by default (.writable_image) so this command is not needed
apt update Update list of available packages
apt install waydroid Install the waydroid package
waydroid init Initialize waydroid (this will also pull the android image, if for some reason the install is interrupted, run waydroid upgrade manually to get the android image)
Reboot the device
sudo waydroid container start
and in a separate terminal run waydroid session start
Dualbooting:​You can dualboot between Android and Ubuntu Touch by backing up your boot.img BEFORE installing ubports. You can switch between your stock boot.img or halium-boot.img or flash one to the Boot partition and the other to the Recovery partition (this will sacrifice TWRP, beware) and booting to recovery to boot to the other OS.
Debugging:​
Spoiler: Using SSH and logcat
How to use SSH:​SSH is enabled by default and uses password authentication, make sure your user account has a password. On any other PC just type ssh [email protected]_PHONES_IP_ADDRESS (obviosuly replace it with an actual IP address)
How to access logcat:​Accessing the underlying Android system using ADB can help in debugging, to use it, enter in any shell (or better yet, SSH) as root:
Bash:
sudo -s #This is just to make sure you're root
unset LD_LIBRARY_PATH
unset LD_PRELOAD
lxc-attach -n android -e
logcat
USB Debugging:​If you can't connect to WiFi or are experiencing any other network problem, please follow these instructions to access SSH and help us debug the problem https://docs.ubports.com/en/latest/porting/build_and_boot/Boot_debug.html
Credits:​Ayman_sp24 - Main developer (github profile)
Simon1511 - repartition script, even though we are no longer using it in V2 and onwards, it really helped us a lot initially. massive thanks
kQuote03 - Testing
ubports and halium developers
..and everyone else who helped in any capacity for exynos7880 development
Screenshots:​View attachment 5616027View attachment 5616029View attachment 5616033View attachment 5616035
View attachment 5616039View attachment 5616041View attachment 5616043
Click to expand...
Click to collapse
both versions are for A7 and none for A5. Too bad, the rom seems to be really good.

rafaellancas said:
both versions are for A7 and none for A5. Too bad, the rom seems to be really good.
Click to expand...
Click to collapse
They have extremely similar boards so it does work on the A5. I have tested it on my own.

Cdd100 said:
They have extremely similar boards so it does work on the A5. I have tested it on my own.
Click to expand...
Click to collapse
Perhaps mine is a Brazillian variant then (the model is SM-A520F/DS), because none of my hardware keys work and the model in settings is the one for A7. Too bad, because I just loved the ROM.

@kquote03 sir, I installed your ROM, but it's very old. Do you have an updated one?
Also, did you send your port back to Ubuntu Touch? I know it's a silly question, but I asked for help in the UBPorts forum, convinced they could support, and they told me they can't.
Thanks for any help, have a nice day =)
P.S.: Here is my post on UBPorts https://forums.ubports.com/topic/8660/ubports-on-a-sm-a520f
P.P.S.: By the way, the ROM works as intended, just some minor issues

No one?

chiaravalle said:
@kquote03 sir, I installed your ROM, but it's very old. Do you have an updated one?
Also, did you send your port back to Ubuntu Touch? I know it's a silly question, but I asked for help in the UBPorts forum, convinced they could support, and they told me they can't.
Thanks for any help, have a nice day =)
P.S.: Here is my post on UBPorts https://forums.ubports.com/topic/8660/ubports-on-a-sm-a520f
P.P.S.: By the way, the ROM works as intended, just some minor issues
Click to expand...
Click to collapse
Hello, i already updated it to focal 20.04
A7 https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20230205.zip
A5 https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20230205.zip

Wow, you're GREAT!!!
Does "no recovery" mean I can't use TWRP to install?

Ayman_sp24 said:
Hello, i already updated it to focal 20.04
A7 https://github.com/Exynos7880-Linux...bports-a7y17lte-devel-norecovery-20230205.zip
A5 https://github.com/Exynos7880-Linux...bports-a5y17lte-devel-norecovery-20230205.zip
Click to expand...
Click to collapse
Sorry, I forgot to click on reply when replying

[GUIDE] VoLTE & VoWIFI for Xiaomi 10T/10T Pro 5G custom roms

Hi all,
I would like to write a short instruction about getting VoLTE and VoWIFI to work on a Xiaomi device. I'm using a Xiaomi 10T 5G with Evolution X, but it has mainly to do with the modem in your device, so it might work for other devices and ROMs as well. If you use a different ROM, the way DIAG mode is enabled might be different for you.
Code:
/*
* I am not responsible for bricked devices or any damage you made
* to your device. You have been warned
* Your are making changes to your modem's firmware. Make sure you
* have a backup!
*/
You have to enable VoLTE and VoWIFI in your device settings.
To check if it works:
- dial *#*#4636#*#*
- chose phone information
- chose in the menu IMS-servicestatus
You will have VoLTE and VoWIFI if it says registered and availabe.
If not, you can continue with the instructions below:
You will need a few things for this, like:
- Qualcomm USB Drivers
- QPST
- Root or another way to enable diag mode
- ADB
- Xiaomi firmware zip file
You can find many tutorials on XDA about these things, so I'm not going into detail about how to set this all up.
If you have the above installed and working:
Open a command prompt
Code:
adb shell
Code:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
After you install QPST search in winodws for PDC (a yelllow and white icon) and open it.
Select 'Qualcomm HS-USB WWAN adapter'. (if this doesn't work, check if you've installed the Qualcomm USB Drivers correctly)
You'll now see a list of all modem configuration files. Check if your carrier is in the list. If so, right click on it, select SUB0 and SUB1, and click 'activate'. Check if VoLTE and VoWIFI works, if yes, reboot and check again.
If you do not see your carrier in the list, download the firmware for your device.
Extract the zip file
Navigate to \firmware-update\NON-HLOS.bin and extract this file
Navigate to \firmware-update\NON-HLOS\image\modem_pr\mcfg\configs\mcfg_sw\generic\ and search for the .mbn file for your carrier. Mine was in fw_apollo_miui_APOLLOGlobal_V14.0.1.0.SJDMIXM_2e94304468_12.0\firmware-update\NON-HLOS\image\modem_pr\mcfg\configs\mcfg_sw\generic\AF\Vodafone\Commercial\EG
Go back to PDC and chose 'load'
Select the .mbn file you've found above
PDC will reload the list and you'll now see the profile for your carrier.
Right click on it, select SUB0 and SUB1, and click 'activate'. Check if VoLTE and VoWIFI works, if yes, reboot and check again.
Now go back to adb and write
Code:
setprop sys.usb.config mtp,adb
to go back to default usb settings.
This should do the trick. You'll now have VoLTE and VoWIFI working.
It took me days to come down to this, with a lot of Google-Fu and very helpfull XDA topics. So I hope it might help you as well.
This has been tested for Vodafone Egypt, mbn for Vodafone EG has been attached (extracted from latest global firmware V14.0.1.0.SJDMIXM), just load and activate.
reference: https://forum.xda-developers.com/t/guide-volte-vowifi-xiaomi-phone.4573331/