XBOX Corona E Problem

[sky19]

I have this xbox (250GB) corona E ,release date "17/07/2013" , Work without problems (Glitched of course)
and i have another 2 Xbox (Glitched) Corona E with release date
28/07/2013 & 11/10/2013 i can power on them but No Xell / No Boot
when i restore the original firmware they work without problem

 

[N.E.Modz]

I have this xbox (250GB) corona E ,release date "17/07/2013" , Work without problems (Glitched of course)
and i have another 2 Xbox (Glitched) Corona E with release date
28/07/2013 & 11/10/2013 i can power on them but No Xell / No Boot
when i restore the original firmware they work without problem

have you updated them to the latest dash (16756) If so, thats your problem. If No, then check all your soldering connections. What glitch method are you using ? CR rev C or?

Dale

 

[playingmax]

http://www.hackfaq.net/main/xell_wb2k

 

[sky19]

the dashboard was 16203 for both , and glitch method i've used 360 ACE V1 / X360RUN

 

[john mathews]

the dashboard was 16203 for both , and glitch method i've used 360 ACE V1 / X360RUN

u need to get a tx chip

 

[N.E.Modz]

the dashboard was 16203 for both , and glitch method i've used 360 ACE V1 / X360RUN

OOPS :facepalm: Crashed & Burned mate, This is a TX product forum, Your gonna have to go a forum which deals with non tx products as your not gonna get any help here

 

[playingmax]

the dashboard was 16203 for both , and glitch method i've used 360 ACE V1 / X360RUN

u will also need postout fix.

 

[XDK]

have you updated them to the latest dash (16756) If so, thats your problem. If No, then check all your soldering connections. What glitch method are you using ? CR rev C or?

Dale

FYI for future reference dashboard/kernel has no bearing on wether or not the 360E or 360 in general can or cannot be glitched.

 

[N.E.Modz]

FYI for future reference dashboard/kernel has no bearing on wether or not the 360E or 360 in general can or cannot be glitched.

FYI, I was not asking what dash/kernel it was on before he glitched it, I was asking whether he updated to 16756 after he glitched it and that does have a bearing on why his glitched console had stopped working.

 

[Antalpromille]

FYI, I was not asking what dash/kernel it was on before he glitched it, I was asking whether he updated to 16756 after he glitched it and that does have a bearing on why his glitched console had stopped working.

And why wouldnt they boot If he made xebuild images with dashboard version 16756? I tested that on one of mine recently and the only issue was that DL had no support for it, but it did boot.

 

[N.E.Modz]

And why wouldnt they boot If he made xebuild images with dashboard version 16756? I tested that on one of mine recently and the only issue was that DL had no support for it, but it did boot.

your both missing the point ? if he updated the dash after glitching, then it could've blow a efuse and glitch image could be conflicting with the updated LDV etc. Thats all I was getting at. Nothing to do with building xebuild images etc

P.S he also stated that when he wrote original nand back it booted, which would indicate a problem after update

 

[Antalpromille]

your both missing the point ? if he updated the dash after glitching, then it could've blow a efuse and glitch image could be conflicting with the updated LDV etc. Thats all I was getting at. Nothing to do with building xebuild images etc

P.S he also stated that when he wrote original nand back it booted, which would indicate a problem after update

So what you are trying to say is that if he accepted an official update on your glitched console and it burned efuses, the retail nand would boot even tho the efuses didn't match? Sounds real logic to me in my world you would get a red dot.

+ the glitch image doesn't care about LDV, but an official update would overwrite the nand but the chip would keep the console from booting and causing a red dot.

 

[XDK]

So what you are trying to say is that if he accepted an official update on your glitched console and it burned efuses, the retail nand would boot even tho the efuses didn't match? Sounds real logic to me in my world you would get a red dot.

+ the glitch image doesn't care about LDV, but an official update would overwrite the nand but the chip would keep the console from booting and causing a red dot.

exactly ^^