[Rom][Unoffical][CM-13.0] D2SPR CyanogenMod 13.0 ABANDONED

[jeremybrown82]

Your welcome, I actually completely forgot the fact that there was a security update. I just felt like it had been a while since the last build.



I think someone posted a like to a guide @madbat99 made on getting 4g working a couple pages back. It had some weird steps involving flashing the rom, gapps, and vm fix, booting to Android, then dirty flashing the ROM and the VM fix again.

Thanks, you are a life saver, I finally got it working thanks to dirty flashing! 4G FTW!

 

[mikel81]

Has anyone had trouble with screen rotation? The only way I have been able to get the screen to rotate was by fullscreening a youtube video but then it was stuck sideways even after closing the app. I had to turn the screen off and on to get it back normal.

 

[Lrs121]

First official nightly is out. As usual, with the release of the official nightlies my builds are done. Please redirect all further questions and problems to the proper official CyanogenMod thread.

 

[jeremybrown82]

First official nightly is out. As usual, with the release of the official nightlies my builds are done. Please redirect all further questions and problems to the proper official CyanogenMod thread.

LRS121, you seem like an elite coder, so please allow me to ask you this, is there anyway to get cm13 working with LTE AND playstore apps from 6.0?

Right now I am able to install the Virgin Mobile Patch, and dirty flash etc.

It works, except then when I proceed to install gapps 6.0 it seems incompatible with the underling dirty flash.

I know this, because 4.4 open gapps is flash-able and working on the stock rom, and D2LTE which seems compatible with gapp 4.4, however cm12 or cm11 is not.

I am thinking some of the framework is not forward compatible with the dirty flash and gapps.

Is there any way to remedy this? Good job on all your hard work!

Jeremy

 

[Lrs121]

LRS121, you seem like an elite coder, so please allow me to ask you this, is there anyway to get cm13 working with LTE AND playstore apps from 6.0?

Right now I am able to install the Virgin Mobile Patch, and dirty flash etc.

It works, except then when I proceed to install gapps 6.0 it seems incompatible with the underling dirty flash.

I know this, because 4.4 open gapps is flash-able and working on the stock rom, and D2LTE which seems compatible with gapp 4.4, however cm12 or cm11 is not.

I am thinking some of the framework is not forward compatible with the dirty flash and gapps.

Is there any way to remedy this? Good job on all your hard work!

Jeremy

I've mentioned this once previously but I'm not certain this helps. You must flash gapps when installing the rom, before you boot into system for the first time. This is an absolute requirement with Android m and likely anything newer. Part of that requirement is the use of gapps packages meant for Android m. This may require flashing the gapps package when updating to ensure that gapps are installed. So, I'd recommend, when first setting up, you'll wanna flash the ROM, gapps and the fix, reboot, the flash the ROM and fix. Also keep in mind cyanogenmod messes with a ton with the framework.

 

[jeremybrown82]

I appreciate your prompt, and curious feedback.

You suggestions are great! I will try them out.

Just wanted to clarify a couple things, Right now I have J2D rom flashed on my virgin moble with 4g working.

I have removed knox, loving how everything just works, but interested in furthering the development of cm13 on (sph-l710)

In your sentence: "So, I'd recommend, when first setting up, you'll wanna flash the ROM, gapps and the fix, reboot, the flash the ROM and fix."

when you say ROM, in both those instances, I am assuming you mean cm13? Is this correct?

What do you recommend formatting after each flash?

