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.
Related
So I got careless while prepping my phone for warranty return, unrooted and wiped, and then discovered that the su binary was baked into the ROM. I'd re-root the phone, but the problem is, the reason I'm returning it is the USB port is screwed up. I can't get a reliable connection with a computer to root. Is there a way to root wirelessly, or via download?
EDIT: I'm still running 2.3.4 (UCKH7)...could I just do an OTA update? That would basically flash new firmware on the phone, right?
Check 3A in this thread, or check out this thread. Mobile Odin should be able to do what you want to do.
Red5 said:
Check 3A in this thread, or check out this thread. Mobile Odin should be able to do what you want to do.
Click to expand...
Click to collapse
So I kinda feel like an idiot...I didn't actually think the Superuser app was still usable (I assumed my previous kernel flash somehow wiped root...not sure what I was thinking), so I didn't try Mobile Odin. After your suggestion, I went ahead and tried it...and it prompted for authorization. If the app is there, it should work...duh.
I was able to do a full update via Mobile Odin, which appears to have flashed a completely stock kernel, rom, etc. I then did a factory reset. Everything appears to be stock. Thanks!
nd_geek said:
So I got careless while prepping my phone for warranty return, unrooted and wiped, and then discovered that the su binary was baked into the ROM. I'd re-root the phone, but the problem is, the reason I'm returning it is the USB port is screwed up. I can't get a reliable connection with a computer to root. Is there a way to root wirelessly, or via download?
EDIT: I'm still running 2.3.4 (UCKH7)...could I just do an OTA update? That would basically flash new firmware on the phone, right?
Click to expand...
Click to collapse
I can't thinik of any way to root the phone without usb. Mobile Odin requires the phone already be rooted.
I believe the OTA update in incremental, so I don't think it will touch the su binary.
Are you sending it back to Samsung, or taking it to AT&T? What is the chance that anyone is going to look in the file system? Probably non existant with AT&T. Don't know with Samsung.
creepyncrawly: looks like I posted after you started to but before you finished...you're probably right on AT&T not noticing, but they already almost wouldn't take a warranty exchange via the phone support due to the USB port issue (they wanted to call it "physical damage"), so I figured I'd better do everything I could to make it look stock.
nd_geek said:
So I kinda feel like an idiot...
Click to expand...
Click to collapse
You should. Everything you've posted today could have been dealt with in 1 thread instead of 3.
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Shawnkanan said:
OK so here is the story and I was debating if this is the right place to post but I do feel it is more on the developing side. I originally rooted and unlocked my bootloader following Casuals method and everything was just fine. I had an option to sell the phone in preparation for buying the GS4 so I used the return to stock method posted in the forums to return my device completely to stock. After doing so everything was also fine. I received an update to LL4 and that went OK straight from Verizon but last night when the VRAMC3 update was pushed to my phone it soft bricked it. It ultimately was stock on the splash screen stating Samsung Note 2. After trying to ODIN back to stock with multiple FAILS I was able to get it back to the Root66 MR Robinson by using the pit file but every time I try to update and or root/unlock bootloader it soft bricks again. I am assuming that the update that was pushed updated my bootloader and as of now I am stuck till there is a new bootloader Jailbreak. If not I would love some instruction on how to get my phone rooted with an unlocked bootloader or a flashable ODIN file that will at least get me to the latest VRAMC3 fully stock ROM. Thank you for the HELP.
Click to expand...
Click to collapse
I had the same problem. Flash the pit file with odin and wait for the phone to turn on. the problem is fixed to get the phone working. Then you can flash other stuff.
Thank you for the replies even though one was not helpful at all. I have flashed the root66 file with the pit and it does work but if I try to run the casual jailbreak or flash any other odin files it fails. My assumption is my bootloader got updated and has locked me out and I will just have to wait for a new boot loader exploit. Thanks
Sent from my SCH-I605 using xda premium
droidstyle said:
Next time read the stickies...when they say NOT to accept OTA updates, usually there is some meaning behind it.
Click to expand...
Click to collapse
Is best advice u can get to avoid unwanted situations
XT912 CDMA
1droidmod said:
Is best advice u can get to avoid unwanted situations
XT912 CDMA
Click to expand...
Click to collapse
No I can give more, but I get tired of repeating myself all the time...especially when its posted in every section of this sub forum.
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
1droidmod said:
Read Read, Search Search... U will figure it out..
XT912 CDMA Pac Man 4.2.2
Click to expand...
Click to collapse
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
madtowner11 said:
Is there a sticky or something definitive on the subject of rooted (via Casual) Verizon Note 2 users getting the OTA update and retaining root? I'm currently VRALL4, rooted via Casual, with SDM frozen to avoid the OTA update. But I'd rather not stay in this state indefinitely.
Click to expand...
Click to collapse
Once you are rooted via Casual there is no such thing as accepting Verizon's OTA if you want your phone to keep working. (This info can be found in 1 or 2 basic searches, which everyone should do first.)
If you want to get the 4.1.2 features there are 3 options that I know of: 1) flash a zip of the 4.1.2 update, 2) flash a full 4.1.2 stock rom, or 3) flash a custom rom that has 4.1.2 features in it. You can find all 3 options in the Original Development section of xda. Imnuts has implemented #1 but read the forum on the ins and outs. Beanstown106 has created #2. And Beanstown106's latest Jellybeans 16 is a custom rom that incorporates 4.1.2.
I need to send in my MDK S4 for screen repair to Samsung, and I'm worried about them flashing the update killing access to loki. Is there any way to to prevent flashing of ME7 / retain loki exploit post-flash, or am I doomed?
SellswordShev said:
I need to send in my MDK S4 for screen repair to Samsung, and I'm worried about them flashing the update killing access to loki. Is there any way to to prevent flashing of ME7 / retain loki exploit post-flash, or am I doomed?
Click to expand...
Click to collapse
Kinda screwed because you have to root it to do so they could check, see it was rooted and then deny warranty claims. I would call ahead and make sure they know you dont want it updated or include a note that states you dont want it updated.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
hexitnow said:
Kinda screwed because you have to root it to do so they could check, see it was rooted and then deny warranty claims. I would call ahead and make sure they know you dont want it updated or include a note that states you dont want it updated.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Click to expand...
Click to collapse
Its an out of warranty repair (cracked screen), so the rooting doesnt matter. I know OTA can be blocked via root, but doesnt prevent from them just flashing it via ODIN/Other firmware software. I was hoping there was some way to dupe the firmware updaters but couldnt find any from my search. I guess I just have to leave a note and hope they dont flash the update.
SellswordShev said:
Its an out of warranty repair (cracked screen), so the rooting doesnt matter. I know OTA can be blocked via root, but doesnt prevent from them just flashing it via ODIN/Other firmware software. I was hoping there was some way to dupe the firmware updaters but couldnt find any from my search. I guess I just have to leave a note and hope they dont flash the update.
Click to expand...
Click to collapse
A kind note is probably your best way to not have them update, because if they wanted to I'm sure there's nothing you could do to block it... but my question is why would they need to update your device if they're just replacing the screen? Seems like that would just be a waste of their time
Crawshayi said:
A kind note is probably your best way to not have them update, because if they wanted to I'm sure there's nothing you could do to block it... but my question is why would they need to update your device if they're just replacing the screen? Seems like that would just be a waste of their time
Click to expand...
Click to collapse
When my brother sent his HP computer into repair for a broken fan they reimaged it for no reason...
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Under the settings in the Superuser app is an option to "Full Unroot" Will this really work for unrooting the device, or do i need to do the odin thing i keep reading about? Why would odin even be necessary if this is an option. It seems to easy.
You will need to return your phone to stock, root will prevent the OTA. You can try to unfreeze SDM and take the update, it won't brick your phone, it will just fail to install because root will cause it to fail.
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Paramemetic said:
There are threads about using Odin and no-wipe MK2 or MJ7 files to return your phone to stock without losing data. That is the best way to roll your phone back to take the update. Alternatively, you could just do a factory reset from the stock recovery, but you'll lose all your data on the phone. Otherwise, you can just update using the Odin tars that are available now, but since it seems like you don't want to do the research on how to do that, you'd probably better not try.
Click to expand...
Click to collapse
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
Thanks,
So you do not recommend or know about the "Full Unroot" option in the Superuser settings.
I do not mid a factory reset, as this is phone is only a month old. If it is that easy, I will probably go that route.
I am currently downloading a file called VRUAMDK_NoWipe.tar.zip which I understand to be a stock image of my android before i rooted that is supposed to take me back to pre-root. But if factory resetting will accomplish the same goal, then that seems like an easier way to go.
I do like the openness of being rooted, but My concern about updating with the root, is that some functions may not work like they are supposed to. I haven't been involved in rooting since the days of playing with my HTC Eris, and Droid X. Maybe things a re different today, but most roms I played with were found to have issues with thinks not functioning correctly. Do the 4.4 "tars" that you are referring to have all the functions?
Click to expand...
Click to collapse
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
jmgib said:
The no wipe image you are downloading is probably not the correct version for your phone unless you are still on the MDK firmware.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Bummer, I was wondering about that after i started looking at different image names. I started seeing the common theme, and no I am not on MDK, I am on MK2. Bummer because that file took along time to download here at work.
kude87 said:
I'd sit tight and see what comes from the latest tar files of NC5. Maybe nothing, but can't hurt to wait.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Rageboardr said:
What is the difference between a tar file, and ROMing. Are TAR files more reliable?
I am in no real hurry, but as this is my daily phone, I need everything to work correctly, and no reason to wait if its like ROMs, and there seem to always be things that are quirky in a ROM.
Click to expand...
Click to collapse
If it is your daily and you aren't in any hurry, I strongly suggest waiting it out. Read some forums and get a better feel about rooting and romming.
A tar file is flashed through Odin, and depending which one you download, could lock your bootloader (I forget which firmware you're on). I'd personally wait for/if NC5 is rooted and proceed then.
"Romming" is a broad term used to define flashing custom roms. Predominantly, this means you have an unlocked bootloader and are flashing zip files through a custom recovery.
Sent from my SCH-I545 using XDA Free mobile app
Rageboardr said:
I rooted my phone to prevent KitKat from installing, because I didn't want to lose access to FoxFi. I forze the SDM file so it wouldnt look for updates. Today FoxFi has fixed the problem, so I no longer fell the need to be rooted, and I would very much like a taste of that KitKat. If I understand correctly I should not unfreeze the the SDM file and take the OTA update, because it could "brick my phone". Is that the case?
Do I need to unroot first, and is there a thread without a hundred pages that explains how to unroot. I am on Build VRUEMK2.
Thoughts?
Click to expand...
Click to collapse
Hi I had the same issue. mk2, rooted, wanted to take the ota update and didn't mind losing root.
You won't brick trying to take the update it will just fail with error 402. I wrote out my steps below to guide you thru the process I used and were successful for me.
1. Unroot using SuperSU.
2. Use Kies to update/restore firmware on your PC.
3. Once rebooted search for system update.
4. Download and install the update. I did the whole process using only data no WiFi (not sure if it makes a difference but that's what I did).
5. Once your phone reboots you will be greeted by a lovely red Verizon splash screen.
Hope this helps you and others!
Sent from my Hp Touchpad Android 4.4.2 using Tapatalk Pro
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)?