I've spent a bunch of time trying to understand why the modem in a particular E980 doesn't work in Cyanogenmod 12. Others should benefit from my efforts.
Searching reveals several posts about the modem issue, but quite a few of the responses are either links or references that require significant background to understand.
The community consensus is that one must flash "madmack's modem" when using CM with the E980 & variants. Without it, many phones can't enter deep sleep and thus drain the battery. Others can't use the modem at all.
(Madmack's modem post: https://forum.xda-developers.com/showthread.php?t=2430456)
(Current source of CyanogenMod 12.1: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html)
"Madmack's modem" is the image for the BM9615A-CEFWMAZM-3.0.113012. Some users had a driver for a CM9615A[...] variant instead. For those users, flashing the BM9615A driver allowed the phone to go into deep sleep. Hooray!
---
Unfortunately, other E980 owners have a completely different modem: the APQ8064/MDM 9x15M. In this case, flashing the BM9615A file doesn't help.
If your modem appeared as an APQ8064/MDM9x15M on stock, it appears as the BM9615A upon flashing CM12. Unfortunately, its still an APQ8064 on the inside. This makes it seem like CM 12.1 is hard-coded to the BM9615A modem. When CM tries to speak BM9615A-ese to an APQ8064, the result is "No Sim" (or rather intermittently detecting and dropping the SIM).
Flashing the BM9615A image on an APQ8064 doesn't help -- the modem can't understand itself. CM and the modem firmware may speak the same language, but the image that runs the modem isn't right for the hardware.
At least, thats what I think is happening. I would appreciate it if someone with experience could please let me know if my understanding is incorrect.
Until someone finds a way around this, those people whose modem is APQ8064/MDM9x15M on stock may want to hold off on trying the available roms. Most are based on CyanogenMod and thus can be expected to have the same problem.
I wrote this post both to consolidate information and to ask for help. Does anyone have a way of getting an E980 with a APQ8064/MDM9x15M to work with CM 12.1?
(Note: Tried Emmanuel's wild kernel. Didn't help.)
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
ShadySquirrel said:
No custom ROM changes (or should change) change your modem firmware, so neither should you unless told to do for your variant.
That specific modem was for AT&T variant of G Pro and many people who upgraded to stock kitkat and then tried to flash anything else, required it. No other variant should ever use that modem - if the need arises, just reflash back to last available jellybean stock firmware.
If you have deep sleep issues on any other variant but E980, just revert your phone to stock jellybean and flash whatever you want. Never had any modem-related deep sleep issues with Jellybean base, while with kitkat base there were some issues in KK roms, but not later... that I remember. I've used E988, built ROMs and kernels for it so I should kind of know
No SIM issues were solved later in 2015? if I'm not wrong. It was just a change in LGE RIL subclass, required after cyanogenmod updated their telephony framework.
Click to expand...
Click to collapse
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
facepalm5 said:
Thanks for the reply.
I guess I'm not understanding things well. How would one change the LGE RIL subclass appropriately, assuming a move from stock JB to CM 12.1 without any modem flashing?
Click to expand...
Click to collapse
Which CM build are you trying to use?
ShadySquirrel said:
Which CM build are you trying to use?
Click to expand...
Click to collapse
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
facepalm5 said:
This one: http://www.cyanogenmodroms.com/2014/01/cyanogenmod-rom-lg-optimus-g-pro.html
Click to expand...
Click to collapse
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
ShadySquirrel said:
October of 2016? I'm pretty sure there were no 5.1.1 builds for e980 back then. Can you try SlimLP from my downloads? That's a build from February 2016.
Click to expand...
Click to collapse
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
facepalm5 said:
Thanks. That does seem to make the SIM work, but with a couple of quirks.
Tapping "build number" repeatedly doesn't activate developer options. Has this been moved?
Also, the usual root method seems to be disallowed and SuperSU disappears after being installed.
Click to expand...
Click to collapse
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Intended a direct reply. See below.
ShadySquirrel said:
SuperSU should be available via Settings menu (if something hasn't changed with newer versions) and Developer mode is on by default if I remember correctly, if not, taping on build number 7 times should tell you 'you're a developer now' and enable it.
Click to expand...
Click to collapse
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
facepalm5 said:
Thank you for your reply and the work that you have put into making this device usable.
Developer mode normally lives under Settings-> System. The Feb 6 2016 SlimLP build includes "Date & Time", Accessibility, Printing, Kernel Auditor, Check for Updates and About Phone.
Was developer mode moved somewhere else?
Naturally, I've tried tapping "build number" many times. I don't get the usual "almost a developer" and "you are now a developer" response sequence.
Click to expand...
Click to collapse
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
ShadySquirrel said:
It should be somewhere near the end of settings menu, nowhere else. I guess something got borked somehow, so you may want to reboot.
P.S. Use SlimLP build from 16.02.2016, it has some new things fixed, and refflash rebuilt kernel I've mentioned in SlimLP post.
Click to expand...
Click to collapse
Thanks. I'll give it a try, but let me make sure that I understand which one. There are two mirrors on the EOL thread: basketbuild & androidfilehost.
The newest build on basketbuild is 02072016. Androidfilehost has a 021816, however there is a note in the EOL thread that 021916 shouls be deleted because it doesn't work. Is that the same as 021816 or is 021616 really the same as 021616?
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
ShadySquirrel said:
Sorry, I totally forgot that my mirrors are a bit different.
You should use this one (md5sum, it's the last stable build. Don't let date scheming confuse you, I've used kind of weird build system because my machine isn't as powerful as it's needed and builds sometimes take up to two days... nightmare. Later just flash kernel mentioned in the op over after the flash.
EDIT: You may want to drop SuperSU now or use some older version (before acquisition) and freeze it from updating.
Click to expand...
Click to collapse
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
facepalm5 said:
Thanks.
The core items seem to be OK. I noticed a few odd items within the build. Since its been on an advertising host, I'd like to confirm that the file which you uploaded hasn't been modified. Could you please share your sha256 sum (md5 has been retired for a while now) for Slim-e980-5.1.1.beta.0.15-UNOFFICIAL-20160218.zip from your own hard drive?
Click to expand...
Click to collapse
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
ShadySquirrel said:
Sorry, I had two hard drive failures in last year and a half so only copies I have are uploaded to AFH with their original MD5 sums (sum which site shows you is sum they are generating after upload; sum I've linked you is sum generated after file was created). You can compare these two if you need some reassurance, but files are uploaded by me and were used by me, too, so should be no issues if no server-side corruption happened.
Click to expand...
Click to collapse
I can confirm the builds he has uploaded work for me, including the kernel fix for LMK which he posted this past year. ROM runs great
Related
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
March 19,2014
Added new Version for newer CM11 nightlies
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
March 25 Note: Added zip for new versions of Commotio Rom
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
arifqur said:
Many people who have bought phones from the US and are using them outside of US, are having problems with connecting to the Wifi. For me it started to happen on OGP after Jan 21, 2014 CM11 nightlies.
A workaround was to check anyone of the countries in the settings>wifi>advanced> Region codes. Problem was that this region code would not persist after a reboot and you would have to go through the settings again.
The reason for this problem is the change in code in the MccTables in system>framework> telephony-common.jar which queries the SIM for the locale and since the locale codes in the SIM do not match the Wifi codes in the MccTables, the region does not persist as a permanent entry.
All credits to the dev who figured this out in the HTC sensation Forums: http://forum.xda-developers.com/showthread.php?t=2368501
The method that this dev has posted is based on adding a line in the MccTables which skips the locale checking from the SIM during startup and so the Wifi is able to scan the available networks and connect to the desired one.
The telephony-common.jar is slightly different in different custom roms, therefore we need to patch this file for the individual Roms.
Attached below are the zip files which can be flashed in recovery right after flashing the rom if on a new installation or can be flashed at any time on an older installation in which case after reboot it stops for a while at android is upgrading and then boots normally into the rom.
Note: A wiki page on this problem also provides a lot of insight into this problem: http://forum.xda-developers.com/wiki/WiFi_regional_problem_on_Android#CyanogenMod_based_ROM
Note: The CM11 patched file works on the Mokkee nightlies as well.
Hope this helps the poor sods like me who have been stuck with this problem for a while now.
A word of caution. Make a Nandroid and flash at your own risk
Click to expand...
Click to collapse
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
atifsh said:
why is it theming the system?
personally im happy with the kernel change, M2 kernel is as good as M3 or later
Click to expand...
Click to collapse
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
arifqur said:
The flashing zip package that I used is an old vr theme package. It just says that its theming when actually it is replacing the required file in the system>framework.
The rationale for using this workaround is that if we keep flashing the old kernel we would miss out on all the new changes that are incorporated in every build.
You don't want to be left happy with an old kernel on a spanking new build.
Click to expand...
Click to collapse
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
atifsh said:
no it is changing morethan just the framework, ill build the file myself and see if it works, thanks anyway.
Click to expand...
Click to collapse
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
arifqur said:
Why don't you unzip the file and see what's inside?
Anyways you can re-download the files.I have deleted the lines in the updater-script that said stuff about theming.
Click to expand...
Click to collapse
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
atifsh said:
i did and only required file is the framework, but as i say ill try to build one myself later, im kinda like that . seems pretty simple in the link you provided, just have to edit a line.
Click to expand...
Click to collapse
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
arifqur said:
Yup it is pretty simple. Glad this problem has been sorted out, kind-of
Click to expand...
Click to collapse
yeah flashing every time you update is a mess
atifsh said:
yeah flashing every time you update is a mess
Click to expand...
Click to collapse
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
arifqur said:
Hey it isn't that bad. We flash the rom, gapps, sometimes supersu, so flashing another zip is not going to mess up your whole day.
The reality is that any workaround this problem would involve some work. You can't complain at a simple process which rids you of a problem which cannot be solved in any other way and gets you to enjoy the finest and brightest of latest kernel/rom development.
BTW the only other way to get out of this mess is to go to the US and get an AT&T connection.LOL
Click to expand...
Click to collapse
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
atifsh said:
strange just tried latest nightly on moto atrix hd and it doesn't have this issue, atrix HD also an ATT phone
Click to expand...
Click to collapse
Not all phones have this problem and also a lot of custom rom devs apply this patch directly in their roms.
I have an S3, S4, HTC One, Note 2, S2 Skyrocket, Nexus4 and none of them have this problem. Even on OGP this problem started from CM11 Jan 22, 2014 build. The Jan 21st build flashes without this issue.
Flashable zip added for new Commotio Rom Nightlies
Any chance to apply the patch to a stock rooted rom?
Thanks
Region Code
Hi can someone fix this file for region code?
nagi_007pk said:
Hi can someone fix this file for region code?
Click to expand...
Click to collapse
Sorry man.
Tried to patch it but seems to be way different in code from the rest of the roms that I have seen.
Can someone post the patch for latest cm nightlies?
nagi_007pk said:
Can someone post the patch for latest cm nightlies?
Click to expand...
Click to collapse
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
nagi_007pk said:
Yeah man here. Patch this file for me. It's from the rom I'm currently using. It's cm11 based
Click to expand...
Click to collapse
Here you go.
Hope it works
arifqur said:
I think the latest cm11 nightlies have this fixed by default.
Had no problems with the April 21st nightly.
If you still have trouble let me know and I will make a patch for you.
Click to expand...
Click to collapse
just tried it latest nightly, still the same.
Unofficial LineageOS 13 (Android Marshmallow) for JBBL dated March 18, 2017 from the 4PDA forums courtesy of developer ilichva!
Again, this is only for JBBL. Flash at your own risk and please do a nandroid backup prior to doing so!
All credits and thanks go to the original developer ilichva!
____________________________________________
Latest Build - LineageOS 13:
lineage-13.0-20170318-port-ilichva-xt907_jbbl.zip (405.4 MB)
Mega
SolidFiles
PCloud
MD5 :: 63FB23666399844E5BB7A8D9C347374D
____________________________________________
Prior Build - CM13:
cm-13.0-20161205-ilichva-xt907_jbb.zip (411.9 MB)
Original Link
Mega
SolidFiles
PCloud
MD5 :: 3c786a57929d024010a0fce36287ea7d
____________________________________________
NOTE: If you are on KitKat Bootloader (KKBL), you will need to revert to the JellyBean Bootloader (JBBL) before you can flash this ROM. Instructions on how to do so may be found here and here and here
____________________________________________
Latest TWRP 3.0.2 recovery by ilichva may be found/downloaded here
Updated to 03.25.2016 build
Hallo Rahimali
Thanks for the share. I have tried this and apparently works ok. I'm unable to get WiFi working. Tried different gapps but there are force close issues. Any recommended gapps versions available?
Opengapps usually does the job. Flashing gapps with marshmallow is different than with prior android versions. With MM you have to flash gapps immediately after you flash the ROM (before booting up the ROM for the first time). Try and see if that resolves your FC issues
Updated to April 02, 2016 build!
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Updated to April 05, 2016 build!
ultrasoniic said:
I managed to get the force close issues resolved. Everything works fine except Wifi. I am unable to enable wifi as the button is greyed out. I tried enabling wifi from terminal using svc wifi enable, it enabled the button but wouldnt detect any available wireless networks. Any fixes for this?
Click to expand...
Click to collapse
Sorry no idea. Nobody is complaining in the 4pda forums about any WiFi issues. Did you do a clean flash? Maybe the developer, @ilichva can help?
bootloader and recovery
My XT907 is showing that my bootloader is "0x109B" and I am unsure what version of TWRP supports 6.0.1 (currently running 2.8.6.0)
Can anyone verify their settings and let me know?
I am running CM12.1 currently, so I should be able to dirty flash correct?
Thanks guys!
KKBL?
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
crzypcdude said:
Anyone know of a marshmallow based rom that works with the kitkat bootloader for this device?
Click to expand...
Click to collapse
Marshmallow not yet available on KKBL
rahimali said:
Marshmallow not yet available on KKBL
Click to expand...
Click to collapse
Are there any significant reasons to stay on the KitKat bootloader? Otherwise I'll just downgrade now that I'm rooted with an unlocked bootloader.
One of the most compelling reasons to stick with the KKBL would be the availability of the 3.4x kernel as opposed to the 3.0x kernel on the JBBL but feel free make your own decision. I was on the JBBL (by choice) for a considerable length of time without any apparent side effects...
Would you mind adding dates to post #1?
Any updatefor this rom?
crzypcdude said:
Would you mind adding dates to post #1?
Click to expand...
Click to collapse
The dates are already present in post #1 as well as in the filenames.
dedik46 said:
Any updatefor this rom?
Click to expand...
Click to collapse
Updated!
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
crzypcdude said:
Are all the builds being updated in the 4PDA post linked in #1 as well as TWRP builds?
Click to expand...
Click to collapse
That is correct.
Confirmed Working!
Can confirm this works, flashed the recovery included in the 4pda post, used it to flash the rom, gapps, and supersu. Initially booted up in Russian, but after waiting for 30 seconds or so, switched to English on its own. Setup was flawless after that, no issues to report as of now. Anyone that needs help installing the rom or downgrading from kitkat to jellybean just message me.
I thought I was the only one that ended up with default language in Russian... All the previous builds defaulted to English on install... Also when I downloaded the latest update it downloaded on my phone as a .bin not a .zip I checked the file size and contents vs what is online (after changing the extension to .zip) and everything seemed to be Ok so I installed and been up and running on latest version for 24 hours....
Had a few FC's in the beginning while changing the language to English (I have a feeling that some of my already installed apk's caused the issue) . I did do a test run before restoring my stuff and didn't have any issues during initial setup and the phone auto corrected language based off sim during initial setup.
Haven't gotten a chance to fully test this build, but I know that the issue that I was having with the native tethering soft rebooting the phone every couple of hours when active is gone! After a few more days of messing with it I will post any other issues that I come across
Sent from my Moto Razr M on cm13 4-16-16 using XDA Free mobile app
Any clue about why I'm getting error 7 while finishing the last steps of the ROM flashing procedure?
Hello XDA, I have been working on an Aosp-ish nougat rom for our beloved trltetmo. It has nearly no features yet, since it's an AOSP ROM. I'm a Nexus dev, and just recently started working on the trltetmo because I bought one. I had a marshmallow rom and kernel(but tend not to release stuff to anyone to avoid drama and the eta requests).
Downloads: https://www.androidfilehost.com/?a=show&w=files&flid=111459
I have uploaded my work to GitHub: http://github.com/TrlteNougat
For now until I get my gpu back, you have to flash this kernel for MM bootloader support: https://www.androidfilehost.com/?fid=529152257862667083
Known issues:
- Camera is wonky. It's going to be difficult to fix
- The phone acts like it's a dual sim phone, no usability is sacrificed, it just shows two APN settings and the carrier on Dialer
Features:
None yet, it's AOSPish
What is being worked on:
Bluetooth
Call audio (mixer_path issues)
The kernel source is up: https://github.com/TrlteNougat/kernel_samsung_trlte/commits/n7.0
Manifest located here: https://github.com/TrlteNougat/manifest
Nice! Subscribed.
Test build
https://www.androidfilehost.com/?fid=24723757092306996
This one doesn't reboot randomly. Still has ril and Bluetooth errors. Sound doesn't work. Camera does.
I m not dev. But great to see work on 7 ...cheers to all devs...hoping for a stable one soon thx again
I'm keeping my eye on this thank you
Sent from my SM-N910T using Tapatalk
Ril is now partially working. I can send and receive texts. Calls cause a soft reboot, but shouldn't be hard to fix. Still no data connection yet, but that'll be fixed soon enough. Wifi connects but doesn't access internet for some reason. I haven't looked into that any.
Because why not
improper bootloader and in some cases modem can cause Wi-Fi to behave similar to how you have described. I'm not a TMO user but I think there should be several versions newer than OK2
if you have any desire to return to 5.1.1 or keep the option open to do it in the future, you may want to steer clear of the newest 2 or so bootloaders as they may prohibit further downgrading. if TMO is anything like Sprint, anything PE2 and older should still permit downgrades. newer versions I have not tested or seen any info on the topic.
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Sterist said:
[QRCODE][/QRCODE]ok I did a quick check and you are in fact on a 5.1.1 modem. I don't know if you've updated your bootloader but I get the feeling you would know if you have or not lol
all TMO MM firmware is newer than the Sprint firmwares (PB5, PC1, PD1, PE1, PE2) that I know to not prohibit downgrades, so you're on your own there.
if you believe the test builds to be compatible with the Sprint model, I'd be happy to help test as time allows for it
Click to expand...
Click to collapse
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Manan79 said:
910T can be downgradable to DOK2 but not below that (unless you use work around and flash 910T2 firmware, which will allow you to go to 4.4.4 BL , and still can come back to latest) but thats a different story, regardless of that , however , you can anytime switch among DOK2 to PE3 to PG2 in any order. I think android N for 910T should be tested on EPG2 and not on DOK2 , atleast should give it a try on EPG2. I think the dev @USA-RedDragon , already must have tried all bootloaders and basebands , i m just replying to above posts.
Click to expand...
Click to collapse
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
USA-RedDragon said:
I tried EPE3 on mm but got too frustrated with the issues. So I've been weary to try it again. But you do have a point that I should try with newer bl/modem combos. I've got a mm rom compatible with epe3, so I might as well flash that. The Odin files are on my desktop staring me down
Click to expand...
Click to collapse
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Manan79 said:
to make it easier ,why dont you just flash EPG2 BL and CP using odin (as opposed to entire MM rom) .and see if it fixes any of the issues with current N build.
Click to expand...
Click to collapse
I'll do that. Progress is still ongoing with all this. But this week I've been busy with an Android Dev's biggest bane: a full-time job ?
USA-RedDragon said:
Side note, the logs point to something bring wrong wkth the code and not a bl/modem -> rom compatibility. But I could be wrong. Never hurts to try
Click to expand...
Click to collapse
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Manan79 said:
sure ,i do understand that I do want to ask , how about xda devs who work for CM14 unofficial? i dont see much active devs on this thread, i would have thought all the note 4 devs who worked on CM13 unofficial would jump on this to help you out
Click to expand...
Click to collapse
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
USA-RedDragon said:
Eh. I have other devs at my disposal. Most don't use XDA, and I tend to not either, but this(like any major version bump on a Samsung) is a big endeavor, so I made the thread for people to jump in if they wanted
Click to expand...
Click to collapse
got it thx, let me know if you want me to test 910T builds, however i do need sim to be working for incoming/outgoing calls , cant live without that rest all i can test.
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20200304-UNOFFICIAL-judypn
lineage-17.1-20210304-UNOFFICIAL-judypn.zip
drive.google.com
Prev.:lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Click to expand...
Click to collapse
Is LOS 18.0 "Pre Alpha or Alpha" suitable for daily use?
Haven't noticed exact description what works and what are the current bugs.....
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
Click to expand...
Click to collapse
Do you think most of the bugs will be cleared out by the end of the year? Also, which kdz should I use if I want band 71 support?
camray00 said:
Do you think most of the bugs will be cleared out by the end of the year? Also, which kdz should I use if I want band 71 support?
Click to expand...
Click to collapse
I don't know anything about the bugs, but for b71 2 of the roms have it; US OP Pie (no Q yet) and KR OP which is Korean Open (Q version available) has b71 also.
cheers
AsItLies said:
I don't know anything about the bugs, but for b71 2 of the roms have it; US OP Pie (no Q yet) and KR OP which is Korean Open (Q version available) has b71 also.
cheers
Click to expand...
Click to collapse
I was thinking it might be possible to grab the modem partition from sprint or unlocked pie and write them over before installing this ROM. Would that work, or would it be incompatible?
camray00 said:
I was thinking it might be possible to grab the modem partition from sprint or unlocked pie and write them over before installing this ROM. Would that work, or would it be incompatible?
Click to expand...
Click to collapse
I'm not sure, have not tried that. I've read others suggesting the same thing but don't know if they've had success with it. I'd bet it wouldn't as there are so many threads, in various model phones, about which rom supports which bands. If that problem could be resolved by simply using the modem partition from a diff rom, it happening would almost certainly be common knowledge and many threads with various modem partitions available, but there aren't.
AsItLies said:
I'm not sure, have not tried that. I've read others suggesting the same thing but don't know if they've had success with it. I'd bet it wouldn't as there are so many threads, in various model phones, about which rom supports which bands. If that problem could be resolved by simply using the modem partition from a diff rom, it happening would almost certainly be common knowledge and many threads with various modem partitions available, but there aren't.
Click to expand...
Click to collapse
Ended up trying it and it prevents boot to system and recovery. I replaced all 4. modemst1,modemst2,modem_a,modem_b
I think we'll have to wait for them to make Q for v405qa unlocked.
I used v405ebw with lineage 18. VoLTE and VoWiFi aren't supported, which basically makes Mint Mobile unusable except for data.
camray00 said:
Ended up trying it and it prevents boot to system and recovery. I replaced all 4. modemst1,modemst2,modem_a,modem_b
I think we'll have to wait for them to make Q for v405qa unlocked.
I used v405ebw with lineage 18. VoLTE and VoWiFi aren't supported, which basically makes Mint Mobile unusable except for data.
Click to expand...
Click to collapse
I'd suggest another option, as 405qa Q arrival is ???, use the korean open 30e. That's what I have. One mod makes it quite workable; copy the US Open /OP partition (from Pie) and use it instead of the KR Open partition. Everything works, including vowifi and volte. And it does get b71. There's only 1 other small change needed to get vowifi to work.
It's very solid and haven't had any trouble with it at all. Something to consider.
I just found out that a great deal of work can be done with Cellular Support via the Qualcomm PDC tool.
AsItLies said:
I'd suggest another option, as 405qa Q arrival is ???, use the korean open 30e. That's what I have. One mod makes it quite workable; copy the US Open /OP partition (from Pie) and use it instead of the KR Open partition. Everything works, including vowifi and volte. And it does get b71. There's only 1 other small change needed to get vowifi to work.
It's very solid and haven't had any trouble with it at all. Something to consider.
Click to expand...
Click to collapse
Can you link the Korean open download? Also, what is the small change for VoWiFi?
Yes it's on this link. It's at the top of the list, the KR Open, 30e is the last one in the beginning section.
The other change is minor, have to enter the service menu with the dial code and it's one of the SVC (iirc) fields you have to enable vowifi. I can find it if you decide to do it.
There's a little 'trick' u need to do when cross flashing, to avoid the 'NT_Error' thing when u first boot up. It doesn't cause a problem, it's just annoying. Just after doing a partition DL of the rom, let it boot of course, to finish. Then shut it off, don't touch anything. Then use LG up and do a refurbish with same rom. No more nt-error code thing.
Also, even though the firmware page (above) doesn't indicate it, that rom does have b71. I have a screen shot of the phone using lte discovery connected to b71 on that rom. It's there.
AsItLies said:
Also, even though the firmware page (above) doesn't indicate it, that rom does have b71. I have a screen shot of the phone using lte discovery connected to b71 on that rom. It's there.
Click to expand...
Click to collapse
I'm trying to boot TWRP. When I run
Code:
fastboot boot judypn_TWRP_bootable-metadata.img
it reads out this:
Code:
downloading 'boot.img'...
OKAY [ 0.942s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.946s
This is after flashing the Korean Open version. I'm not sure what to do. I made sure USB Debugging was on and changed the driver to the official LGE one, but no luck.
I tried everything on google. Still no luck.
camray00 said:
I tried everything on google. Still no luck.
Click to expand...
Click to collapse
Hi, so we've hijacked this thread long enough, let's move this over to this thread which is kor open specific.
Sorry about the hijack xenius.
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
xenius9 said:
Initial topic - https://forum.xda-developers.com/lg-v40/development/android-10-0-0-lineageos-17-0-v40-t3970119
So far I am only doing compilation without testing the result.
Download:
LOS-17.1
Latest build: lineage-17.1-20201118-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/1QT_yRNtydEZmplZvl5oSq1xiySv53NK9?usp=sharing
LOS-18.0
Latest build: lineage-18.0-20201126-UNOFFICIAL-judypn
https://drive.google.com/drive/folders/17d7f1QdUoljNnU00VRJYC776KhAwIq4R?usp=sharing
Contributors
xenius9, SGCMarkus
Many thanks to SGCMarkus for the sources.
Click to expand...
Click to collapse
Thank you for your work, @xenius9 - спасибо большое. Using lineage-17.1-20201118-UNOFFICIAL-judypn on Sprint LM-V405UA for about a month without problems.
praiseeee said:
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
Click to expand...
Click to collapse
You should get fastboot working via 9008 guide (I suggest not to wipe lafs on both slots), then fastboot TWRP.
praiseeee said:
Please help me. My LG v40ua is switched into los-18.0 and recovery is also los-18.0. Now I want to change back to the previous system, but I can't do it without root. Please tell me what to do, thank you
And my phone can't enter FastBoot mode
Click to expand...
Click to collapse
If you install this apk (only on los), it will allow you to switch to the other side and reboot recovery. It's hard coded (I changed the original file) to boot to recovery after you select the other slot. Did it for the exact situation you're experiencing.
cheers
LOS 17.1 updated
xenius9 said:
LOS 17.1 updated
Click to expand...
Click to collapse
Is it stable? Good for daily driver? Thanks!
Hello forum!
I have LG LM-V405QA and would like to have a ROM flashed that removes all Google everything. I have flashed ROMs in the past, but have already spent too much time researching with no results. I am in California, USA.
This is a serious inquiry. Please help.
Thank you.