yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
upgraded the image to userdebug to enable more functions and privileges. compiled for the new update lineage os20240119nightly-star2lte- modified the .config file to show the system that no modifications have been done so that the boot error message goes away. please note if you use usb gadget tool to check the procconfig.z file it will report as standard it will show no hid is enabled etc or no docker modifications enabled. because it is presented with the fake .config file. you can flash the dmverity disable force encrypt disable first or if you don't you will have to install the nethunter image via twerp and then install it again with magisk via the modules tab. so encryption is preserved. up to you. there is a full image without nethunter and an overlay for nethunter to go over the stock lineage kernel or the one i have modified. up to you. hid is working, proxmark is working, docker is working. rtl88xxxau wifi injection and monitor is working. there is no native firmware from nexmon for this chip the or blue tooth firmware. i had to copy the apps over to the system/xbin folder like airmon-ng yet suggest using a alfa network rtl88 wifi dongle.to use in the termux comand or with the native aps or just use liiux kali terminal. i incressased the power to usb devics so they can all be powed of thephone battery. also via usb hub is working.wifite etc via command line is working. proxmark i used the termux compiler and it worked on port ttyACM0. you have to chmod -x 777 the fodlrder ttyACM0 or 1 whatever each time you plug in the usb proxmark. or termux cant read it. hackrf is working sdr is working. for the proxmark3 the rdv2 was tested. the aps like rfid tools detett it nd comunicate with it but odnt get a reponce as i haeve the rv2 versio. so dont know about rdv4 ersion. yet assume the apps would work. the linux headers are included also include.zip.in case you need to compile any modules etc that are not included. . if you need again you can get from the github repo mylesgoose lineage-20update source code
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
to enable HID function for rubber ducky etc you type setprop sys.usb.config hid in the android root terminal,
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
FINALLY!!! someone made nethunter to work on s9plus! good job man.

I tried to follow your instructions but somehow nethunter doesn't recognise any external usb wifi adapters. I tried with alpha and tl-wn722n but no luck....

I don't know if i missed something on the process but everything seems to work properly.

The steps i followed:

Installed lineage rom (the one attached on your last comment) according to the lineage wiki.

reboot and installed magisk

reboot on the system and finished the magisk installation.

installed twrp

reboot on recovery (now twrp instead of lineage recovery)

install nethunter and nethunter-hid

reboot the system. start nethunter (everything runs without errors) and update nethunter terminal and nethunter itself.

Attached usb wifi but no interface shown apart form the inbuild wlan0.

Any suggestions?
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
I am happy you tried it out. Pretty cool. I have an alpha card here I will test now procedure. Two questions did you put the full lineage ROM I made the user debug one or the official one and the the nethunter zip over that? Secondly how are you connecting the USB cable to the device? Is it plugged directly into it with c cable or USB adapter? Like OTG adapter or power hub? What model is the alpha board is it rtl88xxau? How are you assessing if its plugged in and showing on nethunter? Did you type airmon-ng start wlan1 or something?
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
I plugged in my alpha card and first I used USB c direct to device and it was not detected I restarted phone and plugged the USB c cable in a different way up the other way. And this time it was detected. I then tried again with a USB hub and also worked. As attached. There is a command you can type and it lists all the USB devices attached. "For example in terminal type

lsusb and it will output this

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 002: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub" or via hub

┌──(root㉿kali)-[/]

└─# lsusb

Bus 002 Device 003: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer

Bus 002 Device 002: ID 2109:0822 VIA Labs, Inc. USB3.1 Hub

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 001 Device 003: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter

Bus 001 Device 002: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

┌──(root㉿kali)-[/]

└─#
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
hey man! thnx for the response.

So everything i flashed was attached to your latest comment. first i flashed lineage-20.0-20240126-nightly-star2lte-signed.zip following the official guide and then nethunter-20240128_102814-star2lte-los-thirteen-kalifs-full.zip.

for the cable i used an otg usb c cable. No powerhub or y-cable. I thought it might be a power problem but lsusb recognizes my usb card as atheros so i think i m ok.

I tested 2 card tl-wn722n v1.1 and an alpha awus036nha. Both tested and working fine on my kali laptop.

i tried the custom command "start wlan1 in monitor mode" but i get an error "can not find device wlan1"

