Those who are stucked at OTA manual lollipop update for D800 (for those who tried http://forum.xda-developers.com/lg-g2/general/dlpkgfile-lg-g2-att-lollipop-file-t3082867 and failed on the update screen (err 0x1111004) - credits to @Zero4 )
First you have to go back to D80020C and then to D80020Y and then to the lollipop
I made a silly mistake by not flashing D800Y and going straight from D80020C to lollipop. This way the OTA lollipop will work without err 1111004
Kasvinda said:
Those who are stucked at OTA manual lollipop update for D800 (for those who tried http://forum.xda-developers.com/lg-g2/general/dlpkgfile-lg-g2-att-lollipop-file-t3082867 and failed on the update screen (err 0x1111004) - credits to @Zero4 )
First you have to go back to D80020C and then to D80020Y and then to the lollipop
I made a silly mistake by not flashing D800Y and going straight from D80020C to lollipop. This way the OTA lollipop will work without err 1111004
Click to expand...
Click to collapse
Do you know if I can go from D80020k to D80020Y? I tried manual OTA from D80020k to D80020U and it gave me that error code. I'm debating whether it's worth it to go back to D80020C, which mean everything will be wiped.
Apparently your stucked. Even i couldnt find an answer to that problem. I recommend to backup everything. Just once in a life time do it. I did it too.
I were also facing similar issues with my LG-F320K and the issue was due to ROOTED device.
I simply unrooted and attempted to update my phone and it goes smoothly without any issue.
Afterward re-rooted my phone and it seems all doing great
Related
I have installed gohma 2.3 custom rom with twrp recovery and root and have taken gohma-gwatch-1.2 to get back 4.4 stock with stock recovery and unroot.
After that I clear all inside the recovery to have a fresh stock without old data. I got the setup and the paring to the phone and after I check for an update the lg told me that one is available and start the download.
After it was finished the watch boot into the recovery and start the flash but aborth with an error 7 message
Can anyone explain me why? After I start the watch again the update told me that 4.4 is latest and there is no update available.
The OTA is from 4.4 to 5.0.2 but now I dont get 5.0.1 like before. Another watch work fine with this method but why this one not? Andy ideas please
Same issue here. Returned to stock on 5.01 and when upgrading to 5.02 I get that error 7. Tried everything, wiped several times but no way to install.
thats strange because my own watch work fine with the downgrade and changing the recovery back to 4.4 stock. My dad can use the watch with 4.4 but I dont understand this :crying:
Solved. Used RootJunky v8 to go back to stock 4.4 and then flashed OTA 5.02. Worked.
http://www.rootjunky.com/download/LG G Watch/Script Super Tools/LG G Watch Restore Tools V8.zip
but I cannot extract without crc error :crying: can you please do a mirror for me?
Javierinnn said:
Solved. Used RootJunky v8 to go back to stock 4.4 and then flashed OTA 5.02. Worked.
Click to expand...
Click to collapse
Thank you sir :highfive: , you just saved my LG G Smartwatch!!! i wasn't able to update to smartwatch to the newest android wear 5.0.2 update without getting error 7 on recovery, i was using the LG G watch restore tool v9.5 to restore my watch and kept getting the Error 7 when trying to update, so i stumbled upon this forum and decided to use the v8 of the tool instead of the v9.5 and it worked perfect, i was able to update my watch to 5.0.2 without any errors :victory: i will share this news with other users that are in the same boat as i was and will give you the credit bro... awesome find really!!!
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?!
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.
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!
My friend has a verizon LG G3. It is currently running 5.1.1 lollipop 35b. It was having a bunch of random reboots, we put in a new battery and the reboots stopped. The phone is working fine, except it keeps downloading the 46a 6.0 marshmallow update, but when it reboots to install, it gets to 2% and says error and reboots and I am back in 5.1.1 lollipop still. I checked software status, and it said "official" and I even used the Lg upgrade and repair assistant from verizon and chose to repair, which downloaded a 1.64 gb file (the 35b software kdz I'm pretty sure) and flashed it to the phone. I have also used lg flash tool 2014 to flash the 35b kdz. It always flashes the 35b kdz just fine, but still fails to take the marshmallow update.
I don't need root. All I'm trying to do is get from stock 35b lollipop to 46a marshmallow since it keeps failing. Since it didn't work even after successfully flashing the kdz, do I have to go all the way back to 10b and then just take a bunch of software updates ota until I get to 46a? I helped her get this phone on ebay, and it wasn't rooted when we got it, but for some reason it just won't take the update.
I understand there is no 46a kdz available right? I have been reading around about downgrading to 10b and whatnot here on xda, but I would prefer to not have to go through all that extra hassle if I don't have to. I don't need root, just need to update.
Any tips / ideas would be great! thanks.
steven_computer_guy said:
Since it didn't work even after successfully flashing the kdz, do I have to go all the way back to 10b and then just take a bunch of software updates ota until I get to 46a?
Click to expand...
Click to collapse
I doubt if that would make any difference - OTAing to 35B gets you the same thing as flashing the 35B KDZ, but this is such a weird problem, I don't know... Try it and let us know.
You could try any extra factory reset even though flushing the KDZ with the official tool does that.
The only other thing I can think of is to try taking the OTA without the Micro SD card in.
I understand there is no 46a kdz available right?
Click to expand...
Click to collapse
Correct, haven't seen it. The tool you used should've downloaded the 46A KDZ if it had been available.