My non-rooted DINC sucessfully updated to GB (2.3.4) and firmware 4.06.605.3. It has subsequently tried several times to do an OTA to 4.08.605.2.
The screen says that the update has downloaded and been verified, does its countdown to the reboot, then hangs on the "rebooting now..." screen.
Verizon wants me to wipe the phone to factory and wait until Verizon once again tries to push the update, then rebuild my phone.
I don't think that is going to happen. So, has anyone else seen this and found a solution?
Related
running stock 4.0.2 on vzw. just received update notification for 4.0.4 update. downloaded and rebooted for installation, problem results when it reboots. gets stuck on google logo and only fix is battery pull. then after turning device on it says download failed and i have to redownload the 38mb update, reboot, and then it gets stuck on google logo again. happened 4 times. anyone have any ideas about this? ive let it sit on the google logo for over 15 minutes to try to reassure myself that there wasnt a problem, but only solution is a battery pull
jttate04 said:
running stock 4.0.2 on vzw. just received update notification for 4.0.4 update. downloaded and rebooted for installation, problem results when it reboots. gets stuck on google logo and only fix is battery pull. then after turning device on it says download failed and i have to redownload the 38mb update, reboot, and then it gets stuck on google logo again. happened 4 times. anyone have any ideas about this? ive let it sit on the google logo for over 15 minutes to try to reassure myself that there wasnt a problem, but only solution is a battery pull
Click to expand...
Click to collapse
Have you ever used a toolkit for anything on your device. It may have messed up your recovery. You need to flash either (a) the stock recovery that come with your device (from here, instructions here) and it will install automatically, or (b) flash CWM and install the update with that (instructions here).
Jelly Bean for yakjuxw is rolling out now, but mine will not install.
I have used the Google framework services "trick" to get and download the update 3 times now.
It downloads 160,3 mb, confirms and restarts for install. Then the Google logo shows for about 10 seconds and then just a restart again without installation. No error messages or anything.
4.0.4, yakuxw.
Any ideas?
Have you rooted the device, flashed a custom recovery, flashed a radio or changed any system files (fonts, mods, themes)?
All of these things (and many more) will cause the update to fail.
No, it is totally stock and not rooted.
Seems weird to me - can it somehow download a wrong update file?
It does not even show the red Android on the first reboot.
Also it seems, that the phone is unable to go into Recovery. Pressing both volume buttons and power and then selecting Recovery modes gets me to the same thing: The white google logo on black screen, and then a auto reboot to normal phone operation.
Can Recovery get broken in any way and thus also prevent the update?
ThomasDK said:
Also it seems, that the phone is unable to go into Recovery. Pressing both volume buttons and power and then selecting Recovery modes gets me to the same thing: The white google logo on black screen, and then a auto reboot to normal phone operation.
Can Recovery get broken in any way and thus also prevent the update?
Click to expand...
Click to collapse
I am expieriencing the exact same problem. Recovery seems to be corrupted and cannot enter it. This cause installation of update impossible. We need help here.
Is flashing to yakju will fix recovery mode?
Try manually flashing the stock recovery. You'll need an unlocked bootloader for that though.
I have fixed my problem by flashing yakju. I have used this method: http://forum.xda-developers.com/showthread.php?t=1787503&highlight=yakju
Now i will get OTA updates from Google instead from Samsung because i had yakjuux firmware since my phone was orginally from Bell. Yay!
I sent mine in for repair.
Received it back with re-flashed software, and it's ok again.
I had to resolve to making a thread because google isn't helping... And I've looked through everything.
I was running Hurricane rom v6 and I wanted to upgrade to the latest version, so I went ahead and tried to install the mj5 bootloader. I followed all the instrcutions but something didn't seem right... Right after the flashing process in Odin finished, my phone rebooted into the recovery (CWM PhilzTouch) instead of rebooting to the OS. I went to check if the new bootloader was installed and I don't think it was, because it didn't say KNOX WARRANTY VOID as it was supposed to, according to the instructions.
So I tried it again a few times and eventually what happened is that I got the "go into Kies and do the emergency recovery etc" which I did, a few times, unsuccessfully. It failed every time. So I uninstalled Kies, went back to Odin, tried to a few other ports, and finally it finished the flashing process successfully.
Now I can get into both recovery and download mode, but when I try to reboot the phone, the Galaxy Note 2 logo shows up, after that the screen goes black and then the phone vibrates every two seconds until i remove the battery.
I tried going back to recovery and then factory reset the phone but still the same thing happens. Now I'm downloading the stock firmware from samsung to try to flash that since I can still get to download mode but it's going to take an hour and until then I wanted to ask if the vibrating behavior was normal or it indicated a more serious problem. In all fairness I haven't tried installing the new version of the Hurricane rom after I tried flashing the new bootloader, but I figured that as long as I don't know that I have the new bootloader for sure I'd rather skip that step.
Any ideas?
We my son was using my phone GS3 and pressed on to update. he thought it was a game update, but once it ran it boot then it will be stuck in the ATT logo. I kept tying to reset nothing it boots but once in att logo it stops. i also went in to clear the cach anf reset to factory and still no responds please help.....
Was the phone rooted? Does it have a custom recovery? These two things can cause an ota to fail.
Not sure if it's a common issue or not but since my phone took that latest garbage of an update every time I go into the recovery menu it says installing system update. This is a first for me seems how I've had several samsung phones. Then goes to the dead Droid with no command and after a few mins it loads the menu. I've done several resets and it hasn't changed
It's gone now. I connected it to the Verizon repair assistant. Although the Verizon 2.0 sua. Failed I rebooted the phone and its gone and finished initializing the update.