Error 402 when taking OTA to 4.4.2 - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Hello, I am currently running MJE on my Verizon Galaxy Note 3 (rooted with Root De La Vega). Currently, I have SuperSU set to survival mode as I want to take the OTA update to 4.4.2. But every time I take the update, my device restarts and the update gives an error while it's attempting to upgrade. It then restarts and tells me that it failed to upgrade with error 402.
What I've Done:
Unfrozen all frozen apps within Titanium Backup
Used Wanam Xposed to set system status to "Official"
Set SuperSU to "Survival Mode" and disabled SuperUser
I'm not sure where to go next, as I don't want to have to remove everything from my device and start fresh again (I've already had to do that before!!). What should I do so that I can take OTA and keep my root status?

computerlife22 said:
Hello, I am currently running MJE on my Verizon Galaxy Note 3 (rooted with Root De La Vega). Currently, I have SuperSU set to survival mode as I want to take the OTA update to 4.4.2. But every time I take the update, my device restarts and the update gives an error while it's attempting to upgrade. It then restarts and tells me that it failed to upgrade with error 402.
What I've Done:
Unfrozen all frozen apps within Titanium Backup
Used Wanam Xposed to set system status to "Official"
Set SuperSU to "Survival Mode" and disabled SuperUser
I'm not sure where to go next, as I don't want to have to remove everything from my device and start fresh again (I've already had to do that before!!). What should I do so that I can take OTA and keep my root status?
Click to expand...
Click to collapse
Did you ever install Safe Strap? If so, you can not use the OTA.
Sent from my Note 3 via Tapatalk

I had something similar happen. Rooted with kingo, installed safestrap, used tibu to freeze every updater possible. Then was going to take the OTA did exactly as you did error message and all. I finally had to odin back to stock with the 4.3 tar file. I didn't reroot and just took the OTA after that.
Sent from my SM-N900V using XDA Free mobile app

Is there anyone out there that was able to overcome the update failed without going back to stock first?

I had the same message but when I tried to flash stock back to it Odin and the computer won't recognize it

Related

Update keeps failing?

I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
shizumie said:
I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
Click to expand...
Click to collapse
Any modifications to system will usually cause the update to fail. Xposed and wanam can cause the update to not work. You can download and odin the update and then re-root with kingo. This thread might help http://forum.xda-developers.com/showthread.php?t=2483380
shizumie said:
I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
Click to expand...
Click to collapse
This is what I did. Rooted phone with Dela Vega. Left stock rom clean no mods, no safe strap , no rooted applications except SuperSu. Disabled SuperSu , enabled survivor mode. Took OTA. Disabled survivor mode enabled SuperSu.
Sent from my SM-N900V using Tapatalk
Thanks guy's.
I had read that after root ota would fail because system showed not stock, and that you had to use Xposed and wanam to change the system to look stock.
I will oden back to mi9 and try again, without doing anything but rooting, and using su to save root.
Thanks again, and ill post back tomorrow my findings.
Ok, So i Odin'd back to mi9, re did (de la vega), after root, updated SU hid and protected it. Took the ota. After OTA re-enabled SU, installed safestrap. and all is well.
Thanks for the help, and direction guys.

Issues taking OTA on ATT G2, stock recovery

So I just tried to take an OTA and it gave me an error on the install screen then rebooted. Upon restart it gave me a message saying my device was suspected of rooting and that no OTA will be taken. All I've done is root, install root Explorer and titanium and hidden a few apps. Recovery is stock so I'm on the stock ROM. I really have no use for root so I don't mind if I lose it.
Should I just uninstall superuser or do I need a factory reset before I can take an OTA?
I have AT&T G2 rooted and stock recovery. I took the OTA update and all went fine and I didn't lose root either. All good on this end other than not knowing what was in the update.
EDIT: I now know what was in the update lol! A quick google search usually answers most question

OTA fails on rooted d802

I have a rooted d802 on 4.2.2 (80210e-eur-xx).
When I try to install the update it attempts to install, then gives an error code in the "please don't turn off your phone during update" screen and reboots, telling me that it suspects root and can't install the update
I was under the impression that this should work and specifically chose Ota to keep root with the survival mode
seth4u said:
I have a rooted d802 on 4.2.2 (80210e-eur-xx).
When I try to install the update it attempts to install, then gives an error code in the "please don't turn off your phone during update" screen and reboots, telling me that it suspects root and can't install the update
I was under the impression that this should work and specifically chose Ota to keep root with the survival mode
Click to expand...
Click to collapse
Experienced the same issue. i had to flash my phone back to original firmware and do the OTA update. Flashing removed the root and enabled me to OTA kitkat upgrade.
seth4u said:
I have a rooted d802 on 4.2.2 (80210e-eur-xx).
When I try to install the update it attempts to install, then gives an error code in the "please don't turn off your phone during update" screen and reboots, telling me that it suspects root and can't install the update
I was under the impression that this should work and specifically chose Ota to keep root with the survival mode
Click to expand...
Click to collapse
If you have modified anything like removing/freezing bloatware, xposed framework, or modified anything in the system it will suspect your phone of rooting
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

[Q] some issues unrooting and ota update

So I deleted SU off of bin, xbin, and apk. deleted xgel and what not checked root checker and verified i had no root access. tried installing ota lolipop and got a script error status 7, then next time error in cache where the update was. then tried odin flashing stock software. that failed.
attatched pictures of my problems. we want to put my g.fs back to stock due to her upgrade next month.
thoughts?

Keeping root after OTA update?

Hi
I have Android 5.1.1 running with root on my Nexus 4 (using Nexus Root tool kit)
So there's a stock recovery installed.
There's Superuser installed.
There's an update waiting to be installed and I would like to keep the root or be able to root without losing data.
My phone has bootloader unlocked. And SU app installed.
Cheers
Sent from my Nexus 4 using Tapatalk
I don't remember if you need to be unrooted or not, but you can just try to see if it works rooted first. If it doesn't you can unroot your phone by going to settings in the SuperSU app. To reroot after that just flash the SuperSU zip.
EDIT: You can get the zip from this thread: http://forum.xda-developers.com/showthread.php?t=1538053
Hi again
So I tried to apply the OTA update and it restarted and started to install the update and it gave me an error in the midway with a red exclamation () mark in the androids stomach.
So I pressed power + Vol up button and restarted my phone using the menu.
I thought it was probably because of the root. So I went to SUPER SU app and Uninstalled it (un rooted). Restarted and SUPERSU was gone.
After a while the update came back. And I applied it again. And this time the same error.
So I pressed power + Vol up again and checked the log and it says that /cache/update.zip has unexpected contents.
Anyone got any idea why is this happening?
This time I've formatted cache. And so far (5 mins) no update Notification yet.
Looking forward to your help.
Cheers
Sent from my Nexus 4 using Tapatalk
You can't have an amended /system partition to use the OTA with 5.0+. Even uninstalling SU will not work. If you want to use the OTA Process, you will need to flash the factory /system image, which will cause you to lose root (and is sort of redundant in light of the fact you can just extract the updated system.img file from the latest Factory Image and just flash that to upgrade to it). That said, it only takes a minute to root so would suggest just making sure you are comfortable with the process as opposed to trying to preserve root.
Thanks.
Sent from my Nexus 4 using Tapatalk

Categories

Resources