Develop Bugs

Wifi Region code Connectivity problems: A Solution

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.

[Q] Very low screen bright after reboot

Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot

reypescador said:
Hello everybody,
I,ve read all around the forum but I couldn´t find information about my problem so i try it here.
From stock V500 20d I rooted and Installed TWRP 2.7.1.0 thanks to the good information in the Forum. After that, I've installed the ROM CM11 (M10) and, from the first reboot, the screen bright is very low. I hardly could do the first configuration and when it finished I selected the full bright.
After some time working it seems that it recovers some bright and I can down a little bit the bright from top.
Every time I restart the device I have the same bright issue.
Can anyone help me?.
Thanks a lot
Click to expand...
Click to collapse
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411

muiriddin said:
Extremely common problem when you were on the 4.4.2 base and are now an AOSP based rom. You either need to change kernels to RedKernel or flash the tablet back to the 4.2.2 base and then reflash your CM rom.
RedKernel info is here: http://forum.xda-developers.com/lg-g-pad-83/development/kernel-redkernel-t2856297
4.2.2 base info is here: http://forum.xda-developers.com/showthread.php?t=2719411
Click to expand...
Click to collapse
Thank you very much
I try to read the info and decide what to do.
Thanks again

Ok it´s done
First I´ve installer V500-4.2.2-Base from recovery, I have reinstalled CM 11 and everything OK.
I have tried a step beyond and I have installed [KERNEL][v500][4.4.4][AOSP] RedKernel [16/09] (everybody seems to be very happy with it) but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help

reypescador said:
but, after install synapse I run it and appears "No UCI support detected". Seems that kernel doesn´t support it.
Thank you again for your help
Click to expand...
Click to collapse
Seems to be problems with Super SU but I can´t solve them at the moment

You must install the UKM scripts from recovery. Read the op from the red kernel thread...

edisso10018 said:
You must install the UKM scripts from recovery. Read the op from the red kernel thread...
Click to expand...
Click to collapse
What he said!
This confused me at first too. In the very early days of redkernel he included his own forked version of the UKM scripts those have been removed because the UKM script maintainer agreed to merge his changes and therefore he doesn't have to maintain his own copy (better for all involved so he can focus on kernel development). Search the thread you will find a link to where you can download the official UKM scripts and your problem will go away.
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...

muiriddin said:
I currently run redkernel on the 4.4.2 base myself. I have not reverted to the 4.2.2. base since my last factory restore. I am very happy with this configuration...
Click to expand...
Click to collapse
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium

ncguy68 said:
Originally I had issues with the sd card mounting with the 4.4.2 base. Has this been fixed with Red Kernel?
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.

muiriddin said:
I had the same problems. Mine was two fold, my sd card was dying (I have since got a new one) and the 4.4.2 base was still sometimes having an issue that sd card monitor would show as a bad removal. This was even with the new sd card. Once I switched to Infected's build of slimkat with the redkernel I have not had a bad removal (after running this way now for over a month) and the sd card monitor used to track at least one bad removal a week with stock 4.4.2. I have no idea if this will help others but it is working so far for my device. I am always running sd card monitor since I had problems and it is still reporting a clean record.
Click to expand...
Click to collapse
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium

ncguy68 said:
Thanks. I am already using Infected's Slimkat, but I am still on 4.2.2 base. I may flash 4.4.2 base and give redkernel or mani kernel a try.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.

muiriddin said:
You didn't ask, but my approach would be:
Use LG tool to revert to 4.4.2 stock
Root with towel root
Install recovery and loki (I need to get you a link for this, but it involves editing a batch file to tell it to still install with revision d instead of b)
reboot recovery using adb, and immediately unplug cable
flash a recovery designed for 4.4.2 (2.7.0.1) from this link http://forum.xda-developers.com/showthread.php?t=2551499
Then install infected slimkat, redkernel and the ukm zip files
I never use the 4.4.2 base files to flash the device to 4.4.2 I always use the LG Tool and go from there.
Click to expand...
Click to collapse
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium

