I have a baseband.bin firmware of device Samsung Galaxy M21. I want to extract it into raw code format and re-edit it upload it to the phone. Please help me, i don't know how to extract this firmware file into raw code format.

I want to transmit and receive custom wireless data by using Android's baseband. So the question remains: - How to do it? - Is that true that the baseband operates on separate SoC & separate firmware? - If the baseband operates on different firmware, then can it be changed? - As we know, OTA updates exist on Android, so it means it's possible to upload a different firmware. But, is it possible to change the baseband firmware using a Cable-USB-PC method or not? Case 2: if the baseband shares the same storage unit with the main OS, then it could be easier, but where to locate the firmware, what does the firmware extension look like, converting binary files to relative files? Scenario 3: We can modify the stock ROM which contains baseband firmware. The stock ROM file contains baseband firmware which can be edited/modified or replaced with custom firmware, then we can upload it to the phone. There could be multiple cases. Please help me. I have experience in coding, custom Android firmware cooking, mobile rooting, extracting firmware of TVs/routers, etc. Please remember my ultimate goal is to transmit and receive wireless custom data using a built-in Android baseband radio chip.

Software Defined Radio (SDR) devices are very costly and not everybody can afford them. Even if they could, **some people are not willing to invest their one-month salary into it.** There are RTL-SDR dongles in the market costing some ten dollars, but this is not about external SDR devices. I am thinking of making some code changes in the Android Linux kernel to act as the wireless-cellular chip as SDR. There are projects in XDA Forums where they have built codes that put their WiFi into monitor mode, let's say it is a monitor mode support driver for Android. So as a context to that; what I am trying to do is; make/write some code changes to the Android Linux kernel which will set the cellular chip into SDR mode. Is it possible? If it's possible, then can you give me some ideas on where to begin? I expect only Android core developers from the networking field to correctly answer this question + those of Android hardware engineers.

I attempted to root my (new) Samsung A24 - and while that worked, I've been having issues with the phone suddenly being unable to make or receive calls after a random number of hours until I reboot it. I'm trying to work through this. While I did flash the phone with firmware that claims to be for my region (NZ - so XNZ), the CSC files don't mention "XNZ" in them, they mention "OLM". I've been unable to find out what this means. I did discover OXM is some kind of universal software, so I'm wondering what OLM stands for, and also wondering if it is appropriate for my region!

I have backup of my EFS partitions in raw and also in .Img format. So now i want to: 1. replace my current EFS partitions via Termux/Terminal emulator app. 2. replaced EFS should also sync with modem without any reboot. **I have successfully done above via Fastboot and Recovery but that i don't want to.** **My Findings:** I found EFS and modem partitions are mounted as modemst1, modemst2, modem and fsg etc in /dev/block/ and /dev/block/by-name. But replacing them via Termux won't make any difference to actual EFS partitions. Also after reboot these again gets re-created/replaced. But if i replace all these partitons via Recovery/Fastboot then it make actual permanent changes to EFS partitions and sync with modem and also sustain reboot.

