Develop Bugs

Unfixable boot loop... Help?

Hey everyone,
So this is my last ditch effort to attempt to save my device. I would really prefer not to perform another warranty exchange given that I am not under insurance, but I'm afraid I have no choice.
My phone was rooted and I was using Darkside without issues, as I had been for the past two weeks. I am always careful when I flash roms and I made sure to follow every possible protocol. That's the background information.
My battery life was running at approximately 6 percent yesterday and I sent a text message as normal, and it was stuck at sending. I tried turning wireless data off from the toggles in the pull-down and it was unresponsive. When I went to Wireless Network in the settings option, my phone rebooted. Once it started up again, my service would not come back, and the phone would continually bootloop once it got past the traditional "media scanner running", etc. My window of opportunity to do anything was really slim.
I charged my phone to see if it made a difference, but it didn't. Tried with my SIM card removed and it still bootlooped. I was able to get to CWM from the advanced power menu before it rebooted again and I fixed permissions and cleared cache and dalvik. Now the phone wouldn't even get past the boot animation before rebooting.
I put the phone into download mode and reverted back to stock using Odin. The phone now got past the boot animation in stock mode, but was unable to find service and after about 10 seconds fell into the same bootloop pattern. I tried removing the SD card but that didn't help either. Using Odin again, I reflashed recovery, followed by root and tried reinstalling a rom through CWM (I have only used regular CWM, not the touch version) with a superwipe to ensure a clean flash. Once again, it wouldn't make it past the boot animation before bootlooping. I reverted back to stock using Odin, and this is where I stand.
I have tried all traditional methods to salvage the phone and, for the life of me, I cannot understand what happened. The only thing I notice is that regardless of how long the phone stays on before rebooting, it is never able to find service. It's like the radio or modem broke and the phone has no other choice but to restart forever. But reflashing the stock UVKL1 should also reflash the proper modem and radio, right?
Has this ever happened to anyone? Any suggestions (aside from the typical reverting to stock) as to how I might be able to stop it? I searched but haven't been able to find a situation quite like this one. Thanks in advance for your help.

Really sorry to hear about your problem. Assuming the 2.3.6 stock image you flashed via Odin is the one provided by Przekret and that that didn't work, then I'd try one or both of these two longshots to try to clear possible corruption problems in either the kernel or modem spaces:
For each of the following wipe cache and Dalvik cache in CWM before flashing and again wipe Dalvik afterwards and also fix permissions:
1) Format system (do this 3x) under mounts & storage in CWM. Flash the standalone Darkside kernel X v1 final immediately after flashing, e.g., the current Darkside rom. (You'll need to wipe data, too, if not coming from a Darkside rom. Do not do any Superwipe - neither the standalone version nor using a flag.)
2) Flash the KID modem (do this 3x). Both Odin- and CWM-flashable versions are available. (You can always flash back to KL1 if the problem is fixed.)
Hope this is clear. It's late! These are both things that have helped get my phone out of troubles, though not as bad as yours. Good luck!
Sent from my SGH-T989 using XDA App

Also if u used the one from przekret then I'm almost positive that Odin package flashes the new radio too. If memory serves me right. Op let us know what happened

Thanks for your help. Unfortunately, nothing has worked. I'm on the phone with T-Mobile, I see no other solution but to get it exchanged under warranty and it's not getting here until March 15th, according to the representative. I suppose I'll just use a replacement phone in the meantime. It's just really weird and frustrating... I could understand a bad flash or something similar, but I followed every step accurately as I always have and everything was working just fine until it randomly decided to die without warning.

Well since you're getting another one anyways I would continue trying to fix this one, just in case you come up with a solution and for another worst case scenario for your new phone.
Powered by the SGSII....

I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA

shehrammajid said:
I think your efs folder got corrupted. Its scary to see this happening so often. Many other users have also reported corrupted efs ....
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
Forgive me for asking, but what is the EFS folder?

[Q] boot loop...(sort of)

I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)