airmon-ng start wlan1 says that it only found phy0 with no interface assigned.

ifconfig returns 3 interfaces: wlan0, lo and dummy0.
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
Is your drive encrypted your data partition? How did you have the nethunter apps etc installed via twrp without flashing again in magisk? Did you do dmverity force encryption zip? Because this is what I had to do. Flash magisk over stock lineage ROM. The zip file. With recovery. Reboot and have magisk setup again by patching boot via magisk app once booted. Download twrp apk app give it permission via magisk and flash that twrp recovery partition. Reboot to recovery. Flash the nethunter zip. Because I kept my data partition encryption it flashed only the system and vendor partition and boot with the nethunter zip via twrp with all partitions mounted. I then rebooted to system and used magisk to install the nethunter zip again as a module and also the hid. Zip as you also said you flashed that. So we should have identical systems now. And mine is working with any USB device I plug in. Likely I think your issue is method of plugging into device for example my proxmark would only work with a certain cable and adapter. This WiFi USB c cable on alpha only worked plugged in one way up. They are supposed to be multi directional yet I have not found that to be the case. All the time. . Like otg cable. Can you try USB c to USB c cable? Sounds to me like you installed everything correctly if The nethunter app showed up and chroot etc. Also that mind the gaps google apps won't install with twrp recovery have to install it with normal lineage recovery FYI.
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
If you type airmon-ng start wlan1 it says found phy0 do you want to assign interface and you type n then enter. What does it say? It seems to me your WiFi device has a different chipset to my alpha one your is this

Chipset	Atheros AR9271

And mine is this Realtek™ RTL8812AU

so we need to check that that driver for your one is installed.
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
So quick update: i tried plugging in a 3rd usb card ralink rt5370 with the same cable and works. switched to monitor mode using the custom command wlan1 and then started wifite. Scan worked. Injection worked. captured successfully handshake of my wifi network and cracked it using a custom wordlist containing the password.

I guess it is a matter of cable. I'm curious though. I will test it again in a few hours.
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
lsusb show Atheros AR9271. I really believe that it is a matter of cable. Maybe i need an external power source for this type of chipset.
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
Is it one of these

CONFIG_WLAN=y

CONFIG_WLAN_VENDOR_ADMTEK=y

# CONFIG_ADM8211 is not set

CONFIG_ATH_COMMON=y

CONFIG_WLAN_VENDOR_ATH=y

# CONFIG_ATH_DEBUG is not set

CONFIG_ATH5K=y

# CONFIG_ATH5K_DEBUG is not set

# CONFIG_ATH5K_TRACER is not set

CONFIG_ATH5K_PCI=y

CONFIG_ATH9K_HW=y

CONFIG_ATH9K_COMMON=y

CONFIG_ATH9K_BTCOEX_SUPPORT=y

# CONFIG_ATH9K is not set

CONFIG_ATH9K_HTC=y

# CONFIG_ATH9K_HTC_DEBUGFS is not set

# CONFIG_CARL9170 is not set

CONFIG_ATH6KL=y

# CONFIG_ATH6KL_SDIO is not set

CONFIG_ATH6KL_USB=y

# CONFIG_ATH6KL_DEBUG is not set

# CONFIG_ATH6KL_TRACING is not set

CONFIG_AR5523=y

CONFIG_WIL6210=y

CONFIG_WIL6210_ISR_COR=y

CONFIG_WIL6210_TRACING=y

CONFIG_ATH10K=y perhaps that other card chipset is missing its driver. Just make one for it as a module. Here is instructions. Because in this kernel I enabled loadable module support

GCOV-based kernel profiling

#

# CONFIG_GCOV_KERNEL is not set

CONFIG_ARCH_HAS_GCOV_PROFILE_ALL=y

CONFIG_HAVE_GENERIC_DMA_COHERENT=y

CONFIG_SLABINFO=y

CONFIG_RT_MUTEXES=y

CONFIG_BASE_SMALL=0

CONFIG_MODULES=y

Here is a guide https://github.com/marco-pratesi/android/blob/master/HOWTOs/Android-Build-Kernel-Modules-HOWTO.txt

And here is the source code

GitHub - mylesgoose/android_kernel_samsung_exynos9810 at lineage-20update

