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.
Related
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'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
cfales25 said:
I'm new to developing and not too experienced. I attempted to root my phone, but was only successful with unlocking the Boot loader. When I attempted to download the new Kit-Kat update, my phone encountered a Firmware upgrade issue. Now in recovery mode, Kies 3 fails to connect nor recognize my phone.
Click to expand...
Click to collapse
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
es0tericcha0s said:
Bah. Kies sucks. Odin is a much better tool for updating / fixing things. What update were you on, as it is important to know the actual build version as well because there are often mini updates that keep the same android version but update other things that can cause a headache if not rooted or modified properly. Also, are you sure it was the bootloader that you unlocked? There is the Loki option and SafeStrap recovery, but not a way to unlock the bootloader unless you have a Dev Edition. I think you had to go to 4.3 before 4.4.2 too. What part did it get to before it failed and you got the error message? If you're lucky, it didn't actually do anything important before it failed, because then you can use Odin to install the original system update you did have then restart from there. If not, then you will need to go to 4.3, then 4.4.2. Once you update to 4.3 and above, your only options for custom roms are via the SafeStrap recovery which has some serious limitations.
Click to expand...
Click to collapse
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
cfales25 said:
I tried to gain root access awhile ago, it showed that my bootloader was unlocked, but I don't recall ever gaining root access, so I left it alone and figured I was just gonna wait for Kitkat. It's weird what is happening to my phone now. It just says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." After trying Kies Lite and normal both versions 1 & Kies 3, my phone won't even be read nor connect to Kies anymore. It won't show up in Odin. I have tried fully uninstalling all the Samsung programs on my computer then redownloading and installing them and still no luck. I really don't know what else to do. Should I just take my phone into Verizon and try my luck?
Click to expand...
Click to collapse
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
es0tericcha0s said:
The chance of finding someone at VZW who could fix this is pretty slim. But the open lock graphic that shows up when you first boot the phone does not imply the bootloader is unlocked on Galaxy phones, unlike say, a Nexus. It just means that something has been done to trip the custom binary check. If you tell me what update you were on, I can tell you how to fix your phone, or if you don't know, then you just need to follow this :
http://forum.xda-developers.com/showthread.php?t=2578209
It should show up in Odin. Not when it has the warning like that, but when you boot to Download Mode. I've bricked plenty of Galaxies like that and have been able to recover every one.
Click to expand...
Click to collapse
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
cfales25 said:
Ok. Thanks, man. I was running on 4.3. My laptop runs Ubuntu, is Odin compatible with this software?
Click to expand...
Click to collapse
You'll either need to use Heimdall or the http://casual-dev.com/2014/01/04/jodin3-web-browser-or-offline-flashing-tool/
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 have a SCH I545 (verizon s4) and i am currently running kit kat 4.4.2 version vrufnk4 with kernal version 3.4.0. I was once rooted but i am no longer rooted and as far as i know everything is stock except the recovery which seems to be different than what i remember was on the phone from factory. The phone also boots with a logo saying custom with an unlocked pad lock. The recovery says android system recovery <3e> at the top and in the middle is an android dude with a red triangle on him and under him it says no command . I had cwm recovery on the device when i was rooting it but don't remember if i got rid of it or left it but i don't believe this is cwm recovery or the factory recovery. But here is my issue, i wanted to update to the new lollipop via the OTA update verizon has issued for my phone and the update came in 2 parts the first part upgraded kit kat to vrufnk4 and the 2nd update was suppose to be the actual lollipop update. The first update to vrufnk4 did fine but when i try the 2nd update to lollipop GOC1 i believe is what it is the instal fails every time. I did try a factory reset via the boot recovery but that did not help.
Thanks for any help you can give me I'm so lost as to what to do to fix this and i just want lollipop on my phone for now possibly root the phone later if i get bored until i can get a s6 edge.
Did you ever get an exact answer? I'm in the exact same situation and don't want to brick my phone. Thanks... back to searching.
I figured it out l. When you plug you phone into your computer there is a Verizon update that pops up you will need to update your phone using that and it will work like a charm. But it's like Verizon updater or something I can't remember but it pops up when you plug your phone in or it did for me. Hope that helps!