Related
So I finally made the jump and got S-Off using the Moonshine method (Love that sh** BTW) and I flashed CM10 Stable from the Cyanogen website directly. The first error I got was the keyboard would not come up and I was unable to even do anything. I tried using a different keyboard under setting and wouldn't even let me change it.
Next I flashed the latest Nightly thinking this would maybe be more stable and that one gave me the "no SD card error" so I can't use the camera whatsoever.
My question is what version of CM10 fixes both of these issues, or at least somewhat fixes them? I having been flashing for several years so I am used to things being broken in CM10, but these two things are very crucial. Is there a CM10 ROM or variant that works stable enough for daily use? I know there is a flashable zip file fix for the SD card issue, but I really wanted to use the stable version, but the keyboard issue really kills that idea. Am I doing something wrong when flashing the stable version?
Any help would be appreciated. I have no problem using a custom AOSP CM10 based wrong, but there are so many I don't know what to choose?
Thank all.
SoFaKiNgStOkeD said:
So I finally made the jump and got S-Off using the Moonshine method (Love that sh** BTW) and I flashed CM10 Stable from the Cyanogen website directly. The first error I got was the keyboard would not come up and I was unable to even do anything. I tried using a different keyboard under setting and wouldn't even let me change it.
Next I flashed the latest Nightly thinking this would maybe be more stable and that one gave me the "no SD card error" so I can't use the camera whatsoever.
My question is what version of CM10 fixes both of these issues, or at least somewhat fixes them? I having been flashing for several years so I am used to things being broken in CM10, but these two things are very crucial. Is there a CM10 ROM or variant that works stable enough for daily use? I know there is a flashable zip file fix for the SD card issue, but I really wanted to use the stable version, but the keyboard issue really kills that idea. Am I doing something wrong when flashing the stable version?
Any help would be appreciated. I have no problem using a custom AOSP CM10 based wrong, but there are so many I don't know what to choose?
Thank all.
Click to expand...
Click to collapse
You need to get on IIRC... channel: #htc-evo-4g-lte
get the latest unofficial version from there, read the OP in the Original Development Thread here: http://forum.xda-developers.com/showthread.php?t=2110920
Instructions in the first page...
jocarog said:
You need to get on IIRC... channel: #htc-evo-4g-lte
get the latest unofficial version from there, read the OP in the Original Development Thread here: http://forum.xda-developers.com/showthread.php?t=2110920
Instructions in the first page...
Click to expand...
Click to collapse
I think I am digging the Carbon ROM for now, everything's working great. I will for sure check out your suggestion too. Thank you very much!
Sent from my CM10 Charged EVO LTE using xda app-developers app
SoFaKiNgStOkeD said:
So I finally made the jump and got S-Off using the Moonshine method (Love that sh** BTW) and I flashed CM10 Stable from the Cyanogen website directly. The first error I got was the keyboard would not come up and I was unable to even do anything. I tried using a different keyboard under setting and wouldn't even let me change it.
Next I flashed the latest Nightly thinking this would maybe be more stable and that one gave me the "no SD card error" so I can't use the camera whatsoever.
My question is what version of CM10 fixes both of these issues, or at least somewhat fixes them? I having been flashing for several years so I am used to things being broken in CM10, but these two things are very crucial. Is there a CM10 ROM or variant that works stable enough for daily use? I know there is a flashable zip file fix for the SD card issue, but I really wanted to use the stable version, but the keyboard issue really kills that idea. Am I doing something wrong when flashing the stable version?
Any help would be appreciated. I have no problem using a custom AOSP CM10 based wrong, but there are so many I don't know what to choose?
Thank all.
Click to expand...
Click to collapse
Please close this thread, all good.
Sent from my EVO using xda app-developers app
SoFaKiNgStOkeD said:
Please close this thread, all good.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
wait, what was wrong, im having the same issue and ive flashed cm10 a hundred times now without this issue before.
Q&A for [ROM][Official][4.4.4] CyanogenMod 11.0 Nightlies for the Verizon Galaxy S4
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Bluetooth fixes in VRUFNG6
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
consultcory said:
I saw today that Verizon released an updated build (VRUFNG6) that supposedly contains bluetooth fixes. Does anyone know if these are going to be Touchwiz-specific and/or if they could be pulled and incorporated into the current CM11 nightlies?
Many are reporting terrible bluetooth connectivity and related issues, so just thought I'd ask.
Click to expand...
Click to collapse
They have been "kangbanged" from NF3 and merged today. You can see this awesome goodness in the 10/13 nightly.
See here:
http://www.cmxlog.com/11/jflte/
Look under to be included in next nightly. The new camera fix has also been merged.
Post Content Edited. Sorry, I was frustrated and had a moment of weakness.
The silence is deafening.
Just load m9. It's perfect. Eventually you'll lose the urge to Crackflash and enjoy your s4 for what it is (a pretty good 2 year old phone).
There are 4 v*rizon phones out there that 'do it for me'. I just need to figure out which one is the least 'Verizoned'. In really not too anxious though. I like my s4.
Installing Cyanogen on Verizon Galaxy S4
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
I am running CM11 Nightly and the only modification I have made to the actual file system is deleting the DSP Manager apk in system/app because it was taking precedence over other equalizer apps I was trying out. Long story short, I couldn't find an equalizer that boosted the bass correctly as well as the equalizer built into the stock S4 Touchwiz did. So, I reflashed the DSP Manager apk through CWM. Now, neither Google Play Music nor Apollo will play my music on the external SD card. And for my last question, why are no equalizers working correctly with bass boost? When I have either a preset or use the bass booster slider bar in any equalizer (including DSP Manager) it just makes my music crackle. Its not my headphones either, as they worked perfectly on Touchwiz. Thanks in advance for your reply.
evesira said:
Hello all,
Now that this NG6 update recently pushed to my phone has made it practically unusable, I've decided it might be time to install a custom ROM. Alas, the handy Cyanogen "one-click" installer does not support my phone Since I'm new to this and really afraid of bricking my phone, I've come here just to get some assurance.
I've seen this post which gives instructions on how to install, but one thing concerns me. This link from the CM website gives pretty different instructions, and moreover adamantly warns that the build version of your phone must be I545VRUAMDK, which mine is not. Why the discrepancy in instructions?
Why is installing an alternate kernel necessary to obtain a root? Can Towelroot not be used (does that app involve installing an alternate kernel)? Is the motochopper app listed necessary to root the device in a "certain way"? Is the clockwork app the only CM supported app to make a recovery image, or can I use another standard like TWRP? And what part of this process that they list absolutely requires you to be on that build version???
I know, I have no idea what I'm doing. Please advise, or at least point me in the right direction! Also, I know the original post says that asking about rooting is off topic here, but it's only part of my question, and sort of relevant in this case because the official CM installation instructions suggest some kind of compatibility concern.
Many thanks!
Click to expand...
Click to collapse
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
FernBch said:
Since it sounds like you updated to NG6 via a VZW OTA update CyanogenMOD is unfortunately out of your reach. CM needs a custom recovery such as CWM or TWRP and they can only be installed on a GS4 that is running the MDK bootloader. The later versions are locked down and only a SafeStrap compatible ROM can be installed.
Click to expand...
Click to collapse
Thank you for the response. I actually solved my problems a couple of days ago. I'll post them here for posterity.
Regarding those Cyanogen instructions, they say that you should only attempt this on the MDK build, but they don't say why. Are the particular tools they suggest using incompatible? No, Cyanogen itself is only compatible with the MDK build of the I545 Verizon S4 (US), for the reasons that Fern explained above. Took me some forum snooping to actually determine that one.
For those who are going through the horrors of the NG6 update, but don't want to wait until the rumored fix in early December, do what I did. See this thread:
http://forum.xda-developers.com/showthread.php?t=2735172
The no-wipe version didn't work for me unfortunately. It booted with all my stuff still in tact, but errors constantly popped up making the phone unusable. I had to do the full wipe, which gets rid of all your apps and personal data (unless it's on the SD card I believe). So try the no-wipe first, and if it doesn't work, back up all your data and apps, then do the full wipe.
Download Odin 3.09 (no need to root first), and use the full wipe ROM from the thread and watch the video for instructions. That will get you back to NC5, the previous working version before the NG6 fiasco. However, you still need a way to stop the update from happening again. Oddly, some users get a "no thanks" option, but I didn't get that. I had to root, which I had never done before. On your phone, google towelroot, go to the site, click the lambda, download it, install it (in settings allow android to install apps from unknown locations other than the app store), press "make it rain". Still on your phone, install SuperSU from the app store and go through that process. Then buy the Titanium Backup Pro app from the app store, find the SDM.apk, and freeze it. This should stop the update prompt from happening!
Now that you had to wipe your phone and root it (possibly for the first time if you're like me), reinstall all your old apps and move your data back. And since you're now rooted, you might as well take advantage of it. Download the Xposed framework, and install some useful modules for it like Wanam, NoMapTips, Disable Clear Defaults Dialog, and more. Then you can get rid of a lot of annoying TouchWiz bull**** like "loud volume can damage your hearing" warning, low battery warning, and etc.
Hopefully this helps someone who has no Android "modding" experience like myself, and saves them some research.
Cheers
For clarity, the reason that you can only run CM on a MDK device is the MDK bootloader is the only one that can be exploited by a process called loki to allow flashing a custom recovery. All later bootloaders have had this exploit blocked (Thank Big Red). Because of this the only option is SafeStrap. On MDK ONLY this allows one to flash custom kernels and recoveries which are required in order to flash any AOSP ROM such as CyanogenMOD.
Cm11 m12/rc1
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
consultcory said:
I can't remember where, but I read something about the next milestone build being available around November 7th, and that it may even be labeled as a release candidate instead. Obviously there's been no such release and the CyanogenMod blog hasn't been updated in almost a month.
Has anyone heard anything about a release date for M12/RC1?
Click to expand...
Click to collapse
I guess I should have just waited a day... M12 is now up!
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
xuhdev said:
At first glance on the download web page, I thought Galaxy S4 version is unsupported since the begining of the year. You should really post the information that you are building unified build to the download page.
Click to expand...
Click to collapse
Its hard to miss on the first page of the thread.
" CyanogenMod:
Nightly:*http://download.cyanogenmod.org/?dev...w&type=nightly
As of 20140218 we are doing unified builds. Get them here:
Unified Nightly:* http://download.cyanogenmod.org/?dev...e&type=nightly "
Sent from my SCH-I545 using Tapatalk
TMYINC said:
Its hard to miss on the first page of the thread.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
xuhdev said:
If you know Cyanogenmod, you would probably go to the cyanogenmod download page directly but not visit from here, right?
Click to expand...
Click to collapse
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
TMYINC said:
I do know CM. That's why I know the download page has been different since Feb. 18th. I always stay I'm touch here for updates, bug reports, or just to answer questions. I wasn't trying to be rude.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I'm not saying you don't know. "You" means someone. Not everyone sees xda as official document; neither do I. But I found the official wiki, so the problem I mentioned should not be a problem.
Deleted
hey guys
have you seen this? there are some new updates!
v3.53
http://www.needrom.com/download/update-nubia-z7-max-v3-53/
v3.54
http://www.needrom.com/download/update-nubia-z7-max-v3-54/
based on Android 5.1.1
sounds cool!
someone here tried it? are these versions beta?
TopTomy said:
hey guys
have you seen this? there are some new updates!
v3.53
http://www.needrom.com/download/update-nubia-z7-max-v3-53/
v3.54
http://www.needrom.com/download/update-nubia-z7-max-v3-54/
based on Android 5.1.1
sounds cool!
someone here tried it? are these versions beta?
Click to expand...
Click to collapse
Am currently running on v3.53. Have not tried v3.54 yet (no changelogs). So far smooth sailing, but this should be treated as an upgrade rather than a clean install. I did a clean install and it causes my IMEI info to disappear. Took me a while to restore back my imei. As to whether this is a beta or not, i am not sure, but i should think it's official by now since v3.54 is already out.
Update : According to bbs.nubia.cn, both v3.53 and v3.54 are BETA releases.
petrofsky77 said:
Am currently running on v3.53. Have not tried v3.54 yet (no changelogs). So far smooth sailing, but this should be treated as an upgrade rather than a clean install. I did a clean install and it causes my IMEI info to disappear. Took me a while to restore back my imei. As to whether this is a beta or not, i am not sure, but i should think it's official by now since v3.54 is already out.
Update : According to bbs.nubia.cn, both v3.53 and v3.54 are BETA releases.
Click to expand...
Click to collapse
Stable versions of ROMs get posted here by ZTE, anything that isn't there is BETA.
any news from lineahe os rom for vs985 other lg g3 have this rom
I would look in the Original Development forum for any news possibly if it ever comes to the VZ985. From the Lineage OS web site, it only lists the D855, so until they update that page, or if someone else downloads the source and ports it to the VS985, I doubt we'll see it, especially since this is over 2 years old and most developers have probably moved on to bigger and better things.
And just because other versions of a phone have it, doesn't mean it will be available for all versions. It all depends on which versions of the phone the developers have.
thank you for info.. and wich the best rom for battery life?
madara12345 said:
thank you for info.. and wich the best rom for battery life?
Click to expand...
Click to collapse
I unfortunately can't help you there. First, I no longer have my G3 as it died back in December. Sad day.
Secondly, I ran stock, unrooted and I was able to get about 1.5 days on a full charge, as long as I didn't play my games. lol
Good news! LineageOS 14.1 will be rolling out for vs985 this week.
source: http://lineageos.org/Last-Week-in-LineageOS-4/
niiiiiiice when can download it?
ngato35 said:
niiiiiiice when can download it?
Click to expand...
Click to collapse
They haven't uploaded the build yet. They'll do it by the end of this week. Keep checking download.lineageos.org/vs985
thank
madara12345 said:
any news from lineahe os rom for vs985 other lg g3 have this rom
Click to expand...
Click to collapse
The rom released today! download.lineageos.org/vs985
Anyone tried it? Any bugs? Any thread to discuss this further in?
pairdime said:
Anyone tried it? Any bugs? Any thread to discuss this further in?
Click to expand...
Click to collapse
As it is an initial release, there might be some bugs, but as far as I know, I haven't found out any, but battery optimisation is not so good and the phone heats up. And I think many features are missing, because the file size of lineageos for d855 is around 390mb and that of vs985 is only around 350 mb.
I hope they'll add all of the features in future updates.
Also, if you were using substratum, you cannot use it in this rom very well because this is not a substratum (masquerade) enabled rom. I reverted back to Resurrection remix today.
Ive been running it since yesterday. some issues:
I can onlyget root through ADB, despite flashing the Super SU twice. They are aware of this issue
I couldnt' get Gapps to install correctly. That may be due to the fact that I tried to use The Aroma package. I'm not familiar with that one.
You cannot turn on developer options, tapping the build number 8 times only brings you to the home screen and a large logo that wont' go away until restart.
It's very early for this release and it looks good so far. I''ll be back, but I just bought this device (for development/learning purposes) and I want to try some more roms
Thanks for the heads up about early issues on LineageOS. When I saw they had a version for the VS985 I figured it might be worth some risk to check it out. Unfortunately (or fortunately) I couldn't get it to flash.
I am on Android Version; 5.0.1
Baseband; VS985-MPSS.DI.2.0.1.c1.13.00073-M8974AAAANPZM-1
Kernel; 3.4.0-perf-g2d182d3
Build number; LRX21Y
Software Version; VS98524B
I tried unsuccessfuly to flash the 35B bootstack so I could never get into LineageOS 14.1. (It looks for 35B during install) Maybe I will wait a while and see if LineageOS cleans up a bit before trying to flash it again.
I was wondering why there's no Thread for this to talk about.
Info about oriole | LineageOS Wiki
wiki.lineageos.org
HSD-Pilot said:
I was wondering why there's no Thread for this to talk about.
Click to expand...
Click to collapse
Maybe because nobody cares?
Anyone know how I could go about troubleshooting the OTA update failing?
I have a Pixel 6, with official LoS installed per the instructions on the wiki.
It seems to work fine, but after downloading the OTA, the Install/Apply Update step does nothing.
It throws an "Install error" message, but with no details or error code.
I have some experience with flashing devices, but much less with over the air updates.
quirkyjoe said:
Anyone know how I could go about troubleshooting the OTA update failing?
I have a Pixel 6, with official LoS installed per the instructions on the wiki.
It seems to work fine, but after downloading the OTA, the Install/Apply Update step does nothing.
It throws an "Install error" message, but with no details or error code.
I have some experience with flashing devices, but much less with over the air updates.
Click to expand...
Click to collapse
Its only been out for like a month I would download the current FULL version and flash on top of your current build and hope the next ota works on saturday
adm1jtg said:
Its only been out for like a month I would download the current FULL version and flash on top of your current build and hope the next ota works on saturday
Click to expand...
Click to collapse
This did end up fixing it.
At the time I posted it, there were two pending updates, and I manually flashed the first with no change in behavior (still wouldn't update via the built in OTA updater).
Manually flashing the next update did resolve the issue though, so it seems like they may have fixed something in those updates.
Thank you for taking the time to help anyway.
Flashed! With the kernel blue spark is an excellent bunch.
GAPPS - MindTheGapps.
The OTA update installed without problems.The kernel was patched after and flashed blue spark now.
Nice ROM! Thank to Lineage Team)
Hello! Has anyone tried build-myself?
maximusfoa said:
Hello! Has anyone tried build-myself?
Click to expand...
Click to collapse
Yes, I'm almost there I just need to stop Linux from killing the end process (android.pb). Did you have any questions?
For some reason, after the command 'breakfast oriole', can’t find the tree ..
Esim doesn't works for me!
Scan works but not add esim
Jossye said:
Esim doesn't works for me!
Scan works but not add esim
Click to expand...
Click to collapse
GAPPS installed?
Great ROM!