I found a problem, that with flashing anything other than d2LTE (tested newest updated release), unless I format the /Data partition in twrp 3.0.0-0, after having install a stock rom, via odin, I get an error message upon flashing cm11,12, (haven't tried 13) but I assume it is the same deal.

The error message states that data is incompatible and will not flash. I have erased the /Data partition, and found that it proceeds to install the new cm11/12 when attempting to do so.

So, do you recommend erasing the /Data partition only? Or do you recommend erasing Dalvik, and cache as well?

It seems I get errors like, system not responding, along with other errors, but I may have never tried flashing gapps immediately after installing cm11/12. It seems like I have flashed a million different ways.

Does dirty flashing only relate to /system partition?

Which /partition is crucial for 4g to correctly work?

Please describe the steps in greater detail.

I appreciate your hard work and contribution to the android community!

Currently running: Virgin Mobile (sph-l710)
(open gapps 4.4)
(offical stock J2D ROM, spr)
(Knox removed)
(4G working)
(rooted)
(TWRP-3.0.0-0)

 

[Lrs121]

I appreciate your prompt, and curious feedback.
You suggestions are great! I will try them out.

Just wanted to clarify a couple things, Right now I have J2D rom flashed on my virgin moble with 4g working. I have removed knox, loving how everything just works, but interested in furthering the development of cm13 on (sph-l710)

In your sentence: "So, I'd recommend, when first setting up, you'll wanna flash the ROM, gapps and the fix, reboot, the flash the ROM and fix."
when you say ROM, in both those instances, I am assuming you mean cm13? Is this correct?

I found a problem, that with flashing anything other than d2LTE (tested newest updated release), unless I format the /Data partition in twrp 3.0.0-0, after having install a stock rom, via odin, I get an error message upon flashing cm11,12, (haven't tried 13) but I assume it is the same deal. The error message states that data is incompatible and will not flash. I have erased the /Data partition, and found that it proceeds to install the new cm11/12 when attempting to do so. So, do you recommend erasing the /Data partition only? Or do you recommend erasing Dalvik, and cache as well? What do you recommend formatting after each flash?


It seems I get errors like, system not responding, along with other errors, but I may have never tried flashing gapps immediately after installing cm11/12. It seems like I have flashed a million different ways.

Does dirty flashing only relate to /system partition?
Which /partition is crucial for 4g to correctly work?
Please describe the steps in greater detail.

I appreciate your hard work and contribution to the android community!

Currently running: Virgin Mobile (sph-l710)
(open gapps 4.4)
(offical stock J2D ROM, spr)
(Knox removed)
(4G working)
(rooted)
(TWRP-3.0.0-0)

I'll address the need to wipe /data first.
When coming from stock or most stock based roms to newer versions of android and vise-versa you must wipe the /data partition. From my understanding this is because of the changes Samsung made to how android handles or formats the /data partition in their modified version of android that makes it incompatible with most roms that is AOSP based like CyanogenMod. I don't know why the d2lte builds worked but I ran in to that issue back when cm-12.0 (android 5.0) came out and a wipe was the only fix.

Though when installing new roms, I typically recommend wiping /system, /cache, /dalvik, and /userdata (not including internal storage) before installing the rom.
However, everything but the external sdcard should be wiped if the conditions listed above have been met.

When I said Rom, I was meaning any Android 6 based rom including cm-13.

Dirty Flashing, however, refers to the act of flashing a rom (not stock) without wiping /userdata or other partitions. So yes it does involve the system partition, but usually it's not the only one that is effected, /boot is usually included as well.

I don't recommend any wiping after flashing anymore, not since early android gingerbread days. I dont know how the Virgin fix works, but with the opengapps, and maybe others, for android 6 there are important files stored in cache until the first boot, after installing a new rom, that are needed or will cause the exact problems you are describing when you get errors like the system is not responding. Flashing the gapps after the rom has started the first time after installing it will cause the same problems.

Having to flash gapps before the first boot is a new thing related to how android 6 handles app signing and how Google signs the Google apps for the /system partition. Here's a reference that I used to understand why. https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0

Last, from what I can tell, the problem with 4G isn't related to any specific partition. However, it does somewhat affect the /system partition since, from what I know, the problem stems from the APN's. I don't know if they are wrong, not included, or just handled wrong, but I do know these kinds of issues generally stem from some sort of APN issue. https://en.wikipedia.org/wiki/Access_Point_Name

An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.

• Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
• Add the rom to the flash queue (eg. cm-13.0)
• Add an android 6 compatible gapps to the queue
• Add the Virgin fix to the queue
• Run the flash queue (or flash the above file individually without rebooting)
• Reboot into system for the first time
• Once booted reboot into TWRP
• Add the same rom zip to the flash queue
• Add the Virgin fix to the queue
• Run the flash queue (or flash the above file individually without rebooting)
• Reboot to system
• Everything should be functioning (at least mostly)
• Enjoy

It's starting to get late and I am tired while writing this, so if I forgot something or something isn't clear please let me know.

 

[Lonelyskatter12]

First official nightly is out. As usual, with the release of the official nightlies my builds are done. Please redirect all further questions and problems to the proper official CyanogenMod thread.

Just wanted to say, thank you for giving us unofficial Cm-13.0 builds while the official builds were being worked on.
You're the best. :good:

 

[jeremybrown82]

Your welcome, I actually completely forgot the fact that there was a security update. I just felt like it had been a while since the last build.



I think someone posted a like to a guide @madbat99 made on getting 4g working a couple pages back. It had some weird steps involving flashing the rom, gapps, and vm fix, booting to Android, then dirty flashing the ROM and the VM fix again.

I'll address the need to wipe /data first.
When coming from stock or most stock based roms to newer versions of android and vise-versa you must wipe the /data partition. From my understanding this is because of the changes Samsung made to how android handles or formats the /data partition in their modified version of android that makes it incompatible with most roms that is AOSP based like CyanogenMod. I don't know why the d2lte builds worked but I ran in to that issue back when cm-12.0 (android 5.0) came out and a wipe was the only fix.

Though when installing new roms, I typically recommend wiping /system, /cache, /dalvik, and /userdata (not including internal storage) before installing the rom.
However, everything but the external sdcard should be wiped if the conditions listed above have been met.

When I said Rom, I was meaning any Android 6 based rom including cm-13.

Dirty Flashing, however, refers to the act of flashing a rom (not stock) without wiping /userdata or other partitions. So yes it does involve the system partition, but usually it's not the only one that is effected, /boot is usually included as well.

I don't recommend any wiping after flashing anymore, not since early android gingerbread days. I dont know how the Virgin fix works, but with the opengapps, and maybe others, for android 6 there are important files stored in cache until the first boot, after installing a new rom, that are needed or will cause the exact problems you are describing when you get errors like the system is not responding. Flashing the gapps after the rom has started the first time after installing it will cause the same problems.

Having to flash gapps before the first boot is a new thing related to how android 6 handles app signing and how Google signs the Google apps for the /system partition. Here's a reference that I used to understand why. https://github.com/opengapps/opengapps/wiki/Notes-for-Android-6.0

Last, from what I can tell, the problem with 4G isn't related to any specific partition. However, it does somewhat affect the /system partition since, from what I know, the problem stems from the APN's. I don't know if they are wrong, not included, or just handled wrong, but I do know these kinds of issues generally stem from some sort of APN issue. https://en.wikipedia.org/wiki/Access_Point_Name

An example of the steps with the assumption someone was coming from the stock android with TWRP installed and everything to be flash stored on the external sdcard. Assuming the user is in TWRP to start.

• Issue a full format of the following partitions, /system, /userdata, /internalstorage, /cache, /dalvik
• Add the rom to the flash queue (eg. cm-13.0)
• Add an android 6 compatible gapps to the queue
• Add the Virgin fix to the queue
• Run the flash queue (or flash the above file individually without rebooting)
• Reboot into system for the first time
• Once booted reboot into TWRP
• Add the same rom zip to the flash queue
• Add the Virgin fix to the queue
• Run the flash queue (or flash the above file individually without rebooting)
• Reboot to system
• Everything should be functioning (at least mostly)
• Enjoy

It's starting to get late and I am tired while writing this, so if I forgot something or something isn't clear please let me know.

This is perfect I will give it a go, thanks. I tried something similar, with the exception of not flashing internal storage /sdcard/emulated/0, but I will do it from ground zero.

 

[jeremybrown82]

This is perfect I will give it a go, thanks. I tried something similar, with the exception of not flashing internal storage /sdcard/emulated/0, but I will do it from ground zero.

Did everything as you said, exactly. 3G works, but 4G does not...

 

[peterfeteråå]

This is perfect I will give it a go, thanks. I tried something similar, with the exception of not flashing internal storage /sdcard/emulated/0, but I will do it from ground zero.

Sent from my GT-I9100 using XDA Labs