[SM-G355M][LineageOS 14.1] No mobile data, (how to debug?) (disabled during comp?) - Samsung Galaxy Core 2 Questions & Answers

Hi All!
I have a Galaxy Core 2 running LineageOS 14.1 (Nougat 7.1.2). It works really well, but ... I can't get the mobile data working.
I downloaded the ROM from "Sandroid Team" (XDA doesn't allow me to post the URL)
The "author" (Ih24n) seems to be unreachable (COVID-19 problems?).
I found that /system/build.prop mentions:
Code:
#
# ADDITIONAL_BUILD_PROPERTIES
#
...
ro.com.android.mobiledata=false
This make me think the mobile data support was disabled at compile time. Is this correct?
What can I test in my phone? I can use adb shell and I have some Linux knowledge.
I took a look to other Nougat ROMs from Ih24n and all has the same value in adb shell.
Note that when I say "I can't make it work" I mean that I don't even see the option to enable it in the settings menu. I already configured the APN.
If I can solve it I'll be forced to try Android 6.
Does anybody has experience with other ROMs from Ih24n?

Related

[PATCH 3.1][27-06-11] 100% Working 3g huawei compatible USB dongle

*I'm not updating it, but many users find this useful, so thread is kept as is for now*
Not sure if anyone got so far, to getting the honeycomb showing connection and selectable APN in settings?
anyways,
from my port of honeycomb to folio100, and now experiments with a500.. i got huawei dongle's running using the builtin functions.
you will need to have root'd your device. and this might break a system-update, if any of my files are updated during next OTA..
but back to the working 3G.
Working 3G USB dongles:
Do note, your modem version can be seen on its white label written with very small text.
some modems require zerocd (linuxtool) or commands executed in windows to disable the mass storage part of it. (search google for the commands)
* ZTE MF 639 (might need roaming enabled to get data working)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173
* Huawei E1550
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1820
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Download View attachment 3g-usb-stock1.zip for 3.0.1 stock release Acer_A500_1.141.01_EMEA_GEN3: (vermagic=2.6.36.3 SMP preempt mod_unload ARMv7)
Download View attachment 3g-acer31stock-usb.zip for 3.1 stock release Acer_A500_3.019.01_COM_GEN1 (vermagic=2.6.36.3-00005-g5dff38c SMP preempt mod_unload ARMv7)
HOWTO:
- first: Backup your /system/build.prop on the tablet , just copy the file to a safe place, as its important if you wish to do a online update later on.
- updated zip, so you can now install the zip as an "update" using ClockWorkMod/CWM if you got this installed.
- download the "system.zip" attached to this post.
- unpack all files to a temporary folder ie. C:\myfiles
- assuming you got adb running
* push files to your tablet with;
adb shell mkdir /data/local/temp
adb push C:\myfiles\system /data/local/temp/
* next run
adb shell
* then run all commands below in the shell
su -
mount -orw,remount /system (i forgot this line, ITS IMPORTANT)
cp -a /data/local/temp/* /system/
chmod 4755 /system/bin/pppd
chmod 4755 /system/bin/rild
chmod 755 /system/bin/rild.run
chmod -R 755 /system/etc/ppp
If you done these steps correctly, and you reboot.
you will now have a working 3G option in Settings -> wireless networks
so you can configure your APN now and connect to your 3G network.
and you got it all automated with honeycomb 3g! no terminal needed to start 3G!
HINTS
- Other reports are to remember to "Disable PIN" on the card.. I have no personal experience on this part, but check up on it, if its not working perfectly, or no data, but network is ok.
- I got reports back about enabling roaming to make it work, and also remember the story from Folio100 with 3G dongles..
so if you cannot get data connection at all, try to enable roaming and see if APN does not appear which matches your isp. maybe read you ISP website to confirm it.
- If you happen to remove the dongle, there is a solution (using as example gscript) to restart the ril daemon.
in a shell you can restart the ril-daemon if you reinsert the 3g usb dongle.
do it like this in the shell:
su -
stop ril-daemon
start ril-daemon
HOWTO FOR RESET'ing ,massstorage on Huawei modems.
tasmak said:
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
You need also put sim card from modem to any phone and disable pin checking.
Click to expand...
Click to collapse
Remember to press "thanks" if you find it useful
you forgot to say to remount the system to rw....
thor2002ro said:
you forgot to say to remount the system to rw....
Click to expand...
Click to collapse
i believe that line is even highlighted and commented as forgotten previously, so its there for sure..
you cannot miss it
or do you mean some other /system mount?
Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?
JackMetal said:
Looking forward to testing this. Mine is a Verizon Novatel Wireless, do you think this will work with it?
Click to expand...
Click to collapse
it would probably work, if you got the huawei dongles..
the major is if you need different kernel modules.. those are in the other thread if needed, i included those without -gxXXXX version info.. as thats the ones for the latest EU model update and works here.
Thanks Dexter. One question. Can these files be pushed using terminal emulator instead?
Sent from my A500 using Tapatalk
Yes,
this can of course be done in a terminal, if needed.
just forget the part with "adb",
but all the commands should be executed, and the files copied to a sdcard temporily and copy from that location to the /system
Dexter thanks. What Huawei modem do you recommend?
Sent from my A500 using Tapatalk
manfly9884 said:
Dexter thanks. What Huawei modem do you recommend?
Click to expand...
Click to collapse
i use a E1752 model myself, which i have disabled storage on, before using it on my tablets...
Thanks
Sent from my A500 using Tapatalk
this wil break the OTA ... because of the build.prop modifications...
thor2002ro said:
this wil break the OTA ... because of the build.prop modifications...
Click to expand...
Click to collapse
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..
Dexter_nlb said:
Correct, that is also mentioned in post #1.
custom build.prop can be made if the lines at the bottom are copied to your own version you got with a simple one-liner in a shell.
echo "picasso.3g=true
rild.libpath=/system/lib/libhuawei-ril.so
rild.libargs=-d /dev/ttyUSB2
ro.pad.features.modem=true " >>/system/build.prop
so it works on any new build.prop change..
Click to expand...
Click to collapse
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...
thor2002ro said:
got an idea.... make two scripts for applying and removing....
so we can maintain the OTA capability...
Click to expand...
Click to collapse
ill figure something out.. maybe an actual patch can be made?
i do know how to make the different update.zip's ... just got A500, so not sure what is possible and not, on this semi-blocked tablet..
but also know motorola mobiles, i have had my part of blocked devices, and do workarounds to make something work.
1 update.zip to install? and another to remove?
we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...
thor2002ro said:
we dont have custom recovery working.... so update zip wont work... scripts or apk are the only choices i see...
Click to expand...
Click to collapse
no no, i dont talk CWM.. i use the builtin tegra recovery for the additional functions.. the recovery is very close to CWM, but uses the old htc way, and do have specific write command for writing images..
ill check it out soon.. a500 is still new to me, although tegra is not...
I know im probably not doing something right, i followed the steps, and when i tap mobile networks it force closes?
Good news. Thanks
manfly9884 said:
Thanks
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
wounderful work!
good point!
Any reason this wouldn't work on the asus transformer?

[unofficial][linux3.4][native][tarchive][multirom]ArchLinuxARM release for N7 2013

This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
looks interesting will give it a crack and see how it goes
thanks for the work. it boots impressingly fast.
castrwilliam said:
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Click to expand...
Click to collapse
if I activate the onboard keyboard ist shows at the bottom of the login screen. login works without password. when beeing logged in the keyboard is gone. I can see the keyboard symbol on the left besinde the speaker symbol but tapping on it doesn't trigger anything. also changing any options in the control center -> onboard settings have no effects. logging in without keyboard activated and then control center -> onboard settings has no effects either.
I cannot "adb shell" due to lack of permissions
Code:
# adb devices
List of devices attached
???????????? no permissions
and I'm not owning a bluetooth keyboard. so right now I can only play minesweeper - oh wait, it's not installed...
is there any way to rotate the screen as its really annoying having it in portrait all the time
Toby0897 said:
is there any way to rotate the screen as its really annoying having it in portrait all the time
Click to expand...
Click to collapse
Yeah it is in the monitor options but it's worthless since Xorg crashes when changing the rotation
Great stuff!
I would remove the KDE plasma etc packages as that desktop seemed to unusable. (Due to broken hw acceleration?).
what's next?
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
hugomc92 said:
Hi, I'm having a big trouble...
While I'm trying to do the installation (by adb shell or terminal emulator, both of them) and I enter the command posted in the OP it says:
127|[email protected]:/ # tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
tmp-mksh: tar: not found
What can I do to resolve this error? I really would like to install it on my Nexus 7
Thanks in advance!
Click to expand...
Click to collapse
You will need to install busybox for tar to work
daringblaze said:
You will need to install busybox for tar to work
Click to expand...
Click to collapse
Thank you very much!! That make tar to work!!
Gonna try archLinux ASAP!!
Thanks!
updates
Hi, great stuff!
After installing it, I tried to update arch (
Code:
sudo pacman -Syu
) but this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
computer-whisperer said:
this resulted in a blank screen upon boot. I assume that this is due to updated packages overwriting parts of the OS that were installed manually, but I don't know what or where. Would you have any ideas of what packages would be responsible for this, so that I know not to upgrade them?
Thanks!
Click to expand...
Click to collapse
Make sure you ignore xorg and mesa stuff. Add
Code:
IgnorePkg = glu mesa mesa-dri mesa-libgl xorg-server-common xorg-server-devel xorg-fonts-misc xproto libdrm
IgnoreGroup = xorg
to /etc/pacman.conf.
The list probably contains some extra entries, but works for me
It took xda 2 years, but they finally did it.
In all seriousness, props to you. I've been waiting for this for along time.
castrwilliam said:
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/......
Click to expand...
Click to collapse
Hi castrwilliam, would you mind sharing what step you went through to create arch_flo_20141210_multirom.tar.gz ?
Great work guys! I was looking for this for a really long time and i am writing this on my n7 with linux but i have a few questions:
1. is it possible to overclock(and how) because my n7 runs on 1.89ghz and 477mhz gpu in android with elementalx kernel and it would be nice to have some more power
2. can the screen be rotated so the hardware buttons are on top (i saw a post saying it chrashes but i cant even find the setting xD) because it would be alot easier to use the OTG cable
And thank you guys for making this happen, i love linux on the note 10.1 and im so glad to have this run it too(would be maaad if it can be overclocked )
Thank you for this wonderful package!
I recently updated all packages ) and iam trying to fix the issue without reinstall (challenge accepted)
It seems that the xorg-server 1.17 is the problem. I compiled. Freedreno and the freedreno mesa 10.3 and libdrn packages without success. The xserver is segfaulting when it loads libexa.so.
Now i try to downgrade to 1.16 . ive read that the xf86-video-freedreno-git package is not working with flo. Is that correct? Did youbuild this packages with modificationa?
I believe this is why i love arch. Its like lego for nerds or something
castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
What's NOT working
Hello, is there some instruction howto run (native) arch on nexus 4? I see only for n7, n10...
castrwilliam said:
This is not an Android project so I don't feel that posting it in the Android Development forum would be appropriate.
ArchLinuxARM for the flo (2013 Nexus 7) - Native Boot with MultiROM
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the deb (LTE) tablet, though mobile data is highly unlikely to work.
Big thanks to crondog at github for the initial porting work. https://github.com/crondog/arch-flo
Working:
3D Acceleration (OpenGL ES 3.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_flo_20141210_multirom.tar.gz is in the root of your internal storage (/data/media/0).
Code:
su
tar -C /data/media/0/multirom/roms -xpzvf /data/media/0/arch_flo_20141210_multirom.tar.gz
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Downloads
MultiROM hierarchy tarchive: https://drive.google.com/file/d/0B4WUjKii92l2X1F1LVhsaG5DbUE/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_flo
Also available for:
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
HP TouchPad: http://forum.xda-developers.com/hp-touchpad/other/unofficial-archlinuxarm-release-hp-t2969310
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Click to expand...
Click to collapse
Having my favourite distro on my pocket is very exciting so thank you very much...
I have to carry only a development lamp server so using a pacman tip I revert to a base, base-devel system removing everything about xorg and DE.
Now I connect using ssh but I've noticed that the tablet screen is simply blank: no tty, no text console.
There is a way to have a text only console at boot to make a login (may be using an usb keyboard) when device is not connected?
Hello, I have some trouble when I boot.
config: rastapop 5.1.1 (AOSP based) + last multirom v32A + Kernel w/ kexec-hardboot patch (Stock 5.1.1)
Installing archlinux correctly from the terminal emulator. Load it --> black screen (about 6seconds) --> Google Logo forever
Someone know what I can do for make it work ?
Cool I will give it a try.

WiFi monitor mode

OK, I don't think this thread will get any attention, but I want to document it anyway. All this should work on other devices with qcom WiFi drivers.
TL;DR:
Grab iwpriv binary somewhere (i've got my here: https://github.com/kriswebdev/android_wireless_tools/tree/master/bin)
adb push iwpriv /data/local/tmp/
adb shell su -c chmod +x /data/local/tmp/iwpriv
Code:
#!/system/bin/sh
ip link set wlan0 down
sleep 1
echo 4 > /sys/module/wlan/parameters/con_mode
sleep 2
ip link set wlan0 up
/data/local/tmp/iwpriv wlan0 monitor 1
/data/local/tmp/iwpriv wlan0 MonitorModeConf 9 40 1 111 0
And enjoy your airodump output
NO PACKET INJECTION! (stubbed out in driver, removed previously?)
If you don't receive any packets, issue "/data/local/tmp/iwpriv wlan0 monitor 1" again.
How does this all work?
Some time ago I discovered these strings in wlan_hal_msg.h: (they appeared in google):
Code:
...
/* Monitor Mode */
WLAN_HAL_ENABLE_MONITOR_MODE_REQ = 302,
WLAN_HAL_ENABLE_MONITOR_MODE_RSP = 303,
WLAN_HAL_DISABLE_MONITOR_MODE_REQ = 304,
WLAN_HAL_DISABLE_MONITOR_MODE_RSP = 305,
...
Then I unscrambled some indirections:
WLAN_HAL_ENABLE_MONITOR_MODE_REQ to WDI_MON_START_REQ in WDI_2_HAL_REQ_TYPE
WDI_MON_START_REQ sent in WDI_ProcessMonStartReq <— actual message sents here!
Called from "Request Processing Array" in function WDI_MonStartReq
Wrapped in WDA_ProcessMonStartReq, which is called in WDA_McProcessMsg by message WDA_MON_START_REQ
Which message is posted by wlan_hdd_mon_postMsg if (MON_MODE_START == pMonCtx->state)
Which is called in __iw_setint_getnone with sub_cmd = WE_SET_MONITOR_STATE
Which is set by iw_priv cmd "monitor"
And then figured out that driver works in different modes:
(vos_types.h)
Code:
/// Concurrency role. These are generic IDs that identify the various roles
/// in the software system.
typedef enum
{ /*ON linux maintain 1-1 corespondence with device_mode_t in hdd*/
VOS_STA_MODE=0,
VOS_STA_SAP_MODE=1, //to support softAp mode . This is misleading. It means AP MODE only.
//The constant name has historical reason
VOS_P2P_CLIENT_MODE,
VOS_P2P_GO_MODE,
VOS_MONITOR_MODE,
VOS_FTM_MODE = 5,
VOS_IBSS_MODE,
VOS_P2P_DEVICE,
VOS_MAX_NO_OF_MODE
} tVOS_CON_MODE;
Mode can be changed by "con_mode" module parameter.
(idk why they reinvented the wheel and not used the default "iw dev wlan0 set mode monitor")
Combined all this and... got a kernel panic. You may get it too. Main reasons are:
- You have not disabled WiFi before changing the mode
- The sleep time after disabling interface is short
- Driver is old. Yes, you can get crashes on some kernels. If you are, flash AGNi.
After successful switching you'll get a working monitor (check this with tcpdump -i wlan0), but with ethernet packets instead of radiotap, so airodump will not work. Luckily, this giant crappy driver can work with radiotap, but you need to configure it. This is done by another iwpriv call:
MonitorModeConf: <channel> <bandwidth> <crccheck> <filter> <conversion_required>
Filter: 3 decimal numbers
least to most: management packets, control packets, data packets
Conversion: 1 - ARPHRD_ETHER (802.3 packets), 0 - ARPHRD_IEEE80211_RADIOTAP (802.11 packets)
(again don't know why they implemented these calls instead of default ioctl's for channel switch, etc. This makes airodump unable to switch channels)
As a result you may get something like on a screenshot
Happy sniffing!
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Crayvolt said:
Who said it will not be an interesting , I my self appreciated your effort to bring this up. Kudos to you friend.
Click to expand...
Click to collapse
Thanks. I wanted to say that kenzo development is almost dead, we've lost official LOS and keep losing devs.... So it's most likely we'll not see working packet injection (cuz devs who know driver's internals better than me are left), and, possibly, a wrapper library implementing the default ioctl's (like channel switch) used in most programs.
i understand, hopefully we can have new devs. who will continue
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
you dont have permission to capture on that device sokect operation not permitted
aldhi said:
This is a perfect news. At least if this device became obsolete, it should still be useful to be a portable linux pen test device, if possible. Anyway, awesome job mate. Very much appreciated
Sent from my Note 3 using XDA Labs
Click to expand...
Click to collapse
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
cerg2010cerg2010 said:
Thank you. I forgot to say that monitor mode requiers support from firmware (there's some code in driver that checks for it). Kenzo guys are lucky because we have it enabled . There's also sta+monitor mode (so you can have working wifi connection while sniffing), but it also requiers support from firmware and kenzo's fw compiled without it. I forgot how to enable it, but i think you need to issue "iwpriv wlan0 monitor 1" in default con_mode and check dmesg - there will be a string that says it's not supported (if it is not).
And if someone is interested, our wireless chip is wcn3680b, simmilar one (or same, idk) can be found in nexus 4 (mako)
Click to expand...
Click to collapse
Can you ziping code and flashable instal on twrp?
Khimin said:
Can you ziping code and flashable instal on twrp?
Click to expand...
Click to collapse
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
cerg2010cerg2010 said:
There's nothing to install except iwpriv binary... But OK, I'll try to create a magisk module with enable/disable scripts.
Click to expand...
Click to collapse
Thx, im waiting
Khimin said:
Thx, im waiting
Click to expand...
Click to collapse
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Thx dude
thank you you are awsome +thumbsup
---------- Post added at 08:49 AM ---------- Previous post was at 08:03 AM ----------
filter expresion syntax error using command tcpdump -i wlan0
help please
---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------
can you help me?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
Is it safe to flash with magisk in note 5 pro ?
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Perinban Parameshwaran said:
@cerg2010 Tried to flash with magisk in note 5 pro. System apps are not working after disabling the module from magisk it returned to normal. Any solution for this ?
Click to expand...
Click to collapse
Please understand that I don't have any "note 5 pro". You can send me logcat and I can try to identify the problem or ask your ROM developer to take a look (if it's not MIUI lol). Anyway, that's just scripts, so you can copy them to /data/local/tmp or /system/bin manually.
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Op_Flashpoint said:
Lol I'm a n00b what does this do? Is this a packet sniffer or something?
Click to expand...
Click to collapse
Sort of. It makes your sniffer to work - you will be able to capture raw WiFi packets from your device without any dongles.
plis whats rom u use ¿
cerg2010cerg2010 said:
Ok, I made it quickly!
Source: https://github.com/cerg2010cerg2010/qcmon
There's 2 scripts, run them from shell:
monen - enables monitor mode (you can specify configuration in the parameters, see system/xbin/monen)
mondis - disables monitor mode. You can use your wifi connection again.
Click to expand...
Click to collapse
thank you man, monitor mode now working on my poco F1, using its module magisk + aircrack-ng