kalifork. Contribute to mylesgoose/android_kernel_samsung_exynos9810 development by creating an account on GitHub.

github.com

Yet that seems a mission. Easier just just get the models that the drivers are built in.
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
Haha that's really cool. Maybe the rl driver is there and that specific atheros one is not. I did activate all the ones the nethunter guys said needed to be installed in the kernel.

Except if you put the password on the wordlist its cheating. How can we power the 4090rtx of the android phone . To brute force the hash? Can run of this power bank see picture lol. I wired all the laptop battery's on top a power bank. 50,000mah.

Perhaps you where first person in world to crack the WiFi on the s9+ :-) Fun.
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
hahaha yeah it's cheating but it was for the sake of testing. i didn't want to wait long. Also my password is super secure and brute force wouldnt crack it for sure.

Interesting setup. I might buy a y cable or another hub to test it. any brand/models suggestions?
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
UGREEN USB C Hub, 7 in 1 USB-C Hub with 10Gbps USB-C & 2 USB-A Data Ports 4K HDMI, 100W Power Delivery, SD/TF Card Reader, USB C Dongle for MacBook Pro/Air, iPad Pro, Surface, XPS, Thinkpad and More. These are very cheap. On Amazon. And if you only have a few items it can be powered of the phone. But its really great for outputting Kali Linux to the monitor via HDMI. Or Dex. I'm glad you got it working. I think the driver must be there if its being identified by kernel yet if Tue same cable works on a different device clearly its not the cable. Unless plugged in upside down​
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
I don't think i need to add it as module. We already have the same chipset so it should work as it is. (it is also too complicate for me to make the module. i'm a noob)

I strongly believe that the cable and power source is the main issue here. :/
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
I think we have the same alpha brand but they have two different chipsets. Yours is # CONFIG_ATH9K or possibly ATH9k_HTC one is not set and one is and the one you got to work was a realtech one completely different again. Which is different chip . mine was a rtl88 au which takes a different driver to your one. The fact your one shows up in lsbusb means its not a cable issue. And that is a low power adapter compared to the double antenna one I have here. Which power no problems directly on the phone. So personally I would recommend just using the one that does work with the phone. Or make a module for it.
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
i think you are right. For now my only option is to use the one that works since i don't know how to make the module ( honestly the guide seems difficult to me).

I'm going to experiment more though. either ways kudos for your work man. Greta job!!
[Samsung Galaxy S9+ Guides, News, & Discussion] nnyx:
QUICK UPDATE

Irepeated the whole process a bunch of times just to make sure that everything is working.

tl;dr : external wifi works smoothly!

Boot to recovery and Wipe phone completely.

Followed the official lineage wiki guide and flashed lineage-20.0-20240126-nightly-star2lte-signed.zip, MindTheGapps-13.0.0-arm64-20231025_200931.zip and magisk.

Reboot to system. Finished the setup and install magisk-27.0.apk. Installed twrp-3.7.0_9-0-star2lte.img. Reboot to recovery (twrp as of now)

Install nethunter-20240104_033206-star2lte-los-thirteen-kalifs-full.zip. Now this is the tricky part: 2 out of 3 seems to installed successfully which is misleading. Reboot to system.

Flashed again nethunter through magisk modules. (even if there was no error during the previous flashing. )

Reboot again to system when installation finishes. Go to nethunter store and refresh. Update nethunter and nethunter terminal. Make sure that root privilleges are granted.

Now at this point i tested tl-wn722n v1.1 (AR9271), alpha AWUS036NHA (AR9271), and a RT5370 card and they all worked. I guessed my mistake was not flashing again nethunter as a module since i got no errors during the flashing from recovery.

Next step is to upgrade to nethunter-20240128_102814-star2lte-los-thirteen-kalifs-full.zip and flash nethunter-hid-gadget.zip

