Database Develop

[HELP] OTA KitKat update error on rooted D950

I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium

Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload

Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.

lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app

brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.

lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app

Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD

KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?

santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.

[Q] Get rid of update popup?

Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!

daniel178 said:
Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-g2/general/how-stop-ota-pop-rooted-device-t2885667

Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?

daniel178 said:
Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?
Click to expand...
Click to collapse
I did not unroot to update and retained root after the update... If you lose root, I heard stump root will root 26a.
Sent from my Xposed G2

my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2

somnambulator said:
my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2
Click to expand...
Click to collapse
That is correct.

Help! Accidentally clicked on the update button that popped up and have root
I do have my phone rooted, but as stated above, the update software pop up box kept popping up and I accidentally clicked on the update button. My phone went into the twrp backup screen where I was told the only thing I could do was revert back to a previously saved backup. I tried this and now I can't even get my phone to turn on. If I hold the power and volume down buttons at the same time I just get vibration from the phone but the screen doesn't turn on. When I plug the phone in, it displays the LG start up display and nothing else, it will stay on that display even when I unplug then... So the big question, can I save my phone? I had a buddy do the roots am unaware of how to save it. Thanks for the replies in advance.

[Q] S5 Stuck at Boot Animation With Blue LED After Stock Flash

I searched and found nothing exactly like what I was experiencing and nothing I hadn't already tried. Hopefully someone has seen this before. I HAD a nice rooted stock SM-G900A 4.4.4 and now I have a flashy gold brick (soft). I rooted by downgrading the kernel to use towelroot then flashed stock kernel back. Everything worked fine for about a week or so. I'm not sure at what point I started having issues exactly so I'm not sure if an app or mild mod could have caused my issues. The only thing I had done was use SuperSU to block Knox and change the terrible TW stock sounds to standard ogg clicks and what not. The trouble started with the camera. I opened my camera and the screen would flash green then I would have red ghost images in a pattern on the screen. The pictures I took had the same effect when viewed in the gallery. If I switched modes the problem would go away with the camera until I closed then opened the camera app again so I assumed it was a software rather than hardware problem. I couldn't find any info on a fix so I did a factory reset. The problem persisted. I decided finally to flash back to stock. That's when it really got bad. After flashing to stock the phone will boot to the Samsung animation with the swoosh, freeze there for a few seconds without completing the boot animation then the screen shuts off and the phone becomes unresponsive. The only signs of life is the blue LED is constant lit. I have to do a battery pull to start over. I have flashed just the PDA and I have flashed the whole shootin match (except for BL) and I get the same results. I have tried stock tar files from a couple different sources. It will go into download mode as well as stock recovery where I tried a factory reset after flashing. PLEASE HELP!

So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.

Acer904 said:
So I flashed OA1 stock kernel and got it to boot. Of course now I get the Update interrupted message when I try for the OTA to anything newer than the 4.4.2 it's running. And after 8 hours of messing with this gem the camera issue persists.
Click to expand...
Click to collapse
Go here and flash back to NCE. Then take the OTAs.
http://forum.xda-developers.com/showthread.php?p=60012961
Sent from my SAMSUNG-SM-G900A

That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.

Acer904 said:
That is what I ended up doing just an hour before your reply and all is well again. I suppose my first attempt to go back to NCE didn't work because I didn't use the downgrade flash, just a regular 4.4.2 stock. There must be a difference between the two. The OTAs still wouldn't work so I ended up installing the updates from external sd. The lollipop OTA is downloading fine though. Thanks for confirming I FINALLY went the right route. This root screw up wasn't as bad as my last (efs S3 debacle) but it still took too many hours to fix.
Click to expand...
Click to collapse
If you take the 5.0 ota you won't be able to root. Just FYI. There is no root for it yet. There is a pay however in the general section on how to upgrade to 5.0 and keep root.

SM-G870A stuck at logo

I'm currently stuck at the s5 active logo screen and then it boots into recovery. I've tried flashing the full odin.rar (yes I extracted it) and it fails everytime. I get the message "Sw REV CHeck Fail: [aboot]Fused 2> Binary 1. I've already tried wiping the data from the recovery menu. Nothing is working.

We need more info. What were you attempting to do and from what ROM. Are you sure you are using the proper ROM 900 or 870?

I was attempting to downgrade back to stock from 5.0 and hit the stock kernel instead of the firmware accidently when in odin. And yes I am absolutely sure i'm using the 870 rom.
Edit: What if I use a stock img and a PIT file for the phone? OR is it because I need a 5.0 lollipop firmware to flash through odin?
Edit number 2: okay I'm stupid, im on G870AUCU2BOF3. I'm going to have to reflash the of3 zip aren't I?

Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.

if you loaded the 2400258.cfg you probably loaded the OF3 bootloader as well and now you can't go back. No root at this time and it doesn't look good for the future.

Cloudsdabomb said:
Okay so I found the OF3 cfg on another thread and was able to load it and flash it and get my phone working! Now, the next question is can I root in my situation or downgrade or am I just stuck?
Edit: Going to wait for a possible root! Mod can close this thread.
Click to expand...
Click to collapse
At command prompt type without the qoutes.
"getprop ro.bootloader"
Then paste output.
Sent from my SAMSUNG-SM-G870A using Tapatalk

If you took the of3 ota or are otherwise on the of3 bootloader your stuck there....no downgrade or root as of this time.

Me too
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again

