Root CM12.1-CAF BETA

[aurey2244]

To anyone still using this ROM, what was the primary reason this ROM didn't work? And how did u make work arounds for it too? I believe it was the dialer giving problems mainly? I could try to port the galaxy grand 2 ROM for us but I can't guarantee anything, I believe what I really have to do is replace a few apps, maybe edit (or swap) the boot.IMG, and lastly edit the updater.sh, I'll give it a whirl and see how far I get, lol who knows I might just try to port an htc sense ROM for us lmao, it's been done for my nexus so I think I'll try to do it for us as well

 

[aurey2244]

Well for people who can't find the camera app in this ROM I found a way to temporarily bring it back. I used luckypatcher to find the app and it has 2 system camera and I looked through some system files and could not find any camera lib in system folder. Please correct me if I'm wrong

I can't remember, what did u need the camera for again? And were u referring to this ROM? You'll have to forgive me for being a total newb, it's been forever since I've been here

 

[GreyWolf42]

I can't remember, what did u need the camera for again? And were u referring to this ROM? You'll have to forgive me for being a total newb, it's been forever since I've been here

I need the camera fix for reasons that I wont go into and yes this Rom, it can be completed its just people finish this on there downtime and it might take another year for it to be an unofficial Rom instead of a beta Rom

 

[GreyWolf42]

could someone help fix the 5ghz band wifi

 

[kfiltz]

I can't remember, what did u need the camera for again? And were u referring to this ROM? You'll have to forgive me for being a total newb, it's been forever since I've been here

Fk camera and everything else except Wi-Fi!! I looked everywhere for reason as to why Wi-Fi doesn't turn on after clean install of CM 12 nor on CM 11 but depends on some thing unknown to me.. Like either cm12 boots without Wi-Fi working Or it boots and bootloops after starting initial setup.. (usually bootloops if gappswere installed)

 

[Ions97]

Ok I'm new here to this forum but I've been using this rom for about a year. So far it's great. It runs well( minor problems will explain). I'm running it with pico gapps and with the xtrememusic v8.9 on it. My only problem which started randomly recently is that when I try to access my downloads in the internal storage any file app including the built in file manager crashes about half way through the list. I've tried everything from factory reset to a complete wipe on everything including reflashing twrp. I cannot get it fixed and would greatly appreciate if someone could help thanks.

 

[Ions97]

To anyone still using this ROM, what was the primary reason this ROM didn't work? And how did u make work arounds for it too? I believe it was the dialer giving problems mainly? I could try to port the galaxy grand 2 ROM for us but I can't guarantee anything, I believe what I really have to do is replace a few apps, maybe edit (or swap) the boot.IMG, and lastly edit the updater.sh, I'll give it a whirl and see how far I get, lol who knows I might just try to port an htc sense ROM for us lmao, it's been done for my nexus so I think I'll try to do it for us as well

I use the lawnchair launcher to make it look better and I usually set the processing speed for each cpu core to the max with a more adamant memory dump to reduce ram usage and control temp and battery life. With the state of this rom it's like driving a car that needs minor repairs daily to run correctly. And I don't know if it's just me but every once in a while it'll allow me to use a 5ghz network but not always I don't understand how or why but I'm not complaining. I'd honestly pay for this to be completed or for a newer rom such as cm13 or lineage os 13 to be made if I had more time to do so I'd build my own but there is nothing I can do about that

 

[3happypenguins]

Every time I try to access the security settings, system crashes. I flashed the ROM cm-12.1-20160102-UNOFFICIAL-afyonltetmo.zip which is supposed to have the proper keymaster files so that system doesn't force close. So just in case, I flashed the recents fix that was supplied. Didn't make a difference. So I took all the keymaster files and manually pasted them using fx file explorer and rebooted. System still crashes. I checked the permissions for the files in /system/vendor/firmware/keymaster and made sure they were:

Root
Root

0644

And they were.

Any ideas? My phone is actually a G386W (Canadian) and not a G386T.

 

[3happypenguins]