ncguy68 said:
Just curious … is there something wrong with flashing the base files to switch between 4.2.2 and 4.4.2?
Now that I have two Gpad's I plan to install 4.4.2 base on one and compare it with 4.2.2 base on the other. Just wonder if I can tell any difference.
Thanks for the info.
Sent from my LG-V500 using xda premium
Click to expand...
Click to collapse
I am unaware of a problem with the 4.4.2 base files provided. I have just never used them, I already had the LG Support Tool downloaded and it was easiest to use the path I knew and was comfortable with.
The key thing (and why I run the 4.4.2 base instead of the 4.2.2. base) that is different is the brightness at its lowest setting. The 4.2.2 base on many of the V500's suffers from alternating light and dark spots on one side of the tablet when viewing the tablet in low light with the brightness at its lowest setting and viewing gmail (any app with a white background basically). I use my tablet mostly in dark conditions like this (man I make it sound like I live in a basement somewhere *laughs*). The 4.4.2 base firmware changes the tablet so it functions well at the lowest brightness.
The first picture in this thread shows the screen problem I refer to (although not on a white screen):
http://forum.xda-developers.com/showthread.php?t=2553055

[ROM][D802][5.0.2][V39A] Thank You Verizon

BEWARE: This is only for D802!
In short: extra softkeys, nice messasing (bigger text box and floating circle - contacts app has floating circle too) and music app, no lagg i.e. on YouTube like rest of LP ROMs, and of course wireless storage. Verizon gave the perfect update.
So, this is a D802 ROM fully based on V39A, which is Verizon's stock 5.0.2 firmware.
Instructions:
Recommed to use latest TWRP by blastagator
Do a full wipe
Flash ROM zip (DONT reboot phone yet): Mega - ROM
Flash signal fix right after flashing the ROM, THEN REBOOT AFTER FLASHING THIS: Mega - Signal fix
After first reboot, finish startup wizard, reboot back into recovery and flash fix for proper baseband, correct D802 info and possibly better connectivity: Mega - Fix V2
Reboot.
Add-on (optional): LG Backup (seems Verizon does not have this app installed by default) Mega - LG Backup
How to enter TWRP recovery (thanks to @marek_poland):
Power off. Press and hold vol- and power button until LG logo appears. Then release and press and hold vol+ and vol- until reset screen shows up. Press yes twice and you enter TWRP.
I have no mobile data?!
Set APN manually in settings.
I get a weird sim card icon status bar?!
Try flashing the modem from post #16.
My rear led stays on forever when I enable notification led
Either disable notification led or flash Xceed kernel. Note: flashing any other D802 will remove the floating pop up circle in messages, contacts & music app.

Reserved.

natalya said:
Pictures speak louder than words. This is what I have on my D802 after flashing VS980 based 5.0.2 stock LP rom. Fully working and YouTube does not lagg like the rest LP I tried.
In short: extra softkeys, nice messasing (bigger text box and floating circle - contacts app has floating circle too) and music app, no lagg, and of course wireless storage. Verizon with the perfect update to 5.0.
Sent from my LG-D802
Click to expand...
Click to collapse
link please? and how to flashed vs980 rom on D802

The Verizon model is supports all bands since it is a worldwide phone. There is a Official Lollipop 39A flashable version and several others (stock extreme, stock minimal, etc) over in the Verizon Dev thread.
I am NOT suggesting you flash it, but giving some info. I think techinically it will work though.

player911 said:
The Verizon model is supports all bands since it is a worldwide phone. There is a Official Lollipop 39A flashable version and several others (stock extreme, stock minimal, etc) over in the Verizon Dev thread.
I am NOT suggesting you flash it, but giving some info. I think techinically it will work though.
Click to expand...
Click to collapse
is Dori's LP kernel compatible with the verizon roms?

Vz roms have Vz Kernels, so if we flash it in D802, won't it give Bootloops?

Dont just flash stuff, you'll definetly end up in bootloop if not bricking your phone!
Either tonight or tomorrow I can try to upload this D802 ready ROM. But it will be for D802 only.
Update: After I started the upload process I remembered I forgot a few files. Did not want to re-upload so I made a small flashable zip containing those files. You will have to flash the ROM and then another zip right after. Flash both zips right after each other, don't reboot phone in-between flashes. Consider this your warning.
Update2: Everything added to OP. Maybe I will get this thread moved to D802 development section later. But I'm done for now. Enjoy.

natalya said:
Dont just flash stuff, you'll definetly end up in bootloop if not bricking your phone!
Either tonight or tomorrow I can try to upload this D802 ready ROM. But it will be for D802 only.
Update: After I started the upload process I remembered I forgot a few files. Did not want to re-upload so I made a small flashable zip containing those files. You will have to flash the ROM and then another zip right after. Flash both zips right after each other, don't reboot phone in-between flashes. Consider this your warning.
Update2: Everything added to OP. Maybe I will get this thread moved to D802 development section later. But I'm done for now. Enjoy.
Click to expand...
Click to collapse
Thank you, waiting for the download link

