Stuck on the green boot screen after a restore factory defaults with E303 8007042C error

On July 20, as I was playing CoD Ghosts, the xbox became unresponsive during the map loading screen, so I hard resetted it. Tried to play again, but the same thing happened, so I tried to play BF4 now, but it would take some time before an error came up
saying the game took too long to start, so I went ahead and restored from the settings app. After the restore, installed CoD again only to run into the same problem, extremely slow map loading and then unresponsive yet again and I could not open any app. Hard
resetted it again, only to get stuck on the green boot screen, and once in a while I would get the E303 00000000 8007042C error. Since nothing seemed to work, I found that the offline system update diagnostic tool could restore it by forcing the restore file
with a NTFS formatted USB. But after following the steps, the double power up tone never came, everytime I did it I would get only one power up tone. Is there another option besides sending it back to Microsoft?

:)

 

Xbox one error E303 0000000 800706BE

Hello guys, I have a similar problem. On July 20, while playing CoD Ghosts, the xbox one stopped responding in the map loading screen. I did a hard reset, with and without kinect, disc, etc and no improvement. So I decided to restore it. After it was done,
resintalled CoD and tried to play it, but again it stopped responding. After another hard reset, the xbox gets stuck on the green boot screen all the time, with a few error e303 00000000 8007042C. This error has nothing to do with updates, so I guess my only
option is to send it back right?

 

Green Xbox Logo Followed By Black Screen When Powering On

If you can access your xbox one settings app, go there, then choose console, then restore factory defaults. If your xbox one does not boot (stuck on the green logo), you may use the OSUDT restoring file.

 

I even tried the OSUDT 2 file, but never hear the second powe up tone, anyone plz help....

 

So why can't you play the game as intended?????

Insert disk, Install, update, Play........

Why the need to restore anything????? Why try things Off Line???? Why the need for USB????

After the factory defalts are in place, an update is needed. A simple internet connection will solve this issue....... What are you trying to do anyway???

 

When you do the hard reset do you remove any discs that are in the tray?

 

The game would stop loading and become unresponsive, had no choice but turn if off. But it wouldn't turn off, so I did a hard reset. It did not solve the problem, and after that I could not open any app or game, it would say "took to long to start". I thought
CoD had some problems, so the restore deletes app and profiles only, it does nothing to the OS. But after the restore, and reinstalled CoD again only to run into the loading problem. After turning it off, it gets stuck on the green boot screen, with some times
giving me that error. The USB is to use the OSUDT, but it didn't work either

 

Yeah, no discs in the tray, no kinect plugged, also tried with kinect plugged, nothing

 

The code seems to be an update error caused by having a disc in the console while updating.

The only solution i can find is to unplug for a few minutes without a disc in, and restart.

If that doesn`t fix it there may be a bigger fault on your console and you may need a new one.

 

Are you talking about a OS update? or an app/game update?

 

I guess that my final choice, send it back and get a new one... I was trying to avoid that because I will miss the Destiny beta, damn it

 

I am only going off the couple of bits of info i found when i searched that error code.

If you search your error code from the drop down menu at the top of the page it will open a couple of other threads on the same topic.

The hard reset fixed the problem for some of those that tried it.

 

User error maybe an issue here......

 

I tried all ways, hard reset, also while holding the eject button, with kinect plugged/unplugged, nothing

 

But it was working fine 2 days ago... when the problem started to appear, also notification messages would not go away, something went wrong with the OS I think