Is this even possible if my device is rooted and running custom kernel?
Thank you!
Short Answer ----- No!
Long answer, you need to be completely stock, with an untouched system partition, stock recovery and boot images to accept OTA.
Even with systemless root, if something has modified the system OTA's will fail.
corkiejp said:
Short Answer ----- No!
Long answer, you need to be completely stock, with an untouched system partition, stock recovery and boot images to accept OTA.
Even with systemless root, if something has modified the system OTA's will fail.
Click to expand...
Click to collapse
Thanks. I appreciate quick response.
dirtblade said:
Is this even possible if my device is rooted and running custom kernel?
Thank you!
Click to expand...
Click to collapse
if you're bootloader is unlocked you can manually flash the updated images via fastboot
Flashfire App is an option.
If your system partition is completely stock, untouched by root file manager/twrp and you have systemless root.
Chainfire Flashfire app should be able to apply the OTA even with a modified kernel, as it restores the stock boot and recovery images.
Chainfire said:
Release notes: https://plus.google.com/+Chainfire/posts/FjWwBm9vGyj
Changelogs: http://forum.xda-developers.com/showpost.php?p=59962696&postcount=8
Enjoy, and remember to re-report any issues, even if previously reported for an older version.
Click to expand...
Click to collapse
Chainfire said:
v0.27 released - https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx
Click to expand...
Click to collapse
Related
I really like the way my OneMax w/verizon is and am not really interested in updating. The automatic firmware downloads is eating up my data daily. I just accepted to install it so it would stop, but it won't install due to error (it's a rooted device). I have S-Off on the phone right now and used the SuperSu unroot feature to try and let the update do it's thing just so it would stop downloading. Now, the root checker apps say I'm not rooted (but i think i still am). I tried the virtuous manual stock update but it gives me a installation aborted message while in recovery mode. Any help would be appreciated!
I think you need to have stock recovery & stock rom installed to accept the ota.
jerrycycle said:
I think you need to have stock recovery & stock rom installed to accept the ota.
Click to expand...
Click to collapse
so i have to fully unroot, update my phone then root again?
FrankieTheSqueeler said:
so i have to fully unroot, update my phone then root again?
Click to expand...
Click to collapse
Yes, if you want the update you will.
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
FrankieTheSqueeler said:
one last question, my device won't pop up on ABD devices on my PC anymore. Am I still rooted?
Click to expand...
Click to collapse
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
dottat said:
you only need to have stock recovery installed AND 100% stock system files. no system mods whatsoever.
assuming you enabled USB debugging under the developer options on the phone....you may need to update your version of adb/fastboot.
The root question....are you s off? If so that question is irrelevant as you only need to flash a custom recovery and flash the latest su zip from there to root any ROM...even the stock ota.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply!
Yeah I have S-off on the phone. I will update the ADB version and retry. I don't know why I thought the su would be able to do a one-click unroot. All it ended up doing was just confusing me. I'm new to rooting and flashing, and it's fun figuring these things out. You guys are really helpful around here. I'll look for a tutorial on how to flash a custom recovery.
Hi There,
I'm running a rooted version of KitKat 4.4.4 on my Z2 (23.0.1.A.0.167) and I was just wondering about the process of upgrading to a rooted version of Lollipop. Can I just upgrade using the standard method (from the settings menu) and retain root access? Or will I have to flash an entirely new Lollipop ROM onto the device and then root that separately?
I'm in no rush for Lollipop so I'm happy to wait for the official upgrade, but if it won't be possible or will mess up my device then I'd rather just do whatever it takes to get it flashed.
BottleGreen said:
Hi There,
I'm running a rooted version of KitKat 4.4.4 on my Z2 (23.0.1.A.0.167) and I was just wondering about the process of upgrading to a rooted version of Lollipop. Can I just upgrade using the standard method (from the settings menu) and retain root access? Or will I have to flash an entirely new Lollipop ROM onto the device and then root that separately?
I'm in no rush for Lollipop so I'm happy to wait for the official upgrade, but if it won't be possible or will mess up my device then I'd rather just do whatever it takes to get it flashed.
Click to expand...
Click to collapse
I guess your bootloader is still intact, if so you're good to go. You will will only lose root when you update to lollipop through OTA.
On the other hand, if you've unlocked your bootloader and probably have a custom kernel, then I'm afraid ota will not work.
Hope this helps.
BottleGreen said:
Hi There,
... and I was just wondering about the process of upgrading to a rooted version of Lollipop.
Click to expand...
Click to collapse
sublinker said:
I guess your bootloader is still intact, if so you're good to go. You will will only lose root when you update to lollipop through OTA.
On the other hand, if you've unlocked your bootloader and probably have a custom kernel, then I'm afraid ota will not work.
Hope this helps.
Click to expand...
Click to collapse
If the desired outcome is root on lollipop, don't do ota.
Install recovery (if you don't have one) and flash a rooted lollipop zip through recovery.
@o0 Matt 0o, you've made your point but I guess quoting me wasn't necessary.
Thanks for the replies, a couple of questions still though:
o0 Matt 0o said:
If the desired outcome is root on lollipop, don't do ota.
Install recovery (if you don't have one) and flash a rooted lollipop zip through recovery.
Click to expand...
Click to collapse
I think I have recovery, though I can't remember to be honest. I followed a guide here when I rooted my Z2.
If I flash a rooted L zip does this mean I'll lose all my apps/data? I remember that I did when I rooted 4.4.4 but the process was such a headache that I can't remember which parts required wiping everything from my phone.
Also, is there a ROM version you'd recommend? Is the current one stable or should I wait a little while longer for a better one?
Google recovery and Xperia to see videos of how to get into recovery to find out if you have it.
You don't 'need' to wipe, but it's always advised. Before I flash I do a nandroid backup and wipe and recovery specific app data with nandroid manager.
Have a look at the dev section, there is a rooted stock lollipop room there. lollipop is stable and awesome.
If.I helped don't forget to hit thanks [emoji14]
o0 Matt 0o said:
Google recovery and Xperia to see videos of how to get into recovery to find out if you have it.
You don't 'need' to wipe, but it's always advised. Before I flash I do a nandroid backup and wipe and recovery specific app data with nandroid manager.
Have a look at the dev section, there is a rooted stock lollipop room there. lollipop is stable and awesome.
If.I helped don't forget to hit thanks [emoji14]
Click to expand...
Click to collapse
Is it worth waiting for a Lollipop 5.1 ROM or would this ROM update to 5.1 without needing to be flashed? http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150/ (I presume this is the ROM you were talking about?)
Thanks, turns out I do have recovery. I followed this guide all the way through: http://forum.xda-developers.com/xperia-z2/general/how-to-root-23-0-1-0-167-fw-sony-xperia-t2928591/
So seeing as I have CWM recovery on there. Does this mean I can just use flashtool to put the lollipop ROM onto CWM Recovery and then do 'install from zip' and all should be good?
What would happen if I flashed without wiping the data? I'm more inclined to wipe too, but I wondered if it's possible to do it without wiping.
BottleGreen said:
Is it worth waiting for a Lollipop 5.1 ROM or would this ROM update to 5.1 without needing to be flashed? http://forum.xda-developers.com/xperia-z2/development/stock-d6503-23-1-0-690-bal-rooted-t3057150/ (I presume this is the ROM you were talking about?).
Click to expand...
Click to collapse
Yea that's what I was referring to. Once 5.1 comes out you'll need to do the same thing to keep root so it's up to you if you do it once or twice.
BottleGreen said:
Thanks, turns out I do have recovery. I followed this guide all the way through: http://forum.xda-developers.com/xperia-z2/general/how-to-root-23-0-1-0-167-fw-sony-xperia-t2928591/
Click to expand...
Click to collapse
Good
BottleGreen said:
So seeing as I have CWM recovery on there. Does this mean I can just use flashtool to put the lollipop ROM onto CWM Recovery and then do 'install from zip' and all should be good?
Click to expand...
Click to collapse
No. No flashtool needed just get the zip into the phone (either download it on the phone or use a usb cable to copy it over) then go to install zip.
BottleGreen said:
What would happen if I flashed without wiping the data? I'm more inclined to wipe too, but I wondered if it's possible to do it without wiping.
Click to expand...
Click to collapse
What would happen depends on what you've done:
Best case nothing happens
Medium case apps misbehave
Worst case bootloop
It is possible and give it a go. Make sure you do a backup first and copy the backup to your computer just in case. If bad things happen, recovery the backup and try again another way.
o0 Matt 0o said:
Yea that's what I was referring to. Once 5.1 comes out you'll need to do the same thing to keep root so it's up to you if you do it once or twice.
Good
No. No flashtool needed just get the zip into the phone (either download it on the phone or use a usb cable to copy it over) then go to install zip.
What would happen depends on what you've done:
Best case nothing happens
Medium case apps misbehave
Worst case bootloop
It is possible and give it a go. Make sure you do a backup first and copy the backup to your computer just in case. If bad things happen, recovery the backup and try again another way.
Click to expand...
Click to collapse
Okay perfect, thanks for that. One last question though, in that thread with the Lollipop ROM someone mentioned that you could lose your recovery if you install it (I guess because of a bug or something). Will this affect me if I want to install 5.1 later on?
Not really. You'll just need to get back to a ROM with recovery for locked bootloader or wait until they get recovery working on locked bootloader on 5.0
o0 Matt 0o said:
Not really. You'll just need to get back to a ROM with recovery for locked bootloader or wait until they get recovery working on locked bootloader on 5.0
Click to expand...
Click to collapse
Okay, so my bootloader has been unlocked. Does that mean I won't be affected at all?
BottleGreen said:
Okay, so my bootloader has been unlocked. Does that mean I won't be affected at all?
Click to expand...
Click to collapse
Is that first sentence a statement or a question?
Bootloader unlocked means freedom. Life is a lot easier, just flash a kernel with recovery and upgrade
o0 Matt 0o said:
Is that first sentence a statement or a question?
Bootloader unlocked means freedom. Life is a lot easier, just flash a kernel with recovery and upgrade
Click to expand...
Click to collapse
Yes my bootloader is unlocked, I used the Sony method. I didn't think I could flash a rooted ROM without it to be honest.
Hmm, I think I'm confusing recovery with Bootloader though here. I thought Recovery was part of the bootloader unlocking process and was separate from the ROM. Kind of like a small management interface to flash new ROMs and manage the device from the boot partition.
Does anyone have an answer to the above? I'm just trying to make sense of the process here.
What do you want to know? What the bootloader is?
http://forum.xda-developers.com/wiki/Bootloader
o0 Matt 0o said:
What do you want to know? What the bootloader is?
http://forum.xda-developers.com/wiki/Bootloader
Click to expand...
Click to collapse
I'd really like to know what 'recovery' is exactly and how it differs from either a ROM or a bootloader. I understand the Xperia Z2 stock rooted Lollipop ROM has no recovery, so I want to know what exactly that means and what the implications are in the event I choose to upgrade to 5.1 in the future.
hi guys.i have nexus 9 with unlock bootloader, rooted mmb29s lte and twrp installed.do i need to flash all mmb29r stock rom or there are another method how to flash update from google.
thanks in advance
Sent from my Nexus 9 using Tapatalk
As no one else replied.
http://www.digitaltrends.com/mobile/how-to-install-android-factory-image/
Can be done without wiping data if needed.
Also checkout Chainfire's Flashfire App, if you have systemless root and an unmodified system, which can update by ota.
Can also be used to flash factory images.
Alternatively just flash boot, system and vendor images.
Reboot to recovery, wipe cache and dalvik cache, flash, reboot system = dirty flash.
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
TheMuffnMan said:
I assume we're talking about going from MMB29S to MMB29R? For the February security patches?
I'm currently downloading 29R and have a rooted MMB29S (TWRP). Have we confirmed or played with Flashfire on the Nexus 9? I've used it with my S5 with success but haven't on the tablet.
Click to expand...
Click to collapse
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are you hoping to update by OTA or using it to flash factory images?
corkiejp said:
Let us know if it works out for you.
I tried it with February OTA, but my system had been mounted RW so it failed.
Flashed the Factory Image with NRT instead, then was playing with Flashfire and successfully applied the R OTA on top of it (even with ElementalX Kernel installed).
Are hoping to update by OTA or using it to flash factory images?
Click to expand...
Click to collapse
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
TheMuffnMan said:
Definitely not OTA - probably bricking that if I tried haha.
Flash the factory images separately I'm thinking.
Click to expand...
Click to collapse
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
corkiejp said:
As long as your bootloader is unlocked, it would be pretty hard to brick it.
I will be trying it by OTA for March's update.
Click to expand...
Click to collapse
I say brick, I actually mean like boot loop - where I'd need to do a full erase and rebuild. Not an actual creation of a paperweight.
it hard to flash whole rom for every update.and i once have brick my tab.twrp not recognise internal storage,it state internal storage 0mb.
Sent from my Nexus 9 using Tapatalk
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Then I just did my usual process, extracted each file, flashed each - except recovery which I flashed with TWRP 3.0.0.2 and then rebooted into Recovery where I flashed SuperSU 2.6.6 Beta, wiped Dalvik/cache and then booted tablet.
Retained all my data and it seems to be running fine.
TheMuffnMan said:
Just completed it last night, tried OTA for ****s and giggles with FlashFire (it auto detects an OTA pending) which did absolutely nothing. Just booted back up as it was MMB29S.
Then I tried just the OTA for fun, got a dead Android symbol.
Click to expand...
Click to collapse
Any chance you still have access to the logs? Try posting to the linked thread.
Chainfire said:
In case of issues, immediately after rebooting back into Android:
- Post /sdcard/FlashFire/lastlog
- Post /proc/last_kmsg
The latter may not be present, and is replaced on every reboot. So if you rebooted twice, no sense posting it.
Click to expand...
Click to collapse
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
corkiejp said:
Any chance you still have access to the logs? Try posting to the linked thread.
Click to expand...
Click to collapse
I'm sure I could probably dig them up!
corkiejp said:
Didn't know TWRP was updated, just used flashfire to flash the updated version.
Why not the latest SuperSU 2.67?
Click to expand...
Click to collapse
Didn't know about the 2.67! Already had the 2.66 Beta on the device so I just flashed that guy.
How can i root this rom? Is there anyway to do it without twrp?
chtsarts said:
How can i root this rom? Is there anyway to do it without twrp?
Click to expand...
Click to collapse
Your can root it by following the guides funnily enough. No there is no way to do it without first flashing TWRP.
shame as the custom recovery will block ota updates.
ill hold off root for now.
mixterz said:
shame as the custom recovery will block ota updates.
ill hold off root for now.
Click to expand...
Click to collapse
No it doesn't, I and other users were able to successfully flash the 20160419 update from within TWRP.
It's up and here https://developers.google.com/android/ota
gm007 said:
It's up and here https://developers.google.com/android/ota
Click to expand...
Click to collapse
Changelog?
Sent from my Pixel 3 using Tapatalk
nickporwal said:
Changelog?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-12-01.html
One of this days the 'Check for Update' button will work damn it! Hahahaha
Hahaha right, I have been flashing the OTA manually, its no biggie for me I am used to manually flashing the ota now
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
AntLyoN2053 said:
One of this days the 'Check for Update' button will work damn it! Hahahaha
Click to expand...
Click to collapse
I got it through ota 1 hour ago.
gm007 said:
I got it through ota 1 hour ago.
Click to expand...
Click to collapse
You know Im mashing the button, lol. Only google phone that got all the updates pretty much same day was the Nexus 6P, I used to get the update notification even before any site would announce that it was out
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Do you have the Magisk uninstaller on your phone? Run it from the temp TWRP .img, and then it should boot OK. Go back to temp TWRP, and install Magisk again. The Edge Sense Plus module is broken again. Don not reinstall it until fixed.
Bluffer94 said:
Can anybody sucessfully root again?
Just flash-all works fine, but after flashing magisk 17.3 again and reboot, phone instant restarts to recovery and tells me devices is corrupt.
Click to expand...
Click to collapse
sulpher said:
Same, not able to root with beta or canary builds atm.. seems to just boot back to twrp every time.
Click to expand...
Click to collapse
Flash all after removing the -w, rebooted and let it finish. Boot to TWRP and installed the latest canary. Did not install TWRP.
All good.
jd1639 said:
I've rooted with 17.3 without a problem. Are you just booting into twrp, not flashing it?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ah figured it out, edge sense broken.
edit- thanks guys~
sulpher said:
Ah figured it out, edge sense broken.
Click to expand...
Click to collapse
There's no magic. I sideload the ota in the stock recovery. Booted into the system to make sure everything worked. Powered off the device and booted into the bootloader. Then booted twrp and flashed magisk. Then booted into the system. That's it.
Sent from my [device_name] using XDA-Developers Legacy app
No OTA here... It usually comes days later with unlocked Google pixel using TMobile. -.-
Installed the full version to update it, root just after and everything's fine!
There is only the edge sense that is'nt working as already told
TWRP keeps getting error 1 when flashing the OTA, bit odd
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
laill said:
TWRP keeps getting error 1 when flashing the OTA, bit odd
Click to expand...
Click to collapse
Archangel said:
The TWRP for this device has never been able to side-load the OTA it always errors out. I just use the full firmware and take out the -w and all good.
Click to expand...
Click to collapse
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
What I do is download the full updated firmware, unzip that in your platform tools folder,,,make sure you also unzip the second zip inside there as well. If you have the Pixel edge module installed uninstall it and I also uninstalled Magisk in TWRP before I updated just in case there were any problems. Then find the flash-all.bat file in your platform tools folder, right click on it, open with notepad+ and find the -w at the bottom and delete it. After this, save the flash-all.bat notepad xml file and do not just close it. You can then flash the full firmware without it deleting your user data. After this you will have to fastboot boot TWRP and flash the TWRP zip over again. I rebooted then used TWRP to flash the Magisk 17.1 zip. I am up and running and did the same thing last month for the Nov update,,,hope this helps.
Rumsfield said:
So then how do we flash the OTA and keep root? Pardon my ignorance on the matter but taking out the -w, do you mean through terminal on the device or flashing with adb or something? Just need a little more detail.
I am used to putting the OTA on the device and flashing through TWRP then flashing TWRP&Magisk again before a full restart.
Once again I am new to this style of flashing so sorry for asking a dumb question.
Click to expand...
Click to collapse