Sorry I'm a newbie. I recently installed Android L using factory images but didn't love it cause I couldn't root it using the SU binaries. So, I re-installed Android 4.4.4 using factory images and rooted it as it was before. My question is will I ever get Android L update over OTA or rooting will prevent the OTA. In About Tablet it always say Your system is up to date with recent check time. Many websites said that rooting does not hinder the OTA. Also some said that you do get notification but the OTA does not get installed because of some script checking your system.
Can anyone please clarify me what is it actually? Has any of the rooted Nexus 7 here got update for Lollipop?
P.S. I know that I can always use the factory images but my question is regarding OTA update on rooted device.
If you search, you'll find 2 different methods to gain root on Android L.
The only things that will prevent an OTA from installing are a custom recovery and modified system files.
Google has all the answers that you seek.
nhizzat said:
If you search, you'll find 2 different methods to gain root on Android L.
The only things that will prevent an OTA from installing are a custom recovery and modified system files.
Google has all the answers that you seek.
Click to expand...
Click to collapse
I did install Android L and was out of luck with rooting so had to revert back to 4.4.4. I searched the forums then but none helped. Only thing I have is TWRP custom recovery and Gravity Box installed (which I think makes UI changes so system changes I suppose, not sure about that). But, even in these cases from what I read I found that you will get an OTA notification in the System Update section but thing won't get installed returning an error.
Can you post the links regarding the two methods that works on lollipop. I tried the chainfire's SUPERSU zip and installed it using TWRP recovery but that gave an error saying "SU binaries not found. Did you recently update to 4.4.3."
meteors2313 said:
I did install Android L and was out of luck with rooting so had to revert back to 4.4.4. I searched the forums then but none helped. Only thing I have is TWRP custom recovery and Gravity Box installed (which I think makes UI changes so system changes I suppose, not sure about that). But, even in these cases from what I read I found that you will get an OTA notification in the System Update section but thing won't get installed returning an error.
Can you post the links regarding the two methods that works on lollipop. I tried the chainfire's SUPERSU zip and installed it using TWRP recovery but that gave an error saying "SU binaries not found. Did you recently update to 4.4.3."
Click to expand...
Click to collapse
Are you still looking for an answer for this? Use Chainfire's CF-Auto-Root.
It is my understanding (perhaps incorrectly) that you can OTA from 4.4.4 to 5.0 with root, but any further upgrades (say, to 5.0.1) will fail if any system files have been modified. Xposed works by modifying system files, so it must be uninstalled, and root must be removed. Like I said, I'm not 100% sure about the ability to OTA from 4.4.4 to 5.0 with root, but I am sure about NOT being able to OTA from 5.0 upward with root.
Hello NPOA556, Today I'm still on 4.4.4 and I got update notification for 5.0.1 of 389 MB. But it keeps saying insufficient space on device when I still have 4.3 GB free. Does it need free space in system ROM which is just 133 MB free of 867 MB. Or this issue if because I'm getting OTA directly on 4.4.4 for 5.0.1 which is again rooted and with Xposed and other things installed?
Please guide me.
Related
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Pickle_Jr;4f86 said:
After some vigorous searching I've found out that if you don't modify the boot loader then you should be okay receiving OTA updates. I'd like to root my nexus 7 so I can run some apps that require root access. I've looked at many methods on how to root the nexus 7, but from my noob understanding, the majority of these methods require unlocking the boot loader and getting TWRP recovery. Won't that mess up the OTA? I've searched a couple threads but I don't necessarily understand the difference between an unlocked boot loader and a rooted device. The reason I still want to have OTA updates is so that I can still update android and so on.
Thanks for taking the time to read this and help guys!
Click to expand...
Click to collapse
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
sfhub said:
On this platform, at this time, you need to unlock the bootloader to install root.
You don't need to flash/install twrp if you don't want to, but you need to boot into twrp temporarily to install the root files.
Even if you install twrp rather than boot into it temporarily, it won't cause your ota to fail.
The things that cause the ota to fail are
1) modifying or deleting any files with your root permissions
This includes root apps which do things you might not realize
2) installing custom kernel
3) installing earlier version of supersu
Click to expand...
Click to collapse
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay? I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Pickle_Jr said:
Awesome! Thanks! So if I understand correctly, as long as I be careful about what root apps I have as well as have a newer (newest) version of SuperSU installed I'll be okay?
Click to expand...
Click to collapse
Yes.
For example, if you freeze a stock app in titanium, that is ok, but if you remove a stock app, then an OTA will likely fail.
If you use stickmount, it modifies a system file and backs it up, then restores it when it is done, but sometimes that gets out of sync, in which case the OTA fails.
There are other examples.
Pickle_Jr said:
I'm assuming I'll lose root when I get an OTA update but hopefully when the time comes, there'll be a way to root android 4.4 when the n7 get's it as well. And if something goes wrong I guess I could just unroot, factory reset, and update OTA that way too. Thanks for the help!
Click to expand...
Click to collapse
If you install root through the stock recovery, you'll lose root permissions (but the files will still be there). Just re-root using the existing procedure.
If you want to save a step, boot into TWRP to install the OTA (which you download manually) and then "chain" install the OTA, then the root install files.
This way, you lose root for half a second until the 2nd install file in the chain runs. Essentially you won't lose root (or won't notice losing root) because the first time you boot into 4.4, you'll have root.
Hello,
I am fighting since yesterday to get the OTA update to install so I wanted to share my current steps and hopefully someone can suggest how to move on.
I have a GT-I9505, initially 'samsung version'. I installed TWRP in order to install the GPe edition. My phone is rooted.
I used to have TWRP 2.6.x
A few days ago, I got like many the OTA update for Lollipop. I let the phone download it and reboot. That´s when things became a bit more complicated.
After reboot, it went to TWRP where no update happened. If I reboot, I get back to be GPe version 4.4.4
I tried upgrading TWRP to a recent version without better results. I tried with TWRP 2.8.1.0
I have read in several places that the issue is that the OTA update expects the stock recovery.
Unfortunately so far I did not find a stock recovery for my S4 that does the trick.
I tried using the "Miustone_stock_recovery-flash-GE4.3". I could install the recovery.
I did save the OTA zip but I don´t know how I can skip the download and use the OTA zip... so so far I do it the 'lazy-lengthy' way and I wait for the download.
After flashing this 4.3 recovery, I get a slightly better result (but nothing better than I got using TWRP): After downloading the OTA, the phone reboots, goes to recovery and it tries to install the OTA update but it fails with the following message:
mmc_test.ko has unexpected content... Status 7
Can anyone suggest a way to easily install this OTA? I guess using a correct recovery could help... if I could find it.
Any hint appreciated.
if your rooted, you cannot OTA update.
justda said:
if your rooted, you cannot OTA update.
Click to expand...
Click to collapse
Are you saying the recovery is NOT the issue and if I unroot (I guess this is possible) it would work ?
As an update, I just tried now using Miustone_Stock_Recovery-flash-XXUBMF8.zip and I get the same result.
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
justda said:
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
Click to expand...
Click to collapse
Hi Justda,
First of all, thanks for your time and answers. My expectations are fairly low actually I installed the GPe version thinking it would make it simpler.
I was happy to get the OTA thinking I could upgrade in a click...
I realize from your answer that the OTA I am getting on my I9505 is actually meant for the I9505G and thus will not work whatever I do (correct me if I am wrong).
I will follow your advice and pick up one of those ROMs. Do you recommend a specific one?
iBastid or Danvh are my go to guys. Both are active and have a large following of users.
Danvh is straight up no aroma install, you mod it yourself.
Bastid uses aroma to give you more initial choice with his customizations.
But its up to personal preference right now, GPE is still to new for a lot of ROM pimping...
Sent from my GT-I9505G using XDA Premium HD app
I would suggest you to use antaresone's lollipop rom
link here http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934
Questions, it's not here, ask to move this thread in the good section... Q & A
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
How I Did it...
From a site with this in the title:
can_i_manually_flash_601_also_does_ota_work_with
Systemless root doesn't break ota, non-stock recovery breaks OTA.
Unlock bootloader, flash 6.0.1, flash TWRP, flash systemless root...
I did this:
Went back to stock recovery, by flashing via ADB, rebooted downloaded and attempted to install OTA on phone. Process started, rebooted, proceeded and then failed with error . Rebooted, got Factory image.
Extracted and ran flash-all.bat ONLY AFTER Removing the -w from this line:
fastboot -w update image-bullhead-mmb29k.zip
Got latest SuperSU v2.61 zip with auto boot patcher:
See androiding.how/android-6-0-1-root
Copied this to Memory on phone.
Flashed/Installed TWRP Recovery using ADB.
Booted into TWRP Recovery and installed SuperSU.
So now I'm running systemless rooted 6.01 on a Nexus 5X with mmb29k and every thing is working.
I think even though I rooted systemless 6.0, the modified Boot Image was still not letting OTA work.
We shall have to wait and see on the next OTA. Maybe just going back to stock recovery will be all that's needed.
There are some ADB commands that allow you to temporarily select a recovery image, but I'm not sure how that works.
Good Luck!
teapea said:
I know there are several threads covering similar things, however I still can't find the relevant info for my specific question.
I am on 6.0 Build L
I rooted using systemless root - I have changed nothing in my system partition as far as I know as I wanted root for AdBlock and TitaniumBU.
I am using the stock kernel too.
TWRP 2.8.7.2
I now have a 6.0.1 OTA - but I'm 100pc confused as to exactly how to go about installing this.
Some people seem to say OTA on this setup will work fine on similar setups.
Others say I need to flash 101 things to get it working.
Literally no idea.
Click to expand...
Click to collapse
Hi everyone
I want to root my nexus 5x to have xposed but the main issue is that I wouldn't be able to install otas even if I rooted with systemless root because xposed misses up system partition , so systemless root becomes pointless .
My question is if I rooted with systemless root and installed xposed , if I wanted to install any new ota if i just removed xposed will this be enough to return system to unmodified status and I can now install the ota , or my system will become modified untill I reinstall the whole binary image ??
Hope I made my question clear as possible and sorry for my bad English
Thanks in advance ...
Or, instead of worrying about OTAs, you could just get the images from the Google website since this is a Nexus device, we are supported for something like 3 years I think I read, with security updates persisting 1.5 years after that.
https://developers.google.com/android/nexus/images
(you would use fastboot flash to accomplish this)
I know , but I don't want to flash everytime the whole binary image if I just can install a ~< 10 mb OTA .
If i can Just uninstall xposed then install the ota that will be much easier ...
I don't think you can take ota updates with a custom recovery and without a custom recovery you would have to flash a system image to get it back to stock in order to take the ota
flashing updates manually via TWRP is very easy once youre used to doing it.
No I can install OTAs using flash fire if the system partition is unmodified , so that's why I'm asking if uninstalling xposed return system partition to unmodified status ?
@2x4 installing updates is very easy with chainfire's flashfire only if you have unmodified system partition , and I want to install xposed but at the same time I want to know if I just uninstalled xposed will that make my system unmodified again ...
Running the xposed uninstalled will undo any changes to the system partition. So to answer your question, yes.
@t-r-e you're coming from the angle of keeping your system partition intact for the SOLE purpose of OTAs (you've said nothing about android pay). Given that, it's easier to just update manually via TWRP instead of doing OTAs, so you won't have to worry about xposed or any other mods.
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
randallrbaker said:
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
Click to expand...
Click to collapse
right now xposed isn't compatible with nougat anyway.
to got back to M or L follow section 11 of this guide: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
after that you can install twrp, supersu and xposed again.
I kNow nougat doesn't have Xposed yet and I was content with waiting it out but root doesn't even work. And I have some Google app that need to be removed lol. Thanks for the help I'll get back to you on the process!
randallrbaker said:
Let's make this quick. Received nougat update, decided to root device, nougat version is nrd90r, twrp recovery version is 3.0.2-2, superSU tells me that I properly have root, root apps ask for root, the root apps never end up working and now I just want lollipop back. Tried cm 13 nightly but the zip file errors every time and I've downloaded it many times. Can someone give me some help. All I need is a rooted phone that works with Xposed. Thanks in advance for the help
Click to expand...
Click to collapse
It isn't that root isn't working, is that the apps your using need an update on how they call su. Su has changed with Android n and some things need updates to support it
Sent from my SHIELD Tablet K1 using Tapatalk