I have tried to look for this but can't seem to find info on this, maybe I'm not searching for the right thing, if anyone can point me in the right direction that would be fantastic.
I keep getting a msg on my phone that there is a software update on my phone, I go to install the update, it downloads it, then says my phone needs to be restarted. it restarts and I get to the CWM boot screen... then tells me it failed to update my phone. I'm assuming it isnt working due to the fact my phone is rooted. any suggestions on how to's to do this?
Thank you
Unroot phone .
Update OTA
Root phone
Or join XDA developers and flash stock rom via odin.
jje
MaximoKnight said:
I have tried to look for this but can't seem to find info on this, maybe I'm not searching for the right thing, if anyone can point me in the right direction that would be fantastic.
I keep getting a msg on my phone that there is a software update on my phone, I go to install the update, it downloads it, then says my phone needs to be restarted. it restarts and I get to the CWM boot screen... then tells me it failed to update my phone. I'm assuming it isnt working due to the fact my phone is rooted. any suggestions on how to's to do this?
Thank you
Click to expand...
Click to collapse
If you want a samsung update you have to flash a stock rom without root with Odin. You could also use Mobile Odin Pro for flashing a newer firmware and still keep root. You get the firmware here www.sammobile.com/firmware.
Disable Update
That sounds like a bit of a process that I'm not looking to get into right now... until then, is there a way to disable the update notification so that it doesn't keep alerting me that there is an update? it's starting to get rather annoying, it keeps pooping up from time to time.
You can freeze or remove the Update app. An app that doesn't exist cannot give you notifications.
It's not needed for the phone's correct functioning.
Flashing through Odin + Re-Rooting is a procedure of roughly 5 minutes, 4 of which for the firmware transfer and double-checking of the input.
Update CWM and re-run the root process
MaximoKnight said:
I have tried to look for this but can't seem to find info on this, maybe I'm not searching for the right thing, if anyone can point me in the right direction that would be fantastic.
I keep getting a msg on my phone that there is a software update on my phone, I go to install the update, it downloads it, then says my phone needs to be restarted. it restarts and I get to the CWM boot screen... then tells me it failed to update my phone. I'm assuming it isnt working due to the fact my phone is rooted. any suggestions on how to's to do this?
Thank you
Click to expand...
Click to collapse
I had the same issue. I had rooted the phone using an older version of CWM. In this version OTA updates download but fail to install after booting to recovery.
Download the latest versions of CWM from here and re-run the rooting process. The newer version of CWM (1.5 and up) supports OTA. Worked a charm for me!
Or you can just plug the handset into your pc and update with kies. You will need to reroot following this though.
Sent from my GT-I9300 using xda app-developers app
I have 4.1.1 Jellybean on my phone, is unlocked, an had no trouble updating to 4.1.1 from ICS. Now that my phone shows "Updates Available", downloads them files( I think), but does not install and rather says "Your device has been modified. Software updates are not available". The new updates I have seen in my mate's phone are good, and as he told me he had no trouble updating to it unlike mine.
What is the problem and the best way to solve this issue?
Also I'd like to ask, if I used Odin to update it manually, will I be able to update my phone with later releases without having to use Odin again?
airbends said:
I have 4.1.1 Jellybean on my phone, is unlocked, an had no trouble updating to 4.1.1 from ICS. Now that my phone shows "Updates Available", downloads them files( I think), but does not install and rather says "Your device has been modified. Software updates are not available". The new updates I have seen in my mate's phone are good, and as he told me he had no trouble updating to it unlike mine.
What is the problem and the best way to solve this issue?
Also I'd like to ask, if I used Odin to update it manually, will I be able to update my phone with later releases without having to use Odin again?
Click to expand...
Click to collapse
You answered your question yourself...modified = no ota update. Go back to stock unmodified or easier, download the new version from xda or sammobile and flash via odin
Sent from my GT-I9300 using xda app-developers app
OTA on rooted phones.
airbends said:
I have 4.1.1 Jellybean on my phone, is unlocked, an had no trouble updating to 4.1.1 from ICS. Now that my phone shows "Updates Available", downloads them files( I think), but does not install and rather says "Your device has been modified. Software updates are not available". The new updates I have seen in my mate's phone are good, and as he told me he had no trouble updating to it unlike mine.
What is the problem and the best way to solve this issue?
Also I'd like to ask, if I used Odin to update it manually, will I be able to update my phone with later releases without having to use Odin again?
Click to expand...
Click to collapse
Well i don't know what you mean with "unlocked" . If you mean rooted then it's easy :fingers-crossed:. You might have rooted with CF-Root or Toolbox or whatever. And in that process you were forced to install Clockworkmod Recovery and that's the reason you can't get OTA. If you want to have a rooted phone and OTA all you have to do is. Root your phone, stay on stock rom and flash the stock recovery via odin. But this means you loose CWM Recovery and a lot of the fun part about a rooted phone is gone.
Pure Drive GT said:
Well i don't know what you mean with "unlocked" . If you mean rooted then it's easy :fingers-crossed:. You might have rooted with CF-Root or Toolbox or whatever. And in that process you were forced to install Clockworkmod Recovery and that's the reason you can't get OTA. If you want to have a rooted phone and OTA all you have to do is. Root your phone, stay on stock rom and flash the stock recovery via odin. But this means you loose CWM Recovery and a lot of the fun part about a rooted phone is gone.
Click to expand...
Click to collapse
What part of "Unlocked" is confusing to you? It means the phone can run any sim card of any sim provider, thats what I meant, and no, the phone is not rooted or never even have tried rooting it... Never mind, I factory reset the phone and the update is done. Anyways kudos for your reply
Cheers!
Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
bbroydri said:
Really new to this. I did the verizon root methed for ME7. It says can't complete upgrade. Do I need to unroot in order to upgrade to MI1? If so, how do I do that?
Click to expand...
Click to collapse
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Had same problem, now soft bricke my phone and need help
k1mu said:
You don't need to unroot, but you do need to have the device in a stock condition. If you've debloated and removed stuff, or frozen apps, then the upgrade will likely fail.
I wouldn't be in any rush to install MI1.
Click to expand...
Click to collapse
I was in the same position trying to accept the update from ME7. I had re-downloaded the stock apps and was in the process of converting them to system apps when my phone froze. When I tried to reboot I could not get passed the Verizon screen. I have been trying to read about how to fix this but I am unable to get odin to recognize my phone. I have downloaded the Samsung drivers and tried every version of odin but nothing happens when I put my phone into download (odin) mode and connect it with odin open. The rest of the steps seem easy if I could just get it to see my phone. Any thoughts, going on 3 days with no phone.
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
bmwmcrider said:
I just received a notice from Verizonwireless that there is a new software update available. So I went ahead and downloaded the update and attempted to install it. After a few seconds a new window opened showing the stupid Android robot laying on its back and the word "error" displayed. Thinking something bogus is going on with my phone I did a factory erase and retried the software update - same results.
Any way to determine what the error is and correct it so I can do the SW update? Out of curiosity I tried using ClockworkMod Rom Manager to install a custom ROM but got the same error indication.
My phone is a Verizon Galaxy S4 with Andriod version 4.3. The baseband version is I545VRUEMK2.
Thanks.
Click to expand...
Click to collapse
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT be attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
es0tericcha0s said:
Sounds like your phone has been rooted / modified. This would be why. Samsung + VZW conspire to make it a mess to update officially when you have modded the phone. Just install the update via the PC and Odin. It is more reliable anyway than OTAs. If there is not an official 4.4 Odin version yet, then install the MK2 update that way and then factory reset then take the OTA.
But sounds like you really aren't sure what you are doing because you should NOT being attempting to use ClockWorkMod Rom Manager on a Verizon S4 with that update!! With the whole locked bootloader fiasco, this operation is not permitted as you can only use the SafeStrap recovery system to load custom roms. Really have to read up some more before you get your phone into a situation it might not find it's way out of...
Click to expand...
Click to collapse
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
bmwmcrider said:
Hi es0tericcha0s - Thanks for pointing out that Rom Manager shouldn't be used on a VZW Galaxy S4. I knew that but totally forgot about that fact.
Click to expand...
Click to collapse
You're welcome. What you need is here:
http://nasirtech.blogspot.com/2014/04/i545vrufnc5-android-442-kitkat-firmware.html
Or a 100 other places, but that one came up first.
I also find it best to factory reset after the update for best results.
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.....