Does Samsung provides official firmware (old phones included)? I have found only user manuals on the web page. I'm looking for equivalent of Google's https://developers.google.com/android/images which allows full reinstallation with Linux (I know that fastboot was replaced by Odin, thus I'll have to use https://github.com/Benjamin-Dobell/Heimdall) . I've found these sites, but these aren't official, right? * https://www.sammobile.com/firmwares/ * https://www.sammobile.com/ * https://updato.com/ The reason I want is that I'd like to test postmarketOS (https://wiki.postmarketos.org/wiki/Samsung_Galaxy_J5_2016_(samsung-j5x)) and then I'd like to revert back. UPDATE: the question is not "which tool should I use" (although that is useful to know), but "what is the official URL for downloading images. Is there any for updating by user clicking on the web page? (there might be just REST/other API for devices). Looking at * SamloaderKotlin : * https://www.odinrom.com/samsung/ (https://github.com/zacharee/SamloaderKotlin/blob/9fee3940855d1a4cd565ae2f6896cdb0ee826782/common/src/commonMain/kotlin/tk/zwander/common/util/Firmware.kt#L27) * https://fota-cloud-dn.ospserver.net:443/firmware/ (https://github.com/zacharee/SamloaderKotlin/blob/9fee3940855d1a4cd565ae2f6896cdb0ee826782/common/src/commonMain/kotlin/tk/zwander/common/util/Firmware.kt#L45) * https://neofussvr.sslcs.cdngc.net (https://github.com/zacharee/SamloaderKotlin/blob/9fee3940855d1a4cd565ae2f6896cdb0ee826782/common/src/commonMain/kotlin/tk/zwander/common/tools/FusClient.kt#L76-L89) , document: "Make a request to Samsung, automatically inserting authorization data." - is this really Samsung official? * samloader (already deprecated): * https://fota-cloud-dn.ospserver.net/firmware/ (https://github.com/samloader/samloader/blob/95d2ac8fb9027b7908d201e4ce807a5b338f923a/samloader/versionfetch.py#L20) * http://cloud-neofussvr.sslcs.cdngc.net (https://github.com/samloader/samloader/blob/95d2ac8fb9027b7908d201e4ce807a5b338f923a/samloader/fusclient.py#L40) * https://neofussvr.sslcs.cdngc.net/ (https://github.com/samloader/samloader/blob/95d2ac8fb9027b7908d201e4ce807a5b338f923a/samloader/fusclient.py#L19)

How do you pull radio images off an Android device? Is there any way to do this?

I am asking a similar question to this https://android.stackexchange.com/questions/27597/tap-off-raw-rf-data-from-antenna but would like further explanation. First off, I'm an electrical engineer, so I have no experience with android systems besides the average phone user experience. What I am trying to do is use a mobile device that can read RFID data at 2.4 GHz. This is as low-level as you can get, but I know we don't have access to raw RF data. Is there a way I can collect the RFID data without needing any external peripherals?

I have a few ideas for a couple local cell to cell apps, but want to use the radio signals to extend the range (the extra work is fine with me). Just curious if it is possible to control the transmission and receiving of bits. If so, any good docs on it? 😁

My searches on the web didn't provide suitable answers to these questions: 1) **Where is the baseband firmware stored?** My understanding is that this particular firmware is a RTOS built for the Baseband Processor (BP/CP). BP is part of a SoC, so it uses its own RAM and its own storage for the firmware. **Is the firmware really stored in another eMMC than the Android firmware ?** 2) **How does Android interact with the baseband firmware?** Again, my understanding (which may be incorrect) is that the BP communicates directly with the AP via a serial connection UART trough Radio Interface Layer (RIL). This RIL interact with Android telephony services. **When does the baseband firmware take action ?** 3) **When the modem/baseband/radio partition is used ?** It seems to me that it only contains the firmware. One thing I've found is that this partition isn't mounted during Android runtime. **Is it only mounted for modem firmware update ?**

Qualcomm SDM660(modem- MSM4114), Mi A2, Android One 9(stock), 2 sim I founded two devices(not links), that can recieve at commands and answer them. Its /dev/smd8 and smd11. Smd7 is owned by root:root, smd11 - radio:radio. What is the difference between them?

I have recently been reading about SDRs and based on what I have understood so far SDR consists of a radio hardware capable of transmitting and/or receiving radio signals within a given radio spectrum range and a software backbone to control its radio operations, so I thought it should be possible to achieve similar operations using an android smartphone therefore I tried to search for projects in the internet and the closest I have found is SDR Touch which requires an external dedicated hardware. Now since a smartphone has so many radio interfaces (Cellular, Wi-Fi, Bluetooth, GPS etc.) is it somehow possible that I can make a project (using root or whatever) that utilizes smartphone's radio components and why isn't there any project that exists performing such functionalities?.