Well, I learned a whole ton, such as how to unpack and repack the system.dat.new file. I fixed the keymaster issue (system settings crash), as well as incoming calling not working. The reason why incoming calling was not working was because telephony-common.jar was messed up. I was comparing the build.prop file on a cm 12.1 rom for the Avant where incoming calling was working, and noticed that in this rom (where incoming calls do not work), it was ro.telephony.ril_class=SamsungMSM8226RIL whereas in the all previous roms (even cm 11), it was ro.telephony.ril_class=afyonlteRIL

At first, I just changed that line in the build.prop file to match the previous rom versions. But then I'd get an error where no sim is detected. So I found this handy thread where apparently ro.telephony.ril_class calls on a framework jar file: https://forum.xda-developers.com/showthread.php?t=1948560

I used JesusFreke's classes.dex decompiler and started poking around the smali files and found SamsungMSM8226RIL.smali and looked in it. A bunch of information seemed to be missing. So I just deleted it and replaced it with afyonlteRIL.smali from a previous rom. Then compiled classes.dex again and replaced the classes.dex file in telephony-common.jar. I also changed the build.prop file to be ro.telephony.ril_class=afyonlteRIL.

And guess what?! It worked! We now have incoming calls!!!

I don't have data, so if someone could please test this to see if data is working as well. You can download the rom here: https://www.androidfilehost.com/?fid=889764386195927823

Next on the list is camera. Camera (both picture and video) is a must have for me! I would love to have Marshmallow or Nougat, but that is beyond my skills right now. Maybe down the road. I'm just glad to get something newer than KitKat.

 

[aurey2244]

Nice job! The only thing that stuff is how long and behind we are in updates they already got Oreo going I just bought a real pc laptop so I might look into building a ROM for that phone

 

[3happypenguins]

I think what I'll do is write another couple of tutorials on some of the specifics of bug fixing roms. I find that many of the supposed "noob" instructions are not clear. I like to think of tutorials/instructions like recipes. It shouldn't leave questions in the reader's mind, and each step should be reproduced with the same result. And each computer should be taken into mind (prerequisites needed need to be stated).

I ended up writing a tutorial on how to unpack and repack the system.new.dat file. I kept attempting it with various Windows tools, but either they wouldn't work at all (for example, the .bat file just opening command prompt and then disappearing right away), or if it did work, it would produce a file that wouldn't flash.

So I resorted to installing Ubuntu 16.04 LTS Xenial Xerus on VirtualBox, and forcing myself to learn to use command line (I'm a GUI person). What a difference that makes. The tools actually work properly!

Anyways, here is my tutorial on unpacking/packing system.new.dat. That will at least get someone started: https://forum.xda-developers.com/android/general/tutorial-noob-friendly-instructions-t3662590

Man, if you could build an Oreo rom for this phone, that would be amazing!!! I at first attempted to set everything up for compiling a rom from source code (on Ubuntu), but I got lost with the whole device tree and kernel thing. It's all there on github, but none of the tutorials are clear on where to place it on the drive and what to do with it exactly (what kind of information to extract for the manifest file). Again, not to knock those who write the tutorials, but a good tutorial makes no assumptions on a user's previous experience. When I write baking recipes (I do gluten free baking, which gets very complicated fast), I treat them the same way. Make no assumptions.

 

[3happypenguins]

I have been plugging away at this and I can't get anywhere with the camera right now. If I try to replace the camera .so files with either stock or a previous cm11 rom, I can't boot up and it gets stuck on the cm boot logo. If I try to replace any of the camera .smali files from framework.jar, again, won't boot.

I figured that the best route would be to use logcat... something I am not familiar with. What do I do with it? Have it running, and while it's running just try to open the camera app? What's weird is that camera app isn't in the app drawer (but it's there in the system). So I have to install a Google Camera apk. So when I open the Google Camera app and it says that it can't connect to the camera, logcat should log what is happening?

I looked through the log and I don't see anything about the camera in there. So I don't know if I'm running the log right. If someone could please explain what I need to do. I tried both catlog (an app), as well as typing "logcat > /sdcard/logcat.txt" (without the quotations) in Android terminal.

With catlog, it produced this:

