[Solved] Soft Brick keeps coming back - Galaxy S II Q&A, Help & Troubleshooting

Hello, i'm a XDA noob and i have a Problem with my i9100.
I figuered out that i have a Soft Brick and thanks to the Guide i fixed that one.
The battery was full when i went sleeping. And half an hour ago everything seems to be fine. 95% battery, phone is working. I had flight mode activated and just deactivated it. I got an Error that the SMS app was closed, but everything was still fine. I locked the Screen, 5 minutes later i came back and it Soft Bricked again. (The first Soft Brick came from out of nowhere, too).
i Had the Original Samsung Stock 4.0.3 (the download from in the Guide) installed. It worked fine after Step 4.
Symptoms:
Does not boot
No Recovery
Download mode works if connected with USB
Loading works partially, the symbol apears, but after 9 seconds it disapears and after 6 seconds it apears again...
If i try to enter Download mode with low battery and no USB conection, i get a Screen warning that Battery is low
I Randomly get a Screen flicker which lasts about 0.1 - 0.5 seconds. The 0.5 ones show the Andorid logo who is installing something . I Think the 0.1 second ones show the same thing but i'm not sure.
Odin Flash works ! Here's the log
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9100-MULTI-CSC-OXALPH.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> boot.bin
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> factoryfs.img
<ID:0/003> data.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After Odin it wont boot directly nor Recovery works, but if i wait a few minutes and change battery ( i have 2 batterys ) multiple times, it somehow starts to show the same old "andoird is working" screen and then boots in a nice stock Android 4.0.3.
Additional Information
I had installed CM 10.1 (with CWM) before. And it worked fine for months.
Someday the battery usage became extrem (there is a Problem with the SD card, because it's always saying the SD was removed and installed, checking for errors, and that costs a lot of battery power...
I deleted all the data/data manually and some system folders --> Boot Loop , so i decided to swich back to Stock Android 4.2.2. That worked fine, Memory usage is high too if using with a SD card. But OS was stable, till yesterday...
I neither connected my phone with Google yesterday, nor did i sign up with Samsung services, nor did i changed anything, nor did i installed apps.
Now my Question is:
What should i do to get a stable system? Is there any option to get my phone back to factory status? (no i don't mean factory reset, because this only change a few folders but not all on the phone...)
Thank you.

---

Search for a nuke script in order to get rid of previous ROMs leftovers.
Sent from the little guy

---

That seemed to work.
I installed CWM and CM 10.1, then i ran the script and after that reinstalled the newest version of CM10.1.

---

mac.2013 said:
That seemed to work.
I installed CWM and CM 10.1, then i ran the script and after that reinstalled the newest version of CM10.1.
Click to expand...
Click to collapse
Please add [SOLVED] to the title of ur post then.
"To err is human, to forgive is divine"
Sent from my SGS II