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)?
Related
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
androidy_guy said:
hi,
just got my GS4 today and, very stupidly, agreed to let the phone update to the new firmware via verizon's OTA update to VRUDMI1. realizing i had already made a mistake, i used ODIN to try and flash it back to the stock firmware, which failed. i tried a couple packages for the stock VZ image, but both have failed. also, apparently the VZ GS4 does not give you a serial number, so Samsung's KIES is not an option, unless i am mistaken. i tried downloading that and using my IMEI as the serial but it says the serial is incorrect.
am i completely screwed? or maybe just for the time being until a new image for flashing back to stock from the new firmware is released? the phone boots into ODIN but gives the message that there was an error while updating the firmware, and to try the software repair assistant. based on what i've been reading, it seems that this is sometimes fixable, but perhaps it is just too early for this firmware at this point? ugh.
long shot: the phone was not rooted at the time, locked bootloader, running the fully stock VZ image and new firmware -- perhaps they would provide assistance? i wouldn't hold my breath though!
Click to expand...
Click to collapse
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
spc_hicks09 said:
Yeah once you go to ME7 or MI1, there is no going back. You can only stay where you are, or go forward. You'll need to use Odin again and this time flash the MI1 file.
Which can be found here thanks to Surge1223
http://forum.xda-developers.com/showthread.php?t=2484726
Click to expand...
Click to collapse
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
tech_head said:
Chances are it will also flip the knox warranty to void because knox status/warranty is now included in the new firmware.
Click to expand...
Click to collapse
hmm, interesting. perhaps i should try my luck with VZ first? i guess it can't do any harm. currently when it turns on it shows knox status 0x0, which is apparently good. perhaps VZ can flash it somehow? i have no idea what kind of support they provide for this kind of thing.
edit: also it seems this KNOX is mainly relevant for creating a secure zone for corporate applications? i am not using it in that setting. perhaps it would just reduce the resale value somewhat? or is there something i'm not understanding about it.
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
tech_head said:
That flag if set will have Samsung trying to deny any warranty.
They are not going to flash it for you.
Not advocating fraud or anything., but you have only had it one day.......
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Flash the Odin posted in post 2. Then you can root and use safestrap the same as it being on me7 like it was.
androidy_guy said:
yea, i figured as much. it does say "system status: custom" though - maybe that alone will screw me? not sure how VZ will see that. if they refuse is it worth contacting samsung directly?
also, bought the phone used from a friend, so that prob eliminates any hope from VZ to begin with.
Click to expand...
Click to collapse
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
^^^^^^^^^ what he said
tech_head said:
Okay, bought from friend not Verizon.
So back to ODIN it is.
You just need the latest firmware to flash. You can't use ME7 but you can use the latest one.
The file is in this thread -> http://forum.xda-developers.com/showthread.php?t=2484726 like one of the previous people posted.
You already know how to use ODIN and this should work. Just remember PDA mode.
Once you flash Me7 there was no going back and MI1 is the same. No going backward.
You should be fine if you can get into download.
Click to expand...
Click to collapse
will do - downloading the package now. should be able to fool around with it after work today. i feel like a real idiot for rushing into this without knowing enough about the OTA firmware that i ignorantly accepted.
at this point i don't really care if the KNOX is triggered or whatever - i always purchase my devices out of warranty and activate them so i can keep my grandfathered unlimited. it's the risk i run for wanting stock android on verizon with unlimited data
ooooook, the package in that thread worked. thanks a lot guys! i was really kicking myself all day over this one, and really had only myself to blame. my only questions now are:
how can i check my KNOX status?
is it likely that there will be a root/CM version for this phone, post UMI1?
Reboot into download and read the tiny text with a magnifying glass
Sent from my SCH-I545 using Tapatalk
Im glad the odin image worked...pulling that thing was kinda difficult lol.
ok i booted into ODIN again and KNOX comes up 0x0, so it looks like i came out unscathed all around. too bad i inadvertently locked my phone down with this update. i got the GS4 so i could upgrade from my GN, in hopes of flashing the latest CM10 on a phone with some nicer hardware.
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
So, I dropped and cracked another screen, 4 but whose counting. I called Assurion and they said they'll send me a new i605 without updating it to OTA 4.3
Now my main question is how do I go about unlocking the bootloader, and rooting it from stock. It's been so long since I was on a bone stock rom. I know the last time I did it there was some "suck it verizon" file and a .pit file. Do I follow these direstions: http://forum.xda-developers.com/showthread.php?t=2043636
Also, When I get it unlocked and Philz recovery on the phone can I restore a backup of Sophisticated rom, or do I have to reinstall from scratch?
crbnfbr said:
So, I dropped and cracked another screen, 4 but whose counting. I called Assurion and they said they'll send me a new i605 without updating it to OTA 4.3
Now my main question is how do I go about unlocking the bootloader, and rooting it from stock. It's been so long since I was on a bone stock rom. I know the last time I did it there was some "suck it verizon" file and a .pit file. Do I follow these direstions: http://forum.xda-developers.com/showthread.php?t=2043636
Also, When I get it unlocked and Philz recovery on the phone can I restore a backup of Sophisticated rom, or do I have to reinstall from scratch?
Click to expand...
Click to collapse
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Bonkurei said:
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Click to expand...
Click to collapse
Thanks, that will be a lot easier than the original method I had to do over a year ago. I just really hope they send me a non upgraded phone. The guy said he would put a note in my claim not to do the 4.3 OTA upgrade, fingers crossed.
Bonkurei said:
If its 4.1.2 go here to root, unlock bootloader and install custom recovery in 1 click.
Since u already have a backup, I think after you have custom recovery, you just can restore your backup.(cmiiw)
Click to expand...
Click to collapse
Thanks, that will be a lot easier than the original method I had to do over a year ago. I just really hope they send me a non upgraded phone. The guy said he would put a note in my claim not to do the 4.3 OTA upgrade, fingers crossed.
Turns out to be a moot point. New phonrle came with 4.3. Even though the Assurion guy I talked to yesterday said it wouldn't. Now they say they "have" to update to the newest firmware, or it won't work with the network. What a bunch of BS.
So, I'm sort of confused right now. I'm getting "internet unstable messages" on 4.3, and I only got those was from Beans 4.3 leak.
Could it be that my phone was flashed with a leaked 4.3 then sent in to the insurance company, and never updated because it'd already be running 4.3?
Hey guys... I need some help.I have many questions.
So as the title says. My S4 over heated. It's actually been happening for a while and the glass had begun separating from the digitizer over the last few months. A few day ago I awoke to a blotched out black screen that blacks out every so often.
I held off getting a replacement because I was rooted, loki'd on the MDK bootloader.
My replacement arrived today and it was the MK2 baseband. Upon start up VZW tried to push the OTA to me. i stopped it and postponed it to 6:00 AM eastern, MDK was easy, but I'm not familiar with this new process and had some questions. So using searches on XDA I have:
1) Rooted with Saferoot
2) Installed Wanam Xposed
3) Renamed SDM.apk & FWUpgrade.apk to .bak's to the update <-- was this right? I dont want to wake up to a voluntarily installed OTA.
Questions
1) Should I install SafeStrap, if so which version? I see there's an ATT version out there for upgrading to NC5, but there's also a MK2 version.
2) I see a lot up people were able to update to NC5 and keep root with Surge's method. Is there an advantage to this?
3) What's everyone doing for hotspot/tethering now on MK2 and up?
4) On MDK, most of the ROMs were debloated. What do I do to get rid of some of this VZW bloat on here.
Now I need help with the old phone.
Even though the other phone over-heated. I can just see VZW rejecting the exchange because I was rooted, Now with the screen being all black blotches and cutting out, I can't really return it to stock. The phone turns on, and works. I just cant see what's on the screen.
Is there a way for me to utilize my computer to unroot, return to stock recovery, and install a stock ROM all without being able to see the screen on the phone?
I don't want to delete my old Clockwork Mod nandroids from my SD card until I can return the old phone to stock.
Thanks for your help in advance.
ymDroid said:
Hey guys... I need some help.I have many questions.
So as the title says. My S4 over heated. It's actually been happening for a while and the glass had begun separating from the digitizer over the last few months. A few day ago I awoke to a blotched out black screen that blacks out every so often.
I held off getting a replacement because I was rooted, loki'd on the MDK bootloader.
My replacement arrived today and it was the MK2 baseband. Upon start up VZW tried to push the OTA to me. i stopped it and postponed it to 6:00 AM eastern, MDK was easy, but I'm not familiar with this new process and had some questions. So using searches on XDA I have:
1) Rooted with Saferoot
2) Installed Wanam Xposed
3) Renamed SDM.apk & FWUpgrade.apk to .bak's to the update <-- was this right? I dont want to wake up to a voluntarily installed OTA.
Questions
1) Should I install SafeStrap, if so which version? I see there's an ATT version out there for upgrading to NC5, but there's also a MK2 version.
2) I see a lot up people were able to update to NC5 and keep root with Surge's method. Is there an advantage to this?
3) What's everyone doing for hotspot/tethering now on MK2 and up?
4) On MDK, most of the ROMs were debloated. What do I do to get rid of some of this VZW bloat on here.
Now I need help with the old phone.
Even though the other phone over-heated. I can just see VZW rejecting the exchange because I was rooted, Now with the screen being all black blotches and cutting out, I can't really return it to stock. The phone turns on, and works. I just cant see what's on the screen.
Is there a way for me to utilize my computer to unroot, return to stock recovery, and install a stock ROM all without being able to see the screen on the phone?
I don't want to delete my old Clockwork Mod nandroids from my SD card until I can return the old phone to stock.
Thanks for your help in advance.
Click to expand...
Click to collapse
1. Install Safestrap for your corresponding baseband. If you have mk2 then install safestrap for mk2.
2. If you upgrade to NC5 and keep root you can flash 4.4.2 touchwiz roms on the stock slot usingthe att 3.72 safestrap
3. For tethering you can use foxfi or you could use surges tethering unlock
4. You can debloat stuff by just disabling the apps you dont want.
For your old phone,
1. You should be able to get your data off of it by just connecting it to your computer then copying stuff from your old phone to your computer.
2. To reset it back to mdk stock, you should boot into odin mode doing the keypress when your phone is off, then after a few seconds press volume up to comfirm boot into odin mode. Then you should be able to odin mdk stock from here: http://forum.xda-developers.com/showthread.php?t=2751461
Best of Luck
joshuabg;52899257
2. To reset it back to mdk stock said:
http://forum.xda-developers.com/showthread.php?t=2751461[/url]
Best of Luck
Click to expand...
Click to collapse
THANK YOU.
Quick question. Does this odin MDK flash install the stock recovery back.
ymDroid said:
THANK YOU.
Quick question. Does this odin MDK flash install the stock recovery back.
Click to expand...
Click to collapse
It should, I think it goes over all partitions, boot, persdata, system, recovery, modem, etc.
Won't hurt to try.
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.