jaidev.s said:
Thank you, waiting for the download link
Click to expand...
Click to collapse
Links are in OP

natalya said:
Links are in OP
Click to expand...
Click to collapse
Downloading
What process did you go through to convert for D802?

natalya said:
Links are in OP
Click to expand...
Click to collapse
Can u kindly post the md5 value of the rom file, pls?

Can i flash directly v39a kdz on d802??
Sent from my LG-D802 using XDA Free mobile app

Dorimanx lolipop kernel supported?

I am using LG G2 32 GB D 802 with Cloudy 2.2. Currenly installed this rom + Dorinmax 2.2 .Everything working perfectly.
P.S Found only problem with signal.Not weak signal.Just dropping and come again.

@Mvalev95 try to logcat the problem, perhaps we just need to replace some libraries to fix the issue, I see the awesome wireless storage button I wonder why International doesn't have all these stuff.
Hmm I see a signal fix for the rom hope that is for the signal drops but I'll check it out later,
Thankyou for the rom port

Fixed it. Flashed LPBaseBand d80230e. Here a LP Base Band D80230e

Mvalev95 said:
Fixed it. Flashed LPBaseBand d80230e. Here a LP Base Band D80230e
Click to expand...
Click to collapse
Nice that you have found the solution to the problem. I am going to miss the kitkat dropdown menu again from Og3 but I'll make a backup and test the rom.
And the OP can definitely ask an moderator to move this to the d802 forum as this stock rom is an port from the Verizon V39A to the d802 and also to prevent some "newbies/rookies" who don't read to flash it.
But ofcourse it can only be moved IF the work is from the OP and if there are proper credits in the OP
I just wonder how why are there also L01F mentions in the vs980 v39A Rom?

Cannot get through start wizard, after language select and pressed Next pop up info "Wait for activation" and stayed here. Any idea what to do?

marek_poland said:
Cannot get through start wizard, after language select and pressed Next pop up info "Wait for activation" and stayed here. Any idea what to do?
Click to expand...
Click to collapse
Just back to language select and again next it will fix.

