I'm coming from a nexus 5 (sad story, power button is broken).
I've loved not having any bloatware from day one.
On the other hand, LOVING the feel of this HTC so far.
I'm not finding a great deal of search results about the xposed framework on these phones. I see there is some hesitation with some htc one phones (couldn't determine which ones from what i read), So i thought i'd ask if anyone has any reason why it wouldn't run on a newly wiped stock OTA 5.0.2 install that i just rooted.
Thanks in advance and happy to join the community here.
Haven't had any issues (I'm new to the phone myself, love it, had it for 2 weeks so far), but I S-OFF and converted mine to GPE. Make sure you're using the official alpha xposed for 5.0 http://forum.xda-developers.com/showthread.php?t=3034811. There is also a different unofficial one for 5.1 http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 if you decide to upgrade. I'm running a bunch of modules and they work as far as I know.
008freak said:
Haven't had any issues (I'm new to the phone myself, love it, had it for 2 weeks so far), but I S-OFF and converted mine to GPE. Make sure you're using the official alpha xposed for 5.0 http://forum.xda-developers.com/showthread.php?t=3034811. There is also a different unofficial one for 5.1 http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 if you decide to upgrade. I'm running a bunch of modules and they work as far as I know.
Click to expand...
Click to collapse
As mentioned, Xposed should work. It was broken for a while, meaning it didn't work on Lollipop, so many folks had to stop using it for a while for that reason (or use KK ROMs until Xposed was updated). And I think there was a point where Xposed framework itself was updated for LP, but many modules were not (and therefore did not work with LP). But I think a lot of that has ironed itself out, by now. You might run into a few modules here or there that don't work on LP; but most things should work fine.
008freak said:
Haven't had any issues (I'm new to the phone myself, love it, had it for 2 weeks so far), but I S-OFF and converted mine to GPE. Make sure you're using the official alpha xposed for 5.0 http://forum.xda-developers.com/showthread.php?t=3034811. There is also a different unofficial one for 5.1 http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 if you decide to upgrade. I'm running a bunch of modules and they work as far as I know.
Click to expand...
Click to collapse
GPE is such a great suggestion, I hadn't considered that as an option. this(http://forum.xda-developers.com/showthread.php?t=2716306) seems to the the most supported I can find, you mind me asking what version you are using as GPE.
redpoint73 - My mileage varied from module to module also when it first got alpha support for 5.1, but everything I was looking for customization wise was met eventually. My quirky preferences aren't as numerous as they used to be.
I would love to learn more about fastboot flashing from the terminal, I know enough to be dangerous at this point. Do you all have any good pointers or tutorials you could direct me to?
Thanks for the prompt replies everyone! Now I have yet another reason to procrastinate the research paper I'm supposed to be writing today .
wakeboardsam said:
GPE is such a great suggestion, I hadn't considered that as an option. this(http://forum.xda-developers.com/showthread.php?t=2716306) seems to the the most supported I can find, you mind me asking what version you are using as GPE.
I would love to learn more about fastboot flashing from the terminal, I know enough to be dangerous at this point. Do you all have any good pointers or tutorials you could direct me to?
Thanks for the prompt replies everyone! Now I have yet another reason to procrastinate the research paper I'm supposed to be writing today .
Click to expand...
Click to collapse
Disclaimer (I can't remember the exact steps I took, so in addition to me being vague, obligatory: I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE!)
I'm on the latest GPE 5.1 LMY470.H6. I didn't flash a rom maintained by a user, I did the conversion through changing MID, CID, flash RUU, so I could get official OTA updates.
I followed a combination of the following guides. READ BOTH CAREFULLY FIRST as this is probably a bit more involved than just flashing a ROM in recovery: http://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
http://forum.xda-developers.com/showthread.php?t=2708651 Has a guide for loading the official GPE RUU. The guy's website has 4.4.2 to latest 5.1 GPE
I installed 4.4.2 un-rooted, then updated through OTA to 5.1, flashed TWRP, installed SuperSU, rooted, installed xposed, DONE!
Then go to town on xposed. I would just say read carefully. I spent a good half a day converting mine xD
If you don't feel comfortable doing this, going with a dev/team maintained GPE ROM is probably fine and might even be better maintained.
wakeboardsam said:
I would love to learn more about fastboot flashing from the terminal, I know enough to be dangerous at this point. Do you all have any good pointers or tutorials you could direct me to?
Click to expand...
Click to collapse
There are good fastboot guides on XDA like the following: http://forum.xda-developers.com/showthread.php?t=2277112
Honestly, I can't say I know much more, aside from the few commands I've had the occasion to use: wipe cache, flash kernels, flash zips, flash recovery, etc. For the most part, when I need a certain command, I just look it up.
Related
I was wondering if there was a way to flash AT&T ROM to work on the verizon model. I know how to flash international Roms but not AT&T.
For example, currently I am running Echoe 32.1 (International version), but when I try to flash Goldenfinger (AT&T) my phone calls work but I get no SMS or data.
Any help is appreciated!
Thanks!
Someone with ROM building (from source or porting) experience can better explain this, but the simplest answer is that because the frequencies that AT&T and T-Mobile operate on differ from those of Verizon and Sprint (typically). So the ROM you are trying to use has different radio drivers for frequencies your phone doesn't use, which results in most or all your antennas to not function. I know that at the very least you need to modify the ROM to utilize the Verizon radios. There may also be some system configurations to be altered in the install of the ROM so it's instructed to use the right frequencies, though a more qualified individual will need to verify that.
Hope that gives you a general idea.
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
joshm.1219 said:
http://forum.xda-developers.com/showthread.php?t=2674280
This patch can be used to flash roms from international and other carriers. It has an aroma installer allowing to decide how much Verizon stuff you want to install, anywhere from just the APN's to the full phone & messaging apk's. Read the OP and thread to understand which patch to use and how to use it.
Click to expand...
Click to collapse
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
luke24 said:
Thank you for the help! But I tried the patch you suggested on two different AT&T ROMs, and I didn't have any luck. It works on international version ROMs, but not AT&T..
And I just realized I forgot to put in the OP that im on Safestrap
Click to expand...
Click to collapse
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
joshm.1219 said:
Yeah, unfortunately things have been weird with that patch lately. It's a mix of the dev not having time to update while everything has been getting significant updates pretty quickly and lost user interest overall. I've used that patch with AT&T roms before, but admittedly not since Jelly Bean. It should theoretically work still, but there's other variables you have to consider. All I can say is that if you're really interested in running one of those roms, read through the patch thread to see what particular aroma settings and additional zips, etc. people are using to get those roms to boot.
And Safestrap users can use that patch too. I would PM @shindiggity for assistance. He seems like a helpful guy and he uses that patch on Safestrap.
Click to expand...
Click to collapse
Thank you for all your help! Im gonna PM him and read through the thread and if and when I find a solution, I will post it here.
I've flashed Goldfinger and it does work. These are the steps that I do. Flash rom, patch,signal bar fix, modules and finally SU. In the patch I select minimal and everything else I leave pre selected. First boot does take a couple minutes. Let me know if that works.
http://www.androidfilehost.com/?fid=23501681358559252
http://www.androidfilehost.com/?fid=23578570567713275
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
So I've had the phone for less than a week. I've performed the ioroot procedure and installed twrp. Other than that, the phone is stock right now - 10B. I've performed a backup.
My phone is offering to install 11C. I'd like to update to that version, but at a glance it seems like there may be issues if I ever need to downgrade, or.. I may lose root.
So, for our specific phone, the VS985 model, what is the best way to upgrade to the latest stock ROM and keep root / the ability to downgrade?
Sorry for the noob question, but I'm new to the phone and am seeing some conflicting information, probably due to variances between different versions of the phone. I just want to do this right the first time and avoid having to ask more dumb questions
Look for the thread by bweN diorD in either General or Q&A that starts with [REF] and has img or images in the title.
Use the links in that thread to flash the 12b modem and system images, using autoprime's flash2Modem and flash2System zips (bweN links to that thread).
Your choice on whether you also want to flash the 12b boot image. I did flash the 11c boot, didn't bother with 12b.
After flashing the new images, anything you've tweaked in /system has to be re-nudged -- freezing verizon bloat, freezing "System updates..." (or renaming the /system/app LGDMSClient files), reinstalling the hotspot mod (if you need it). It's a pretty painless evolution.
(Definitely freeze System updates.... Once you've got twrp, if you try to install an OTA directly you'll get stuck in a boot-to-recovery problem. Autoprime has a flashable zip that wipes out the files causing the boot-to-recovery, I keep a copy of that zip loaded on my phone's user volume, but it's simpler to just not try to install an OTA.)
Wow. Okay. Thanks a lot. This is super helpful. I'm downloading as we speak. I hope you don't mind a followup question...
My understanding is that it is safer to avoid flashing the boot image because changes to the bootloader could affect root or the ability to roll back. Is there a reason you bothered flashing 11C?
For anyone else, the thread mentioned is: http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
NegativeOne said:
Wow. Okay. Thanks a lot. This is super helpful. I'm downloading as we speak. I hope you don't mind a followup question...
My understanding is that it is safer to avoid flashing the boot image because changes to the bootloader could affect root or the ability to roll back. Is there a reason you bothered flashing 11C?
For anyone else, the thread mentioned is: http://forum.xda-developers.com/verizon-lg-g3/general/reference-stock-img-files-t2966958
Click to expand...
Click to collapse
There is no downside to flashing it at this point, but I haven't seen proof there is any benefit either. I'm still on 10b running L ROMs no problem, so I don't see any point in updating anything but the modem.
Sent from my G3, rockin Illusion
Which rom are you using?
Look down lol
Sent from my G3, rockin Illusion
You can root 10B and tell supersu to maintain root and take all the OTAs and still keep root. I did that so that I'd have VoLTE and I could take an OTA in the future without issue if it was shown root would survive. Your choice I guess, but we know root survives all the way to 12B so why not go the stock route to ensure you are fully updated? Just my thoughts anyway.
Schaweet said:
You can root 10B and tell supersu to maintain root and take all the OTAs and still keep root. I did that so that I'd have VoLTE and I could take an OTA in the future without issue if it was shown root would survive. Your choice I guess, but we know root survives all the way to 12B so why not go the stock route to ensure you are fully updated? Just my thoughts anyway.
Click to expand...
Click to collapse
im running android version 5.0.2, stock is whats not "fully updated" lol
bweN diorD said:
im running android version 5.0.2, stock is whats not "fully updated" lol
Click to expand...
Click to collapse
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
I tried 5.0.x for a few days but the negatives weren't worth it to me. I am fully updated at 12B as I can still use the G3 with the stock goodies that were added by LG and not cripple the device by putting AOSP on it. Don't get me wrong, I prefer the look of AOSP, but one of the major reasons I got this phone was for the camera and without the 5.0.x roms including LG camera app with them, it's a no go for me. Google camera app just doesn't do it and laser focus is gone so pics are crap in my opinion.
Instead I use g3 tweaks and Nova to make my phone look more like AOSP. I'll wait for the devs to get ahold of 5.0.x for the g3 so we can still keep the g3 goodies before I update any further.
So, I'd say 12B is as fully updated as there is at this point. Just my opinion though.
Schaweet said:
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
I tried 5.0.x for a few days but the negatives weren't worth it to me. I am fully updated at 12B as I can still use the G3 with the stock goodies that were added by LG and not cripple the device by putting AOSP on it. Don't get me wrong, I prefer the look of AOSP, but one of the major reasons I got this phone was for the camera and without the 5.0.x roms including LG camera app with them, it's a no go for me. Google camera app just doesn't do it and laser focus is gone so pics are crap in my opinion.
Instead I use g3 tweaks and Nova to make my phone look more like AOSP. I'll wait for the devs to get ahold of 5.0.x for the g3 so we can still keep the g3 goodies before I update any further.
So, I'd say 12B is as fully updated as there is at this point. Just my opinion though.
Click to expand...
Click to collapse
the camera doesnt stand up to stock, no doubt, but thats the only thing i wish could be better. the rest of that stuff i dont use.
it all depends on what you want/use/need.
i prefer custom roms the majority of the time.
bweN diorD said:
the camera doesnt stand up to stock, no doubt, but thats the only thing i wish could be better. the rest of that stuff i dont use.
it all depends on what you want/use/need.
i prefer custom roms the majority of the time.
Click to expand...
Click to collapse
You're right for sure. It's all personal preference. I figure if the only thing that looks different from stock is the settings menu and not having the quick settings tiles, I'm close enough that I'm not bothered by all the LG colors and added stuff.
I'm waiting for the camera app to get ported then I'm all in on a custom 5.0.x rom. That may be a while, but I can wait.
Schaweet said:
Yeah we all could be as well. The issue is your camera is jacked and you lose things like multi window, ir remote, and quick memo writing.
Click to expand...
Click to collapse
For anyone reading this, I just wanted to let them know that there is a ported version of Quick Remote that works under AOSP / CM including Lollipop. I think it's in the non-variant G3 sections.
Sent from my VK810 4G
Thank you for this thread. Honestly this should be Pinned, I am an extremely saavy/experienced Android user and XDA forum member, and I could not believe how long it took me to find this sort of info for such a popular phone.
This is my first LG phone, and I'm having to learn all the LG and Gseries specific "stuff". The info above was invaluable. :good:
I just purchased an Xperia Z4 Tablet and have been researching the different options when rooting. It seems like the AndroPlusKernel is the most popular choice but I'm not entirely sure why. From what I can tell, that will allow me to use the stock ROM and as such it may be the most issue free?
Another popular option appears to be the CyanogenMod 13. I know that the kernel and ROM are different and I can choose either or both. But after reading through quite a number of posts, I'm not sure what this custom ROM offers that I can't get by just doing AndroPlus followed by some cleanup of unwanted bloat. And would anyone actually want to use both?
Can anybody else provide some insight and direction? I'm not looking to do anything crazy extravagant here, just root access to allow for ad-blocking as well as some additional functions I don't get with stock.
Thanks for helping me learn!
Jadog said:
I just purchased an Xperia Z4 Tablet
Click to expand...
Click to collapse
Congrats and welcome to the club
From what I can tell, that will allow me to use the stock ROM and as such it may be the most issue free?
Click to expand...
Click to collapse
Exactly. AndroPlusKernel is the only custom kernel available for the stock ROM. The stock ROM is the only thing available that runs totally fine. CyanogenMod and derivatives have only just popped up and are still having issues. Even if there were no issues left, I have learnt throughout the years on different Android systems that (rooted) stock will probably run smoother and better battery-wise.
Another popular option appears to be the CyanogenMod 13. I know that the kernel and ROM are different and I can choose either or both. But after reading through quite a number of posts, I'm not sure what this custom ROM offers that I can't get by just doing AndroPlus followed by some cleanup of unwanted bloat. And would anyone actually want to use both?!
Click to expand...
Click to collapse
With Xposed you can add a lot of functionality that years ago you had to flash a custom ROM for. I don't miss anything in stock+root+xposed that I remember from the old days using AOSP-variants on my previous Android devices.
jelbo said:
Congrats and welcome to the club
Exactly. AndroPlusKernel is the only custom kernel available for the stock ROM. The stock ROM is the only thing available that runs totally fine. CyanogenMod and derivatives have only just popped up and are still having issues. Even if there were no issues left, I have learnt throughout the years on different Android systems that (rooted) stock will probably run smoother and better battery-wise.
With Xposed you can add a lot of functionality that years ago you had to flash a custom ROM for. I don't miss anything in stock+root+xposed that I remember from the old days using AOSP-variants on my previous Android devices.
Click to expand...
Click to collapse
Sweet.... and thank you! You answered my question with everything I needed to know. I'll add xposed if I feel I need something extra, but for now, I'm going for the AndroPlusKernel. Time to go hunt for the instructions on doing this!
***Edit*** I think I found what I'm looking for here: http://forum.xda-developers.com/z4-tablet/development/kernel-andropluskernel-v1-t3170689.
However, it shows the latest version is .34. But when I go to the download links, the latest I see is .31. Anybody else have this issue?
jelbo said:
Exactly. AndroPlusKernel is the only custom kernel available for the stock ROM. The stock ROM is the only thing available that runs totally fine. CyanogenMod and derivatives have only just popped up and are still having issues. Even if there were no issues left, I have learnt throughout the years on different Android systems that (rooted) stock will probably run smoother and better battery-wise.
.
Click to expand...
Click to collapse
Actually, stock ROM is supposed to be used with no root and tweeks. For example, YouTube background module for YouTube works with the bug, it just stops to play videos after a while. Only reboot helps to fix it. And according to stability, Resurrection remix is the same stable as stock ROM. Moreover, custom ROM is much easy and faster to upgrade. No flash tool needed, with loss of data.
Battery life with custom ROM is good.
For the simple of heart who don't need the diversity of a custom ROM, but moreso hate the pain of re-rooting after OTA installation. Not intended to host this thread so much as I am here to inspire it...
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
pickupman66 said:
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
Click to expand...
Click to collapse
Can you please explain how to do this? I'm on 7.0, and wanna go to 7.1.1 also
Skickat från min Nexus 6P via Tapatalk
Taken from here:
http://forum.xda-developers.com/nexus-6p/general/nougat-7-1-1-roll-begins-t3513139/page8
1. Download the factory image from here.
https://dl.google.com/dl/android/aos...y-ef607244.zip
2. Select the firmware option on FlashFire.
3. Select ONLY system, vendor and boot images. ***DO NOT SELECT BOOTLOADER OR RADIO***
4. Select Flash.
5. Wait for some time.
6. Might bootloop a couple of times. Do not panic.
7. ENJOY!!!
Techstro said:
For the simple of heart who don't need the diversity of a custom ROM, but moreso hate to pain of re-rooting after OTA installation. Not intended to host this thread so much as I am here to inspire it...
Click to expand...
Click to collapse
Seriously! Not to be rude, but if flashing a zip is that painful for you, perhaps you're in the wrong place.
Sincere apologies...
mikexda said:
Seriously! Not to be rude, but if flashing a zip is that painful for you, perhaps you're in the wrong place.
Click to expand...
Click to collapse
Please forgive me sir. I love custom ROM's, I'm just in a phase right now and I figured that what helps me may help someone else. I don't understand how I offended you though sir. Is it because this thread is a waste of space or that it has no business on XDA? I need clarification in order to understand my error. My only clue is that you said flashing a zip, which leaves me feeling misunderstood... I have been flashing zips since the original HTC Desire which was on 2.1 donut before it's final OTA of eclair. Rooted, S-Off'd, flashed all kinds of mods and ROMS, even had a buggy ICS running on it for a while.
HTC Amaze, how hard was it to S-Off that? The wire trick? Had xPosed, custom boot animation, etc. Then there was Alcatel, had 2 that I rooted, the venture and the evolve2, same as above custom everything.
I'm on my Nexus 6P now, as long as we're getting updates OTA I want to remain stock for a change, at least till the updates stop coming. Maybe it's cuz I said there is pain in re-rooting... it's not just the process of re-rooting, it's everything that is undone and uninstalled when you update with a stock zip, and wiping data is a big step for those in my sort of position so flashing "some" custom ROM's is an un-worthy sacrifice at this phase.
If need be I will edit or delete my original post you quoted. I hope I did manage to bring into focus to some degree at some part of cause for the confusion emoji. Any ideas are welcome and thank you for your analytical input.
pickupman66 said:
I updated with flash fire. It worked perfectly. I am on stock rooted. went from 7.0 to 7.1.1.
Click to expand...
Click to collapse
A perfect example. I have flash fiire but never used it, I read somewhere that it doesn't work as one would expect. That it does not preserve root against OTA, and that there truly is no solution available as if it were not possible. I take your word for it though. I personally am not ready to try it yet, just to provide resources for those who are and to be well educated when I am ready.
I'm still waiting for xPosed for the new architecture, I don't want to update just to find out it's available for 7.0 and not 7.1.1 however unlikely that may be. I know I can always back up, but I'd have to do so regularly to keep it up to date which can't be done once you've upgraded and it may be months before the framework is available if it can be done which I hear it has...
Too many variables, I'm on stand-by, ready to pay and grateful for my memories and the devs responsible for them...