Related
Some people like sticking with stock, and there isn't a huge issue with that as the stock ROM is pretty good on the Note 2. However, if you want to be stock and remained unlocked, it's quite difficult to do as every new OTA re-locks the bootloader. It's also difficult to stay stock and keep a custom recovery as it will be over-written on every boot.
Now, users that want to stay unlocked and have custom recovery have an option available. This will require you to be fully stock, if you've modified anything in /system, it won't work. The only change you can have is root, but if you've modified build.prop, the kernel, or removed any files, you need to restore. If you have any doubts, flash the alternate restore file (after extracting it) from here.
There is one other requirement for this, and that is you need a custom recovery installed. If you've unlocked, you'll already have one. If not, you'll need to be rooted and you can use ROM manager or GooManager to flash a custom recovery (after going back to stock of course).
Now you have the pre-requisites down, stock rom and custom recovery, so all you need are the files. There are two updates available, so there are currently two files to flash to be on the latest OTA. You can download them below, and installation is as simple as downloading them to your phone and installing them via recovery. If you went back to stock VRALJB, you'll start with the VRALJB to VRALL4 file, then flash VRALL4 to VRAMC3 to get to the latest system. It should be fairly easy to figure out.
If you have any errors when flashing, odds are, you did something to files in /system and caused a problem. If that is the case, start over and flash the alternate restore file and proceed from there. I'll continue to update this as new OTAs are released then as well.
[size=+2]Downloads[/size]
VRALJB to VRALL4
VRALL4 to VRAMC3
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Digbob said:
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
It updates everything except for sboot.bin, tz.img (both bootloader files), and recovery.
hey thanks for this!
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
it says you must be on completely stock rooted with a custom recovery. being you have a custom kernel is most likely the problem. anything modified in /system will cause a fail. flash back to vraljb alternate restore file, then upgrade...or boot into recovery and flash beans mc3 stock rooted .zip rom
either way you will most likely need to wipe data to upgrade...atleast thats normallya prerequisite when changing bases.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
imnuts said:
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
Click to expand...
Click to collapse
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Hey thanks for this! This'll make my wife very happy. I thought I'd have to clean install beans stock rom. She just loves stock.
Sent from my Note II using Tapatalk 2
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
OTA fails if you have a custom recovery.
Sent from my Note II using Tapatalk 2
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
FAUguy said:
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Click to expand...
Click to collapse
You're setting your phone up again either way.
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
Not everyone is running a custom ROM. Some people are unlocked and on stock rooted with custom recovery and that's it. This is meant so they can stay up to date and remain on stock, rooted, and custom recovery.
TonikJDK said:
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
Click to expand...
Click to collapse
This will be fully stock (minus recovery over-write). Beans did some other stuff to his ROM package from what I saw the last time I looked at the thread. Nothing major or groundbreaking, but it isn't as close to stock as this is.
pmazz850 said:
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
Click to expand...
Click to collapse
Really?
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Mac of York said:
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Click to expand...
Click to collapse
Yah, I think I'm gonna wipe/flash beans odex rom VRAMC3 & radio/restore data from NAND backup from VRALL4, hopefully it should be fine. Unless anyone would know otherwise?
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
What change for Wifi Tether?
imnuts said:
What change for Wifi Tether?
Click to expand...
Click to collapse
WifiTether_TrevE_Mod_11_22_2012.apk
After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
decaturbob said:
Install phone info from play store. ..If you have mk2...bootloader and firmware I have no idea how you got a cm base rom loaded....As for taking an OTA. ..you have to be 100% stock...no root..nothing frozen.
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
apefist said:
I actually don't have a CM base rom loaded, sorry if I made it sound like that. I am still on 4.3 stock w/ root. I wanted a CM ROM, and it seemed like I couldn't do it through safe strap so I tried to put TWRP recovery on there and I got boot-looped (which ended up fixing itself). Now I am trying to figure out how to get a recovery on there, and what my ROM options are (if I can get to 4.4.2 rooted, I would be happy).
I got the phone info program, is there any specific info you wanted off of there?
It says bootloader version I545VRUEMK2, baseband is same
Click to expand...
Click to collapse
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
riker147 said:
Your ONLY option for recovery is Safestrap. You can ONLY install Touchwiz based Roms.
There are a lot of threads in the General and Development sections you should check out before you go any further. I would link them for you, but I'm on my way out. Good luck.
Click to expand...
Click to collapse
OK, well then my current problem is even though I have the safestrap app installed, and the program reports safestrap recovery as being installed, I can't access it. There is no safe strap screen while booting or button options, and even if I do the forced boot into recovery (press power+vol up+home at the same time and hold until you see the "Recovery Booting" message) it just boots to the normal phone every time.
Also worth noting is for every boot, no matter how i start it, it says "Recovery booting" at the top, but never boots into recovery. I have tried uninstalling safe strap recovery through the safe strap app and re-installing but it is the same thing.
apefist said:
After looking through some of the threads, I think I have a slightly unique situation.
I got my S4 through swappa, and it was already on MK2. I rooted using motochopper and installed safe strap, and that worked (when booting, I could get into the options screen mess with stuff, etc). I didn't install any ROMS since there weren't any I was interested in besides cyanogenmod
In my attempt to install cyanogen mod, I tried installing another recovery, I think TWRP. That earned me the unlocked symbol when booting, and I was stuck in a weird boot loop for a while. I started researching flashing a clean ROM onto my phone, but lo and behold, it actually fixed it's own boot loop and started up again.
That was a month or two ago, before the NC5 4.4.2 update. I decided since it had resurrected itself I would just wait for a bit and see what other tools came out.
After the 4.4.2 update came out, I ignored it for a bit. I tried installing the OTA update once and it went through it's song and dance and after it rebooted it said it couldn't complete the update so nothing was changed. I assume that is because it's rooted? I didn't really force uninstall any apps, I just disabled them through the included app manager.
So where I'm at now is I'm still on MK2, I can't install the OTA update, everytime I reboot my phone I get the unlock symbol and it says "Recovery Booting..." in blue letters at the top, but it never boots into any sort of recovery.
I have tried installing safe strap again and the safe strap app says "State: Installed" but when I reboot it says that recovery booting thing, and then just boots into the regular phone. I don't see the safe strap logo or button options at all.
Where can I go from here? Ideally I'd like to get on a custom ROM that's on the rootgalaxys4 website (it won't let me post links) but I don't know if I have the MDK bootloader, or even what my recovery situation is.
If anyone could help shed some light on this, it would be much appreciated!
Click to expand...
Click to collapse
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
k1mu said:
This is really hard to follow.
You can't root MK2 with motochopper, only MDK. Try installing the "Phone INFO *Samsung*" app from the app store to figure out what bootloader and baseband you actually have.
You can't install an OTA update if critical system files are modified, so you'll need to re-flash to a stock ROM to do that. But if it's really MDK, you do not want to allow any OTAs to upgrade your bootloader.
Click to expand...
Click to collapse
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
apefist said:
Ah, ok, I did the root a while ago, so I think I mixed up which one I had used, I believe it was SafeRoot via this thread:
http://forum.xda-developers.com/showthread.php?t=2565758
Someone earlier suggested installing the phone info app above, so I checked it and it says I545VRUEMK2 for both bootloader and baseband.
The OTA update thing was just me trying to provide as much info as possible, I don't really want to do the OTA update because it seems like it removes root, and there is no good way to get it back on NC5.
At this point I would like to install some kind of rooted ROM, but I can't get into any sort of recovery. Safe Strap says it is installed but I can't boot into it.
Would the next step be to reflash a stock recovery? Is there some way to do that?
Click to expand...
Click to collapse
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
decaturbob said:
Installing safestrap is a 2 step process. Did u do both steps?
sent by bajarom v2.2 kitkat
Click to expand...
Click to collapse
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
apefist said:
If the two steps are:
1: Install the safestrap app (v3.71)
2: Go into the app and install the recovery.
In the app the recovery is listed as "Installed"
Click to expand...
Click to collapse
ok buddy you want to upgrade i take it?
click on the thread in my signature and download the 1st file listed called the COMPLETE PACKAGE it has everything you need.
you'll start tho by reflashing MK2 system through Odin then rerooting via Saferoot then reinstall Safestrap. Then the 4.4.2 ROM you want to use then reboot to Odin/Download mode and flash any of my NC2/NC5 1 File Upgrade packages. This is the easiest and most simplistic way to help you get to where you want to go. This will also keep your bootloaders at MK2 and your KNOX intact at 0x0! THE COMPLETE PACKAGE has all the modules, safestrap, supersu ect then if you have any questions the guys or me in the thread will help u. altho if you really do have CM running on your phone take screenshots I've tried porting to work with 4.3 and altho i can get two AOSP roms working I've never gotten close with CM it needs a custom kernel which is something we cannot use with our locked bootloader. only AOSP/GE Roms that will work for 4.4.2 or 4.3 are ones that are compatible with the stock 4.3 or 4.4.2 kernels theres a thread in the development section for that subject as well.
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Saint Isaiah said:
I've never had any issues flashing ROMs until I tried flashing one of the beta builds of the 4.4.4 Google edition ROM. The creator of the ROM has been having issues with WiFi and data not locking correctly and released an APN zip to possibly resolve the issue. Flashing that zip though, which I'm pretty sure changed the radio, resulted in the phone having connection issues on any ROM. I also noticed that the baseband version was changed from MDK to NC5, so long story short, I used ODIN to revert back to MDK bone stock, reverted back to to MD2 (I believe) to root, then back to MDK.
Here's where I'm a little stumped. I tried to use the ROM manager app to install CWM touch recovery and every time it would say it's successful, but booting into recovery would give me the stock android version, which we all know is pretty useless other than for stock updates and erasing data/cache. So the only way to get CWM recovery installed was to use terminal on the phone to do the Loki flash method. I'm a little out of touch, so can someone explain to me what exactly Loki is other than a "workaround" for the bootloader, how it applies to MDK for running AOSP ROMs without the "unauthorized software" message, and what, if any was the unlocking method for the MDK bootloader? It's been so long that I can't remember how I set everything up initially, and doing a search didn't yield any kind of guide for newbies or those out of touch like myself.
Thanks for taking the time to read and help!
Click to expand...
Click to collapse
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
joshm.1219 said:
Loki is an exploit that allows the system to bypass bootloader checks and load custom software. If this happens again, restoring an EFS backup should fix your issue.
If you ever need to go back to stock MDK, you no longer need to do the downgrade to the prerelease MDL kernel. Just go to towelroot.com, install the towelroot apk, then hit the make it ra1n button. It's a new root method that came out a few months ago and works for a ton of devices. The easiest way to flash a compatible custom recovery for our device is to download Flashify from the play store and from there you can get the latest TWRP.
Click to expand...
Click to collapse
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Also, what in the world does it mean to "Loki" a ROM after installing it? Kinda confused there
Saint Isaiah said:
Gotcha, seems pretty straightforward. Wasn't there an actual unlock method for the bootloader though? I remember getting my download mode to read as custom as well as the boot logo, I just can't remember how and it seems like all traces of how to do it vanished.
Thanks for the help!
Click to expand...
Click to collapse
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
joshm.1219 said:
No, never an actual bootloader unlock, besides Dev editions that came unlocked. My download mode still says "install custom ROM" or whatever. There's no discernable difference to the end user between an unlocked bootloader and an exploit like the Loki bypass.
Click to expand...
Click to collapse
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Saint Isaiah said:
OK, and I'm assuming the reason why being on MDK is so important is because upgrading to ME7 patches the vulnerability that can allow the boot loader to be bypassed, forcing you to use safestrap, which results in no custom kernal being able to be used?
And my question above: what does it mean to install, then "Loki" a ROM in the install steps?
Thanks again, you're awesome!
Click to expand...
Click to collapse
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
joshm.1219 said:
Yes exactly, ME7 patched it.
If you flash a TW ROM not built specifically for our device, The ROM (depending on kernel you flashed or if the ROM includes a kernel) may not have the files included to boot on a device with the Loki specific bypass. So you need to flash the " Loki doki zip " after the ROM and before initial boot. You can find the file on Google.
Click to expand...
Click to collapse
Awesome, thanks Josh! This might make a great sticky for the "what is Loki?" newvies and explaining the importance of MDK for those still on it and not sure why.
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Try to Odin back to MDK, if you had TWRP... If that doesn't work, nc5. You can't do custom ROM's like Cynanogenmod, but you have a limited amount of freedom with safestrap.
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
looneyk said:
I rooted my s4 and installed twrp a long time ago used the phone for a little while then stashed it away. It had the following rom installed I545VRVFNC5 stock root oder I believe it was 4.4.2. The other night I installed flash fire and attempted to flash I545_OC1_Stock_rooted_rom mdk. It flashed ok but now I'm getting the verizon warning message and I can't bypass. I can no longer boot into twrp. I think the bootloader is still unlocked, padlock is unlocked upon boot. How do I get myself out of this message?
Click to expand...
Click to collapse
Sent from my SCH-I545
SnyderGuy said:
The open padlock means the firmware you have installed is custom and not stock, doesn't mean your boot loader is unlocked. I would simply boot into download mode and re-image your device back to MDK, if that's where you were. What's your current boot loader version?
Sent from my SCH-I545
Click to expand...
Click to collapse
I am using an MDK S4.
I can bit to room, but cannot reboot to recovery.
Corrupted recovery after update via TWRP app.
How exactly, do I re-image my device back to MDK?
Do I use this stock MDK ROM? http://forum.xda-developers.com/gal...ment/rom-i545oc1-5-0-1-100-stock-mdk-t3097902
Do I put it in the BL or AP box in ODIN?
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
XxD34THxX said:
No, that is a ROM. You need the stock official software.
http://forum.xda-developers.com/showthread.php?t=2289325
SHOULD be that one...
Put that in AP
Click to expand...
Click to collapse
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
pizza_pablo said:
I just read it all. Looks like fun!
I sure would like to know what I did wrong. I only used the TWRP app to update TWRP.
Click to expand...
Click to collapse
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
XxD34THxX said:
That I cannot answer since I do not have MDK. My assumption is a corrupted download of TWRP or a partial install that was interrupted for some reason.
Click to expand...
Click to collapse
That may have been the case, since my connection was weak.
I'm just about to do the deed and I checked phone info and the bootloader is now I545VRUFNK4, vice MDK.
Here I go....
Well....I tried these to .tar files with no luck:
http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR
https://www.androidfilehost.com/?fid=22979706399752783
I did get the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Now, I no longer have the option to cancel Download Mode and bot ROM.
I didn't want to do anything in Kies, for fear of taking an OTA.
Do I have any options?
Even just taking an OTA and selling a former MDK treasure?
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
OK. So I am going to uninstall Kies, just for safety sake. Uninstall the Samsung PC drivers. Reinstall the PC drivers.
Use ODIN to flash this http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28Verizon%29%20%28SCH-I545%29/Stock%20ROMs/TAR in the AP box. Sacrifice a chicken and dance with snakes.
What do you think may have caused the bootloader to change?
At this point I guess any use of the phone will be a positive and somehow retaining MDK will be a miracle.
Thanks, for your assistance, as I am at a loss, at this point!
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
I used the link file, from my last post.
After I unzip it, delete the " .gz "
Got it. Thanks, again!
XxD34THxX said:
that is a .gz, so make sure to unip it/ delete that extension so Odin can use it.
My assumption is you may have accidently flashed the entire nk4, not just one with the MDK stuff still in.
Click to expand...
Click to collapse
So I just looked at the computer file and there was no .gz extention on the file I flashed thru ODIN.
It was not zipped, either.
On the xda page that you link, there was another choice on thier link. It was titled "one click". It is an .exe, titled "SCH-I545_MDK_562219_Stock_Restore.exe" .
What could ODIN do with this?
The other file I found, that I tried, but no change, was titled "VRUAMDK_NoWipe.tar.md5" .
Do you have any other suggestions,please?
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
I used this one, the other night, with no change, but this time I will delete Kies and phone drivers, then reinstall phone drivers, before ODIN.
You're a champ!
XxD34THxX said:
Use the Full wipe in this thread:
http://forum.xda-developers.com/showthread.php?t=2301259
If that does not fix anything you have either
A)Hard Brick(unlikely since the device is semi-working)
B) lost MDK.
Click to expand...
Click to collapse
Do I remove the .md5 extension as well as the .gz and just leave the .tar on the end?
ETA: Well, I tried removing both extensions and ODIN would not take it. Received error pop up.
I tried, with no success, ODIN flashing the full wipe and no wipe tars, with no success.
Giving up for the night.
XxD34THxX said:
This seems to be happening a lot. A LOT. Before you try kies, go into device manager and uninstall the Samsung USB drivers. Then download the DRIVERS ONLY from Sammobile/Samsung. THEN use Odin with a full wipe and repartition of MDK. If you get the same message again, then you have lost the MDK bootloader, and will have to repeat the process with an nc5 tar, which will loose custom ROMs, but you will have root and safestrap.
Click to expand...
Click to collapse
I woke up in the middle of the night and something popped into my head and I couldn't get back to sleep, so here we go....
The phone was on Echoe v49 which is Lollipop and I didn't like it. So I decided to go to the last Echoe version that was KitKat, v34.
I flashed this https://www.androidfilehost.com/?fid=95747613655044521 Which apparently is T-Mobile based, and the v20 international patch.
What popped into my head was that maybe my phone was thinking it was a T-Mobile S4, because I picked the wrong kernel. At the time everything seemed to work, except sending SMS. I could make phone calls and receive SMS.
This is was got me out of bed. I went to my notes for the Aroma install, to see what kernel I chose. I recalled picking the stock kernel, which may have been T-Mobile, but my notes say that I picked KTOONES kerenel in Aroma and in the Patcher, picked ADD VZW FILES AND BUILD PROP and NO KERNEL.
I was thinking that I had put a VZW version of TWRP onto a "T-Mobile" S4, getting me stuck to bootup in Download mode only, but still able to cancel Download and boot to system. Then I ODINed the VZW MDK stock firmware and am now with either Download mode or the yellow PC connected to phone screen, with the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I woke up thinking that maybe I had a T=mobile kernel and when I lost TWRP and only had stock recovery, downloaded the VZW version of TWRP on top of T=Mobile install. But the note makes it look like I would have been OK as far as the phone thinking it was a VZW S4.
Sorry if rambling, just trying to pass as many details and thoughts as possible.
Do I have any options, now?
I downloaded the stuff to do Heimdall One Click and was thinking about trying that route, with a file named "SCH-I545_MDK_562219_Stock_Restore.exe"
I have a 32GB MDK VZW SCH-i545 S4 that is running fine on ECHOE v29. Can I copy anything from that phone and flash in ODIN to recover the 16GB (was MDK) VZW SCH-i545 that is stuck on Download mode only?
Is there any way to flash a NANDROID via ODIN or some other program from a PC thru ODIN?
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
XxD34THxX said:
hmmm.. The Ktoonez kernal works on any s4. But if you flashed T mobile Files, which I don't think was the case since you flashed the Verizon stuff... I have never used Heimdall, so I can't comment on that. I don't know what to say. There might be a way to make a debrick image... Someone more experienced will have to help, sorry.
Click to expand...
Click to collapse
No need to apologize! You have helped all you can. I appreciate it greatly!
I just want to ensure that I exhaust ALL possibilities of recovering the MDK, before I throw in the Kies upgrade towel.
I wonder if I'll get in hot water for starting a new thread.....
Hi everyone, I haven't been active in awhile, and decided to upgrade from 4.4.4 to 5.0.1.
Device is:
Verizon Galaxy S4
MDK / Loki
TWRO 2.8.7.0
was on 4.4.4
I used the FlashFire upgrade method, because I wanted to have that upgrade modem, baseband etc. everything I needed.
Prior to root, I upgraded my TWRP, I did a TWRP backup.
I downloaded Odexed 5.0.1 stock update from the thread, and followed the instructions, it installed but on final reboot, it just got stuck at the Samsung / Custom screen. When I went to boot into recovery, it's now the stock system recovery LRX22c.I545VRUG0C1
Gives an error on the bottom as
Code:
#MANUAL MODE#
Appling Multi-CSC
Applied The CSC-code: VZW
remove failed file /system/csc_contents/ (read only file system)
If I try to apply update via external storage, using stock update I get:
Code:
footer is wrong
signature verification failed
Anyway I can flash TWRP via adb, then just re-flash the rom with loki manually? Or anyway without having to use odin and downgrade? I won't lose loki root will I? What do I do? Thanks in advanced.
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
notstevek said:
well I'm trying to flash back to MDK via odin, and I keep getting aboot.img failure.. i'm really at a loss here, I can't even odin back to MDK.
Click to expand...
Click to collapse
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Neffy27 said:
What instructions did you use? SS and FF were made specifically for locked bootloaders so they require a different instructions for flashing. You basically ignored the benefits of being on MDK by doing whatever you did. Doesn't sound like you're on MDK anymore and I need more details to help. Someone else might be able to help you.
If all you wanted was the OC1 modem, could have just flashed it from here. People have reported issues with TWRP versions above 2.8.4.0-jfltexx.
Click to expand...
Click to collapse
The tutorial said for mdk, I followed it exactly and it didn't work. I then ****ed up by flashing lollipop through stock recovery so it flashed the new baseband, and I removed loki. That's my bad, however I did follow the instructions and it didn't work. I should have just flashed 5.1 manually. Oh well. Is there safestrap for lollipop, or a way to downgrade to me7 to use safestrap?
Sent from my SCH-I545 using Tapatalk
SS isn't compatible with Lollipop. Recommend switching to FF, apparently it can flash Stang's ROM on stock OC1. Still need root. Or look into MultiSystem but I'm not knowledgeable with them but hear of success with them.
Sent from my SCH-I545 using Tapatalk 2.4.15
You can use king root to get root, then search for instructions to swap to supersu. From here should be able to install FF.
Good luck.
Sent from my SCH-I545 using Tapatalk 2.4.15