Related
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Confirmed. Just ODIN'd back to MJ3 from the VRUAND3 update and regained root using Saferoot.
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Sent from my SCH-I605 using XDA Free mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1
Be sure to thank @droidstyle for taking the time to make this guide
Another confirmation, Odin'd back to MJ9 from ND3 then used saferoot to root.
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
stop the ota notification note 2
Ostate24 said:
Can also confirm working for me and rooted also. Does anyone know how we can stop the OTA notification or do we just ignore it?
Click to expand...
Click to collapse
Change
FWupgrade.apk to FWupgrade.bak
SDM.apk to SDM.bak
I am not allow to post a link at this time so do a search on "stop the ota notification note 2"
Regain root, ND3 question,Correct MJ9, ODIN7
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
mrraya said:
seriously whaaat can u post the needed files and step by step directions ive never used odin before
Click to expand...
Click to collapse
thebat1 said:
This is what I have been looking for except it says to "REGAIN" root.. I have never had it (ROOT) to start with.. So will this still work?
and
where do I get the correct MJ9 since I did not get it off my phone before I lost it.?? or am I ODIN back to out of the box state which is VRALJB?
Odin 7 or Odin 9
I have read ODIN7 ? but Odin9 is newest as far as I can tell...want to double check.
thanks so much!!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Worked great!!!! Thanks for the links guys!!!
Worked Here Too!
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
dbalman said:
I decided to bite-the-bullet after reading your post, and all I had to do was re-root as well. All said and done it took me 30 minutes tops to have my phone back. I also used Kingo last time, but after ND3, the version of Kingo I used to root MJ9 didn't recognize the phone and the latest version was so full of dire warnings I immediately aborted.
Thanks guys!
Click to expand...
Click to collapse
I just received a replacement for my broken Note 2, which I previously had rooted with N3bula. To root my old phone, given it came with 4.1, I just had to Odin the MJ9 files, and then flash N3bula with TWRP . When I got my replacement, it updated to ND3 before I realized what was going on. Does anyone know what files I actually need to flash to get back to MJ9 from ND3? I found a file called I605VRUEMJ9.tar on one of the links posted recently. Since the actual ROM on the phone is the stock 4.3 rom, I assume I don't need to worry about system.img. I don't know about boot.img, cache.img, recovery.img, sboot.bin. I am confident I should flash tz.img, modem.bin, hidden.img.
Thanks!
---------- Post added at 05:51 PM ---------- Previous post was at 05:21 PM ----------
gee1000 said:
I just wanted to confirm that you can Odin back to MJ9 4.3 from the newest ND3 4.3 to regain root. This is for 4.3 bootlocked GN2s ONLY. It was quite painless actually, all my data was as it was before. I backed up to the internal memory using Helium just in case (since I lost root), but I was able use saferoot without issue and am now back to rooted.
I had used Kingo before to root, so I am actually glad to use saferoot this time since I am planning to install SafeStrap and flash N3BULA over stock soon.
Click to expand...
Click to collapse
Is there a particular reason you wish to use safestrap rather than continuing to use Kingo? Is Kingo not working?
Thx!!
nbock01 said:
Worked great!!!! Thanks for the links guys!!!
Click to expand...
Click to collapse
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
Neither of those links are good.
Thanks!!
@Skilover
If you go to Droidstyle's guide here: http://forum.xda-developers.com/showthread.php?p=34891181 , and then go to section 1b of the guide, you can revert back to MJ9 by following the guide's instructions. You'll want to use the stock file for (VRUEMJ9 4.3) if you're wanting to revert back from ND3.
After you get back to MJ9, you can get root access with saferoot..... Here's the link to saferoot-- http://forum.xda-developers.com/show...php?p=48392009
Sent from my SCH-I605 using XDA Premium 4 mobile app
Amazing..WTG, XDA!
New user here. Been reading a bunch of posts lately as I finally got around to trying to root my SCH-1605, which I have through VZW. For a long time, my big concern was interference on the VZW side. Finally, warranties expired and the urge peaked... just in time for the ND3 OTA update. I tried a couple of methods I found - no success. Finally stumbled on some threads that basically said - ND3 = Out of Luck.
Then I found this post.. :victory:
Truly awesome. Worked like a charm. Looking up good info on locking down the OTA pushes next.
My observations of the differences between my previous attempts and what was missing:
My first attempts:
I neglected to include the 16GB PIT file referenced in the links above (** Note: a few guides I popped across mentioned making sure that only "Auto Reboot" and "F. Reset Time" are checked. When you include the PIT file, it will auto-check "Re-Partition". I left this checked, and it worked like a charm. Can't speak as to the offset of UNchecking this, as - like I said - I left it checked)
I used a different .md5 file that would flag as a fail despite my efforts (I was using a CF autoroot md5). I'm fairly certain this failed due to the OTA update, though it may have been the lack of a PIT file. If someone could provide some more info there, I'm totally open to listen!
Bottom line - my experience was pretty painless after doing adequate research. Thanks a ton! :highfive:
_______________________________________________________________________________________________________________________
I also came across some info stating that the downgrade to the MJ firmware might flag the KNOX (I believe?) or a similar issue. Anyone run across any of those issues using these methods? If someone has a quick link to how I could check this for myself, I'd be very appreciative.
@Tangescence
Glad to hear you had success with rooting . This link should help you check on your knox counter status:
http://forum.xda-developers.com/showthread.php?p=48758233&highlight=odin#post48758233
If "Knox Warranty Void" is at zero, you didn't trip the counter.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Knox warranty void: 0
Confirmed. The flashback left KNOX WARRANTY VOID: 0
Lists as Samsung Official Binary with a System Status of Custom.
Looks good!
I know this is a bit of a side tangent, but safestrap should work with MJ9 and saferoot to allow custom ROMs despite the locked bootloader - right?
Again, many thanks to the community!
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
mattnmag said:
Right, safestrap was designed to be used for people with the locked bootloader on a rooted MJ9. Here is the safestrap thread: http://forum.xda-developers.com/showthread.php?p=51616723
I don't know a lot about safestrap, but I believe the ROM slots are not working yet so you'll have to install a custom Rom over the stock ROM if you want to use it. You'll have to do more research to make sure you know how to use it if you want to give it a go.
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Awesome - I'll be researching it tonight and tomorrow. Will post to the safestrap thread with my results and probably a heads up here to redirect. Again, tons of thanks!
Confirmed working
My Verizon Note 2 broke so under warranty I got a replacement device with the latest VRUAND3 build installed. It literally drove me nuts because I was so used to having the advantage of a rooted device with the bootloader unlocked. After doing some research, I came across the information on this thread and it helped me with having at least root access which allows me to take advantage of my Titanium Backup and other apps tailored to rooted devices.
Thank you very much for this post. I hope the devs will one up on Verizon and give the community the ability to have a unlocked bootloader soon. I like the connection speed and coverage with Verizon but their method of controlling how their customers use their devices is just annoying. I paid good money for this phone Verizon! I'm going to do what I wish to do with it to make it unique and personal to me. They just don't seem to understand that. Once again... Thanks. ROOT 4TW!
gee1000 said:
thebat1, since I am assuming you are on bootlocked ND3 from your screenshot, you will mess up/brick your phone trying to flash VRALJB. You can only go back to MJ9 at this point. The thread I used which is the same posted by iooooooc -- http://forum.xda-developers.com/show...4207&nocache=1 says "4.1.1 VRALJB- http://forum.xda-developers.com/show....php?t=2043636 (Unless you purchased your device within the first month of release and never took the OTA update, DO NOT use this)".
I am pretty sure it doesn't matter if you rooted under MJ9 or not. I was able to Odin without root and I wouldn't see why not being rooted when on MJ9 would not enable you to use Odin (since the whole point of Odin is to flash Samsung phones). I'd make a Helium backup just in case though.
You can read the thread I linked and posted by iooooooc to find out how to reflash. It's the same one I used. It has links to Odin and the MJ9 firmware (look for "VRUEMJ9 4.3" with the warning "ONLY USE THIS IF YOU TOOK THE 4.3 OTA!!") and the PIT file you'll need.
You can also read about and get links to all flavors of Odin (you need v3.07 for the VZ Note II) here: http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
Finally, to root, here's the main thread for Saferoot: http://forum.xda-developers.com/showthread.php?t=2565758
Everything I read is pretty straightforward.
I also haven't received any notification to upgrade back even though I haven't used the .bak renaming method which is interesting.
Click to expand...
Click to collapse
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk
I am making this thread because I took the OC1 update while rooted and I am asking more experienced members what I should do next.
I mistakenly took the OTA because I had read somewhere that some users upgraded from 4.3 to 4.4 with root from the OTA. I was wrong.
The OC1 OTA removed my root and prevented me from upgrading to LP. I have flashed other kernels and tried everything. I have read every thread in this forum on the topic and I see it mentioned that if I did take the OTA that I no longer had root, but I have found nothing else.
It is my understanding that after taking the OTA that I'll never have root again. Is there at least some way to get my phone completely back to stock and on LP?
Yeah I know it was a rookie mistake and I shouldn't have been so rash but I am here now and I don't know what to do, even after sifting through all the threads about Verizon's LP OTA.
Thank you for all of your help in advance.
I'm pretty sure you can just odin flash back to nc5 http://forum.xda-developers.com/showthread.php?t=2735172
Jawadbz said:
I'm pretty sure you can just odin flash back to nc5 http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
This causes a boot loop.
However, I was actually able to towelroot on NC5 before the phone restarted, so I am now rooted again! When I encountered this boot loop the first time, I just went back to NK1 instead of trying to towelroot in-between reboots.
I probably could have also cleared cache before reverting back to NC5. Thanks for the help!
If the LP update failed then you were not on OC1. There were two updates. The first was still KitKat NK4. The second was OC1. Those that were rooted were able to take NK4 but the OC1 tended to fail. So there is probably still hope.
Sent from my SCH-I545 using XDA Free mobile app
I had a similar issue , but I flashed the stock 5.0 ROM using Odin on my computer, but now when I try to flash back to NK1 it softbricks it.
I was able to to flash it back to the stock 5.0 ROM using Odin. I guess there's no downgrading after I did what I did....
Yep, Stuck on the new Lollipop. No root insofar as I know of.
sucks
My replacement s4 came with 5.0.1 on it. Very disappointed with it!!! It's driving me crazy. I can't even see a notification in the top bar smh. All it says is Verizon wireless. I miss root and roms so bad (
So just to be clear.
There is literally nothing i can do to downgrade if i have taken the OC1 OTA on the SCH-I545???
No going back to Kitkat on Verizon S4??
And no root?
dovedescent7 said:
So just to be clear.
There is literally nothing i can do to downgrade if i have taken the OC1 OTA on the SCH-I545???
No going back to Kitkat on Verizon S4??
And no root?
Click to expand...
Click to collapse
Yes
Yes
Yes
Hi everyone, just made an account here because I searched and couldn't find a solution to my problem. I have a Galaxy S4, Verizon i545, which I had rooted with towelroot. When the Lollipop OTA update rolled around, I mistakenly accepted the first half, but the second failed. I've since heard a lot of complaints about Lollipop, so I've decided to try to go with a ROM. Here's my issue: I'm currently on Kitkat NK4, and root no longer works (towelroot now said unsupported). Preferably, I'd like to re-root without a factory reset, just long enough to install SuperSu and Titanium Backup, then flash the Hyperdrive ROM. Can anyone assist me in re-rooting Kitkat NK4 without wiping everything initially? If I just can't do it, then it won't be the end of the world, but I figured if there was any way to do it, this would be the place to find out. Also, I'm a little on the noobish side, so step-by-step would be preferable. Thanks in advance everyone!
OK from something I read somewhere else it looks like I can run the MC5 NO-WIPE, then towelroot and be back to where I started to run Titanium Backup. Can anyone confirm this?
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