09-02 14:29:48.353 I/Timeline( 3831): Timeline: Activity_idle id: android.os.BinderProxy@ea6f623 time:379608
09-02 14:30:00.517 I/Timeline( 3831): Timeline: Activity_idle id: android.os.BinderProxy@ea6f623 time:391772
09-02 14:30:07.085 W/InputEventReceiver( 3831): Attempted to finish an input event but the input event receiver has already been disposed.

With terminal, it produced this:

--------- beginning of main
V/Term ( 8754): onCreate
D/OpenGLRenderer( 8754): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
D/Atlas ( 8754): Validating map...
D/Term ( 8754): TermService started
I/TermService( 8754): Activity called onBind()
I/Adreno-EGL( 8754): <qeglDrvAPI_eglInitialize:410>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_LNX.LA.3.5.2.2_RB1.04.04.02.087.006_msm8974_LNX.LA.3.5.2.2_RB1__release_AU ()
I/Adreno-EGL( 8754): OpenGL ES Shader Compiler Version: E031.24.00.14
I/Adreno-EGL( 8754): Build Date: 04/29/14 Tue
I/Adreno-EGL( 8754): Local Branch: mybranch3162585
I/Adreno-EGL( 8754): Remote Branch: quic/LNX.LA.3.5.2.2_rb1
I/Adreno-EGL( 8754): Local Patches: NONE
I/Adreno-EGL( 8754): Reconstruct Branch: AU_LINUX_ANDROID_LNX.LA.3.5.2.2_RB1.04.04.02.087.006 + NOTHING
I/OpenGLRenderer( 8754): Initialized EGL, version 1.4
D/OpenGLRenderer( 8754): Enabling debug mode 0
I/Term ( 8754): Bound to TermService
I/TermService( 8754): Activity binding to service
I/libjackpal-androidterm( 8754): JNI_OnLoad
I/Term ( 8754): waiting for: 8777
I/Timeline( 8754): Timeline: Activity_idle id: android.os.BinderProxy@3571d004 time:894212
W/IInputConnectionWrapper( 8754): showStatusIcon on inactive InputConnection
I/Term ( 8754): Bound to TermService
I/TermService( 8754): Activity binding to service
I/Timeline( 8754): Timeline: Activity_idle id: android.os.BinderProxy@3571d004 time:947003
W/IInputConnectionWrapper( 8754): showStatusIcon on inactive InputConnection
I/Term ( 8754): Bound to TermService
I/TermService( 8754): Activity binding to service
I/Timeline( 8754): Timeline: Activity_idle id: android.os.BinderProxy@3571d004 time:1006212
W/IInputConnectionWrapper( 8754): showStatusIcon on inactive InputConnection
I/Term ( 8754): Bound to TermService
I/TermService( 8754): Activity binding to service
I/Timeline( 8754): Timeline: Activity_idle id: android.os.BinderProxy@3571d004 time:1109999
D/OpenGLRenderer( 8754): endAllStagingAnimators on 0xb8cda490 (RippleDrawable) with handle 0xb8d8e4a0

 

[3happypenguins]

Maybe I didn't give catlog root permissions in time and so it denied it or something, not sure. But anyways, I tried it again, and stuff is actually showing up. The weirdest was this kept happening over and over and over, non stop:

E/Sensors ( 704): Accelerometer: unknown code (code=7)
E/Sensors ( 704): Accelerometer: unknown code (code=9)

Here is more to the log:

