Related
I want to go back to GB as I'm not satisfied with the ICS ROMs I've tried (only had this phone a few weeks). Dev board is flooded with ICS, any GB suggestions?
Sent from my Nexus S 4G using Tapatalk
I highly reccomend Oxygen, only problem I ever had with it was sending and recieving mms. Other than that I say it is lightening fast and stable.
Were you able to fix the mms issue?
Sent from my Nexus S 4G using Tapatalk
i'd say BrainMaster's MIUI 2.3.7 ROM , i was running it before i updated to ICS
qtwrk said:
i'd say BrainMaster's MIUI 2.3.7 ROM , i was running it before i updated to ICS
Click to expand...
Click to collapse
Should have mentioned I want everything to work including 4g.
Sent from my Nexus S 4G using Tapatalk
Try .CIBERGR-MOD 's GB version. It's a fast rom. Although, I'm not sure if he has a NS4G version.
Sent from my Nexus S using Tapatalk
Peter Alfonso's GPA19 ROM is the most stable one that I tried. Look for Peter Alfonso's site and click the Downloads link for crespo. I would post a link here, but XDA's nonsense won't allow it.
Download the 12-07-11 one to get the latest GB version. There aren't a lot of customizations like CM, Oxygen, MIUI, etc., but it's stable as hell. The latest Oxygen (2.3.2) has a REALLY obnoxious, and largely ignored, backlight notification bug where you have to reboot to get the lights to go out... only way I've ever found to fix it is to install another kernel. However, Peter Alfonso's got one of those too... just go to his site and it should be on the second page of the "blog."
I know you said you didn't like ICS, and I didn't either at first, but Pete's ICS ROMs are also great and very stable. The latest is 01-30-12, and you can get it from the same crespo download page.
question.
hey man i got a question, could i use peter alfonso's rooted stock rom for gingerbread (right?) when downgrading, right? instead of re rooting it.
charchuck said:
Peter Alfonso's GPA19 ROM is the most stable one that I tried. Look for Peter Alfonso's site and click the Downloads link for crespo. I would post a link here, but XDA's nonsense won't allow it.
Download the 12-07-11 one to get the latest GB version. There aren't a lot of customizations like CM, Oxygen, MIUI, etc., but it's stable as hell. The latest Oxygen (2.3.2) has a REALLY obnoxious, and largely ignored, backlight notification bug where you have to reboot to get the lights to go out... only way I've ever found to fix it is to install another kernel. However, Peter Alfonso's got one of those too... just go to his site and it should be on the second page of the "blog."
I know you said you didn't like ICS, and I didn't either at first, but Pete's ICS ROMs are also great and very stable. The latest is 01-30-12, and you can get it from the same crespo download page.
Click to expand...
Click to collapse
Loaded up the 01-30-12 ICS this morning since that would be the easiest transition. Using Apex and so far, so good. Thanks!
Sent from my Nexus S 4G using Tapatalk
I'm currently running Euroskank CM7 kangs.
Wow, really. I don't have any ICS envy seeing how sweet those kangs are. They're smooth as butter and stable too! Checking my phone, my current uptime is 132 hours (5.5 days) since my last reboot, which was to flash the latest kang back then.
allenxx said:
hey man i got a question, could i use peter alfonso's rooted stock rom for gingerbread (right?) when downgrading, right? instead of re rooting it.
Click to expand...
Click to collapse
I'm not exactly sure what you're asking. Both of his ROMs are pre-rooted, so no, you won't have to re-/root anything. But since you're going from ICS to GB you'll have to wipe everything, so there's no real "downgrade" path.
From a rooting perspective, the only difference I've noticed, that's kind of annoying, is that his GB ROM contains busybox and his ICS ROM doesn't. It's not a deal-breaker since there are Market apps to add it in, but it's kind of annoying that the binary has to be re-linked after each update/flash.
charchuck said:
I'm not exactly sure what you're asking. Both of his ROMs are pre-rooted, so no, you won't have to re-/root anything. But since you're going from ICS to GB you'll have to wipe everything, so there's no real "downgrade" path.
From a rooting perspective, the only difference I've noticed, that's kind of annoying, is that his GB ROM contains busybox and his ICS ROM doesn't. It's not a deal-breaker since there are Market apps to add it in, but it's kind of annoying that the binary has to be re-linked after each update/flash.
Click to expand...
Click to collapse
Im asking that if i can reverted back to gingerbread version without loosing root, may i install his pre-rooted stock without loosing root. Thats all, but since you mentioned it, im relived to revert it back. but i couldnt find his link could you provide me one? Also is it regular to flash it back to gb or is there a special method to do it?
I can't post links yet because our fine friends at XDA say that I need to post more for the privilege. Pfft.
You should be able to type peter alfonso downloads crespo and get to the page. 12-07-11 is the latest GB version (GPA19).
There's no "special" method for flashing, just do what you would do when going from one incompatible ROM to another... wipe data/factory reset, format cache partition, format /system, wipe dalvik cache. There are probably a million different combinations that different people will give you for the proper install, but that's what I normally do.
Tryout CyberGR's CM7 MOD and you won't go back:
http://forum.xda-developers.com/showthread.php?t=1378469
Just read the feedback in the thread and you'll understand.
perfect, and uh before i do that it could be any rooted gb rom right? just curious, that's all.
Don't mean to hijack the thread but what if I wanted to put a custom GB ROM on top of stock GB rom. I'm curious if you can just flash without wiping? Or should I do titanium backup instead?
charchuck said:
I can't post links yet because our fine friends at XDA say that I need to post more for the privilege. Pfft.
.
Click to expand...
Click to collapse
you have only 5 posts and complaining ? I wonder when you hit 100+ post what would you do ? if you don't like the forums why you're here ?
calisoldier83 said:
Don't mean to hijack the thread but what if I wanted to put a custom GB ROM on top of stock GB rom. I'm curious if you can just flash without wiping? Or should I do titanium backup instead?
Click to expand...
Click to collapse
Wipe.
10 chars.
I just put on the Peter Alfonso rom, it's super fast. Well probably keep this until official ics is released.
Sent from my Nexus S 4G using xda premium
Hi everyone, this is my first post in the sensation forums. Here is my question. A friend of mine has the sensation in stock form and wants to me to install AOKP on it. I've been reading up on how to get s-off and installing cwr. Now I have a vibrant and if on a stock or froyo rom installing a cm7 rom is recommended prior to installing any ics rom to get partitions and such correctly. Is there a rom that needs to be flashed before I can flash his sensation with the aokp rom or is it safe to flash straight from stock rom. Thanks in advanced.
Sent from tapatalk V2 B6 from ics powered vibrant
The process goes basically like this:
A) Unlock the bootloader by means of Revolutionary.io
B) Root the Stock Rom
C) Flash 4EXT recovery from the APK downloaded at 4ext.net
D) Download the 3.32 unlocked firmware from the dev thread.
E) Put firmware PG58IMG file on root of SD card and hit up the bootloader, apply firmware.
F) Remove firmware file from SD card so you can get to 4EXT recovery from the bootloader.
G) Put rom on SD card, reboot into recovery, flash rom.
Only one problem is that AOKP isn't really supported, or 100% ready to roll on this device. Virtuous Inquisition or ARHD + Shnizlon's AOSP mod is a much more stable, feature-packed approach.
Thanks sshede, that's a pretty good tut you wrote for me there. And I'll definitely search and look into the roms you recommend. And also time for me to start downloading all those files and the drivers for his phone. I probably won't mod his phone till this weekend so it will give me more time to do my reading up. Thanks once again.
Sent from tapatalk V2 B6 from ics powered vibrant
Lol wut. Aokp is faster, more stable and smoother than VI. I have been using it for like 1 month without a single reboot. Only few bugs (480p camcorder) that don't affect the experience at all. Give it a try, you will think CM is a joke after using AOKP's ROM Control (which is a compilation of a LOT of tweaks/mods/etc).
Sent from my Sensation using Tapatalk 2
BurnRubber90 said:
Lol wut. Aokp is faster, more stable and smoother than VI. I have been using it for like 1 month without a single reboot. Only few bugs (480p camcorder) that don't affect the experience at all. Give it a try, you will think CM is a joke after using AOKP's ROM Control (which is a compilation of a LOT of tweaks/mods/etc).
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
Totally subjective. Some people prefer 480p because it doesn't use nearly as much space. Bluetooth isn't 100% functioning either. It may not bother you, but some people need them. And I've tried my fair share of both Sense and AOSP-based roms, nothing is more stable than Sense-based roms right now. All the drivers are straight from HTC, nothing's been patched together.
sshede said:
Totally subjective. Some people prefer 480p because it doesn't use nearly as much space. Bluetooth isn't 100% functioning either. It may not bother you, but some people need them. And I've tried my fair share of both Sense and AOSP-based roms, nothing is more stable than Sense-based roms right now. All the drivers are straight from HTC, nothing's been patched together.
Click to expand...
Click to collapse
Yes. The main problem I had with VI was the random black screen of death. Had to pull battery away every couple days as the phone wouldn't turn back on. That's why I don't like that ROM.
And, well, its personal preferences
Sent from my Sensation using Tapatalk 2
This is a strange problem that I only started to have once I installed Team Nekkid 7.2 RC dated 3/29.
I can flash the ROM no problem, wipe dalvik and fix permissions and I'm good to go without any issues. But if I flash the ROM, then either morfic or faux kernel, then gapps, when I go to wipe dalvik, all I get is a quick screen flash with no option to actually wipe dalvik.
I go back and wipe the overall cache completely, fix permissions, the reboot. I am now stuck at the morfic boot animation until i pull battery.
If i try to install a Faux kernel, same thing happens with dalvik, but gets stuck at the blue LG screen.
Once i battery pull and get back to CWM, i wipe everything, reflash ROM and gapps, wipe dalvik and fix permissions no problem and boot up into whatever ROM i choose.
EDIT: Went back and flashed Bionix 1.4.1 and was able to flash a Faux kernel and wipe dalvik. Booting up this ROM now.
I also have NO problem with ICS ROMS/kernels.
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I did all of that. I flashed the kernel before and after gapps but end up with the same result.
I have a feeling there is an issue with the CWM since I am constantly flashing roms/kernels and have never had these problems before. I'm at work so I cant use the Nvidia tool to flash CWM so I have to wait until I get home.
mariuscm said:
When you say NO PROBLEMS with ICS ROMs, does that include Google Maps and the stock browser working perfectly??
Which ICS ROMs have you tried? How is battery life?
Thanks!
Click to expand...
Click to collapse
I meant I have no problem flashing ICS roms and kernels.
mt3g said:
Flash kernel last, and redownload the kernels!
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
[UPDATE] Ok I got it now. Just read your last message
mariuscm said:
I usually just follow the instructions precisely by the OP. (Wiping/formatting, flashing rom, gapps, restart + let 10 min stand if required by OP) I have not installed another kernel that what the ROM has included. Should I try that? If yes, which one? I currently have EGB AOSP ICS 4.0.4
Click to expand...
Click to collapse
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
stevew84 said:
Short answer: yes, install a different ROM
Long answer: go to the developing section of the G2X forums and find out the info with the countless threads.
Click to expand...
Click to collapse
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
mariuscm said:
I've tried 3 different ICS roms and read hundreds of posts and found nothing that would fix the maps and browser issues. I guess I have to wait a bit more for the devs to work on them. Maybe the lack of drivers is the problem.
Click to expand...
Click to collapse
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
stevew84 said:
Look for Owain's Unnoficial Build 55 thread, and use Firefox browser, that is the most complete ICS ROM and Firefox doesnt have the rotation problem.
Click to expand...
Click to collapse
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
mariuscm said:
I was just downloading that ROM
Thanks!
My main concern is Google Maps not working properly. I rely on it in my job a lot and can't have it blanking out on me like that.
I've tried the replacement solution for the stock browser - I installed Dolphin HD. I'll try Firefox, though. Haven't used that on a phone since I had the Nokia N900 - Ah, the good times when I still believed in Nokia
Thanks for your help!
Click to expand...
Click to collapse
If the maps shows up and then goes blank, simply close the map and re-open it.
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
All the important information will be in the first post of his thread. he doesn't include a change log, though.
mariuscm said:
I know the close/reopen "trick," but I thought there might be a ROM that just has the Gmaps working. If there's none I'll just wait. Is Owain's unofficial 55 based on 4.0.4 ? I'm also going through his thread now in hopes of finding it. I'll probably just flash and see then.
Click to expand...
Click to collapse
Yes, it's 4.0.4 with all of the latest CM9 commits.
Sent from my LG-P999 using xda premium
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
bananagranola said:
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
Click to expand...
Click to collapse
Sure wish i could get some help with this too.
Have you guys tried the latest releases? When full wiping include format all partitions except sd card.
Sent from a dream.
What latest releases are you referring to? Could you please be more specific?
EDIT: I did a full wipe and reformat of everything, including system, data, and cache.
Right now they are on beta 10. Funny thing, I don't recall anyone mentioning a need to do a adsp firmware update. I don't even know what it is.
Sent from a dream.
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Sent from my Desire HD using xda app-developers app
jlochamy said:
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Click to expand...
Click to collapse
Are you referring to this one?
bananagranola said:
Are you referring to this one?
Click to expand...
Click to collapse
That is the one. But if you don't do a full wipe before you do beta 10 it will have errors. It would still boot but have lots of errors.
Sent from my Desire HD using xda app-developers app
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
bananagranola said:
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
Click to expand...
Click to collapse
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
uss..p8triot said:
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
Nope. You only need to flash the stock once; after that, flash back and forth to your heart's content.
uss..p8triot said:
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
fatboyRICH said:
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
Click to expand...
Click to collapse
usspatriot is actually referring to a separate question. Some of us need to update our firmware to run JB, which can only be done by flashing the latest stock before flashing JB. He wanted to know if the updated firmware would be overwritten by flashing ICS, requiring a reflash of stock before reflashing JB. The ICS and JB kernels are not at issue.
I wonder if this has anything to do with my issue with JB on a Desire HD:
I came from SmartDroid_Reloaded_wwe_1.5.2, did a full wipe, installed, everything works fine for me except for cellular data.
I'm wondering if it's something to do with JB not liking my phone? I've also tried a couple of ICS roms.. See below:
SmartDroid_Reloaded_wwe_1.5.2 = cell data works
Sabsa_Prime_v5.0 = cell data works
TrickDroid_v1.1.1 = cell data works
cm-cfX-20120925-OFFICIAL-ace = no cell data
cm-JellyTime_R10 = no cell data
cm-JellyTime_R10.1 = no cell data
cm-JellyTime_R11 = no cell data
i set my APN's to suit my network (crazy johns in australia) but nothing works..
If i connect to wifi, both the wifi signal and cell signal turn blue, if i disconnect from wifi, both turn grey.
MMS, SMS, Phone calls work fine..
Click to expand...
Click to collapse
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
e_poch145 said:
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
Click to expand...
Click to collapse
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
One other thing to note, is AOSP kernels are not compatible with TouchWiz roms, and TW kernels are not compatible with AOSP roms.
Make sure you get the right one, if the developer offers both options.
Sent from my SCH-I535 using XDA Premium 4 mobile app
buhohitr said:
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
Click to expand...
Click to collapse
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Thanks Guys!
SlimSnoopOS said:
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Much appreciated guys! I decided to go with [4.3/4.4][AOSP] ¤ BMS ¤ d2vzw / d2usc 3.4.y (link below). So far so good, flashed easily and no problems at this point. Ill report back and see how the performance gains are.
http://forum.xda-developers.com/showthread.php?t=2133550
Thanks again for all of your advice!
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
wont connect to wifi for me
twistedillutions said:
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
e_poch145 said:
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
Click to expand...
Click to collapse
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
versions im running
SlimSnoopOS said:
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Liquid Smooth 2.37 from 11/06/2013
KT747-AOSP-JB-MR2-3.4-VZW-11-04-2013
BMS_3.4_d2_2014-01-27
U need an older version of BMS thoss new version from dec till now are for 4.4 roms and liquid 2.37 is a 4.3 thats the reason why ur having issues
Sent from my unknown using Tapatalk