Database Info

[WiFi] [Modules] Stock WiFi Modules ( flashable )

Return to Contents Page - doubleshot Developers Reference
Here are the WiFi modules needed for the following HTC software packages if you get 'error' when trying to enable wifi:
- Software Version: 1.63.531.2
- Radio Version: 11.59.3504.00U_11.16.3504.20_2
- kernel Version: 2.6.35.13-gf3a1982
Feb 3rd, 2012 - 21:34:43 CST
doubleshot_Stock_Module_1-63-531-2_installer.zip
Download Link
MD5: 674ad34b41a1de5af61321a2af8f39c3
Size: 310.92 KB
- Software Version: 1.55.531.3
- Radio Version: 11.59.3504.00U_11.16.3504.20_2
- kernel Version: 2.6.35.13-ge4be2bc
Nov 17th, 2011 - 18:32:14 CST
doubleshot_Stock_Module_1-55-531-3_installer.zip
Download Link
MD5: d4d7c22e93f77c9629ab414f08d9e75b
Size: 310.92 KB
- Software Version: 1.28.531.9
- Radio Version: 10.48.9007.00U_10.12.9007.07_M2
- kernel Version: 2.6.35.10-g6dea02d
Jun 27th, 2011 - 13:23:58 CST
doubleshot_Stock_Module_1-28-531-9_installer.zip
Download Link
MD5: 1c4dddcbe0567db6211c527d59bc7f38
Size: 309.8 KB
Just download the appropriate flashable attached to this post and install through recovery.
Some people have been having issues with not having them match the stock kernel?
Hopefully this is helpful to some.
Blue6IX said:
Guys - in /system/lib/modules there is a file called bcm4329.ko and another called kineto_gan.ko
These modules are kernel-specific, meaning that they must match the exact kernel they came from-regardless of who makes it (HTC, me, you - whoever)
If they do not, then you will not have wifi (no you don't NEED both, but if you want full functionality then you do)
Anyone having wifi errors this is why.
Fastboot flashing the boot.img file will actually write the kernel - if you try to do it through recovery there are securities in place preventing it actually writing the kernel (thanks HTC!!!!)
What happens without fastboot flashing the kernel (boot.img) is that you have those modules made for a kernel you don't have installed.
...just in case anyone was unsure as to what the problem was, this is it right here.
so you either have to:
-fastboot flash the kernel for the ROM you are using...
-or-
-install the modules in /system/lib/modules for the kernel you are using.
I will split those modules from the stock software packages and make them into flashable zips now, so i'll have then up within the next half hour or less.
This should make it easier for people on custom ROMs with stock kernels to just get their wifi back, so they can flash the modules they need for stock.
Click to expand...
Click to collapse

[ROM] OFFICIAL CM12.1 KFire HD 7 (LP 5.1.x) [2015-06-24 ALPHA]

OFFICIAL CyanogenMod 12.1 for the Kindle Fire HD 7"
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU FLASH THIS, PLEASE MAKE SURE THAT YOU HAVE A 2ND-BOOTLOADER INSTALLED FROM HERE:
http://forum.xda-developers.com/showthread.php?t=2128848
CHECK KNOWN ISSUES BEFORE FLASHING. MAY NOT BE GOOD ENOUGH FOR DAILY USE.
Official nightly builds can be found here:
http://download.cyanogenmod.org/?device=tate
Download Google Apps for Android 5.1:
https://www.androidfilehost.com/?w=files&flid=25361
(Choose newest *-5.1-* file)
NOTES:
Older versions of TWRP will show a "mount failed error". This is safe to ignore.
First boot after a clean wipe will take a LONG time. Be patient.
KNOWN ISSUES:
Use XDA Bug Reporter
SCREEN SHOTS:
Use XDA Screenshots
XDA:DevDB Information
CM12.1 KFire HD 7 (LP 5.1.x), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Beta Release Date: 2015-06-24
Created 2014-12-27
Last Updated 2015-06-24

Reserved
KERNEL UPDATES for Lollipop Android 5.0 / 5.1
Added F2FS support which can be turned on (with a full /data format) in a future release of TWRP
Combined defconfig setup to better support all HD models
Picked "Wakeup reason" patchset from Google's common 3.4 kernel (not fully implemented yet)
Picked IPV6 routing changes from Google's common 3.4 kernel
Reverted a hardcoded disable of Secure Discard and added the official upstream patch for Secure Discard support detection

Reserved
Android 5.1 / CM-12.1 changes:
SElinux Enforcing as default enabled

Woke up from my nap and saw this! Amazing!!! Downloading now
Edit: I would like to point out that there will be a mount failed error in TWRP when flashing the build. Ignore the error and be patient. It'll flash! It took about 2-3 minutes.
Edit2: And it has booted! Approx time is 8 minutes. Be patient on your first boot guys!

Very very thanks Hashcode you are awesome!

Always knew we could rely on the master. Flashing asap once downloaded.

Hashcode, I flash it and 5Ghz Wifi works for me

davigar said:
Hashcode, I flash it and 5Ghz Wifi works for me
Click to expand...
Click to collapse
Mines not. It's not detecting my 5Ghz network.

Can confirm the 7/8 minute 1st boot. Must be to do with initialising ART?!
Anyway, now for a play and a few customisations.
Once again, Thank you and hope you managed to find some time to enjoy Christmas!!

I just got 5Ghz to work. At least on mine. So since a lot of my android devices don't detect my 5Ghz I had to do some researching. Changing the 5Ghz channel from Automatic/Auto to 44 or 48 will make it work. Can confirm on my Nexus 4 and the Kindle. Works superbly!
Source

Glad to see you sorted out all of the issues quicker than any of the other developers could. We're not horrible, but there's no matching the talent that you have when it comes to this type of thing.

And we thought we were close ?. At least we learned a lot and more to come! Thanks Hash for putting your time and effort into this.

How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94

Everything seems to be working very nicely so far. Just flashed about an hour ago. Seems much smoother than kit kat did. Thank you very much. Looking forward to the updates.
Sent from my Amazon Tate

cell2011 said:
How to fix allot of FC's? Google play is giving me trouble. I flashed 12/20 gapps right? And su 1.94
Click to expand...
Click to collapse
As the title of thread says, its in Alpha. But may I ask what FC's your'e getting? I'm running the build on my Kindle at the moment and the only FC I get is Bluetooth Sharing. Bluetooth was activated on the main user and when I switch to another user it FC's.

I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?

cell2011 said:
I did advance wipe cache system dalvik data and flashed rom gapps and super su 1.94
---------- Post added at 10:10 PM ---------- Previous post was at 09:55 PM ----------
Should i reflash just rom and gapps and supersu after i boot up?
Click to expand...
Click to collapse
There's no need to flash SuperSU . SuperUser is built in already and working. Wipe System, Data, Cache, and Dalvik. Then flash the ROM and gAPPS.
---------- Post added at 04:43 AM ---------- Previous post was at 04:17 AM ----------
Is anyone else getting a bootloop when clicking on reboot? I have to fully power down to be able to make it boot. Also, I'm unable to tick unknown sources when on another user (using Multi-Acc). Don't worry, I'm not downloading pirated apps xD. I download the APK's over at the Android Apps and Games forum.

Awesome work man! Flashing now...

This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.

Random Username said:
This is great! Thank you Hashcode!
When I flash it, I get the error
Code:
mount: failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/sys
(I can't read further)
Is this something to be worried about? It boots just fine.
My other problem is that I can't log in with my Google account? Is this maybe related?
Click to expand...
Click to collapse
I get the same error and google account works fine for me

[STOCK][LP][PATCH][d800] Patch Any Stock G2 ROM for AT&T

Patch a ROM for LG G2 d800!
---- Supports Model d800 ONLY! ----
Lollipop ONLY!​
What this is:
This patch can be flashed after flashing a full non-d800 ROM (DO NOT REBOOT AFTER FLASHING A NON-D800 ROM, even into recovery!) It changes the appropriate system files to the d800 variant version, as well as makes the proper build.prop changes. Note: If you use a vs980, ls980, l01f, or f320 specific ROM, there may be additional build.prop changes that need to be made. I didn't add all those because most of the development is on d80* models. Even if it is specific to these other models, patch will likely work just fine.
I took the basic idea from @dev>null (see here) I had previously dumped all of our stock, d80030f partitions. I took those dumps and combined them with the basic gist of this other patch dev>null made.
What changes this makes:
(1) Your entire bootloader is replaced. (a hybrid of 20y and 30f is applied)
(2) Stock lollipop 30f modem/baseband is installed.
(3) Stock lollipop 30f boot image, that has been bumped, is installed.
(4) Variant specific /system files are deleted. Then they are replaced with the d800 30f version of those files.
Installation:
(1) Boot into recovery, flash your desired ROM. (for my test, I used a d802 ROM)
DO NOT REBOOT RECOVERY, DO NOT!!!! If your ROM asks you to reboot after install, DO NOT!!!!!
(2) Flash this patch.
(3) That's it, you're done! It is okay to reboot now.
Note: Some ROMs might replace your /recovery partition, in which case you should re-flash your recovery before rebooting.
Troubleshooting:
SELinux / Bootloop
This patch properly sets permissions on the files it replaces. That being said, the boot.img in this patch is set to selinux ENFORCING. This means if the ROM you flashed does not have proper support for selinux to begin with, you'll get a boot loop, or hang on the glowing notification LED. Go yell at your ROM dev to fix it, or flash a boot.img that has selinux PERMISSIVE.
ROMs for models other than d80*
There are some additional build.prop changes that might need to be made if the ROM you want to use is f320/ls980/vs980/l01f. There isn't much development on ROMs specific to those models. I'll probably release a version 2 of the patch, eventually, to make these extra tweaks. However, it should work fine as is! The big exception is l01f ROMs. These ROMs are missing NFC files, so either NFC won't work, or the whole thing won't fail.
Major Thanks to:
dev>null
Download:
Did you read EVERYTHING above? If so, proceed -
https://www.gregtwallace.com/lg-g2/d800-rom-patch/
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
XDA:DevDB Information
d800 Lollipop ROM Patch, ROM for the AT&T LG G2
Contributors
blastagator
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Stable
Created 2015-06-01
Last Updated 2019-12-31

Change Log
July 29, 2015 (v1.5) (LP 5.0.x)
-Do not flash misc partition. Not needed.
-Overwrites MAC addresses and things.
June 23, 2015 (v1.4) (LP 5.0.x)
-If /data/media exists, set the proper permissions and context
-DONT use TWRP to wipe Internal Storage after running the patch/fix. If you want to wipe internal, do so BEFORE the patch/fix.
June 23, 2015 (v1.3) (LP 5.0.x)
-Change version number to be same for both files (so skipped v1.2 for permission fixer)
-Updated to latest file_contexts from dorimanx
-FIX!!! - ROM Patch and SELinux Context patch both fix ntcode_listing.sh context
++First boot was hanging on completely clean wipe, d800 does not support context: ubject_r:ntcode_listing_exec:s0
++ntcode file only executes on first boot
++Add build prop tweaks to remove lines that cause execution of ntcode_listing.sh
++In case build.prop tweaks fail and file is executed for some reason, fix its permissions so d800 can execute
June 12, 2015 (LP 5.0.x)
-Permission fixer v1.1
-Fixes a couple of contexts (thanks @dorimanx)
June 11, 2015 (LP 5.0.x)
-Created zip that should fix all SELinux Context and allow boot to ENFORCED mode.
-Posted on my site as "LP ROM SELinux Context Fixer"
-Flash after ROM, ONLY IF SELinux ENFORCE doesn't already work!
June 4, 2015 (v1.2) (LP 5.0.x)
-Added automatic flash of d800 recovery - TWRP 2.8.6.3 (in case ROM overwrote recovery)
-Also posted:
++Added a flashable zip containing devnull's permissive boot.
++Removed my permissive boot, it wasn't working right. Sorry!
June 1, 2015 (v1.1) (LP 5.0.x)
-Supports conversion for Stock Lollipop ROMs from any LG G2 variant, except l01f and lgl22.
-I will probably never add support for those two models since development is very minimal on them.
-Also added other flashable zips to easily switch between ENFORCING and PERMISSIVE.
-Replacement files come from Stock Lollipop d80030f.
June 1, 2015 (v1) (LP 5.0.x)
-Initial Patch
-Fully supports all d80* and f320 ROMs.
-Will do update shortly to add support for converting ls/vs ROMS
-Replacement files come from Stock Lollipop d80030f.

[]

res3

Dude!!! You rock
Sent from my LG-D800 using XDA Free mobile app

Yeah!

Bro thank you! Not only for this, but everything you do for the g2!

thank you.. thank you... thank you.. thank you

So could I use the stock system partition from the d800 lollipop and run it with this?

Thank you very much @blastagator!
Now I can flash any AOSP rom and back to stock easyly. :XXX

I dont think there are any lollipop for L22. L22 is the lonely baby in G2 family without lollipop.

thanks

vannhut07vn said:
thanks
Click to expand...
Click to collapse
You're welcome. Now please kindly delete your quote of the entire OP...

@blastagator
would this patch work with CloudyG2 3.0?

Abrilabr said:
@blastagator
would this patch work with CloudyG2 3.0?
Click to expand...
Click to collapse
It should. If it doesn't boot, permissive-boot flashable would be needed.

You are awesome...insane.. Go on man..!!
Thanks a lot...
Gonna try hunting some Lollipop roms

Nicely Done....
man U R just great.......
thanks for the excellent work....

Hello friends greetings from Venezuela, where I can find a tutorial to update my LG G2 to lollipop, possess a model D800 20Y

@blastagator it's a great idea.Thank you for test with SRKG2
Sent from my LG-H818

it'll work with this rom ?
http://forum.xda-developers.com/lg-g2/development/rom-lg-g2-pro2-v5-final-acura-d802-d805-t3095500

[Completed] Random Reboot and Force Close on Mi4C

Hi
I'm hoping that i'm posting in the right place..
I'm getting an issue since this week end with my Mi4C..
My phone is force-closing some applications randomly, and is also rebooting randomly.
I tried to install several rom, i'm currently under the following version :
Model Number: mi-4C
Android Version: 5.1.1 LMY47V
Android security patch level: 2016-04-01
MIUI version: MIUI by xiaomi.eu 7.3 | Stable 7.3.1.0 (LXKCNDD)
Baseband version: BO.2.6.c1.2-0406_2058_e377129
Kernel version: 3.10.49-perf-g67c73a8
Build number: LMY47V
To install the rom i did a full wipe to ( system / cache / data / dalvik ), i also tried to do a wipe of system / cache / data / dalvik / Internal Storage and install the rom through ADB Sideload with no improvement.
My Current Recovery is TWRP
I tried the same method to install the following rom, but i'm facing the same behavior on it:
- Eu MIUI Developer version
- MIUI Chinese Stable version
- MIUI Chinese Developer version
- CM13.1 Superluminal
Thanks for your help..

XDA Visitor said:
Hi
I'm hoping that i'm posting in the right place..
I'm getting an issue since this week end with my Mi4C..
My phone is force-closing some applications randomly, and is also rebooting randomly.
I tried to install several rom, i'm currently under the following version :
Model Number: mi-4C
Android Version: 5.1.1 LMY47V
Android security patch level: 2016-04-01
MIUI version: MIUI by xiaomi.eu 7.3 | Stable 7.3.1.0 (LXKCNDD)
Baseband version: BO.2.6.c1.2-0406_2058_e377129
Kernel version: 3.10.49-perf-g67c73a8
Build number: LMY47V
To install the rom i did a full wipe to ( system / cache / data / dalvik ), i also tried to do a wipe of system / cache / data / dalvik / Internal Storage and install the rom through ADB Sideload with no improvement.
My Current Recovery is TWRP
I tried the same method to install the following rom, but i'm facing the same behavior on it:
- Eu MIUI Developer version
- MIUI Chinese Stable version
- MIUI Chinese Developer version
- CM13.1 Superluminal
Thanks for your help..
Click to expand...
Click to collapse
Hello,
Please register for XDA account to post and reply in the forums.
You may post your query here Mi4c Q&A with all relevant details, the experts there maybe able to assist you.
-Vatsal

[ROM][Stock] Stock Android 7.1.1 ROM for Moto E4 (xt1766) SPerry - Root, BusyBox

•••• Qualcomm Moto E4 (xt1766) SPerry Only ••••
DISCLAIMER:
By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device. Although this ROM has been thoroughly tested on my own device, I take no responsibility for bricked or otherwise inoperable devices incurred as a result of this thread. Follow the instructions carefully, and things should go smoothly and without negative results.
SPECIFICATIONS:
• Moto E4 (XT1766) SPerry
• Sprint, Virgin Mobile, Boost Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-10
• System Version: 26.231.8.sperry_sprint.en.US
• Radio Version: M8920_15000.280.06.58.05R
• Kernel Version: Linux 3.18.31-perf
• Security Patch Level: September 1, 2018
FEATURES:
• Stock Configuration
• Systemless Root - Magisk v17.1 Stable
• SafetyNet Pass (ctsProfile & basicIntegrity)
• Zipaligned /system/app & /framework
• Optimized RAM efficiency
• Disabled AVB & dm-verity
• Disabled Force Encryption (Opt-Encrypt)
• BusyBox v1.29.2 (Static Binaries)
• TWRP Flashable Installer
PREREQUISITES:
An unlocked bootloader and TWRP custom recovery are required to install this ROM. IMPORTANT: Use @squid2's TWRP v3.2.1-r1 or older for installation https://forum.xda-developers.com/devdb/project/dl/?id=27958 Newer builds will cause a conflict with the /vendor & /oem partitions when installing my partition updater zip. After installation, you may update TWRP to a newer or current version.
The conflict is due to the partition scheme of my updater-script, and is not due to any fault in @squid2's current TWRP builds. Here is a link to @squid2's TWRP thread for the Qualcomm Moto E4. https://forum.xda-developers.com/mo...velopment/twrp-twrp-moto-g4-qualcomm-t3655160 Please be sure and hit the thanks button on his thread if you use his work.
NOTES:
• If you have previously installed the 26.221.3 OTA to bring your build version up to NCQS26.69-64-10, you should have no need to install the partition updater zip prior to installing the ROM. However, if you are unsure of your present firmware build, or if you have not installed the latest OTA, the partition updater should be installed per the instructions below, in order for the ROM to work with the best results;
• As to force encryption, the kernel fstab has been modified to disable this OEM security feature. However, you may still manually encrypt your /userdata by fully charging your device, going to Settings>Security>Encrypt Phone, and following the on-screen prompts;
• This OTA update did not augment the baseband (radio firmware) version (M8920_15000.280.06.58.05R), which remains unchanged from NCQS26.69-64-8. While the radio firmware did receive a couple of minor patches, the changelog in this regard is insignificant, so I did not include these in either the partition updater or the ROM. If anybody wants these radio patches, leave a comment and I'll fix up a TWRP flashable installer.
INSTRUCTIONS:
• 1. Download the ROM and Partition Updater from the download link below and save them to your device's external storage (because the /usedata partition needs to be formatted to disable force encryption, saving the downloaded zips to internal storage would be futile);
• 2. Make a backup of any important files on your device;
• 3. Boot your device into TWRP recovery mode;
• 4. Select Wipe>Advanced Wipe and select System, Cache & Dalvik Cache. Swipe the action bar to commence the wipe;
• 5. Again select Wipe>Format Data, input the word "YES" when prompted, and swipe the action bar to commence the format. Reboot Recovery (often necessary to ensure proper mounting of /usedata after a format);
• 6. Select Install, navigate to the saved location of the Partition Updater zip, and swipe to commence install (this updates your /oem partition, /rpm primary bootloader, /tz trust zone partition, and /devcfg partition to Build No. NCQS26.69-64-10);
• 7. Select Install, navigate to the ROM zip, and swipe to commence install;
• 8. Reboot System.
Kernel Source Code (msm8920): https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
THANKS & CREDITS:
•Thanks to the long-dedicated @squid2 for his TWRP builds for this and many other Motorola devices;
•Thanks to the great @SuperR. for his amazing Windows version SuperR's Kitchen;
• Thanks to the world famous @topjohnwu for his Magisk Universal Systemless Interface;
• Thanks to @madbat99 for his dedication to Motorola devices, and for taking the time to assist so many Motorola device owners;
• Thanks to @osm0sis for his static BusyBox installer and his Magisk Modules;
• Thanks to @Davey126 for his support of Motorola devices, and his dedication to helping other members on various device threads.
DOWNLOAD LINKS:
NCQS26.69-64-10 Partition Updater: https://drive.google.com/file/d/1VmOPXbYBQQkqB475iVzKip2JI_AO0YCM/view?usp=drivesdk
NCQS26.69-64-10 Stock Android 7.1.1 ROM: https://drive.google.com/file/d/1VRuKnSgVHNkewbk5juB7_WWeLm_ptmUP/view?usp=drivesdk

I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.

I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice

Bailey36375 said:
I'm new bee kinda so flashing this os just the update so if I have everything up and running good them really don't need this update seems updates have me screwed from getting data on custom rom now so any advice
Click to expand...
Click to collapse
If you have taken the OTA update and you are on Build No. NCQS26.69-64-10, and everything is running smoothly, you have no need to install anything here.

I'm not on 10 I'm on 8 but would like that debloted version

Bailey36375 said:
I'm not on 10 I'm on 8 but would like that debloted version
Click to expand...
Click to collapse
It'll be up in a couple of days. By the way, there is no danger in taking the OTA. No reported bugs, instabilities, etc. And you can still flash the debloated ROM when I post it.

Thanks for taking time to do this and keep support going for the E4. I'm planning on trying the debloat when you post it.

S o S just flashed and now it is only booting to TWRP it says its flawed but
Only boots to TWRP help after flash
---------- Post added at 05:34 AM ---------- Previous post was at 05:18 AM ----------
Really need help I have TWRP 3.2.1 r1 I did what the instructions said but now just goes to the TWRP what's the issue I'm sure it's something I'm doing help this is my only phone
---------- Post added at 05:52 AM ---------- Previous post was at 05:34 AM ----------
Got it woohoow

MotoJunkie01 said:
I have also made a debloated build of this ROM, with all Amazon, Sprint and OEM related apps removed from /system/app, /system/priv-app, /oem/app, etc. I will try and post this version this coming week for anybody interested.
Click to expand...
Click to collapse
Yayyyyyyy!!!!!! I,ll be waiting for that one. Thanks motojunkie01.

Does Radio work in Custom Roms.

EarthMan1 said:
Does Radio work in Custom Roms.
Click to expand...
Click to collapse
The radio was not updated with the new OTA. The Baseband Version remains the same as the previous build, M8920_15000.280.06.58.05R

That means the voice calls won't work on Custom ROMs.

EarthMan1 said:
That means the voice calls won't work on Custom ROMs.
Click to expand...
Click to collapse
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.

MotoJunkie01 said:
Voice, MMS/SMS, and 4G/LTE data works on my device with LineageOS 14.1 on the 05R radio firmware. Although I am aware that an earlier OTA (NCQS26.69-64-8) did break the cell radio for some device owners running custom ROMs.
Click to expand...
Click to collapse
So, if i want to update I have to wipe my data.

EarthMan1 said:
So, if i want to update I have to wipe my data.
Click to expand...
Click to collapse
No. But if you want to install this ROM, you will need to format /userdata in order to disable force encryption. If you want your data encrypted, you are not required to format /userdata.

No, I want only to install the partition updater.

EarthMan1 said:
No, I want only to install the partition updater.
Click to expand...
Click to collapse
Then formatting data is not necessary. Keep in mind that the partition updater does not change your radio firmware. You'll still have the 05R radio version after updating your partitions. The partition updater updates your bootloader, /devcfg and /oem partitions.
So if your radio didn't work on custom ROMs before, the partition updater likely will not change that.

Why this partition updater size is big compared to the NCQS26.69-56 one.

EarthMan1 said:
Why this partition updater size is big compared to the NCQS26.69-56 one.
Click to expand...
Click to collapse
Because the /oem partition is large (656 MB)

Why isn't it included in the 56 one