Thnx mylesgoose
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
The reason 2\3 fail is because data user partition is left encrypted with our mod. Generally data is needed to be decrypted. Yet it seems to work doing it twice like this quite well and is nice to have data partition encrypted. It fails when it starts to write to the data partition. That's easily solved by writing again as you did with magisk. Nice work man. Also @yesimxev helped allot with guidance. PS I noticed the twrp recovery menu is triggering google play services. So once finished installing flash back the. Standard lineage recovery if you have any issues. I dunno if you need to flash the newer nethunter zip I think the only differences is one is made as a user debug with all restrictions for writing to partitions and root nosuid removed. Can remember I was trying to unlock the restrictions as much as possible. So that it could be used more as a computer rather than a daily phone. In my mind more restrictions removed the better. if I break something just reflash . prefer to have more control over the device. And I like to experiment and change settings in kernel. Is quite fun. Glad your having fun playing with it.
[Samsung Galaxy S9+ Guides, News, & Discussion] Elon Uziel:
hi, can you please update the post to the newest lineage-20.0-20240301? or tell me how to do it :)

I tried to do it on my own using the kali-nethunter-project\nethunter-installer and Disable_Dm-Verity_ForceEncryp, successfully created the nethunter zip and kernel but to no vail, I keep getting errors on TWRP and Magisk- not even showing the kali logo :(

p.s.- do i need to port to the device using this?
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
The installer I gave works with the newest lineage update. Did you mount the partition in advanced menu in twrp. And did you in settings choose untick system in mount system prior to zip install? You can just install the lineage update then root device with magisk and install magisk app. Then use twrp app to replace the lineage recovery with the supplied twrp one. And boot to twrp install the installer it will fail but it installs the kernel. The use magisk modules to install the full update nethunter. And add the hid module and safetnet module zips . It fails to install if your data is encrypted. I have never seen that error yours showed though so just use the zip I supplied. Did you make your own lineage kernel ? Or use the nethunter installer of Gitlab? I don’t use that vbmeta disabler or anything else
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
Reply above
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
Also you can copy the updates etc to an internal sdcard and install from there rather than internal memory or cable. it’s better than side loading. It’s confusing in that android as it’s calls internal memory Sdcard. Also on this forms says preload error is this

Depending on twrp version you could try this

In twrp

Wipe menu

Advanced wipe menu

Select preload

Swipe to wipe
[Samsung Galaxy S9+ Guides, News, & Discussion] Elon Uziel:
Oh, thank you so much. I'll try! And by the way, does HID work for you? I installed the Magisk module. however, I still cannot enable it via USB Arsenal. all I get is a prompt "failed to set USB faction". tried with ADB Enable and Disable according to this thread. any ideas?
[Samsung Galaxy S9+ Guides, News, & Discussion] mylesgoose:
You have to.open an android root shell and type setprop sys.usb.config "win,hid” etc ensure you have android debug bridge disabled in development options. And you have to add that hid module via magisk it is not working to set it in usb arsenal yes i tested Rucky app
[Samsung Galaxy S9+ Guides, News, & Discussion] emcbav:
hi, I can't load thew 20240126 image because OTA is denied case its SPL downgrade, will it work with lineage-20.0-20240524-nightly-star2lte-signed.zip too?

(as its los 20 as well)
[Samsung Galaxy S20 FE Questions & Answers] drooperhaley:
Please help. I'm not terribly technical so please try to tell me if there is a relatively simple solution to my problem.

I have an S23FE model SM-S711U purchased from TMobile and had them unlock it. Updated to Android 14 UI 6. I put an ATT SIM card in it to check if it was really unlocked. It is. I then put the Tmobile SIM back in it. It did not ask to restart to change carriers. It shows the Tmobile APN, phone number and works to make calls and has data access, but will not get TMobile 5G UC. If I enter *#2262# it shows 2 SIMS with SIM 1 being ATT and has the ATT bands specified. SIM2 says TMB and shows the Tmobile bands. If I look in settings -> SIM manager it only shows "SIM 1" but says it is the correct TMobile number. My assumption is that it is only accessing the bands shown in the *#2263# setting for SIM1 which is labeled ATT. So, even tho the phone is working, it is not fully capable of the TMobile facilities. I can't figure out how to force it back to using the settings for a TMobile SIM, ie all the TMobile bands. I've tried resetting the phone to factory specs. Same results. Please help me restore the full capabilities offered by TMobile on this unlocked TMobile SE23FE.

BTW, I have a second SE23FE from TMobile that has not been unlocked and has only had a TMobile SIM in it. *#2263# on it shows SIM1 and SIM2 as TMB with all the correct Tmobile bands.

Perhaps it is not a problem unique to the SE23FE but rather just the Samsung process of switching BYOD functions.

Thanks for help!
[Samsung Galaxy S20 FE Questions & Answers] drooperhaley:
Well... it cured itself. I left it on with the ATT SIM overnight and this AM put the TMobile SIM back in it and it switched SIM1 to TMB.
[Off-topic] orb3000:
What are yor plans to recieve 09?
[Off-topic] liamhere:
ill be @ home

with partner and the dog :)
[Off-topic] galaxys:
watching fireworks and partying on the Las Vegas Strip :D
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] h1951:
I flashed my Samsung Galaxy a7 2016, but I found that some ROMs are not suitable for my phone, but I forgot what model my phone is, can you help me.Below is a screenshot of aida64.(After flashing, the display is not the original model)View attachment 6052208View attachment 6052210
[Galaxy A3, A5, A7, A8, A9 Q&A, Help & Troubleshoot] TheMystic:
Samsung Galaxy A7
[HTC Tornado] slisse:
Apparantly Mobile Navigator 7 from Navigon should work on a windows mobile standard smartphone:

