Database Info

[Q] Error 402 with 4.1.2 Update?

Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.

buckoman said:
Hi guys,
I'm a little new to posting on XDA itself, so I'm not quite sure if I'm in the right section, as I don't have my 10 posts yet. So apologies in advance. Move me where you need to.
Alrighty. I'm running 4.1.1 (stock firmware) and I've been getting notifications to update OTA since about a month ago. However, when I try to update, it stops in the middle of the update, restarts the phone, and gives me an error 402. Not quite sure what that means, though an old Verizon forums posts pointed to a corrupt file in the phone's software itself, preventing the update from happening. Aside from that, the phone's been a mite glitchy with home screen transitions, and it's eating up a bunch of my battery life (not going into deep sleep; overheating) when it hasn't done so in the past.
I don't want to give my phone back to Verizon and get a like-new one back, but that seems like it has been the only option I've been given. I've factory reset, cleared cache through recovery, and still no luck. The error 402 keeps happening when updating.
So my question lies here - What should I do? How can I fix this error? How can I update my phone? Or better yet, is there a ROM of the original ICS software (Day one of GS3 release on Verizon) that I can flash through Odin? Then I'd just log in with Google, and let the phone update for about three hours until I'm on current software, and it really wouldn't be susceptible to software corruption if I just let it update all the way through.
Anyone with a similar problem, or does anyone know what I should do?
Thanks, and hope you can help me with this.
Click to expand...
Click to collapse
Maybe just root(; lol and flash clean Rom stock 4.1.2
Sent from my SCH-I535 using Tapatalk 4 Beta

I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?

buckoman said:
I'd really like to avoid rooting at all costs. This phone's been great for me when it's unrooted, unlike my Droid2 which needed Liberty.
But other than that, any options that don't involve rooting?
Click to expand...
Click to collapse
Not unless you can remove the update and try again. Verizon soft bricked you. Don't know if you can remove the update file from memory and try to download again without root. Get a file explorer and look for the file. Not sure of name as I have only taken one OTA over all the years and it worked. If want to Odin the full MB1 update image is on SamMobile. If Odin that don't have to worry about OTA and will have same thing.

prdog1 said:
Not unless you can remove the update and try again. Verizon soft bricked you.
Click to expand...
Click to collapse
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?

buckoman said:
Which is kind of what I'm asking. Is there a way to re-flash the software completely through Odin? Or just flash the 4.1.2 through Odin? I haven't really been able to find the image online, though. I'd be happy with any software version as long as it deleted and overwrote my current system files with fresh, non-corrupted ones so I could start over. Since backing up files isn't a problem, or even a concern since I could really care less about keeping my files intact at this point, what can I do?
Click to expand...
Click to collapse
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe

prdog1 said:
I was editing when you responded. The Full OTA Odin Image is on SamMobile. Just Odin that and you are done.
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
Actually I have it here. Don't know which one is faster. Forgot I uploaded it to my server.
http://d-h.st/Xfe
Click to expand...
Click to collapse
And just making sure, using Odin will completely wipe the phone, yes?

[Q] Woke up to phone shutting down repeatedly, what?

Hey guys, running a stock build on my Droid Ultra (Mini).
Performed this root method on my droid (http://forum.xda-developers.com/showthread.php?t=2442585)
Had become aware that an OTA update was underway so I unrooted (chose the unroot option in SuperSU ) and left it to charge on the QI charger.
Just woke up to find it constantly restarting and (of course what woke me up is the initial vibrate startup.) What's going on? And where did I go wrong .

Nickrick2641 said:
Hey guys, running a stock build on my Droid Ultra (Mini).
Performed this root method on my droid (http://forum.xda-developers.com/showthread.php?t=2442585)
Had become aware that an OTA update was underway so I unrooted (chose the unroot option in SuperSU ) and left it to charge on the QI charger.
Just woke up to find it constantly restarting and (of course what woke me up is the initial vibrate startup.) What's going on? And where did I go wrong .
Click to expand...
Click to collapse
It may have to do with using the unroot method you chose...you can return to stock using RSD Lite or I believe there is another method by the name of houseofmoto or something similar
Sent from my XT1080 using Tapatalk

ahjee said:
It may have to do with using the unroot method you chose...you can return to stock using RSD Lite or I believe there is another method by the name of houseofmoto or something similar
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
RSD Lite fails multiple times, to my disadvantage. But the weird thing is that it fully boots onto Android, and within 35 seconds the "shutting down" prompt comes up (the OTA update is trying I guess... ) But how can i cancel the OTA ? it just lets it boot up then shut down , but it hasn't damaged anything in terms of the OS itself or the boot sectors as far as I can tell.

Your phone is boot looping. It's easier to get help if you know the term.
Look at the houseofmoto thread. It will help you flash back to stock, but save your data and apps.
Samurai, the developer of the app, has been helping people stuck in a boot loop. The guy deserves a medal.
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Oops, forgot the link.
http://forum.xda-developers.com/showthread.php?t=2450702

Nickrick2641 said:
RSD Lite fails multiple times, to my disadvantage. But the weird thing is that it fully boots onto Android, and within 35 seconds the "shutting down" prompt comes up (the OTA update is trying I guess... ) But how can i cancel the OTA ? it just lets it boot up then shut down , but it hasn't damaged anything in terms of the OS itself or the boot sectors as far as I can tell.
Click to expand...
Click to collapse
if RSD Lite fails...it could be because you are not editing the xml file within the zip you download in order to restore the stock firmware.
You should use this site here http://sbf.droid-developers.org/obake/list.php and download the stock file. The first and third files are the two stock firmwares for the Ultra and the second for the Maxx. The first file is the original out of the box firmware and the third is the first OTA we received neither is the latest firmware.
Anyway, once you download the firmware of your choice you have to extract it and then find the xml file within, edit the xml file, you must remove the gevtar line within the xml, just delete the whole line of text that has the word gevtar in it, after that just save the file as is.
Now you can go to RSDLite, chose the edited XML file, boot your phone into fastboot and plug it in
At this point all should be ready and gucci, just hit start and the process will take care of the rest, once your phone reboots you will have stock unrooted firmware. You'll get an ota, accept it, reboot, you'll get the latest OTA, accept it. Then, if you want, you can reroot your phone and have some real fun again.
Hope that helps you, if not, try houseofmoto which i am unfamiliar with cause i use RSDLite all the time. (yeah i've used it alot cause i play around with my phone and i am not scared to experiment and honestly sometimes i feel after removing and editing a bunch of files it's best to restore to stock to get a fully stable and solid rom working.)

Fixed with HouseofMoto
ahjee said:
if RSD Lite fails...it could......
Click to expand...
Click to collapse
Fixed it with HouseofMoto, definitely worthwhile to have not returned it the day I got my replacement, now I can gladly send it, even though its working now :silly:

Nickrick2641 said:
Fixed it with HouseofMoto, definitely worthwhile to have not returned it the day I got my replacement, now I can gladly send it, even though its working now :silly:
Click to expand...
Click to collapse
glad its working...

Is it possible to restore bloatware apps?

Hello all.
I rooted my Razr HD after the most recent update (prior to KitKat), so I'm rooted but not unlocked. In my ultimate wisdom, I completely removed (did not merely freeze) some bloatware apps, and only today am learning they are necessary to receive OTA updates.
A factory reset did not restore the apps.
Is it possible to get these bloatware apps back onto my device, or am I pretty much screwed?
If there is a way to restore them, am I screwed anyway due to having previously rooted my device and not having a way to flash a ROM?
My apologies if these questions are dumb; I've been looking for information regarding this for a couple hours and have come up empty so far.

Depending on what version you are currently on, you will need to get the correct FXZ image to fastboot onto your device to return it to stock.
Go here to fix you right up:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
Sent from my Nexus 7 using Tapatalk

Thanks a lot for the advice and the links. The process seems to work ok up until it tries to flash system.img.ext4, at which point it returns the message "Phone returned FAIL.; phone connected". If I remove that one line from the XML file, everything else goes through with no issues, so that seems to be the last thing holding me back.
When I attempt to boot the phone, I receive the following:
No valid PIV block in SP for system
piv validation failed (system)
Fastboot Reason: Boot Failure
Click to expand...
Click to collapse
I will double-check some things and try one more thing before I declare myself stuck again.

Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.

A little help..
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??

Worked for me
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.

froyton said:
Well, I'm glad I ran my double-checks because I would have wasted someone else's time otherwise. After updating to a slightly more recent version of RSD Lite, it got all the way through the reflash process.
My phone boots now. The stock apps are back. I'm letting all my apps update before I attempt the KitKat update, but I'm feeling confident about this. iBolski, I can't thank you enough, and I will love you forever.
Click to expand...
Click to collapse
Eustace2 said:
Thank you iBolski. The process failed the first time I ran RSD Lite, but it worked the second time. I did not unplug the phone or take it out of Fast Boot mode before trying it the second time. This is very helpful.
Click to expand...
Click to collapse
Glad it helped.
---------- Post added at 03:05 PM ---------- Previous post was at 03:00 PM ----------
moodaddy said:
Thanks for posting this! However I'm running into an issue. I downloaded the latest firmware for my XT907 as well as the latest version on RSD Lite, but when I go to flash the stock image I get an error message that says "unknown fastboot command [getvar]. Any ideas??
Click to expand...
Click to collapse
Go back to the following link and get the latest FXZ generator. SamuriHL has been updating it as people have been reporting issues:
http://www.droidrzr.com/index.php/topic/45349-rsd-script-generator/
He updated it yesterday to handle issues for your phone (XT907) and the XT926s as well. See if that fixes your issue. Otherwise, I'm not sure how else to help you.

v4.4.4 won't install... gets half way with error!

Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.

Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.

beelow319 said:
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
Click to expand...
Click to collapse
Can you offer up the steps to do that? I know how to do a factory reset, but that will wipe the data. Thanks.

Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do

newtoncd said:
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Click to expand...
Click to collapse
Are you, or have you been rooted in the past?

rmjones2006 said:
Are you, or have you been rooted in the past?
Click to expand...
Click to collapse
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.

beelow319 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
Click to expand...
Click to collapse
May I just say, thank you very much.
That worked ... I am now running v4.4.4 .... and you are right, that was very easy.
Too bad I had already wiped my phone twice ... ugh ... again, thank you!

newtoncd said:
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
Click to expand...
Click to collapse
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.

distortedloop said:
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
Click to expand...
Click to collapse
I had replaced the radios with stock before trying to update to v4.4.4 .... when that didn't work, I thought the reset to factory specs would take care of that; no joy.
In the end, I love the HouseofMoto program .... that was really easy.

Is 21r rootable?

So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?

shxrm_ said:
So AT&T and LG released a new update to 21r two days ago. Has anyone gotten it yet, and if so, are you able to root it?
Click to expand...
Click to collapse
I have the same question. According to the release notes for 21r, the purpose was to update security. It appears that this is the stagefright patch.
EDIT: Appears to still be rootable.

There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.

aybarrap1 said:
I have the same question. According to the release notes for 21r, the purpose was to update security. I hate to think that AT&T might have intentionally worked to prevent rooting and Bump'd. Would not surprise me. AT&T has strangely been releasing a lot of updates over the last 6 months or so which is very unlike them. I have to wonder if they have not been working to prevent rooting as rooting has become harder and harder.
Click to expand...
Click to collapse
That's literally the only reason why I'm still on 20f, and usually I would just update my phone right away to get the security. I just wanted to know if it's possible

autosurgeon said:
There have been a number of security issues of a magnitude that require patches. Whether rooting is a primary reason is debatable but based on the small % that root I doubt it is a major concern.
Click to expand...
Click to collapse
I see your point.

21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk

The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.

pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Hopefully it works for me, cause people said root worked for them on 21q, but it never worked for me

pigrew said:
The short answer is: yes, it is rootable.
The long answer: It took me many hours to wipe and update my phone. I had to try the factory reset a few times for it to finally work (I got stuck at "stage 2"), it was almost two hours waiting for the updates to download, and then I had to try the one-click root script a few times, but finally I have 21R with SuperSU on my phone. Yay. Also, the Zimperium stagefright detector says that my phone is no longer vulnerable. Yay.
Click to expand...
Click to collapse
Looks like I will go through the long process of unrooting now. Been avoiding the OTAs since lollipop update because of the hassle of having to unroot. I am glad to see that AT&T actually worked quickly with LG on patching stagefright. Being able to root again was a main concern.
UPDATE: Thus far, after backing up all my data and apps (I use both LGs backup and TiBu to do batch backups), I have downgraded to stock unroot, and it took 3 OTAs (21f, 21q, and 21r) to get to where I am at. The unroot method only took about 10 minutes but I already had everything set up from my previous upgrade to Lollipop. The OTA updates were painful as they took a while to download and install (700+mB, 205mB, and 23mB respectively so about 1gig of wifi data) along with the optimization of apps each time. I have now successfully rooted.

Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues

Firebourne said:
Hey everyone 21r is rootable. I was on 21q and rooted i went back to stock went through all the updates, and then used this method here:
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
and I cant stresss this enough, YOU HAVE TO USE METHOD 2 WHERE TO TYPE OUT THE COMMANDS.
I used that first time with no issues
Click to expand...
Click to collapse
Thanks for the confirmation of root as well as the the exact method that worked for you. I will be giving this a shot this afternoon. I want to take advantage of the stagefright patch while keeping root.
UPDATE: This root method worked. Had to do it twice but got it working.

Mjengles said:
21r has made. Usb debugging and usb tethering permanently greyed out. Have not been able to root. Yet.
Sent from my LG-D850 using Tapatalk
---------- Post added at 12:33 PM ---------- Previous post was at 11:52 AM ----------
False alarm. McAfee had phone locked down. Got usb debug. Haven't tried rooting yet.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.

It still refuses to work for me. I didn't change the diag port from when I restored back to stock, and I've tried it a few times just now, all to no effect.
Edit: the thing finally worked for me! I just closed the command prompt after the "send_command" part didn't work for me, and just did that part over, and it worked!!

CAUTION!!!!
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh

shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol

shxrm_ said:
To anyone who has succesfully rooted 21r, don't flash TWRP! After I used AutoRec to flash it, went to TWRP, and flashed the Xposed framework, I went to reboot, and my phone wouldn't boot up! It kept giving the LG logo, with security error under it! I am currently in the process of flashing back to do it all over smh
Click to expand...
Click to collapse
You don't need to start all over. Just install the Gabriel kernel in twrp and you are good.
Sent from my LG-D850 using XDA Free mobile app
---------- Post added at 12:25 PM ---------- Previous post was at 12:21 PM ----------
Firebourne said:
if you go here http://forum.xda-developers.com/att-lg-g3/orig-development/bump-unlock-lg-g3-twrp-t2900569 and download the bump'd twrp and flash it through flashify on the phone it will work and then you can use flashify to download and flash the newest twrp the new update doesnt have to be bump'd as long as the first flash is. I did this after getting that stupid error multiple times lol
Click to expand...
Click to collapse
That only refers to secure boot errors booting twrp not booting the phone.
Sent from my LG-D850 using XDA Free mobile app

Link please? I searched the development threads, but didn't find the kernel you mentioned

shxrm_ said:
Link please? I searched the development threads, but didn't find the kernel you mentioned
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g3/development/lollipopstockkernelgabriel5-d855-t3120893

aybarrap1 said:
I noticed that USB Debugging is greyed out when connected to USB. However upon disconnecting it was able to be checked. On my second go round to root, I had to disconnect, uncheck USB debugging, reenable then plug in.
Click to expand...
Click to collapse
Second method of rooting worked for me. Hello control.....goodbye warranty
Sent from my ASUS MeMO Pad 7 using Tapatalk

Is there a bootable zip of the lastest stock Att ROM? Thanks.