I have a OnePlus 5T and I can't install OTA updates anymore because my firmware is too old. In addition to that I don't have a full backup of my device because I'm using encryption and TWRP doesn't understand it. I would like to simply try the new firmware and revert in case anyhting goes wrong without losing any data. Is that possible? I'm not exactly sure what firmware means in this context and where to get it, but looking at the website , there is this download for a zip file with the following contents: I'm pretty sure that this is the complete stock ROM, meaning if I were to install it, it would wipe everything and replace my LineageOS with the stock ROM. What I would like to do is to simply flash "the firmware" and only the firmware without losing data on my internal storage and also not my app data, contacts, sms, wifi passwords, bluetooth pairings etc etc. And before that I would like to create a backup of my old firmware so that I can go back in case it goes wrong. Can this be done? Can it be done with fastboot? Maybe using fastboot flash PARTITION [FILENAME] and some other command to do the backup? **Edit:** The updater-script in META-INF/com/google/android/update-script contains the following code: getprop("ro.display.series") == "OnePlus 5T" || abort("E3004: This package is for \"OnePlus 5T\" devices; this is a \"" + getprop("ro.display.series") + "\"."); is_part_existed("/dev/block/bootdevice/by-name/vendor") || abort("vendor partition is not existed, exit ota!!"); show_progress(0.650000, 0); ui_print("Patching system image unconditionally..."); block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") || abort("E1001: Failed to update system image."); show_progress(0.100000, 0); ui_print("Patching vendor image unconditionally..."); block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat", "vendor.patch.dat") || abort("E2001: Failed to update vendor image."); show_progress(0.050000, 10); show_progress(0.050000, 5); package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot"); show_progress(0.200000, 10); ui_print("Writing static_nvbk image..."); package_extract_file("RADIO/static_nvbk.bin", "/dev/block/bootdevice/by-name/oem_stanvbk"); # ---- radio update tasks ---- ui_print("Patching firmware images..."); ifelse(msm.boot_update("main"), ( package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64"); package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib"); package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp"); package_extract_file("firmware-update/pmic.elf", "/dev/block/bootdevice/by-name/pmic"); package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz"); package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/abl"); package_extract_file("firmware-update/devcfg.mbn", "/dev/block/bootdevice/by-name/devcfg"); package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster"); package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xbl"); package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm"); ), ""); ifelse(msm.boot_update("backup"), ( package_extract_file("firmware-update/cmnlib64.mbn", "/dev/block/bootdevice/by-name/cmnlib64bak"); package_extract_file("firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak"); package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak"); package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak"); package_extract_file("firmware-update/abl.elf", "/dev/block/bootdevice/by-name/ablbak"); package_extract_file("firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak"); package_extract_file("firmware-update/xbl.elf", "/dev/block/bootdevice/by-name/xblbak"); package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak"); ), ""); msm.boot_update("finalize"); package_extract_file("firmware-update/logo.bin", "/dev/block/bootdevice/by-name/LOGO"); package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem"); package_extract_file("firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp"); package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth"); set_progress(1.000000); Should I just take the msm.boot_update("main"), and the msm.boot_update("finalize"), part and flash them like this? # main fastboot flash cmnlib64 ./firmware-update/cmnlib64.mbn fastboot flash cmnlib ./firmware-update/cmnlib.mbn fastboot flash hyp ./firmware-update/hyp.mbn fastboot flash pmic ./firmware-update/pmic.mbn fastboot flash tz ./firmware-update/tz.mbn fastboot flash abl ./firmware-update/abl.elf fastboot flash keymaster ./firmware-update/keymaster.mbn fastboot flash xbl ./firmware-update/xbl.elf fastboot flash rpm ./firmware-update/rpm.mbn # finalize fastboot flash LOGO ./firmware-update/logo.bin fastboot flash modem ./firmware-update/NON-HLOS.bin fastboot flash dsp ./firmware-update/adspso.bin fastboot flash bluetooth ./firmware-update/BTFM.bin Or would this already overwrite a partition that contains some sort of user data? Can I make a backup of these partitions first? And what about RADIO/static_nvbk.bin, boot.bin, system.transfer.list, vendor.transfer.list and all that msm.boot_update("backup"), stuff? **Edit:** I ended up not being able to flash those firmware files via fastboot because it requires more than a "normal" unlocked bootloader. If I had done the necessary step to unlock the bootloader further it would have wiped all my data. Fortunately you can bypass that by creating a zip with the firmware files and a custom OpenRecoveryScript (updater-script). I found an awesome GitHub project that automates the whole process: https://github.com/angela-d/firmware_oneplus I simply sideloaded the generated zip via adb sideload firmware-update-oneplus5T.zip and finally I was able to install my OTA updates. https://github.com/angela-d/firmware_oneplus

