I was rooted with custom recovery on MDK. I decided to restore my Stock rooted backup so I could take OTA path to MJ7.
I’m currently on MI1 waiting to update to MJ7 and noticed the Samsung Custom boot logo. Device Status says “Custom”. I’m no longer rooted, no more custom recovery due to the ME7 and MI1 OTA updates. How should I proceed?
I’m worried about tripping the Knox fuse and I know there’s no going back. Does it matter? Will the MJ7 update overwrite this status? Or do I need to take care of it on MI1 before moving forward to MJ7?
EDIT: While on MI1, I used the ODIN files to go completely back to stock MI1. This returned the Device Status to "Official" and the boot logo returned to normal. This link is for the ODIN files with instructions: (http://forum.xda-developers.com/showthread.php?t=2301259).
Screenshots, for reference.
You could try the [root] triangle away app. I would read through the thread 1st....http://forum.xda-developers.com/showthread.php?t=1494114
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
^^^ what he said. Odin and start fresh. Although it does seem like a shame to see a MDK device getting updated and locked down but hey it's not my device.
Normally reading the first two sentences of this post would have been the most disheartening thing to see in a S4 forum, luckily or unlucky today it comes in second only to garwyn just closing the dev thread about coming up with ideas for unlocking the bootloader, and it happening so shortly and randomly after my post here, which I consider the most significant public progress we've made in unlocking this bootloader, because its the only public progress I've seen since we were gifted with loki.
majeiks said:
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
Click to expand...
Click to collapse
Confirmed. This did the trick. Device Status says "Official" and the boot logo returned to normal. Will update OP with solution.
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
cell128 said:
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
MJ7
matt1733 said:
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
Click to expand...
Click to collapse
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Runamok said:
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Click to expand...
Click to collapse
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
http://forums.androidcentral.com/ve...xy-s4-security-notice-after-update-4-3-a.html
Knox security warnings - No biggie
azraell33 said:
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
Thank you for pointing this out. I checked into it and I doubt it's a bug. I DID get the security warning the next morning after install, which coincided with the timing of your message. My reaction to it was to simply agree to getting the security updates. I have not had any problems since, and my phone is running fine. I tried multiple ROMs while I had Safestrap on my phone, and MJ7 is performing as well as any of them. The caveat is that I'm not able to make as many mods to phone features, but to be honest, a lot of the mods were superficial tweaks that I didn't really use that much on a regular basis.
I APPRECIATE what developers have done to spur Verizon and Samsung into fixing the problems with the earlier versions of the software. Obviously, I was unhappy enough to attempt altering the firmware and risk losing warranty service. Having said that, I've come to a place where the time and effort it takes to act as my own customer service agent isn't serving me well. When I started having problems with my custom ROM and realized there had been not one, but TWO Verizon updates in the space of 3-4 months, I made a choice to accept the good with the bad and go the route of accepting updates in one easy click, instead of expending the energy it takes to be my own R&D and customer service department. .
MJ7 is running fine. Energy efficiency seems very good. Stability appears solid. Response time and hangups appear to be all but eliminated. Those were the reasons I tried a custom ROM, energy efficiency, stability and performance. MJ7 seems to have addressed those reasonably well.
A big THANK YOU to developers who had an influence in nudging Verizon into action. Security will continue to be a looming issue, and hopefully it will not quash the creativity of brilliant independent thought.
Click to expand...
Click to collapse
Related
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
lordbear said:
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
Click to expand...
Click to collapse
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
th3bl3d said:
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
Click to expand...
Click to collapse
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
tech_head said:
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
Click to expand...
Click to collapse
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
lordbear said:
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
Click to expand...
Click to collapse
Look at this thread. -> http://forum.xda-developers.com/showthread.php?t=2301259
I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
calaski8123 said:
I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
Click to expand...
Click to collapse
1)mk2
2) nobody has been able to unlock new boot loader so as long as there is a root method it should not matter. Don't know about mk2 but I believe mj7 has root.
3)mdk
Me7
Mi1 (I think)
Mj7
Mk2
I think I got them all.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
calaski8123 said:
I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
Click to expand...
Click to collapse
Being on ME7 you are being prompted to update to MI1, then you will be prompted to update to MJ7, and finally to MK2 (the most recent). Safe rooting methods for each of these builds are different but readily available if you look in the Verizon Galaxy S4 forums. Recently, Hashcode has provided the community with the only recovery for MJ7 and MK2 - Safestrap. When you say unlock I'm guessing you mean the bootloader which is still locked - and a difficult nut to crack although there are some very smart guys working on it. I recently got my GS4 and am currently on MK2 rooted with safestrap installed. I don't see an advantage of ME7 to MJ7 or MK2 but others may feel differently. For a while ME7 and MI1 were the only builds that Safestrap worked on, but now that MJ7 and MK2 are safestrap compatible, there doesn't seem to be a disadvantage to the newer builds. Hope that helps sort it out a little. Cheers.
CoMtnMan said:
Being on ME7 you are being prompted to update to MI1, then you will be prompted to update to MJ7, and finally to MK2 (the most recent). Safe rooting methods for each of these builds are different but readily available if you look in the Verizon Galaxy S4 forums. Recently, Hashcode has provided the community with the only recovery for MJ7 and MK2 - Safestrap. When you say unlock I'm guessing you mean the bootloader which is still locked - and a difficult nut to crack although there are some very smart guys working on it. I recently got my GS4 and am currently on MK2 rooted with safestrap installed. I don't see an advantage of ME7 to MJ7 or MK2 but others may feel differently. For a while ME7 and MI1 were the only builds that Safestrap worked on, but now that MJ7 and MK2 are safestrap compatible, there doesn't seem to be a disadvantage to the newer builds. Hope that helps sort it out a little. Cheers.
Click to expand...
Click to collapse
YEs thanks... I'll do some research on the newer builds. I really just wanted to know if there was one build that is best to be on and then root. I didn't want to update and find out rooting would be more difficult or have problems but likewise, I didn't want to root on ME7 and miss out on some added features in the newer builds.
If you guys had to pick the best build to be on for a balance of rooting and features, which would it be. For purposes of rooting, I'm OK with stock, I don't need a custom ROM. I just want to delete bloatware, run an ad blocker, wifi tether and Google Wallet (with NFC payments).
And yes, I meant an unlocked bootloader when I said unlocked. I know safestrap works, I just have always been on unlocked with a custom recovery where I could make backups. I felt way safer that way. I'm sure its fine, but safestrap is a new method I'm not yet comfortable with.
Thanks,
Jim
I think MJ7 would be best. I upgraded to MK2 and don't notice much difference (it was a small incremental update - still 4.3). The nice thing is that if you do manage to screw up MK2 or MJ7 you can always ODIN back to MJ7 and start fresh. MJ7 seems to be slightly better for flashing as you also have to flash the kernel module after each new rom and MJ7 has one on Hashcode's page whereas MK2's is "coming soon".
I have been using safestrap for over a year with my Razr prior to the SG4 - very stable and a huge help when you want to try multiple roms but not want the hassle of flashing back and forth between stock and custom roms. Just make sure you read all of Hashcode's instructions on using it.
He probably knows more about it than me I'm on MDK still.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
OK great. So if I do the OTA update Verizon is pushing, it will install each one individually so I can stop when I get to the one I want? It won't just go right to the most recent build?
Jim
calaski8123 said:
OK great. So if I do the OTA update Verizon is pushing, it will install each one individually so I can stop when I get to the one I want? It won't just go right to the most recent build?
Jim
Click to expand...
Click to collapse
Yes. Correct. That one I do know!
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Ok I updated to MJ7. I'm getting this shield notification now that says it detected unauthorized access to a secured area. I searched and found this is an annoying issue that only seems to be fixed with a factory reset... ugh WTF? ! ? Samsung and Verizon are really starting to blow.
If I try and update this security thing it's it going to prevent me from rooting?
Any other way to stop it besides a factory reset?
Thanks,
Jim
calaski8123 said:
Ok I updated to MJ7. I'm getting this shield notification now that says it detected unauthorized access to a secured area. I searched and found this is an annoying issue that only seems to be fixed with a factory reset... ugh WTF? ! ? Samsung and Verizon are really starting to blow.
If I try and update this security thing it's it going to prevent me from rooting?
Any other way to stop it besides a factory reset?
Thanks,
Jim
Click to expand...
Click to collapse
That's Knox. On the initial MJ7 build, it was raising that issue whenever you went from one WiFi access point to another.
If you allow it to update the policy, that defect goes away.
No need to factory reset.
If you root your phone, allow SuperSU to disable Knox and the problem will go away.
I just rooted my SG4 MK2 and that Knox thing showed up on my supersu access. It scared the crap out of me because I thought I was tripping it and on my way to hard bricking my phone. Thanks k1mu. I just hit disable and the shield went away.
Sent from my SCH-I545 using XDA Premium 4 mobile app
After two and a half hours of frustration, I eventually gave up.
I downgraded from NG6 to NC5, and then from NC5 to both NC2 and MK2 (separately) after MUCH Googling and forum searching.
For the longest time I couldn't get anything to work, until I realized that my USB extension cable was the cause of my problems. I finally got down to NC5 rooted. I tried to install Liquid Smooth and Cyanogenmod through Odin, and it wouldn't work. I got Liquid Smooth to install through Safestrap, but it just got stuck at the loading image forever.
I eventually got frustrated and let the Samsung software put NG6 back on, and left it alone. That's where I'm at now.
I assure you I've read absolutely every thing ever written on every subject by every person ever born in the history of mankind while trying to figure this out. Can someone PLEASE give me a walkthrough SUMMARY of how to get custom ROMs on this phone, beginning with NG6? I'm not a newbie. I've rooted and installed custom ROMs on numerous phones and tablets. But I can't keep playing with this phone, trying to get it to work. I'm going to end up becoming a serial killer if I get one more error message. I am now desperate, and asking for help.
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
sponix2ipfw said:
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
"Serial killer might be in your future" lololololol.
Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
rockingondrums said:
Hey everyone. I decided I would unlock my bootloader and trip Knox about two days before towelroot came out. Yay.
I've since gotten the OPO, so I wasn't that concerned. I wanted to give the phone to my mom who lives in another state, so I Odin'ed back to what I believe is the most current OEM firmware available (NK2) because I want my mom to be able to get updates OTA and not have to worry about troubleshooting her phone as much as if it were a custom ROM, or a phone with root.
Unfortunately, checking for a system update says the system is modified (ROM is all stock though) and device status is custom. I also discovered while testing the phone (it had been sitting in a drawer for months) that the microphone isn't working very well. I tried different sims, calling different people on different networks, I'm sure it's hardware problem. Is there any way to re-enable the OTAs? I'd like to get this hardware problem warrantied. The knox tripping didn't destroy the mic, so please no judgement here. I'm also not comfortable in removing the glass to replace the mic. If the mic could be replaced without that step, I would simply do that.
Thank you.
Click to expand...
Click to collapse
Hmm. Last time I Odined back to stock, using the tar file of the firmware version that came before NK2, my device was totally fine to receive OTA, despite Knox being tripped. Try removing root first, then Odin stock NK2, then factory reset.
Hm, so I now need to install SuperSU in order to use the un rooting function? I would've thought a full stock image file would've eliminated root...
EDIT - Simple Root checker says SuperSU is not installed BUT terminal app "does Rooted".
Installed SuperSU, but binary is not installed, so it doesn't run. WTH? What happened to the good old days of just flashing stock images and not worrying about it anymore?
SOLVED
I looked at the slightly outdated stock collection thread, flashed the NG4 stock image, then was able to take the OTA update to NK2. Went ahead and told T-Mobile the whole problem and they really only seemed to care if there was physical damage or water damage (which there is not).
Just leaving this here for future searches. How do I get this thread closed?
I've had my VZ S4 since sometime around Dec of 2013. Previously was on a DroidX, I've really honestly never had any problems rooting or installing custom rom's on my phones (A BIG THANK YOU TO ALL OF YOU HERE that made that possible) so I'm not a noob...but I'm not an expert either. I usually wait and read a lot of threads, follow the instructions and I've always been good to go. My S4 started at MK2, (took the OTA right out of the box, now I now better ) and with the help of K1mu's post on rooting the S4 with Saferoot everything went off with out a hitch (thank you!!). After successfully rooting the phone, I installed Safestrap, backed up the stock rom slot, created a custom rom slot and installed Hyperdrive 11...everything is working flawlessly.
So fast forward a year to KitKat I returned to XDA...read and read and read and followed the Dev's instructions and was good to go again. I know it involved Safestrap-I545-3.75-KitKat-A03.apk, TowelRoot, Odin and ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_Multi_Cert_Tar.md5. Definitely was one of muniz_ri post. Any way I basically used Odin...flashed back to factory stock followed muniz_ri post and was good to go again with KitKat(Thank You!!)
So now to the present, about a week or so ago I had an OTA screen pop asking to update, it actually showed 2 updates available (don't know if there is a log in the S4 that keeps track of the updates). So I came back here of course and started reading and reading and reading...and I was ready to begin the process in this thread by muniz_ri: http://forum.xda-developers.com/gal...-to-update-to-i545oc1-5-0-1-keeproot-t3096558 which again I am sure would have went flawlessly. Then I had an accident...I had been dismissing the update (it popped up a lot ) when the unthinkable happened...I pressed yes, the phone went thru the update process and I don't know what update it was but it wasn't Lolllipop...so I was like phewwww, clicked on my RootCheck (JRummy) and it said Rooted 4.4.2 KitKat (NK4), SuperSu 2.46 so I figured everything was ok. Not so, I don't know what the upgrade was but I no longer have root or access to safestrap, SuperSu or any apps that require root...and this is where I need guidance from the masters. I have a TWRP/Safestrap back up (stock-2014-12-08--19-33-37 KOT49H.I545VRUFNK1) from right after rooting for KitKat, nothing else...just root I'm pretty sure of that. So what would be the best way to fix? Is there a way to re-root the phone in it's present condition? Can I use the TWRP back up some how with out SafeStrap? How far back can I down grade with Odin using a VWZ factory image? Any idea what happened with the update prior to Lollipop? Sorry if this was long winded, just trying to figure out the best way moving forward. I don't really care about the data on the phone. Before going forward I'll do A Keis back up of the stuff I want to save. I appreciate any help/answers/suggestions...Jinx