09-07 21:32:45.104 I/Timeline( 2824): Timeline: Activity_launch_request id:com.google.android.GoogleCamera time:446491
09-07 21:32:45.106 I/ActivityManager( 704): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher (has extras)} from uid 10019 on display 0
09-07 21:32:45.112 V/WindowManager( 704): addAppToken: AppWindowToken{2930fa8 token=Token{440bcb ActivityRecord{dd6a69a u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t11}}} to stack=1 task=11 at 0
09-07 21:32:45.117 V/WindowManager( 704): Adding window Window{17c491fd u0 Starting com.google.android.GoogleCamera} at 4 of 8 (after Window{192d6c4b u0 com.nolanlawson.logcat/com.nolanlawson.logcat.LogcatActivity})
09-07 21:32:45.179 I/ActivityManager( 704): Start proc 5501:com.google.android.GoogleCamera/u0a64 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
09-07 21:32:45.453 W/BackupManagerService( 704): dataChanged but no participant pkg='com.google.android.GoogleCamera' uid=10064
09-07 21:32:45.454 W/BackupManagerService( 704): dataChanged but no participant pkg='com.google.android.GoogleCamera' uid=10064
09-07 21:32:45.454 W/BackupManagerService( 704): dataChanged but no participant pkg='com.google.android.GoogleCamera' uid=10064
09-07 21:32:45.456 W/BackupManagerService( 704): dataChanged but no participant pkg='com.google.android.GoogleCamera' uid=10064
09-07 21:32:45.495 V/CameraHolder( 5501): open camera 0
09-07 21:32:45.501 E/CameraService( 279): CameraService::connect X (pid 5501) rejected (invalid cameraId 0).
09-07 21:32:45.502 W/CameraBase( 5501): An error occurred while connecting to camera: 0
09-07 21:32:45.503 W/CAM_AndroidCameraManagerImpl( 5501): Cannot handle message, mCamera is null.
09-07 21:32:45.503 E/CameraHolder( 5501): fail to connect Camera:-1, aborting.
09-07 21:32:45.503 E/CAM_PhotoModule( 5501): Failed to open camera:0
09-07 21:32:45.508 D/OpenGLRenderer( 5501): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
09-07 21:32:45.522 D/Atlas ( 5501): Validating map...
09-07 21:32:45.528 V/WindowManager( 704): Adding window Window{31537dbb u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 9 (before Window{17c491fd u0 Starting com.google.android.GoogleCamera})

09-07 21:32:55.185 V/CameraHolder( 5501): open camera 0
09-07 21:32:55.188 E/CameraService( 279): CameraService::connect X (pid 5501) rejected (invalid cameraId 0).
09-07 21:32:55.189 W/CameraBase( 5501): An error occurred while connecting to camera: 0
09-07 21:32:55.189 W/CAM_AndroidCameraManagerImpl( 5501): Cannot handle message, mCamera is null.
09-07 21:32:55.189 E/CameraHolder( 5501): fail to connect Camera:-1, aborting.
09-07 21:32:55.190 V/CameraHolder( 5501): open camera 0
09-07 21:32:55.192 E/CameraService( 279): CameraService::connect X (pid 5501) rejected (invalid cameraId 0).
09-07 21:32:55.192 W/CameraBase( 5501): An error occurred while connecting to camera: 0
09-07 21:32:55.192 W/CAM_AndroidCameraManagerImpl( 5501): Cannot handle message, mCamera is null.
09-07 21:32:55.192 E/CameraHolder( 5501): fail to connect Camera:-1, aborting.
09-07 21:32:55.210 V/CAM_VideoModule( 5501): startPreview

I had to install Google Camera (I tried an old KitKat one) because the stock Lollipop camera app wasn't in the drawer and I can't figure out how to open it. It's called camera2. Apparently camera2 may not run on the Avant because it needs supported hardware? If that is the case, how do I "downgrade" things for the camera? I'm a little lost on what to do here.

 

[Ions97]

Is it remotely possible that the kernel could be updated from 3.4. it would be great to use newer magisk but the old kernel isn't supported and causes continuous file system problems that won't go away even after a FULL wipe

 

[Xbryanzx]

So... anyone still woriking?

 

[insalh]

hello is still working ?, at least to have lollipop, I still use this cell

 

[aurey2244]

Supposably nothing past lollipop boots on this phone. The device never really had a big Dev community, I could probably try to figure something out since I have an high-end laptop now and I still have this device but I can't guarantee anything, mainly because everything for this phone is scattered. In all honesty tho if u still use this as your daily driver u need to upgrade, hell even buying a Nexus 5 can get you farther. I have one of those 2 and it runs excellent with great battery life.

 

[Xbryanzx]

Supposably nothing past lollipop boots on this phone. The device never really had a big Dev community, I could probably try to figure something out since I have an high-end laptop now and I still have this device but I can't guarantee anything, mainly because everything for this phone is scattered. In all honesty tho if u still use this as your daily driver u need to upgrade, hell even buying a Nexus 5 can get you farther. I have one of those 2 and it runs excellent with great battery life.

Ok, thanks for the info.