pgross41 said:
I am in a similar situation. Saturday I was on a rooted 4.4.2, flashed a stock unrooted 4.4.2 with Odin (G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5), let AT&T update me to 4.4.4, installed the old kernel with Odin (G870A_NE4_Stock_Kernel.tar.md5), rooted with towelroot, installed the new kernel with Odin (G870A_OA1_Stock_Kernel.tar.md5), updated to 5.0 with Odin and it retained root. However, certain things such as XPosed didn't work and I really really hated the white notification drawer so I just want to go back. I tried flashing the stock 4.4.2 in Odin again and it said success. It restarts and seems to be working but gets stuck on the AT&T logo. Now if I restart it always sticks on the AT&T logo even when I flash again. I don't know what else to try. A different file? Is there a way to go back to KitKat?
Update: I got into recovery mode (I kept trying vol up, vol down, power but it's actually vol up, home, power). I wiped the cache and did a data reset and restarted the phone. It worked! I'm excited to have a black notification screen again
Click to expand...
Click to collapse
How long did you have to wait for your phone to boot all the way up from the ATT logo? Mine is doing exactly the same thing and I've flashed all kinds of kernels via odin and heimdall with no affect. None of the various fixes I've found have helped, including trying to re-apply the OTA file (system just won't do it). All I wanted was to unroot. Awesome.

The first boot can take a while but if it lasts more than 10 minutes it's probably not going to happen. I've gotten it stuck there twice since my last post and I'm always able to salvage it by going into recovery mode (vol up, home, power while powered off). Wipe the cache and data reset and it should be a fresh start like out of the box new.

Hm. So the only real two options are take it in to AT&T and hope they have the full stock G870AUCU2BOF3 image to flash over (since Samsung locked down their bootloader so hard, so downgrading is impossible :good: ) or hope they release G870AUCU2BOF3 on SamMobile/Kies/Smart Switch. This is like the new hard brick... potentially it's salvageable but the company (I'm guessing AT&T here since this is an AT&T exclusive phone) is just screwing us. Guess I'll try the walk of shame to AT&T. Or maybe putting in a claim like that one person did, get a whole new phone because of a mysterious cut on the rear panel seal...

Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.

retro486 said:
Alright, took it in to AT&T and sure enough they had the full 5.0 image available so after signing a no-return data waiver (didn't even confirm my AT&T account or ask for any ID) the tech took my phone in the back and flashed it back to stock. First boot still showed the "custom" with unlocked padlock on the boot screen but after I rebooted it, I guess it updated the bootloader because it was back to normal.
No more root and he confirmed there's no way to go back to 4.4 once you go up to 5.0, so if you want root, I'd suggest staying away from 5.0. At least now I can use my phone again. Just thought I'd post this up in case anyone wasn't sure if AT&T would actually be able to reflash stock 5.0 and at the very least get your phone working again... enough to put on ebay and get a Moto or some other brand that doesn't lock down the bootloader so hard.
Edit: note the first boot will take a few minutes but I knew it worked when there was a quick vibe and the notification light went from pulsing blue to off. Maybe 4-5 minutes.
Click to expand...
Click to collapse
It's not Samsung that locks down the bootloader, it's AT&T. the T-Mobile Version doesn't have a locked bootloader and is easily rooted . Just have to SIM unlock it and you can use T-Mobile phone on AT&T network.

Delete

Need Update Advice (KitKat to Lollipop)

I currently have an LG-D415 running KitKat 4.4.2 that's rooted. I've never had a need to upgrade to Lollipop 5.0 until now. I just bought a new truck that has Android Auto which requires 5.0. My phone has been giving me a message that there's a system update available for quite a while now but I have been reluctant to do it because my phone is rooted and I'm not sure what would happen. Should I just let it do the update or do I need to unroot the phone first. It's been so long I'm not even sure what method I used to root the phone.

If you have rooted phone i recomend you installing latest twrp recovery and flashing lollipop ROM for lg l90d415. the stock ROM van ne found on t
his site

OTA update will fail if device is rooted. If you want to keep root enabled, then follow lgl90 suggestion. If you remove root to update it may work but you will have to root again. A backup is always a good move.

I'm kind of a novice at this so I'm looking for the most painless method of getting Lollipop. I'm not sure I'm comfortable installing twrp and flashing the rom. Also, I've read the bootloader needs to be unlocked which it isn't. Can I use SuperSu to unroot, let the OTA update do its thing and then reroot?

the bootloader is unlocke by deafult on lg l90d415 all you habe to do is download flashify app from play store download the latest twrp for d415 and wipe system,dalvikcache and cache the flash te lollipop stock tom by going to install and chouse the rom file where you have downloaded it inernal or external sd card and the swipe to flash the firsr boot will take maximaly 5-10 minuts .. lollipop is waaay diferent than the kitkat thats why will take to boot longer

So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?

zippster1 said:
So I unrooted the phone downloaded the OTA update and tried installing it. It made it halfway through then the phone restarted without completing the update. The phone is still at 4.4.2 and I no longer get any message to update. When I check for updates it thinks its up to date. When I tried manually updating using the LG Mobile Support Tool it initially said an update was available then changed to the phone is up to date. Why does it think the phone is up to date when obviously it's not?
Click to expand...
Click to collapse
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff

lgl90 said:
HI i told you what is the best solution to update your phone.. you could successfuly hard brick your phone(why did it not update well you didnt had enough of battery life) do what i told you so the best solution is to download the official lollipop rom for lg l90 d415 its same stock rom from lg but it comes pre rooted and all of that good stuff
Click to expand...
Click to collapse
zagreb - as I stated I'm a novice so I chose the path that I thought would be the easiest. My phone was fully charged so I do not believe that was the reason for the update not completing. Is there a thread or link you know of that provides a step by step (from beginning to end) tutorial of what you're proposing. Thanks for your help.