Forcing VoLTE support on Mi-A2 Pie [root] when carrier supports

Hello, Just a small hack that allows me to use the VoLTE that my provider points out is "only available on handsets purchased directly from them" (SFR in France). This got me thinking ==> If VoLTE works on their handsets and not mine then :
a) The carrier infrastructure supports VoLTE
b) The sim cards must be provisioned correctly
c) The difference would therefore be in the telephone configuration ==> I'm thinking build.prop config in their "special firmware"​
So looking through various forums - I came across the following:
https://forums.oneplus.com/threads/root-working-volte-on-stock-oxygen-3-1-0.480128/, https://forum.xda-developers.com/apps/magisk/module-v4-volte-enabler-t3649613 and https://source.android.com/devices/tech/config/carrier (to help understand what IMS is all about)
Here's what I added to the end of my build.prop [you will need root for this]:
Code:
#VoLTE - force the IMS into VoLTE provisioned mode on.
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
If you don't want to do that directly in the build.prop you can do this directly from a debug shell
Code:
adb shell
$ su
# setprop persist.dbg.ims_volte_enable 1
# setprop persist.dbg.volte_avail_ovr 1
# reboot
Please note that this did indeed allow me to make/receive calls and use 4G at the same time.
I also see "HD 4G" logo appear to the left of my signal bars.
When I look at my phone config (dial *#*#4636#*#*) I see VoLTE as provisioned.
I think that these lines force the phone to use VoLTE - the risk is that this might break your 4G - you have been warned. I don't guarantee that this works for you.
Can an administrator place this in the https://forum.xda-developers.com/mi-a2/how-to forum please ?
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
if yuou don't have root you can use *#*#86583#*#* . tested working on sfr too.
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
duxxyuk said:
Tried that but that didn't work... This root build.prop stuff did... I have also added keys for video calling and VoWiFi but until I see those working I'm not keen to publish...
Click to expand...
Click to collapse
VoWifi how? Whats the code?
I've got these lines on the back of my build.prop but it doesn't appear to work for me:
Code:
#WiFi calling
persist.data.iwlan.enable=true
persist.dbg.wfc_avail_ovr=1
rober788 said:
I made this change with temporary root when i activated api for gcam, put this lines with temporary root and get OTA too
Click to expand...
Click to collapse
How does a temporary root work? I can't find anything with Google.
Magisk module VoEnableer maybe the best chois.
Thanks for sharing.. it also works on mi a2 lite
Thanks, It works

N8000 RADIO Baseband firmware collection - Support N8000 - Share your baseband!

I'm starting a N8000 RADIO collection because we're having discrepancies where WiFi works on N8000 for certain ROMs for some people, but not others.
N8000 Baseband Google Drive folder
Here is a current list of Basebands in the Google Drive folder
VERSION Original Stock ROM Comment
N8000XXUDNH1 (South Africa Vodafone Android 4.4 ROM) WiFi works on @TheMorpheus Android 5.0.2 but no @lirokoa ROM's (or derivatives)
Share your baseband and help us all develop better N8000 ROMs
You will find your baseband version in Settings > About > Baseband.
If you have a N8000 with a baseband not listed above, please upload it to https://uploadfiles.io/ or a similar free filesharing site and I'll try add it to the Google Drive (so it'll be available permanently) in a timely manner.
How to dump your N8000's Baseband
You need to run a command as root on your device. I find the quickest, most convenient way is with `adb shell` and `adb pull ...`. But you could do it in a root terminal on the device and upload it from the device also.
Here are detailed instructions for doing it with ADB shell and pull (replace XXXXXXXXX with your baseband version)
1. Enable Dev Options: Go to settings > About > Software info > Tap build number 9x until Developer options is enabled.
2. Enable ADB as Root: In Settings > Developer options: Enable ADB and root over ADB
3. cd /tmp/
4. adb shell
su
dd if=/dev/block/platform/dw_mmc/by-name/RADIO of=/data/XXXXXXXXX.radio
exit
5. adb pull /data/XXXXXXXXX.radio
6. Upload XXXXXXXXX.radio for free at https://uploadfiles.io/
7. Post here
Share the link here with the basic info as per this example mentioning the latest/best ROM (in your opinion) that your device works with:
XXXXXXXXX (?Country? ?Network? Android ? ROM) WiFi works on Android ?version? ?romname? ##.# by @foo
Thank you for contributing to the N8000 community and facilitating new ROM development.
Details of WiFi issues on @lirokoa ROM's (and derivatives)
https://forum.xda-developers.com/ga...ent/rom-lineageos-14-1-nougat-t3884079/page40
In a nutshell: Not working on WPA2-PSK(AES) networks.
Although some N8000's work fine. So I'm hoping it's just a matter of swapping the Baseband.
Reserved 2
Google Drive folder is empty (?)

Categories

Resources