After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
budding_developer said:
After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
Click to expand...
Click to collapse
Hashcode hasn't gotten Safestrap running on MJ7 yet. It may be a while before he's able to find a way around the new enforcement in MJ7. There's some chance it may not be possible.
k1mu said:
Hashcode hasn't gotten Safestrap running on MJ7 yet. It may be a while before he's able to find a way around the new enforcement in MJ7. There's some chance it may not be possible.
Click to expand...
Click to collapse
Yeah, I have found that out... and soft-bricked it twice trying to disable selinux. Verizon sent me a replacement, which was on ME7 out of the box; flashed MI1, Root de la Vega, got back to my set up and locked out updates by uninstalling FWUpgrade.apk and SDM.apk in Titanium.
I guess I'll just stay where I am until the devs figure a way around the selinux thing -- that's what is keeping everyone out.
Verizon is Big Red alright! ! (communist)
budding_developer said:
Yeah, I have found that out... and soft-bricked it twice trying to disable selinux. Verizon sent me a replacement, which was on ME7 out of the box; flashed MI1, Root de la Vega, got back to my set up and locked out updates by uninstalling FWUpgrade.apk and SDM.apk in Titanium.
I guess I'll just stay where I am until the devs figure a way around the selinux thing -- that's what is keeping everyone out.
Click to expand...
Click to collapse
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
theslowhand said:
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
Click to expand...
Click to collapse
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
mmuzzy said:
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
Click to expand...
Click to collapse
I don't think its right to dicker something up then return it, BUT one could say that if they wouldn't have locked the bootloader this wouldn't be a problem and its there own dam fault and serves them right. I am not going deny I have been considering throwing mine under the car tire and returning it in hopes I will get a MDK version, but I pay for insurance that covers that kind of thing. Besides with my luck I would get a reman that had 4.3 on it and would be doubly screwed.
mmuzzy said:
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
Click to expand...
Click to collapse
azraell33 said:
I don't think its right to dicker something up then return it, BUT one could say that if they wouldn't have locked the bootloader this wouldn't be a problem and its there own dam fault and serves them right. I am not going deny I have been considering throwing mine under the car tire and returning it in hopes I will get a MDK version, but I pay for insurance that covers that kind of thing. Besides with my luck I would get a reman that had 4.3 on it and would be doubly screwed.
Click to expand...
Click to collapse
I agree with mmuzzy. Got to eat it your self when you take the risk. Seems like everyone knows how Verizon is operating trying to lock down these flagship phones so everyone knew it going in so To speak.
So if you screw it up I'd have to say you gotta do what's right and eat your mistake regardless of Verizons reasons for locking down the phone...
Sent from my SCH-I545 using xda app-developers app
Cure for the Communist problem...
theslowhand said:
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
Click to expand...
Click to collapse
Check out this post I put up. I am now on AT&T (GSM USA) with the same S4, cut my phone bill in half, and have a kick-a*s custom ROM. Here's the thread I put up as a guide on how to do this --> http://forum.xda-developers.com/showthread.php?p=47328895#post47328895
Mj7 calls for safestrap 3.70 or preferred 3.71
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
budding_developer said:
After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
Click to expand...
Click to collapse
Must use Safestrap 3.70 or 3.71 (recommended) for mj7 I have used both but 3.71 is supposed to be strictly for mj7 and mk2
Related
Hey guys, completely new here. I have had my S4 for awhile now and decided to finally root my device. I came across the vroot method and rooted my MJ7 s4. I now (stupidly) realize that not only is there little support for MJ7, but also that vroot has not been confirmed safe as it is a Chinese root method. My phone appears to work perfectly and I can confirm that it is rooted under MJ7 with no issues so far, but my question is: is there any way to err...uproot it and go back to stock until a safe method is confirmed? Or should I just wait until an Odin file is released? Like I said the phone works perfectly, I am just cautious and don't know what the next step is. Thanks!
No
ProtossPaul said:
Hey guys, completely new here. I have had my S4 for awhile now and decided to finally root my device. I came across the vroot method and rooted my MJ7 s4. I now (stupidly) realize that not only is there little support for MJ7, but also that vroot has not been confirmed safe as it is a Chinese root method. My phone appears to work perfectly and I can confirm that it is rooted under MJ7 with no issues so far, but my question is: is there any way to err...uproot it and go back to stock until a safe method is confirmed? Or should I just wait until an Odin file is released? Like I said the phone works perfectly, I am just cautious and don't know what the next step is. Thanks!
Click to expand...
Click to collapse
Well you're on mj7 like I am and that means we sit and wait for someone to find us a way to either run Safestrap or a bootloader unlock for custom recovery.
There already are Odin files in here and someone made a script to remove the Chinese superuser you're talking about and replace it with chainfires supersu.
Search around on here a little bit Youll find all that.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 05:25 AM ---------- Previous post was at 05:16 AM ----------
Here's a video on the entire vroot method plus supersu
http://forum.xda-developers.com/showthread.php?t=
And here's a link to an Odin file, although I don't think you really need it. Plus it's a full Wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
No
Well you're on mj7 like I am and that means we sit and wait for someone to find us a way to either run Safestrap or a bootloader unlock for custom recovery.
There already are Odin files in here and someone made a script to remove the Chinese superuser you're talking about and replace it with chainfires supersu.
Search around on here a little bit Youll find all that.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 05:25 AM ---------- Previous post was at 05:16 AM ----------
Here's a video on the entire vroot method plus supersu
http://forum.xda-developers.com/showthread.php?t=
And here's a link to an Odin file, although I don't think you really need it. Plus it's a full Wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
Okay great, I assume I used the same method as you did, I also have supersu so I suppose that means the Chinese garbage is gone. There really can't be any harm in leaving it in the current rooted MJ7 state right? I mean support will be released eventually. Waiting for safestrap seems like the best option just as far as safety is concerned. I have zero experience with rooting or flashing so I will wait for support to do a Titanium backup or something.
ProtossPaul said:
Okay great, I assume I used the same method as you did, I also have supersu so I suppose that means the Chinese garbage is gone. There really can't be any harm in leaving it in the current rooted MJ7 state right? I mean support will be released eventually. Waiting for safestrap seems like the best option just as far as safety is concerned. I have zero experience with rooting or flashing so I will wait for support to do a Titanium backup or something.
Click to expand...
Click to collapse
No that's our only option as of now. I'd go into titanium and freeze sdm and fwupgrade so that in the event there is another OTA you can wait to see if there is a method to retain root through it. Always look on here first before taking any OTA.!!!
I'm on mj7 rooted and I'm running xposed framework to customize my s4 quite a bit... And then I just remove /freeze everything I don't want using Titanium. And I'm happy with my phone.
The devs are working on both Safestrap and unlocking the bootloader. It's a lot of work but those guys are on here working diligently.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 06:41 AM ---------- Previous post was at 05:54 AM ----------
Also here's a thread listing some of the things people have been freezing using Titanium.
Maybe itll help.
http://forum.xda-developers.com/showthread.php?t=2314265
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
No that's our only option as of now. I'd go into titanium and freeze sdm and fwupgrade so that in the event there is another OTA you can wait to see if there is a method to retain root through it. Always look on here first before taking any OTA.!!!
I'm on mj7 rooted and I'm running xposed framework to customize my s4 quite a bit... And then I just remove /freeze everything I don't want using Titanium. And I'm happy with my phone.
The devs are working on both Safestrap and unlocking the bootloader. It's a lot of work but those guys are on here working diligently.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 06:41 AM ---------- Previous post was at 05:54 AM ----------
Also here's a thread listing some of the things people have been freezing using Titanium.
Maybe itll help.
http://forum.xda-developers.com/showthread.php?t=2314265
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
I really should have done more research before doing this, but can you explain to me the reason to use safestrap when you have flashed a recovery on Titanium backup? I thought that if you screwed anything up you could just revert to your last flash on Titanium. Also unlocking the bootloader is going to allow us to use custom ROMS right? Sorry, really trying to get up to speed, it's a difficult time to get into this with MJ7. I really just want to go about this in the safest way possible.
ProtossPaul said:
I really should have done more research before doing this, but can you explain to me the reason to use safestrap when you have flashed a recovery on Titanium backup? I thought that if you screwed anything up you could just revert to your last flash on Titanium. Also unlocking the bootloader is going to allow us to use custom ROMS right? Sorry, really trying to get up to speed, it's a difficult time to get into this with MJ7. I really just want to go about this in the safest way possible.
Click to expand...
Click to collapse
Well.. Couple things..
First off since we have an mj7 Verizon S4 there is no flashing anything at all. No roms at all. Titanium backup is a tool that can save all your system and user data/apps. As well as uninstall and freeze things.
Safestrap if it ever gets to us just allows the flashing of roms on a '' safe'' location on our phones. It doesn't touch our actual mj7 Samsung Touchwiz.
No custom recovery like Clockwork Mod for us because the bootloader is locked up!
There are many people on here working on both of these issues with the bootloader itself and going the Safestrap route as well.
For now grab titanium and freeze those two things I mentioned earlier so that your phone recieves no further updates. You don't want an update until you know there is a safe way to root, or keep root, if that's important to ya.
Other than that you can use xposed framework and modules to hook up you're phone.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
Well.. Couple things..
First off since we have an mj7 Verizon S4 there is no flashing anything at all. No roms at all. Titanium backup is a tool that can save all your system and user data/apps. As well as uninstall and freeze things.
Safestrap if it ever gets to us just allows the flashing of roms on a '' safe'' location on our phones. It doesn't touch our actual mj7 Samsung Touchwiz.
No custom recovery like Clockwork Mod for us because the bootloader is locked up!
There are many people on here working on both of these issues with the bootloader itself and going the Safestrap route as well.
For now grab titanium and freeze those two things I mentioned earlier so that your phone recieves no further updates. You don't want an update until you know there is a safe way to root, or keep root, if that's important to ya.
Other than that you can use xposed framework and modules to hook up you're phone.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
First of all, I want to say thanks so much for helping me. I know it wasn't addressed in the title of my thread but I really do appreciate it. I have noticed that people seem skeptical about doing anything on the rooted MJ7 framework so I just thought I should ask of its safe to do Titanium without bricking my phone? Not only have I never done it before but I am cautious if it is safe because I haven't backed anything up yet. Didn't want to use an old method now that we are on MJ7). Can I use the current version of titanium with MJ7 safely? Also what can I do with the Xposed framework? I thought that was used to load custom ROMS?
Thank you SO much.
Alright, so I have some questions that can probably be chalked up in the 'Rooted MJ7, what now?' category. I can't specifically find these answers, but I've read a ton of what basically boils down to, you can't do sh*t with mj7.
So I realize there's no flashing ROMs on mj7, which sucks a big one, but that's fine, I'll deal.
I've rooted the phone via vroot and all is good there. Triangle away doesn't seem to work, but whatever. It's highly unlikely that I'll need to take the phone into the store.
My biggest gripe is that I can't seem to get adb to work to push files to the phone. I keep getting 'permission denied' errors when I get to the 'adb push ..............' part. Near as I can tell from my reading, this is because the bootloader is locked. Is that right? I tried adding 'ro.secure=1' to 0 in default.prop, but that didn't work. I was trying to push a modded services.odex to /system/framework. Does anyone know how to get adb fully working on a rooted mj7? If you check my sig., you'll see that I'm not a total noob persay. I've been using adb for years. I have all the right files installed on my PC and what not.
ProtossPaul said:
First of all, I want to say thanks so much for helping me. I know it wasn't addressed in the title of my thread but I really do appreciate it. I have noticed that people seem skeptical about doing anything on the rooted MJ7 framework so I just thought I should ask of its safe to do Titanium without bricking my phone? Not only have I never done it before but I am cautious if it is safe because I haven't backed anything up yet. Didn't want to use an old method now that we are on MJ7). Can I use the current version of titanium with MJ7 safely? Also what can I do with the Xposed framework? I thought that was used to load custom ROMS?
Thank you SO much.
Click to expand...
Click to collapse
Titanium is not used to load roms. It's used for backing things up primarily and that's it. It can also uninstall /freeze things, but that's all.
There's not really much we can do now except use xposed framework/mods to customize our phones. It is very safe and everything is located right here on xda.
For now take a look at this
http://forum.xda-developers.com/showthread.php?t=2383484
Read from beginning and install the framework first, then Wanam.
It explains everything.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 07:31 AM ---------- Previous post was at 07:22 AM ----------
sharkie405 said:
Alright, so I have some questions that can probably be chalked up in the 'Rooted MJ7, what now?' category. I can't specifically find these answers, but I've read a ton of what basically boils down to, you can't do sh*t with mj7.
So I realize there's no flashing ROMs on mj7, which sucks a big one, but that's fine, I'll deal.
I've rooted the phone via vroot and all is good there. Triangle away doesn't seem to work, but whatever. It's highly unlikely that I'll need to take the phone into the store.
My biggest gripe is that I can't seem to get adb to work to push files to the phone. I keep getting 'permission denied' errors when I get to the 'adb push ..............' part. Near as I can tell from my reading, this is because the bootloader is locked. Is that right? I tried adding 'ro.secure=1' to 0 in default.prop, but that didn't work. I was trying to push a modded services.odex to /system/framework. Does anyone know how to get adb fully working on a rooted mj7? If you check my sig., you'll see that I'm not a total noob persay. I've been using adb for years. I have all the right files installed on my PC and what not.
Click to expand...
Click to collapse
No there's no custom recovery or even Safestrap, which means no roms yet unfortunately.
There's no triangle away either but I've seen some folks working on something like Knox Away which is the same kind of thing since we're all stuck with Knox now!
As far as your ADB questions I'm not your guy for that. I'd say though that maybe it's got to do with the new security we have on these things now for sure.
I'm sure someone way more qualified than me can lead you in the right direction.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
...but I've seen some folks working on something like Knox Away which is the same kind of thing since we're all stuck with Knox now!
Click to expand...
Click to collapse
I've deleted all the Knox files I could find (about 12 or so) using FX Explorer along with some other security stuff that I found. I guess that's not enough to fully get rid of Knox since I still have that 'custom' screen at boot...
Man, I really wish I would have done more reading before deciding to go with a Samsung. Oh well, despite all this, it's still a great phone.
Thanks for your reply.
sharkie405 said:
I've deleted all the Knox files I could find (about 12 or so) using FX Explorer along with some other security stuff that I found. I guess that's not enough to fully get rid of Knox since I still have that 'custom' screen at boot...
Man, I really wish I would have done more reading before deciding to go with a Samsung. Oh well, despite all this, it's still a great phone.
Thanks for your reply.
Click to expand...
Click to collapse
No there's no getting rid of Knox, it's part of the actual bootloader and kernel on some level. You can get rid of the Knox app which is on our phones but that's about it.
I was thinking the same thing about getting an S4 but from what I've read this sort of security is going to be more common on a lot of phones not just Samsung.
That custom screen went away on my phone, I wouldn't worry so much about that.
The s4 is an awesome phone, take a look at all the xposed modules you can add and really customize it.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
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
So my VWZ S4 crapped out on me. About 2 weeks ago, the USB port died completely. I bought some replacement batteries and and external charger and figured I would just swap out the battery every day. Last week, the microphone seemed to go too. On every call, my voice sounded "tinny" and robotic. I brought it to a Verizon store and the rep offered to send me a warranty replacement (I only had 3 days left before the 1 year warranty expired!).
The problem I have is that I had the MDK bootloader unlocked and had a custom ROM install. When I get the replacement phone in a few days, I will have to send my old one back to Verizon. The guy at the store told me I had to unroot and get the phone back to stock, otherwise Verizon charges a $300 penalty (ouch!).
My main problem it that I don't have USB access. It's completely dead. I was wondering if these steps would work:
(I'm currently running Vanir ROM and latest CWM)
1.) Flash TW 4.4.2 Stock Verizon I545VRUFNC5 (found here http://forum.xda-developers.com/showthread.php?t=2721118)
2.) Download/run Triangle Away to reset the Flash Counter.
3.) Use the SuperSU settings to "Full Unroot"
4.) OTA update that will lock bootloader???? (I think this is where I am screwed)
Any other thoughts or suggestions?
to me that sounds legit on how it should be done. or even doing the Kies way of update after you put stock (any bl version) or buy a usb charging port and microphone and fix the phone. couple bucks on ebay or amazon n an easy fix
FordNate, I wish I had the technical skills to replace both. Unfortunately, I do not!
I wonder if this method will be good enough for Verizon. I don't know that this will re-lock the bootloader if I do the steps above?
double zero said:
FordNate, I wish I had the technical skills to replace both. Unfortunately, I do not!
I wonder if this method will be good enough for Verizon. I don't know that this will re-lock the bootloader if I do the steps above?
Click to expand...
Click to collapse
It should, since the bootloader was never unlocked anyway. Loki was a convenient workaround.
wtherrell said:
It should, since the bootloader was never unlocked anyway. Loki was a convenient workaround.
Click to expand...
Click to collapse
Thanks. Sounds good. Do you know for a fact that there will be an OTA update to take if I flash the TW 4.4.2 Stock Verizon I545VRUFNC5. Should I flash something else instead?
double zero said:
Thanks. Sounds good. Do you know for a fact that there will be an OTA update to take if I flash the TW 4.4.2 Stock Verizon I545VRUFNC5. Should I flash something else instead?
Click to expand...
Click to collapse
Idk.
wtherrell said:
Idk.
Click to expand...
Click to collapse
Me neither. I'm not sure what the final step should be. However, I feel like if I flash a stock ROM and unroot, I should be good enough for Verizon.
I don't know if they ever turn them on once they get them.
I recently sent a Galaxy S3 in with full root and the "Custom" text on the screen for replacement.
The only email I ever got was that the phone had been received. YMMV.
tech_head said:
I don't know if they ever turn them on once they get them.
I recently sent a Galaxy S3 in with full root and the "Custom" text on the screen for replacement.
The only email I ever got was that the phone had been received. YMMV.
Click to expand...
Click to collapse
Interesting. When I was at the Verizon store, the guy at the customer service area told me to return it to stock, because they would definitely check to see if the software was modified. That's why I'm worried about trying to return to stock (or as close to possible) before sending it in.
It seems like if I do the steps I suggested above, it would "appear" to be stock, but it would still have CWM installed. Maybe that will be good enough? I don't think I have any other choice.
@Surge1223 Unique situation I think I remember you having a solution for awhile back. Any advice on this OP?
double zero said:
Interesting. When I was at the Verizon store, the guy at the customer service area told me to return it to stock, because they would definitely check to see if the software was modified. That's why I'm worried about trying to return to stock (or as close to possible) before sending it in.
It seems like if I do the steps I suggested above, it would "appear" to be stock, but it would still have CWM installed. Maybe that will be good enough? I don't think I have any other choice.
Click to expand...
Click to collapse
Easiest method would be to find an me7 ota zip and stock mdk recovery.img and boot.img, if you have a stock mdk back up. Otherwise id suggest going to mk2 instead of nc5 that way you would get an ota notification...although I think flashing a stock rom, recovery and kernel then using supersus full unroot method should do the trick.
Surge1223 said:
Easiest method would be to find an me7 ota zip and stock mdk recovery.img and boot.img, if you have a stock mdk back up. Otherwise id suggest going to mk2 instead of nc5 that way you would get an ota notification...although I think flashing a stock rom, recovery and kernel then using supersus full unroot method should do the trick.
Click to expand...
Click to collapse
Surge, I don't have a stock mdk back up, unfortunately. I went through the forums and found this MK2 Rom (http://forum.xda-developers.com/showthread.php?t=2581072). Do you think that would work?
1.) Flash the http://forum.xda-developers.com/showthread.php?t=2581072 ROM
2.) Download/run Triangle Away
3.) SuperSU (Full Unroot)
4.) OTA update to NC5 (lock bootloader)?
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.
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