Now Available!! 5.0.1!!!
Go get your lollipop ON!!!
Hopefully this will result in some bugs squashed with CM12. I am hoping for a better modem and better Bluetooth.
Queuing up downloads now, I have two of them pending for my device
are you able to capture the updates
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
you could try taking it, then flashing the nc5 kernel through odin, and then (if someone's able to do this) get the kernel from nk4 and flash that
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
How many updates are there? What does it mean 1st update? are there more updates?
meazz1 said:
How many updates are there? What does it mean 1st update? are there more updates?
Click to expand...
Click to collapse
apparently this is a 2-part update
part 1 is a build where the last three characters are NK4. this is a kitkat ROM that was likely used to prepare for lollipop
part 2 is the actual lollipop build, OC1. i think it's 5.0.1 but i'm seeing conflicting things from the internet
for some reason verizon likes doing major updates this way (i dont think they did it for jelly bean to kitkat though). but i've had a few of their phones, they've been doing two-part updates since the original galaxy s in 2010 lol
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
gsmitchell said:
Hey everyone! Has anyone solved the mystery of the lollipop update fail? Seems alot of us are getting the first update without any issues, but the lollipop update is failing. It gives error 402, which one person at Vz told me was an error thrown due to having root. ( I don't have root ) Any suggestions appreciated!
Click to expand...
Click to collapse
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
muniz_ri said:
Can someone that has taken the OC1 ota update test to see if the 4.4.2 kernel has been blacklisted by:
1. Flash the I545_NK4_Stock_Kernel.tar.md5 using Odin. The device will not boot after flashing but we are just interested to see if the kernel will successfully flash.
2. To go back to normal flash the I545_OC1_Stock_Kernel.tar.md5 also in Odin.
This is the first test to determine if a downgrade workaround will be available for those that took the OC1 ota update.
Click to expand...
Click to collapse
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Is there a stock Odin TAR for this yet?
xdabens said:
Nope, it fails to flash
Here is the short log from the screen:
Code:
START [224, 1440]
SYS REV CHECK FAIL[K] : Refer 1 > Binary 0
SECURE MAGICCODE CHECK FAIL : boot
Click to expand...
Click to collapse
Not good. The 4.4.2 kernel has been blacklisted. Thx for testing.
Successful update (in two part harmony) yesterday. Stock system. Fox-Fi still works over Wi-Fi so I'm happy. No issues except 2nd update took a loooonngg time on the red Verizon screen. Make sure your battery is full or you are plugged in. No comments on battery life as I've been able to stay charged today. Getting used to it.
Hey everyone! If you getting the 402 Error, there is a thread that might have the fix. Go to the Error 402 when updating to Lolipop? thread. I am going to try it when I get home tonight.
dgutierrez04 said:
I was able to capture the first update because im rooted. But i dont want to lose it if i update it. I hope the developers can find a way to keep root for the first update. if they can. I will happily capture the second update to get lollipop.
http://forum.xda-developers.com/showpost.php?p=60435732&postcount=54
Click to expand...
Click to collapse
Thanks! Muniz_ri mentioned that you also captured the OC1 OTA package. I searched a lot but did not find it. Could you provide the link? Thanks again!
danielzink said:
My update is failing as well.
I've wiped cache in recovery, wiped data and cache in download manager...
Still fails.
I was rooted at one time - not rooted anymore.
I do still get the "custom" boot screen with the padlock though...
Click to expand...
Click to collapse
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Sent from my SCH-I545 using XDA Free mobile app
People getting tthe 40 error did you at one time have safestrap installed? ??
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
I've always found taking out sd card then a fresh Odin back to stock then doing my updates lead me to a flawless update process every time
Guys I'm on NC5 only rooted by towelroot what do I do please?!
Related
I have a S4 ME7. I was stupid and accepted the most recent OTA update. While update was installing I got an error. Now the update is constantly asking for permission to install and it always gets the same error result. I get a message that states no changes made to the phone, but when I look at the Build number and Baseband version, it now says VRUDMI1. I don't want to lose root and I certainly don't want to brick my phone. How can I get past this problem?
There is some way to disable OTA updates. Just Google around. I read somewhere in xda.
Sent from my Nexus 7 using xda app-developers app
keb8880 said:
I have a S4 ME7. I was stupid and accepted the most recent OTA update. While update was installing I got an error. Now the update is constantly asking for permission to install and it always gets the same error result. I get a message that states no changes made to the phone, but when I look at the Build number and Baseband version, it now says VRUDMI1. I don't want to lose root and I certainly don't want to brick my phone. How can I get past this problem?
Click to expand...
Click to collapse
MI1 is fine.
You can flash MI1 with ODIN and the use the root_de_la_vega methond to get root back.
I had the same issue. Now on MI1.
The only problem is if you want to run safestrap.
tech_head said:
MI1 is fine.
You can flash MI1 with ODIN and the use the root_de_la_vega methond to get root back.
I had the same issue. Now on MI1.
The only problem is if you want to run safestrap.
Click to expand...
Click to collapse
Sounds good. Only problem is I have never used Odin and I don't know how to do what you are suggesting. If I can get a little instruction, I am willing to give it a try.
keb8880 said:
Sounds good. Only problem is I have never used Odin and I don't know how to do what you are suggesting. If I can get a little instruction, I am willing to give it a try.
Click to expand...
Click to collapse
There are YouTube videos for every step of the way for the project. I used the ones by Tomsgt123. http://forum.xda-developers.com/showthread.php?t=2337590
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
tuningmode said:
I was searching to see if anyone else was having issues, but couldn't find any. I finally decided to turn the update off for the Verizon update, but it keeps saying unsuccessful and I'm assuming because the phone is rooted at the moment. Is there a way for me to install the mk2 update?
Click to expand...
Click to collapse
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
k1mu said:
Nope, it'll install even though you're rooted, but you need to restore anything you've modified before the OTA will work - or at least any files that the OTA is trying to upgrade.
Click to expand...
Click to collapse
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
tuningmode said:
my guess is maybe the wifi tether, I was attempting to get it to work and there was a file or something to overwrite through a script from one of the threads I was reading. Could that be it?
Click to expand...
Click to collapse
Very likely the tether - it changes the framework, doesn't it? That's very likely to be updated by the OTA.
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Mz8691 said:
Yeah, i have the same issues.. When i download the update ( I'm on MJ7 Rooted) it says please install, i click okay. It reboots it goes into the recovery, tries to update but shows a Error Android image, Restarts, then displays this message saying Error Phone couldn't update nothing was effected or something like that.What's the issue?! i wanna update / root because this message for the update pops up every damn day and it's so annoying! Please help me.
Click to expand...
Click to collapse
Flash the MJ7 no-wipe ROM that you'll find in the Android Development forum. That will restore all of the stock files that you should need (and also cause you to lose root.)Then, update to MK2 and re-root.
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.
Okay here's my tale of woe..
I rooted my phone last year - but at some point - took an update and lost root.
Though the phone still displays the "custom" boot screen with the padlock.
I tried to take the Lollipop update through the OTA but it fails and I get the "laying on his back" failed Android dude...
The phone DID take the first update.
I have: wiped cache in recovery, wiped data and cache in download manager.
No luck.
I have tried loading the NC5 kernel back on (via Odin 3.09) - but that makes the phone 100% unstable...reboots every 3 minutes..no access to apps - they lock and reboot etc etc.
Loaded the NG6 kernel back on to re-stabilize the phone and tried to Kies the update.
Kies downloads the update then when it tries to apply it the phone boots into "download mode"
I have been advised to:
I had the same custom boot screen--even after unrooting. Tried using Triangle Away to reset the binary count, but the count was already at 0. So ultimately I had to re-flash the NC5 kernel via Odin to get things truly back to being recognized as stock.
Then updates started rolling in for NG6, then NK1. Finally the two-part update for Lollipop.
Click to expand...
Click to collapse
and - of course that doesn't work. NC5 won't let the phone run long enough to take an update..
It has been said:
Try to flash the OC1 with the pit file
Click to expand...
Click to collapse
But I haven't found the stock OC1 file anywhere to even try and begin to get it loaded.
Honestly - I'm not even really concerned about rooting right now. I'd really just like to get the phone back to a stock configuration and kernel and lollipop.
Developer mode is enabled. Obviously both Kies and Odin talk to the phone with no problems.
Any ideas ?
Thanks, Dan
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Yes.
Maybe I need to clarify.
I do not care about root at this point. I just want to get the phone back to a stock state and take the Lollipop update.
I'm curious as to why I will never be able to update beyond Lollipop.
Doesn't matter I guess - the phone will have been replaced by then - but still...why ?
Thanks, Dan
CyrusKhane said:
Get your phone to 4.4.2, use the verizon software upgrade assistant program preloaded on your phone to update. I had this exact same problem and that's how I got to 5.0.1
You WILL lose root. And there's no method to root 5.0 right now, and people have been saying that there might never be. You also won't be able to downgrade, or at least there's no method to do so at the moment, so you will be stuck with lollipop for a while, maybe forever.
Click to expand...
Click to collapse
I've downloaded (3) different 4.4.2 Firmwares.
FNK1
FNC5 (No Wipe)
FNG6 (No Wipe)
Any opinion on which one is best ?
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
I would use the ng6. That's what I was running.
Rip Syntaxx said:
Did you download these manually or OTA? When I re-flashed the NC5 kernel, I received NG6 then NK1 then the 2-part Lollipop updates all OTA back-to-back.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Manually - from these (XDA) forums.
danielzink said:
Manually - from these (XDA) forums.
Click to expand...
Click to collapse
Hmm... I'm not sure if it makes a difference to download OTA instead of manually. I would think it's worth a shot flashing NC5 (if it will let you downgrade) and using the software update feature to update OTA the rest of the way.
Sent from my SCH-I545 using XDA Free mobile app
Got it finally !
started out by flashing (FNG6 (No Wipe)) in Odin 3.09
That got me to regular boots with no "custom" screen showing the lock symbol.
Then I had to take OTA updates to FNK1 then the OTA preliminary Lollipop update then (OTA) finally Lollipop itself.
No root - but that's OK.
It took about an hour and a couple shutdowns to get things running smoothly but it's all good now.
Thanks everyone for their help.
Hello Everyone,
I'm a first time poster but have been reading this site for weeks trying to find the answer to my questions. I've acquired a good bit of info but still wanted to clarify some things before I take the plunge.
I'm currently using a Verizon GS4 (I-545) running rooted stock MK2 jellybean. I rooted ~2 years ago to get rid of the bloatware and just never bothered upgrading/keeping up with the firmware updates. There are some new apps that won't work on my phone, but are working on my wife's stock GS4 on OF1. I'd like to upgrade my firmware (and keep root) so that I don't have to keep stealing her phone.
I've come across several threads discussing upgrading from one baseband to the next - none quite match my scenario. Most threads talk about how to upgrade and keep root but now that I'm late to the party, it seems like root methods have been discovered for all stock firmware versions (even OF1 by flashing OC1 kernel, rooting, and flashing back to OF1 kernel). So with this in mind, can I just skip all the complicated stuff and just use Odin to flash OF1 and then follow Edgardo_Uchicha's OF1 root method?
If I can use Odin to flash OF1, will the file I load in the "AP" slot also includes the proper modules, bootloaders, etc. to upgrade everything to OF1? Will it do a factory reset/wipe or will I keep all my data like an OTA? As for getting the Odin file, it looks like I should just use the Samsung site to get it directly?
If I can use the Odin method, are there any drawbacks? If I don't like lollipop I realize I'm stuck and can't go back, but is there anyway to upgrade and be able to go back (downgrade)?
Thanks again for your help!
Mike
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Edgardo_Uchiha said:
Hello Mike,
You can flash OF1 and root via the method others and I posted, some people wrote that other rooting software/apps are starting to work on lollipop builds, I haven't tested yet(since my device have a custom rom and it's rooted) but soon I will and will update the thread. Btw, my suggestion to you is flashing this specific odin package:
[Odin][TAR] I545VRUGOF1 neutered (No BL)
I was on kitkat bootloader, flashed this OF1 build and went back to kitkat without problems
Good luck!
Click to expand...
Click to collapse
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
mike2914 said:
So I followed the thread you linked and it looked like my phone upgraded OK. However, even at lock screen I get the message "Unfortunately, the process com.android.phone has stopped". It reappears as soon as I dismiss it...basically making my phone useless. I was able to navigate to the Settings page though and it says I'm on 5.0.1 but under baseband it says "Unknown" rather than OF1. It does show OF1 under the build number though. I'm guessing it didn't like the MK2 bootloader?
Any ideas how to fix? Help!!
Click to expand...
Click to collapse
Try wiping via recovery, if I'm not wrong this package does not wipe your phone so maybe there are some leftovers that are messing up the new system
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
mike2914 said:
You are correct, the OF1 Odin file you recommended did not wipe my data/apps. You were also correct in that doing a factory reset/wipe fixed the issue. I had some apps that were previously "frozen/disabled" while I had root so I have a feeling that didn't help things when it got updated.
Is there any way to confirm that I still have the MK2 bootloader?
Click to expand...
Click to collapse
Download and install terminal emulator, the run these commands:
1. su
2. getprop ro.bootloader
Awesome! I was able to confirm I'm still using the MK2 bootloader. Thanks for all your help!