I'm currently rooted and running Slimkat. I just got the notification that the 5.0 OTA is available for download. A few questions:
If I want to stay on Slimkat for now, is there a way to turn off the OTA notification?
If I want to try out 5.0, do I have to go back to stock or can I just take the OTA?
If I do take the OTA and lose root, will I have any problem going back to Slimkat if I want to?
Thanks!
5.0 ota notification on a custom rom???
Ota works only with stock
toxtethogrady said:
I'm currently rooted and running Slimkat. I just got the notification that the 5.0 OTA is available for download. A few questions:
If I want to stay on Slimkat for now, is there a way to turn off the OTA notification?
If I want to try out 5.0, do I have to go back to stock or can I just take the OTA?
If I do take the OTA and lose root, will I have any problem going back to Slimkat if I want to?
Thanks!
Click to expand...
Click to collapse
1. not sure (sorry)
2. i'm not sure what'll happen if you try to accept it running a custom rom....worst case scenario, it fails and you need to flash stock img to the n10, best case, you have stock 5.0....backup what you need to before deciding either way and put it on a pc
3. it shouldn't be any different than when you rooted it the first time
that being said, i'm currently using lollipopalooza and as a die hard slim user, am quite happy with it. it lacks the depth of slim but has a few extra options over stock. and running L gives this device much needed life again. i suggest giving it a try if you have the time to play around with it all
XxM4tzexX said:
5.0 ota notification on a custom rom???
Ota works only with stock
Click to expand...
Click to collapse
there's been reports from other slim users from what i've seen in the n5 forums too....there shouldn't be, i know, but he's not the only one
The ota won't work because you don't have the stock recovery installed. I wouldn't accept an official stock ota on a custom rom. The notification is a bug, it shouldn't appear.
XxM4tzexX said:
The ota won't work because you don't have the stock recovery installed. I wouldn't accept an official stock ota on a custom rom. The notification is a bug, it shouldn't appear.
Click to expand...
Click to collapse
Good to know I shouldn't bother with the OTA.
As for the notifications, I'm seeing things about editing the build.prop to trick Google into thinking I'm current. Can anybody provide the proper edits for the N10/5.0?
Related
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Bump...any info on whether or not its possible would be appreciated.
It should work as long as everything is stock (including recovery and kernel). You will however lose root, but that can easily be reobtained by flashing it after updating.
mrlad said:
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Click to expand...
Click to collapse
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others... I am just curious since I see people do this and it confuses me... Just askin and sorry if you think I may be flamin'.
Do people think the OTA is different somehow or works better somehow
playya said:
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others... I am just curious since I see people do this and it confuses me... Just askin and sorry if you think I may be flamin'.
Do people think the OTA is different somehow or works better somehow
Click to expand...
Click to collapse
Pretty sure that if I flash stock ROM I'm going to lose my settings. I've had VERY bad results backing up and restoring going from 4.2 to 4.3 and really don't want to go through that hassle unless absolutely required.
To answer your other question, I just prefer to be on the OTA.
mrlad said:
Pretty sure that if I flash stock ROM I'm going to lose my settings. I've had VERY bad results backing up and restoring going from 4.2 to 4.3 and really don't want to go through that hassle unless absolutely required.
To answer your other question, I just prefer to be on the OTA.
Click to expand...
Click to collapse
If you are on a stock rom and flash the upgraded version you wont lose your settings. Flashing one rom over another can be done its just frowned up in some cases. Lets be honest though there are quite a few back up tools out there for you to achieve a duplicated look going from one rom to another within the hour.
I hear ya if you had issues but you sure its not in your procedure. Be glad to help you if you need it. Thanks for answering the question though but I believe your route is more cumbersome than just a simple flash but what ever makes you more comfortable is best I get that
mrlad said:
I'm running rooted w/stock OTA 4.3. Are there any special upgrade procedures to update to 4.4 when rooted via Koush superuser and using the stock OTA?
Was able to update to 4.3 OTA w/o incident (see thread below)
http://forum.xda-developers.com/showthread.php?p=45183403#post45183403
Click to expand...
Click to collapse
Mine was same specs like yours (stock 4.3 - rooted by Koush superuser) and updated to 4.4 through OTA just fine :good:
Never had any problem with Koush superuser and OTAs on both Nexus 4 & Galaxy Nexus (can't say the same with supersu)
Tried to upgrade to 4.4. The upgrade failed and the phone reports no command when I reboot. Still on stock recovery.
Any suggestions on what I should try next to recover?
Note: I do have TWRP available while running fastboot.
I installed the factory stock image (and formatted the cache but didn't wipe out the userdata image). I know the first boot should take an extended amount of time, but its been showing the rotating circles for about 8 minutes now. What is a reasonable amount of time for the initial boot?
Wiping the cache and the Dalvik cache from TWRP solved it. I'm rooted again and things appear to be back to normal.
playya said:
If you are rooted why not just flash a rooted stock rom? Confused why you wait for answers from others...
Click to expand...
Click to collapse
Well....I'm on the stock ROM now (Google forced my hand).
mrlad said:
Well....I'm on the stock ROM now (Google forced my hand).
Click to expand...
Click to collapse
what does that mean?
playya said:
what does that mean?
Click to expand...
Click to collapse
The 4.4 OTA upgrade failed and wouldn't boot. A poor attempt at humor I guess.
mrlad said:
The 4.4 OTA upgrade failed and wouldn't boot. A poor attempt at humor I guess.
Click to expand...
Click to collapse
root it and flash anything you want my friend... take control of your phone back...
Hey guys. I want to get to 4.4.2 but I'm currently on 4.2. I have root and a custom recovery, and my OTA updates are failing a verification check. The OTA is trying to update to 4.3.
Is there a zip I can flash to go to 4.4.2 without having to wipe my phone? Or do I need to flash in order? Or is my only option wiping everything and flashing stock (how would I do that)? If that's the case I'll probably just stick with 4.2. I want to skip right over 4.3 because that was a buggy mess for me that ultimately resulted in terrible battery life and broken apps. But I've heard good things about 4.4.2
bump..
Sounds like you want a flashable stock 4.2.2 build, right? Haven't tried it myself, but it seems this thread is where you want to look.
Use this : http://forum.xda-developers.com/showthread.php?t=2566042
It's a flashable zip of the 4.4.2 Stock ROM, only zipaligned (doesn't cause problems in OTA). Flash it through TWRP, and you're done. Good luck!
bruinhoo said:
Sounds like you want a flashable stock 4.2.2 build, right? Haven't tried it myself, but it seems this thread is where you want to look.
Click to expand...
Click to collapse
That's not quite what I was looking for but thank you for the answer.
Lt.Win said:
Use this : http://forum.xda-developers.com/showthread.php?t=2566042
It's a flashable zip of the 4.4.2 Stock ROM, only zipaligned (doesn't cause problems in OTA). Flash it through TWRP, and you're done. Good luck!
Click to expand...
Click to collapse
That's what I wanted! Thanks much, seems to be working great. Loving everything but the white phone app and I dislike Hangouts. Thanks much. :]
Android 5.0 (Lollipop) Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.
That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
nice info
lost101 said:
Android 5.0 Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.
juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
As always, very informative thread @lost101.
lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Is stock recovery and stock firmware same? If not how do i get stock recovery back?
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Ermagerd. OTA is live. Just tested myself by unfreezing software update and checking ota. Large file. 683 mb. C'mon rooty goodness
Sorry, its been years since I last rooted a phone. If I'm rooted I cannot do the OTA right? I would have to have a custom recovery and flash it like that right?
Turb0wned said:
Sorry, its been years since I last rooted a phone. If I'm rooted I cannot do the OTA right? I would have to have a custom recovery and flash it like that right?
Click to expand...
Click to collapse
That's correct. You can follow the return to stock method to go back to stock unrooted and ota but doing so may result in you not being able to root as there is no root method for 5.0 yet. Either wait for stock rooted to be posted by one of your awesome devs (should be soon. they are usually quick to offer stock rooted ota pkgs) or go straight stock. Since I read news today that xposed is going live for lollipop soon I am going to wait for stock rooted ota.
BreakingVZW said:
That's correct. You can follow the return to stock method to go back to stock unrooted and ota but doing so may result in you not being able to root as there is no root method for 5.0 yet. Either wait for stock rooted to be posted by one of your awesome devs (should be soon. they are usually quick to offer stock rooted ota pkgs) or go straight stock. Since I read news today that xposed is going live for lollipop soon I am going to wait for stock rooted ota.
Click to expand...
Click to collapse
Thank you! I'll wait, what's a few hours going to do! Hope battery life is improved!
Me too..!!
BreakingVZW said:
That's correct. You can follow the return to stock method to go back to stock unrooted and ota but doing so may result in you not being able to root as there is no root method for 5.0 yet. Either wait for stock rooted to be posted by one of your awesome devs (should be soon. they are usually quick to offer stock rooted ota pkgs) or go straight stock. Since I read news today that xposed is going live for lollipop soon I am going to wait for stock rooted ota.
Click to expand...
Click to collapse
I am also thinking to wait for the rooted stock one to be posted... Currently on Illusion rom and its running great.. Some bugs, but can live with it until stock one arrives.. Good advise @BreakingVZW.. Thanks..
I unrooted and factory re-set the phone. Two different root checkers say I am not rooted. However, I get a message that I cannot update because a root is detected!!! Have tried 3 times now. Any help would be greatly appreciated!!!!!
LG-D850 D85010f on AT&T
Turb0wned said:
Thank you! I'll wait, what's a few hours going to do! Hope battery life is improved!
Click to expand...
Click to collapse
Lol Idk if it will be only a couple of hours. That'd be nice but our devs have lives and do this stuff in their spare time. In theory they SHOULD be able to follow the same method devs from the international versions used to give users their rooted ota updates but sometimes it's just not that easy. This is the first US carrier release for the G3 so there may be security updates that weren't present in the international releases.
Spartanguy83 said:
I unrooted and factory re-set the phone. Two different root checkers say I am not rooted. However, I get a message that I cannot update because a root is detected!!! Have tried 3 times now. Any help would be greatly appreciated!!!!!
LG-D850 D85010f on AT&T
Click to expand...
Click to collapse
You restored stock via flash tools ? That'd be a first I've heard of persistent root after a pure factory reset via that method. Did you get the green pass message when completed and all?
You may want to attempt a 10D flash instead of 10f. I never have issues restoring with 10d
BreakingVZW said:
You restored stock via flash tools ? That'd be a first I've heard of persistent root after a pure factory reset via that method. Did you get the green pass message when completed and all?
Click to expand...
Click to collapse
BreakingVZW said:
You may want to attempt a 10D flash instead of 10f. I never have issues restoring with 10d
Click to expand...
Click to collapse
Yes I did. I found this (via a YouTube tutorial) that I am going to try. I post back!
An applicatin requires and update requested by google play services
When I click on this I just get the options of deactivate and open???
Camera API?
Does anyone know if the Lolipop update has the new Lolipop camera API?
Hope they will release it for d855 soon.
magikmichael said:
Hope they will release it for d855 soon.
Click to expand...
Click to collapse
D855 got official lollipop a long time ago, it was the first G3 variant to receive it.
4ndroid99 said:
D855 got official lollipop a long time ago, it was the first G3 variant to receive it.
Click to expand...
Click to collapse
Yes 5.0. But at&t got 5.0.1 if im not mistaking.
Yep it has: http://www.androidpolice.com/2015/0...rly-700mb-d85020f-update-packs-android-5-0-1/
it may be harder for ATT g3 to get a L flashable rom due to lack of KDZ for ATT devices.. where the international users can just split the KDZ and repack into zip.
if someone wants to send me an AT&T g3 I can make one though
autoprime said:
it may be harder for ATT g3 to get a L flashable rom due to lack of KDZ for ATT devices.. where the international users can just split the KDZ and repack into zip.
if someone wants to send me an AT&T g3 I can make one though
Click to expand...
Click to collapse
So the method of pre-rooting won't work with D850 lollipop BC it uses tot? KitKat for our variant uses tot as well and they still got us a rooted ota 10f update. Most posts I've read about G3 lollipop (lg stock not aosp) have said in order to have root on Lollipop you have to be on KitKat to use the same exploit used on KitKat. Is that not a viable solution anymore? I actually like the lg stock ROM and features. If we can't root the stock g3 rom on lollipop I'm going to have to look into getting a nexus 6 and will sell this. Xposed is apparently up and running well with lollipop and I gotsta has me ma xposed.
How is the 5.0.1 update running? Hope that the D855 version will be releasing soon. I'm on 5.0 V20H version and it's runs great
AndroidCity said:
How is the 5.0.1 update running? Hope that the D855 version will be releasing soon. I'm on 5.0 V20H version and it's runs great
Click to expand...
Click to collapse
Don't know. I want to OTA and all but I need root. I use many programs that require root and just not having the ability to remove bloatware is reason enough for me to wait for a rooted OTA. Really hope one of the devs can figure out how to make a flashable OTA zip.
BreakingVZW said:
So the method of pre-rooting won't work with D850 lollipop BC it uses tot? KitKat for our variant uses tot as well and they still got us a rooted ota 10f update. Most posts I've read about G3 lollipop (lg stock not aosp) have said in order to have root on Lollipop you have to be on KitKat to use the same exploit used on KitKat. Is that not a viable solution anymore? I actually like the lg stock ROM and features. If we can't root the stock g3 rom on lollipop I'm going to have to look into getting a nexus 6 and will sell this. Xposed is apparently up and running well with lollipop and I gotsta has me ma xposed.
Click to expand...
Click to collapse
10f had a rom because there was still root on 10f and you could backup system, boot and modem.
someone may have another solution worked out.. or even a tot to pull the files from. but it's not going to be as easy as it was previously due to no public root for L at the moment, the difficulty of getting a tot and lack of KDZ. Unfortunately I only have the T-Mobile version.. otherwise I'd be able to make one for you guys.
So I checked that once I am rooted, I will no longer get any official updates. Is that true? Any workarounds for that?
If I am on stock rooted rom, then how will I receive updates?
Anyone?
You won't. ..that's the point of rooting...an update is likely to break the root
Do we need to freeze anything to avoid an ota before we know it's safe?
Sent from my SM-G928C
So what's the option to update after rooting? What does the general majority do?
You wait for a dev to take whatever update was released to dissect and tweak and wait for their release.
sacthegreat said:
So I checked that once I am rooted, I will no longer get any official updates. Is that true? Any workarounds for that?
If I am on stock rooted rom, then how will I receive updates?
Click to expand...
Click to collapse
Hello. As I know you wont get OTA update, you can flash original updated firmwares via odin(downloaded from sammobile.com). At the other hand you can flash custom roms which based new firmware, your choice. Thank you.
Ok so effectively, its better to put custom Rom as they will provide updates regularly.. If I install official firmware everyone a new update comes, then again I'll have to root it separately.. That is just irritating.. So better to go to custom Rom then! Thanks!