According to their compatiblity site:

http://www.navigon.com/site/nl/nl/products/navigation_software/windowsmobile_pda#compatibility

I have tried the Try/buy software but I'm unable to get the correct version to work on my mobile, it always installs the pda version.

Did somebody made it work, and does somebody has the full version ?

thank you
[MTCD  Android Head Units Q&A] pdkreitler:
I have a PX6 with Android 11 and a MTCH MCU version. I am trying to sync my Google contacts to the head unit. I downloaded the Contacts App from the Play Store, but the app won't let me sync. The sync options are grayed out and my account is grayed out. Any ideas how to work around this? Is this possibly an issue with the Play Store and Services version?

I don't mind downgrading the play store to an earlier version, I'm just not sure where to start. And, i would rather not root the device.

Thanks.
[Asus Zenfone 9] andlommy:
Hello!

ZF9 unlocked bootloaders prevent usage of OTA. In fact, Asus server will reject client requests from devices that have bootloader unlocked. Apparently, ASUS maintain a list of unlocked devices (probably by servial numbers).

With some help from the community members below, a list of OTA links has been collected and it's now possible to upgrade ZF9 with unlocked bootloader from last publicly available version (build 142) to latest Android 14

All credits to som_bbs for the efforts

It is important to note, that system software must not be altered in order for the FOTA updates to work. As these are block based incremental updates, the update process just patches the content of the partitions directly, rather than replaces files.

As part of the update process there is hash checking, to verify whether partition hash matches expected values, however as we know, nothing's perfect, so be warned - best to flash full firmware first, then attempt flashing OTA files. They have to be flashed in sequence, depending on the version the phone is currently at.
[Asus Zenfone 9] som_bbs:
File on MEGA

mega.nz

165 to 189 OTA
[Asus Zenfone 9] Treklof:
Link does not work. Nothing there. :(
[Asus Zenfone 9] som_bbs:
Because I was preparing a new link. Collected all OTAs, up to android 14

File folder on MEGA

mega.nz
[Asus Zenfone 9] lostsupper:
Has anyone with an unlocked bootloader successfully used these to upgrade to the latest firmware?
[Asus Zenfone 9] andlommy:
yes, i have updated successfully. Make sure to rename the updates to something like

UL-ASUS_AI2202-ASUS-34.0304.2004.75-1.1.4-2412-user.zip

Instruction textfile has UL-ASUS_AI2202-ASUS-34.0304.2004.42-1.1.4-2312-user.zip,

Reason for that for me was that my upgrade path was

A13 142->165->189->204->218->A14 62 -> 75

updating from 218 with file name used in the documentation didn't work, as 218 update has a security level of 2401, whereas A14 62 update has security level of 2312, so update service wasn't picking it up

Initially i had to reflash full 142 firmware over my existing 142 firmware, as hashes for one of the partitions were mismatched for some reason.

For any issues with ota updates, i used the following adb logcat command:

adb logcat update_engine:* UpdateLauncherService:* UpdateFileMatcher:* *:S

Many thanks to som_bbs for sharing the OTA files. Keep it up, as folks with unblocked bootloaders don't get the OTAs :(