Android images (e.g. those for nexus) ship with a radio-(version).img file. I wanted to unpack this file to look at its contents. I tried using simg2img, as is done with system.img, but that approach didn't work for this file. I know that for boot.img, separate tools are available. I wanted to ask if anyone has tried unpacking this img file ?

After getting more involved with the "aftermarket" community, I have this question that's been on my mind for a while now. Since rooting and flashing a custom ROM on an Android phone doesn't give one SIM unlock that means that the SIM lock settings must be stored somewhere else in the phone's memory. My theory goes that the SIM lock information is stored in or along with the baseband. Is this true? And if so, are there any "alternative" or "aftermarket" baseband firmware images? And finally, who makes the baseband firmware - the carrier, or the phone manufacturer?

I believe it's somewhat well-known that the Nexus 5 has had more than a few hiccups with certain wifi networks. However, I'm not sure that the main reasons for wifi connectivity issues is as well known (as it should be). It seems that every other time I update the OS (Cyanogenmod 12/ 5.1.1) I find myself frantically searching for a solution to some wifi-related problem on the Nexus 5. This week, after upgrading the OS I was confronted by the same issue once again--or at least I thought, as I hadn't exactly documented every previous case. My search for a solution led me to the numerous troubleshooting procedures and potential causes of the problem: - IPv6 automatically connecting - Nex5 failed to delete AP properly - outdated radio/modem image After gaining access to adb shell and executing logcat network:V I noticed that the network interface *Associated* with the Access Point and wlan0: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully (based on lower layer success) Then, immediately after that something failed, even though I thought the connection was successfully made! wlan0: WPA: Failed to configure IGTK to the driver I/wpa_supplicant( 5891): wlan0: RSN: Failed to configure IGTK It turns out that **IGTK** meant something with *Protected Management Frames* (**802.11w**). I should note that the router's configuration had the option set as "Capable", as opposed to "Required". After disabling that feature on my router the connection succeeded. Now, given that fact that ALL of my other devices had no problems with this, why did the Nexus 5 persistently fail to attain a connection to the Network with Protected Management Frames enabled? Is there a security risk with this issue, especially if the Network Admin compromises it for the sake of one device's flaw? How would one mitigate this problem on the android side?

i'm new to android. I recently bought a xperia l phone from my friend in which he had Cm11 installed i decided to upgrade to cm13 and it really messed up the phone.. the sim card was not detected and play store didn't work!!! so i came back to cm11 which then entered boot loop. So i decided to go with cm12.1. Now the pay services work like charm... BUTTTT sim not detected problem still persists!!! so can some one here gimme the link of the radio or modem files of xperia l c2104 or help me with any other solution for this problem... thanks in advance