wulsic said:
Nice that you have found the solution to the problem. I am going to miss the kitkat dropdown menu again from Og3 but I'll make a backup and test the rom.
And the OP can definitely ask an moderator to move this to the d802 forum as this stock rom is an port from the Verizon V39A to the d802 and also to prevent some "newbies/rookies" who don't read to flash it.
But ofcourse it can only be moved IF the work is from the OP and if there are proper credits in the OP
I just wonder how why are there also L01F mentions in the vs980 v39A Rom?
Click to expand...
Click to collapse
Nice reminder. Thanks. New fix added in OP (easier to upload a 25MB file than 1.5GB+ file).
This includes:
* As Verizon is in the US, they have US as target for connectivity. Most 30B firmware outside US targets what they name COM. So, this zip changes the target from US to COM.
* Fixed baseband showing unknown in About Phone (modem now being used is from NEU Europe 30B KDZ - you can flash any modem you'd like).
* Changed L01F to D802.
Requests are welcome but don't expect big changes. I have been using this ROM for about a month now and I only share the settings I make for myself.

Any idea to port 5.0.2 from SM-P900 to SM-P600?

OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?

That would be great and highly appreciated. :good:

kornelius1982 said:
That would be great and highly appreciated. :good:
Click to expand...
Click to collapse
start from
http://forum.xda-developers.com/sit...pub-2900107662879704:4763122713&ie=ISO-8859-1
ask help from sktjdgns1189 and arter97

enotar said:
OK, hardware are very similar despite of the screen differences that can be adjust 12.2 instead of 10.1.
Resolution Is the same, processor is the same so I am trying to understand where are the blocks on the road. I am downloading the firmware but I don't know where to start. What are the real differences that make the firmware incompatible. The goal here is to have LL on the 10.1 2014 edition wifi. Am I loosing my free time?
Any ideas?
Click to expand...
Click to collapse
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."

Compile a kernel almost all the effort (95)% to port a room.
Here´s the first thing we need to do.
http://forum.xda-developers.com/android/software/ultimate-guide-compile-android-kernel-t2871276
I´m downloading kernel source of sm-p901.
Here is the index sm-p900´s kernel sources:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=SM-P90
wulkanat said:
Maby you only need a Touchwiz 5.0.2 Kernel for SM-P600. I also tried to port such a ROM, but I failed with normal Methods. Black screen and a reeboot if I try to flash a rom from GalaxyTab S, if I flash another ROM for SM-P600 same issue. But with flashing the right Kernel, it works...
"Steps for android 4.4 and newer
Open dsixda's Android Kitchen
Decompile both boot.img/kernel
Open both init.environ.rc files
In CM/AOSP kernel replace BOOTCLASSPATH by the one from PORT boot.img ROM
In CM/AOSP kernel do these changes:
--> ro.secure=1 to ro.secure=0
--> ro.debuggable=0 to ro.debuggable=1
--> persist.sys.usb.config=mtp to persist.sys.usb.config=mtp,adb
--> ro.adb.secure=1 to ro.adb.secure=0
Save and recompile kernel
Use CM/AOSP modified kernel in your rom."
Click to expand...
Click to collapse

Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk

If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device

enotar said:
Just dowloaded the P900 Rom and created the zip. I will take a look at kernel tomorrow. I didnt tweak the tom at all for now. Why matter and loose time before boot.
Edit: I am thinking of switching to T900 5.1.1 Rom just out to try this....
http://forum.xda-developers.com/gal.../t900xxuboh4-galaxy-tabpro-12-2-wifi-t3192933
Maybe with an existing P600 kernel, not sure.....
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
would be better to use the T900 Version with a existing Kernel (don't know if it works ). Just to have it more simple. If it does not work... we can use the P900 Version
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
Wbdsgnr said:
If I may chime in; Is there a detailed list available of the hardware (sensor chips and stuff) in the p900 and p600. The kernel should be mostly identical except for some different kernel modules and perhaps the memory mapping towards the flash memory. Not sure about a needed bootloader change? Did anyone try booting with the p900 kernel yet? How would you go about testing it without a lollipop ROM the start on.. I have extensive knowledge on Linux on embedded platforms but nothing on android.. Mostly because there's no information available like datasheets and things like proprietary bootloaders and the lack of JTAG. Don't want to brick my device
Click to expand...
Click to collapse
good idea, I will try to boot with T900 Kernel first (Firmware is downloading right now ), but I will also give the P900 Kernel a try, if the T900 Kernel does not work
Found this in a ROM in SM-P900 Forum:
"If you are on KitKat•Make a EFS backup
•Make a Nandroidbackup.
•Download rom and place on your ExternalSD.
•Flash the Lollipop bootloader before installing the rom ar it won't boot.
Here you find the Lollipop Bootloader and Odin package that you need to install it on your device when in download mode.
If you want to revert back to KitKat rom you need to install the kitkat bootloader! You find it here and you flash it with Odin.
•Full wipe is needed and now you can install the rom."
Maby the Bootloader is the Reason why it does not boot?

I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.

enotar said:
I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
already tried it out with a Tab S ROM . And for now, (~10 sec left) i'm on KitKat back.
Did not work. But it was a try... so, black screen, and reboot. Kernel or bootloader? It does not Boot with ValexKernel too, but this is a AOSP kernel. (and yes, I'm back on Kitkat)

Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk

enotar said:
Good! So we need to modify kernel.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I have already a Ubuntu iso, so I will try to install it in VMware Which Kernel? from P900 or T900? I will try the P900, if there is no a reason why not.

I don't think this is a good idea to flash T900 unchanged kernel, I am not sure you can come back to 4.4.2 or any okf the AOSP ROM or CM12.
Click to expand...
Click to collapse
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.

P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk

enotar said:
P900 is 5.0.2 and T900 is 5.1.1 I am working on T900 myself but no succes so far.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Nice!

Wbdsgnr said:
I think it's possible to just boot the kernel without flashing it, using fastboot. This would avoid the risk of getting stuck in some weird brick. The real problem here is the boot loader. I'm not sure wether the one from p900 is suitable.
Click to expand...
Click to collapse
The one who made the TW 5.0.2 ROM for SM-P605 just get it too...

I'm hoping the same that someone will port p900 to p600 as both are 99% identical. @enotar, I think T900 not a Note series Tab and doesn't have S-pen functionality. So, you might wanna try P900 rom.

T900 not a Note series !!!! doesn't have S-pen functionality

alex22280 said:
T900 not a Note series !!!! doesn't have S-pen functionality
Click to expand...
Click to collapse
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk

enotar said:
Right but this is the least of our problem.
If we could boot something, we could star fixing things.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
ask for help from sktjdgns1189 ,Alan-B and arter97 (I am use a port 5.0.2 for my P605 from Alan - B)
for kernel ....arter97

LineageOS 17.1 18.0 new builds

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.