Gzerner said:
I just flashed the newest version of the codename rom (JustLoveCodename-Android-(Alpha1)2.0.0-RC to my epic 4g touch. I also flashed the Google apps pack that comes with it. It seemed nice at first, but then I tried using the market and it just kept telling me there was a server error. I tried re-downloading it from third party sites but nothing was working. So I went to flash back to Calkulins rom. As I got into recovery mode, it seems the phone somehow changed itself to another recovery system (It might've been CWM) instead of the rogue one I had prior from the initial root process. I tried flashing anyway and the a picture of a dead android with his front opened up and a red exclamation popped up. I rebooted the phone to see what would happen. It brought me right back to Code name's rom. I tried it 3 more times yet the same thing happened every time. I also tried a battery pull. It did not work. I am thinking of doing one of two things: I am going to either go through the initial root stages again or I am going to try to delete the Codename rom from my SD card and try flashing another rom (preferably Calkulin). Please tell me if this is the right thing to do or if there is another method of fixing this problem. Thank you for taking time to read this. I really appreciate any help. FYI: My phone is still in working condition, but I am stuck using the Codename rom which I really do not want to use anymore. I just was able to get ES file manager working and i checked my external sd folder, but there is nothing in it. When i look at my storage from system settings, it says i still have the memory on it. So why is ES not displaying it? =( I re-installed rogue cwm and flashed calkulin's rom again and everything is fine. Heed my advice and be wary of the Codename Rom. Editor's, you can delete this thread if you wish. =)
Click to expand...
Click to collapse
K. The reason you aren't getting to the old version of CWM is because you flashed Codename. Codename is an AOSP ROM which has been known to cause bricks when flashing with Rogue. Because if the bricks the developers opted to but include CWM of any kind in the kernel. What you need to do is find a replacement ROM and download it. Once you've downloaded it you need to flash the EL26 stock CWM (you can find it in the OP of the link below) then use it to flash your new ROM.
http://forum.xda-developers.com/showthread.php?p=295021
Well you're at it is suggest reading the How Not To Brick Your Phone thread in general.
Good luck!

Codename rom is an AOSP rom so your external SD storage will be under /emmc and not /sdcard/externalsd. That's why it wasn't showing up. Same thing with CM9 and AOKP, not because it doesn't work. Also I wouldn't recommend flashing anything ICS related from rogue recovery, js.
And recoveries changed because with our phones, the recovery is packed into the kernel itself so when you flashed Codename, the recovery changed to the stock recovery included with the roms kernel. Hope that clears it up lol.
Sent from my SPH-D710 using Tapatalk

If you want a fresh install, the best way is to Odin the el29 kernal. From there, get into your recovery and wipe and flash away.
Sent from my SPH-D710 using XDA

Strange GS2 Flashing Issues

I want to start out saying that I am not a newbie at rooting and flashing roms. I have probably done it over 100 times.
I am having a particularly annoying problem getting my new Galaxy SII(Walmart prepaid one) from T-Mobile flashing properly. I have no issues rooting or installing recovery. I have actually tried TWRP and CWM. When I flash a rom, it either hangs at the boot screen or it will get to the setup menu and hang for about 5 minutes on each screen. I have tried superwipe and everything else I can think of to get it to work. I have done this with just about every rom I could get ahold of and have the same issue. I rooted my friends s2 a couple months ago and had no issues at all.
Please help and thanks in advance.

jasonmatty1 said:
I want to start out saying that I am not a newbie at rooting and flashing roms. I have probably done it over 100 times.
I am having a particularly annoying problem getting my new Galaxy SII(Walmart prepaid one) from T-Mobile flashing properly. I have no issues rooting or installing recovery. I have actually tried TWRP and CWM. When I flash a rom, it either hangs at the boot screen or it will get to the setup menu and hang for about 5 minutes on each screen. I have tried superwipe and everything else I can think of to get it to work. I have done this with just about every rom I could get ahold of and have the same issue. I rooted my friends s2 a couple months ago and had no issues at all.
Please help and thanks in advance.
Click to expand...
Click to collapse
One make sure internet is on so google can communicate with servers. Might be the hang issue. Two try wiping dalvik and partition after flashing new rom before you boot for the first time. Don't know if it'll help but just a thought.
Sent from my SGH-T989 using Tapatalk

I always wipe davik and cache partition. To me it seems like an issue that may be related to the inability to write to the system during boot.

I had a couple issues with boot hangs when I did my first custom ROM install and had the same issues doing the same with a friend's SII. I had to use the Darkside wipes at the time, but from what I've seen on the boards, they're not necessary with newer versions (>6) of CWM. It's been a while, but if I recall correctly, the key for me was first doing a full update with Kies (yea, I know, I know, PITA software, but it did help). Then pushing CWM with Odin, going through both Darkside wipes, and then finally applying the custom ROM (it was CM9 at the time).
If you can push newer versions of CWM, I guess the Darkside wipes aren't necessary anymore, as the CWM wipes work just fine.
Edit: I also ran a permission fix after applying the ROM but before trying the first boot. Shouldn't have made a difference, but I was going with the "nuke from orbit" approach to install.

GaidinBDJ said:
I had a couple issues with boot hangs when I did my first custom ROM install and had the same issues doing the same with a friend's SII. I had to use the Darkside wipes at the time, but from what I've seen on the boards, they're not necessary with newer versions (>6) of CWM. It's been a while, but if I recall correctly, the key for me was first doing a full update with Kies (yea, I know, I know, PITA software, but it did help). Then pushing CWM with Odin, going through both Darkside wipes, and then finally applying the custom ROM (it was CM9 at the time).
If you can push newer versions of CWM, I guess the Darkside wipes aren't necessary anymore, as the CWM wipes work just fine.
Click to expand...
Click to collapse
Thanks for everyone that helped. I put the rom on a sd card instead of the internal storage and it worked flawless.
Would anyone care to comment as to the best rom for the s2? I put Jedi Mind Trick on it.

jasonmatty1 said:
Would anyone care to comment as to the best rom for the s2? I put Jedi Mind Trick on it.
Click to expand...
Click to collapse
I've always been partial to Cyangenmod. If you're into tinkering, it's nice because it's got one of the larger user bases so when you mess something up, it's pretty easy to Google for fixes.

Jedi Jelly 4 or all star Rom v7.
~°~°~°~°~°~°~°~°~°~°~°~°~°~°~°~
Phone: Samsung Galaxy s2 T989 Hercules
Rom: Jedi Jelly 4
Kernel: Insecure Kernel
Radio: LB7 Blaze
~°~°~°~°~°~°~°~°~°~°~°~°~°~°~°~
I am going to try and make an app, if anyone wants help this beautiful talented celebrity in making it just message me!

[Q] Any possible ways to unbrick a softbricked SGH-I747

So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.

Re: [Q] Any possible ways to unbrick a softbricked SHGI747
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app

RPelham said:
This one should be easy, if you got a pass in ODIN, the hard part is over.
Go into stock recovery, wipe cache and perform factory reset. Reboot and report back. This generally fixes that bug. Its very common after an ODIN flash.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:

MeatwadGetTheHunniesG said:
Oh wow, thank you so much. That worked and everything is as it should be, just like when I got it out of the box. I thought I was screwed for a moment, I even had an upgrade and got a HTC One VX a couple days ago haha. Wow. Again, thank you. :highfive:
Click to expand...
Click to collapse
No problem at all =) Its pretty hard to completely brick your device unless you flash something made for a different phone lol. As long as your phone can see any signs of life (even a faint vibration), let us know and we are more than happy to help!
Sent from my SGH-I747 using xda app-developers app

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.

S.O.S. Phone is completely wiped only dowload mode and recovery work.
Okay so I think I kind of put myself in a sticky situation. I tried to flash a custom rom onto my phone but in the process deleted my modem file everything worked fine except for the fact that I couldnt make calls or text messages. Basically a $400 dollar multimedia device. At this point I just want to put my phone back to the way it was when I got it at the AT&T store. My phone model is SGH-i747 Galaxy S3 that came with JB 4.1.1 pre installed.

I once spent four hours trying to hard brick a Galaxy S2 phone (science experiment).
I'd flash ROM's for other phones.
Kernel's.
Recoveries.
Took forever to finally hard brick it.
Click to expand...
Click to collapse
Out of curiosity, how did you finally manage to brick it?
Sent from my Nexus 7 using xda app-developers app

solution
MeatwadGetTheHunniesG said:
So here's the deal,
My ATT Galaxy S3 is half dead, and by that I mean soft bricked and I still believe there is hope in fixing this thing. Here's the entire story, everything was fine before I updated to CM 10.1 via ClockworkMod Recovery. At the time I was running the stable CM10. So I grabbed a copy of GAPPS, The CM10.1 nigthly, and a lean kernel to help improve battery life. I did the factory reset setting in CWM, then flashed CM10.1, Gapps, then the kernel. Then I did the usual after you flash a kernel, clean the cache, dalvik cache, and fix permissions. When I rebooted, the Galaxy S III boot logo was purple and glitchy, and my thought was, "Oh nooooo I bricked my phone." I had a backup saved, but after that glitch, everything was gone, so I had no backup and now I was panicking. I put my ext sd card in my reader on my PC and put the stable CM10 zip file on it, so i flashed it in CWM. My phone booted up normally. But here's the catch, no keyboard. Everything worked fine except my keyboard which kept saying, "Android Keyboard(AOSP) has encountered and error" or something like that every few seconds and would disappear just as fast. But here's the even funnier catch, everything that was my phone was still there except in a folder called 0, and in that folder another folder called 0, and in that contained a 'snapshot' of my phone as it was. CWM would not read the backup folder, or any of the files. So then I put my phone in download mode and flashed the stock ICS Samsung/ATT Rom called I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 to try to revive my phone fresh. It passed in ODIN, and now it boots up like normal except it gets stuck on the last Samsung label of the boot animation with the notification light a solid blue. Any help would be so much appreciated, I know of nothing else to do but I believe this can be fixed.
Click to expand...
Click to collapse
There's another thread called stuck on boot screen with same issue. Had same issue with simular Rom had to boot in recovery and clear cache and user settings. And no longer an issue

Soft bricked...
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?

kinjo1023 said:
I'm currently dealing with a soft brick that I can't unbrick either. Got a replacement Sgh-i747 thru insurance. Rooted and decided to try twrp instead of cwm. Went to flash the ROM and didn't realize twrp didn't read ext SD cards until after i wiped my phone and OS. Tried reverting back to stock but Odin fails on the stock firmware every time. Tried flashing cwm and flashing a ROM but keep getting error 7 and no Roms flash. Any ideas as to where to start over with?
Click to expand...
Click to collapse
I think I did someting like that too nd now I cant install any ROM and TWRP complains that I have no OS inside the phone.I tried modifying the assert-script file but it then eventually ends up at STATUS 6 and not status 7 again.Pls and Pls help us

You have to be on twrp 2.7.x to install any kk ROMs.
Sent from my SGH-I747 using Tapatalk

[Q] Shadow Mastery

Hello Everyone,
I recently formatted my internal SD (Hercules T-Mobile) and I cannot seem to get Shadow Mastery installed. It just keeps boot looping. I have full wiped using infamous. I have tried every recovery possible including TWRP 2.6 as instructed.. Is it because my Preload partition is no longer present? If it is this how can I go about repartioning my device to include preload. I have also went back to stock using Odin. It still does not create a preload.. Thanks in advance for your input. I have been lurking and flashing since my G1 but am now trying to be more active in the community.

shadow master 2.2
im installed it last night and it froze on the green screen for about 20 minutes.....then I took the battery out and re installed it......
it did tha same thing......so I used DARKSIDE.SUPER.WIPE_EXT4 and whipped it again and in stalled shadow 1.5...
any reason why it froze ?

SaTxCowboy said:
im installed it last night and it froze on the green screen for about 20 minutes.....then I took the battery out and re installed it......
it did tha same thing......so I used DARKSIDE.SUPER.WIPE_EXT4 and whipped it again and in stalled shadow 1.5...
any reason why it froze ?
Click to expand...
Click to collapse
Darkside is out dated.... You gotta use the infamous scripts. Both of them.
Sent from my SGH-T989D using Tapatalk

kj2112 said:
Darkside is out dated.... You gotta use the infamous scripts. Both of them.
Sent from my SGH-T989D using Tapatalk
Click to expand...
Click to collapse
r they here on this web page ?
do I search by the name infamous scripts ?
im a rookie at all this... my cell is rooted !!!
---------- Post added at 10:27 AM ---------- Previous post was at 10:14 AM ----------
SaTxCowboy said:
r they here on this web page ?
do I search by the name infamous scripts ?
im a rookie at all this... my cell is rooted !!!
Click to expand...
Click to collapse
I found it...
thx....

I tried all the things that were suggested because, I too, had the never ending boot loops. I returned to stock with Odin, rerooted, and formatted and reset everything and still had boot loops. I even tried a dirty install over Shadow 1000 just for yuks.
Bottom line after returning to stock again thru Odin and rooted, I used Infamous Wipes and installed Shadow Mastery 33 and still got the boot loop. I went back into TWRP and installed Tiberius-TouchWiz-2.4-LINARO-Hercules.zip and, surprise, it works.
I hope this helps others with the boot loop problem. I don't know what it is that could be about the kernel that my phone doesn't like, but it solved the problem for me.

Thanks a million. I will give this a shot. Knew I could count on such a awesome community to help me out. :good::good:
Tried Tiberus worked perfectly. Thanks again.

visualist6x6 said:
I tried all the things that were suggested because, I too, had the never ending boot loops. I returned to stock with Odin, rerooted, and formatted and reset everything and still had boot loops. I even tried a dirty install over Shadow 1000 just for yuks.
Bottom line after returning to stock again thru Odin and rooted, I used Infamous Wipes and installed Shadow Mastery 33 and still got the boot loop. I went back into TWRP and installed Tiberius-TouchWiz-2.4-LINARO-Hercules.zip and, surprise, it works.
I hope this helps others with the boot loop problem. I don't know what it is that could be about the kernel that my phone doesn't like, but it solved the problem for me.
Click to expand...
Click to collapse
Hey there, I have been for the last three hours reading all 24 pages o the Shadow freezerburnt rom (final version) and at the end after so much reading I got confused but I am not allowed to post a question in the developers section, maybe you can help me here. I am now running JMTv7 , i had so far flashed a few cyanogen CM10, cm11, beanstalk 4.4, paranoid android 4.3.. and so far i had no major problems trying them out.
Now I would like to try this Rom from Rushing: Shadow Freezerburnt, but he makes a remark that says (no radio and no recover included) so I have now on JMT7 the CWM 6.0 recovery and the UVMC6 radio.
The question is: if I flash the Shadow FB Rom means I have to flash as well a new recovery and the radio cause it will get lost in the wipe outs? so far preparing for this I downloaded the tiberious kernel, the twrp recovery zip file, I am still trying to get a place to download the UVMC6 radio just in case but no luck with that. Seriously I have been reading forums (all 24 pages in rushing OP) for over three hours and now my head is spinning... I appreciate any pointers... Thank you.

Okay, I flashed today shadow freezerbunt, coming from JMT 7. I read tons before going for it I got all worked up hearing of so many people getting bootloops. I followed the instructions as kj2112 posted and I had no problems at all. So far is going smooth. No need to change kernel here. Thank you rushings this Rom looks great and runs suave...
Sent from my SGH-T989 using Tapatalk

Guess I need to add my name to this list. I have never been able to install ANY of Rushing's Shadow series ROMs. I always get stuck at about 20% load of the Shadow Boot Screen. The only time I was able to get past it was by installing a Linaro Kernel before booting the first time. But I just tried his latest version which is supposed to fix the boot issues, and same exact thing, although this time if I install Linaro it goes past the boot screen, but then has a boot loop. And I've gone all the way back to a fresh ODIN factory reset, but no success. Does anybody have a real explanation as to why this could be happening?
Cheers

Try SHADOW MASTERY 1.2.3
The above file appears to be the same as Shadow Mastery AND includes the radio and recovery. I have been running this for afew weeks no with no problems.

Serious1 said:
Hello Everyone,
I recently formatted my internal SD (Hercules T-Mobile) and I cannot seem to get Shadow Mastery installed. It just keeps boot looping. I have full wiped using infamous. I have tried every recovery possible including TWRP 2.6 as instructed.. Is it because my Preload partition is no longer present? If it is this how can I go about repartioning my device to include preload. I have also went back to stock using Odin. It still does not create a preload.. Thanks in advance for your input. I have been lurking and flashing since my G1 but am now trying to be more active in the community.
Click to expand...
Click to collapse
I had the same issue after formatting my internal sd and the fix was to flash a touchwiz rom , I can see thats what you did