Trying to use a Samsung Galaxy S device coming from China or Korea in Russia [lead to the observation that the quality of the connection to the mobile network is much worse](https://android.stackexchange.com/a/44021/13117) than on Samsung Galaxy S we used previously (which was bought in Russia). I have installed CyanogenMod 10.0 on the device in the hope that the mobile network connection quality would improve. But that doesn't seem to be the case. Now I see information that there are different firmware available for the modem; one should try to flash them to get modem working well in a specific region --: > Well, I guess you should flash another modem file, which is working > well for your region/carrier (use google . A modem file defines how > the radio part of your phone works, it has an influence on signal > strenght/network speed (and might have influence on battery life, > too). and lists a lot various modem firmware for the device. Which one to choose for Russia, Moscow (Megafon mobile network)? (The one that was working bad for us is XXJPK, and--on another device from China or Korea--SPJG2, which also has bad/unstable signal, but not as bad as XXJPK. After the installation of CM10, XXJPK on that device was replaced with XXJVT, which again has very bad signal.)

It started when I factory reset with twrp and flashed a new ROM. I tried different ROMs and stock when I noticed that I couldn't turn wifi. I ran ifconfig with the terminal emulator app and found out I was missing wlan0. Running "adb shell ifconfig wlan0" gave "ifconfig: wlan0: No such device." I was looking at the logcat live while tapping to turn on wifi and it was giving me "Supplicant not running, cannot connect" and the drivers weren't able to be initialized. Going through the phone and entering in *#*#4636#*#* for the wifi information, wifi state was stuck on enabling and the supplicant state is uninitialized. The MAC address was 02:00:00:00:00:00 if that is of any importance. After searching some more for help, I found out /sys/devices/virtual/net/ was missing wlan0 as well. I think that the wlan0 firmware or drivers are missing, but I'm not sure. I tried "fixing" the permissions on the supplicant file and renaming the file, but to no avail. I would like some help on this. Thanks Note 4 (N910T variant) The ROMs I tried TekHD ROM (5.1.1) CMRemix 13 (6.0.1) Resurrection Remix 5.6.9 (6.0.1) Stock (6.0.1)

I come to you with many interrogations about qualcomm msm8939 SoC. I bought the Archos 50 diamond last year and have since been waiting for archos to make their move regarding android software updates. As of october 2015 Lollipop has been released but in a beta version, no sign of any progress or any comunication ever since. Whereas Samsung or others have released binaries and device specific configuration for their boards, archos on the other end seems to have other things on it's plate. I know the binaries for a specific SoC wich is needed to build android or GNU/linux on embedded systems are sometime proprietary and surely in this instance they are, but.. Even if it's only for limited development purposes, would there be any way, known to man to acquire a personal license for a tailored driver binary? Or maybe is it possible to get an exhaustive list of specific msm8939 device tree configurations options? Is it safe to think that i can gather that exhaustive list of parameters from the various sources available on github? Wherever I look for the device tree of the msm8939 I only find repositories for other phones based on this SoC... with a few minor differences. The only thing worth of mentioning (IMHO) is the work of cyanogen Inc. who signed a partnership with qualcomm regarding snapdragon SoC. Then again even if Cianogenmod is an open source port of AOSP(Big up to anyone contributing), Cianogen Inc's work for those boards still remains behind closed walls. That's why I would like to know if it is manageable to use another device tree (based on snapdragon 615/msm8939) to build something worth "risking" flashing? The 50 diamond appears to be a rebrand of the chinese K-touch Touch7 and it would seem it didn't attract a sufficient amount of good FLOSS developpers for me to find the "good & easy to understand" informations in English or in French. I've been puzzled about another thing in regard of this rebranding. In my build.prop the board name is msm8916(Snapdragon 410) instead of 39!!!!! How come? Is this a trap? Did they just tricked us Or even worse, did they advertise the wrong board ?? If Archos or K-touch or both did in fact used the msm8916 device tree to build the drivers and Android for this board, wouldn't it be missing a whole world of features? Maybe someone knows of a good forum or repo wich might house the golden goose!? (not including the Cyanogemod repo) And by that I mean any curated informations about embedded developement for GNU/linux and/or Android (free as in free beer if possible) It's a shame for smartphone manufacturers that I can't progress on this matter, with a little luck i would brick the damn thing and would have to buy another one :D I'll leave to it! This community rocks! Thanks in advance and see you around!! Bye bye etc, etc...