Has anyone on DBT CSC used the OTA rootkeeper in CF's SuperSU comin from LB1-LC1?
success?
I I have mobile odin pro, so could just use that, but the SuperSU OTA rootkeeper interests me, would be cool if it works.
either way I'll make the jump to LC1 shortly.
Just flashed the open Germany (DBT) update by mobile odin, the usual method, don't want to take chances of loosing root!
I'd still be interested to know if it works though.
Side note: the update didn't wipe my phone, I'd heard it was a wipe upgrade, but seems to have been non wipe for me.
Some how my phone threw a fit and refused to update via FOTA and kies just said "this phone is not supported" so used mobil odin aswell.
No one with SuperSU pro that can post fota survival or not?
I think before updating to OTA(with SuperSU support), replacement of CF root n CWM with stock kernel should work.
i m eager to test it too, but india have no recent update.
Related
So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Sent from my LT25i
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
yuskhayru said:
So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Click to expand...
Click to collapse
I don't know about the latest update but I've previously done OTA updates before and kept root (I've got a Xperia T not V).
This thread was helpful at the time - http://forum.xda-developers.com/showthread.php?t=2021150
ci6i said:
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
Click to expand...
Click to collapse
I also had no OTA available so used PC Companion to go from 9.1.A.1.140 to .141 on my Xperia T. I don't know the differences between XT .141 and XV .145 but was able to regain root using Bin4ry's Root Many Android method
http://forum.xda-developers.com/showthread.php?t=1886460, it might work for you.
ci6i said:
I just updated my V to .145 via PC Companion and root is gone
I was on .140 before, and no updates were available ota.
I'm looking for a new root method now.
Click to expand...
Click to collapse
since u has already update to .145, try this bin4ry method : http://forum.xda-developers.com/showthread.php?t=1886460 and i think it might work. i dont have time to test it yet.. im outstation doing my work:angel:
yuskhayru said:
So the .145 update is coming via update center in my device. I just want to know, will i lose my rooted access of i update my phone? And what about the other mod ive done like camera button mod, docomo status bar etc? Please gv some feedback before i update it.
Sent from my LT25i
Click to expand...
Click to collapse
if you perform OTA update (via PHONE), you won't loose anything, actually USUALLY you don't loose anything, and of course, using root keeper...
that's totally obvious when you use PC Companion, you will loose root..
And for regaining root access, use DoomLord EasyRootKit, which is now available in Android Development Section, it actually covers ALL devices, including V
wish you luck
ok. ive try update it via OTA, while keep the root access using voodoo rootkeeper, but no success. the main problem here is ive installed CWM. i for got about this "Keep in mind that at the moment installing CWM will broke OTA updates, even if you unroot and/or remove CWM." so there is no chance to update it via OTA anymore right?:victory:
yuskhayru said:
ok. ive try update it via OTA, while keep the root access using voodoo rootkeeper, but no success. the main problem here is ive installed CWM. i for got about this "Keep in mind that at the moment installing CWM will broke OTA updates, even if you unroot and/or remove CWM." so there is no chance to update it via OTA anymore right?:victory:
Click to expand...
Click to collapse
CHANCES are always CHANCES, so you have to try them
otherwise we wouldn't call them "Chance"
but, in theory, with aforementioned conditions, it's hard to believe that you will be able to update via OTA...
Ok so many of us have successfully rooted our devices and frozen update and renamed security files to avoid losing our root.
What are the proper steps for Dummies like me to accept the Lollipop OTA in December without losing my data?
Also now 4.4.4 is anounced with Bluetooth fixes that I have noticed while streaming
(My gut tells me keep update frozen until a flashable rooted 5.0.)
It was said in another thread NOT to take the 5.0 update until a root method for it has been established. If you wanna keep root, I'd wait. I'm still running stock rooted AND3 firmware/kernel. I'm looking to get the newest update up to today (I think ANG3 or something of that nature.) I'm just not taking updates yet so I can keep my root. I'm having problems with the phone freezing and restarting though so I'd like an update.
Sent from my "ROOTED" SAMSUNG-SM-G900A using XDA Premium 4 mobile app
NG3 is smooth
PS4AndroidHacker said:
It was said in another thread NOT to take the 5.0 update until a root method for it has been established. If you wanna keep root, I'd wait. I'm still running stock rooted AND3 firmware/kernel. I'm looking to get the newest update up to today (I think ANG3 or something of that nature.) I'm just not taking updates yet so I can keep my root. I'm having problems with the phone freezing and restarting though so I'd like an update.
Sent from my "ROOTED" SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am stock rooted with ANG3 pre-installed on my purchased S5. It runs smooth as silk if you use the method posted by muniz_ri in general. All I've done is turned off or frozen some bloatware and installed Chainfire SU 2.16.
My question was more geared towards the person who might want to go from rooted to the lastest OTA without losing data etc. I have been diving in pretty deep to the AT&T side of XDA since leaving sprint a week ago and I think the answer might have been posted by shortydoggg with the soft-bricked thread.
I was hoping someone might be able to tell me a non odin 3.09+ way to remove the freeze on my apps in the correct order to take the OTA without tripping KNOX if I wanted to do that knowing I might loose root.
I thought we might be able to follow muniz_ri and odin the one file back towelroot again after.
Basically I like stock always have, but I want root also for AdAway Titanium Backup Etc. and being a truck driver I wanted the 4.4.4 Bluetooth fix for Iheart radio.
UltraCon79 said:
I am stock rooted with ANG3 pre-installed on my purchased S5. It runs smooth as silk if you use the method posted by muniz_ri in general. All I've done is turned off or frozen some bloatware and installed Chainfire SU 2.16.
My question was more geared towards the person who might want to go from rooted to the lastest OTA without losing data etc. I have been diving in pretty deep to the AT&T side of XDA since leaving sprint a week ago and I think the answer might have been posted by shortydoggg with the soft-bricked thread.
I was hoping someone might be able to tell me a non odin 3.09+ way to remove the freeze on my apps in the correct order to take the OTA without tripping KNOX if I wanted to do that knowing I might loose root.
I thought we might be able to follow muniz_ri and odin the one file back towelroot again after.
Basically I like stock always have, but I want root also for AdAway Titanium Backup Etc. and being a truck driver I wanted the 4.4.4 Bluetooth fix for Iheart radio.
Click to expand...
Click to collapse
It's hard to say what the best approach will be until the update arrives. In the case of 4.4.4, I'm rather confident that a somewhat simple method can be developed to take the update while keeping root. As for 5.0, I have some ideas none ideal but we'll see.
Is Android 4.4.4 for the AT&T version of the Galaxy S5 out? I have a Galaxy S5 AT&T phone but I don't have AT&T service. I am running Android 4.4.2 with build version ND3 is there something newer than this?
Updating to NG3
Het guys, so today I got ahold of Odin 3.09 and the NG3 update, I applied it through Odin in the AP slot and it DID NOT update my phone to NG3. My Baseband still says AND3 and kernel is 3.4.0-2178781
Tue Jul 22 13:58:46 KST 2014. Anybody have any options i can use without having to downgrade to NCE just to upgrade? LOL...Im kinda at a loss,Ive tried it in download mode twice now and no fu go.
Plz disregard my message. I'm good now and running rooted NG3.
I am rooted on 4.4.2 on the N900A Note 3 for AT&T and I disabled the OTA notifications a long time ago to prevent breaking root and upgrading to 4.4.4. Now that the Lollipop update is available I would like to re-enable the OTA but when I go to the Application Manager then the Turned Off section, the AT&T Software update is listed but the Turn off button is greyed out and I can't turn it back on. Any suggestions? Please!
Did you freezed the app by using App Quarantine or another root app to disable it? I just re-enabled mine using App Quarantine.
Did you use Titanium Backup or something to freeze it? If so try unfreezing it there. Unless you Odin back to full stock the update will likely fail anyway though, even if you've unrooted. I would wait a day or two, there's a theoretical chance that the method of having root on 4.4.4 will work again (Be on a version Safestrap supports, flash a prerooted version of the ROM through that, then update the low level stuff via Odin)
Thank you both for replying... I have no idea what I did. I have Titanium Backup installed but I do not see a freeze feature. If I used a different app to freeze it will App Quarantine still unfreeze it? If so I'll try that. I no longer need root.
Even if you unfreeze it'll still likely fail out somewhere around 27% for ever being rooted, even if you unroot. You'll almost certainly have to Odin back to stock and take the OTAs in between, may as well wait for someone to post the Odin files for L so you can do it in one step I figure. If you do want to defrost it should work with anything that has that capability, for Titanium you click on the specific package and it should be the middle of the top row on the default Backup Properties tab, says Defrost
I can say neoman is absolutely correct. My phone is rooted and has 4.4.2. It downloaded the Lollipop 5.0 update today from AT&T but failed during installing. Main reason I rooted the phone was to overcome their Kitkat external SD Card issue. Now they fixed the issue with Lollipop but I can't update. I blame them on that .
I wonder if updating to 4.4.4 first will allow me to update to 5.0? The reason is I don't want to lose any current data or apps or settings. I still have a copy of the 4.4.4 downloaded ota earlier but never installed.
Bottomline is I want to update to 5.0 without losing data.
You'll absolutely have to Odin back to stock NC2 before trying to update to 5.0
andygev35 said:
You'll absolutely have to Odin back to stock NC2 before trying to update to 5.0
Click to expand...
Click to collapse
Is there an external download source for the Lollipop ROM to install via ODIN yet?
You can also Odin to stock NL1 http://forum.xda-developers.com/showthread.php?t=2999317
Typically if you're careful and you know everything you did with root, you can reverse and update... I did this a few times
Sent from my XT907 using XDA Free mobile app
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
fleggett1 said:
I have (or had) an AT&T branded S5 that was previous rooted and running Safestrap (I don't recall the BL version). Due to some EXTREME idiocy on my part, I took an OTA update two days ago, which updated and synched everything to G900AUCU2ANG3.
Naturally, this borked root. But there's some weirdness going on. Even after the OTA update, the phone's device status still says "Custom". And I still see the custom text when the phone boots. Is this Knox related?
Further oddness is that the phone keeps trying to pull down a second OTA update that looks identical to the first based on the filesize (over 400 MB). It goes through the motion, boots into recovery, and starts installing this second update, but stops partway through. Upon rebooting, the phone tells me the update was interrupted and can't be installed.
I realize I may never get root back, but I'm alarmed the phone's status still says "Custom" and that it's trying (and failing) to install this second OTA update.
I've tried factory resetting the phone, both within KitKat and via recovery, but these issues remain. Should I just reapply NG3 via Odin?
Thanks in advance!
Click to expand...
Click to collapse
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
dirtydodge said:
What does your "android version" say in settings. If your still on 4.4.2 you can downgrade bank to nce and reroot with towel root.
Click to expand...
Click to collapse
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
fleggett1 said:
Yes, I'm still on 4.4.2. Like I wrote in my OP, though, I'm VERY concerned that this second OTA update keeps failing. I'm also perplexed as to why the device is still in some sort of custom state since I thought taking the OTA update would, in essence, reset everything except user data.
Is my phone borked in some way? I mean, it works just fine otherwise, but the device's inability to install this second OTA update really sticks in my craw.
I might reapply NG3 via Odin and see what happens. Couldn't hurt, right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3149146
If you want root, go to the OP in that post, scroll down to step 4 or the notes section and download the "downgrade to nce.zip" flash that in odin "ap" slot. Then root with towel root. After that you can either download titanium backup and fees the ota's or use that same thread to upgrade to the OF2 version and keep root.
Edit:
If you want to just take the OTA's and not root your phone then still download the "downgrade to nce.zip" flash in odin but don't root. The ota's will push through with no problem then. But you won't be able to downgrade and root if you take the OTA's all the way up to oc4 i believe.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.