Develop Bugs

[Q] Help, won't boot any custom roms.

After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant

Did you wipe data and cache when you flashed the new rom?

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM

cobraboy85 said:
a few questions:
and i can verify the issue is something on your end, because the ROM you tried was mine, and nobody has had that issue (not booting it)
do this...
1. make sure you have the latest version of clockwordmod, don't use twrp
2. re-download my ROM (just for sake of not adding any other variables to your issue, because mine should boot)
3. put ROM on external SD card
before continuing... take a quick look at my thread here in QA titled "flashing ROMs correctly every time" .... so you can get some instruction on verifying MD5 of the download... don't worry, the thread will explain that you...
now proceed
4. boot to recovery
5. do a factory reset - 3 times do this, just to be thorough. people will say you don't need to, but like i said, just for the sake of removing variables
6. go to mounts and storage, format system 3 times - (yes, through recovery as well)
7. flash ROM, and reboot
EDIT*** i will say this, ALWAYS format system when flashing a new ROM
Click to expand...
Click to collapse
thanks for the info, will try this all out soon. I've been flashing roms for years now and have never run into anything like this, and as previously stated, this didn't occur solely with your rom which has me thinking something has happened to the phone itself. will get back to you soon and once again thank you

chucktdriscoll said:
Did you wipe data and cache when you flashed the new rom?
Click to expand...
Click to collapse
of course, wiped data, cache, & delvik

nyyankees1237 said:
of course, wiped data, cache, & delvik
Click to expand...
Click to collapse
my point is...
coming from a cm based ROM, or aokp, whatever you said... you would want to format system as well.

nyyankees1237 said:
After trying to flash a new rom after being on AOKP M1 for a little while (http://forum.xda-developers.com/showthread.php?t=1875923) the phone got stuck at the Black and white Samsung Galaxy SIII screen and didn't boot upon hitting reboot system now on cwm. Tried again, tried reflashing and the whole 9 yards wouldn't boot at all. So I turned to odin and went to the prerooted latest JB build (http://forum.xda-developers.com/showthread.php?t=1949687) and then reflashed touch cwm and tried to reflash the rom. Same problem. So, I odin'd back to the non rooted UVDLJA. Rerooted and reflashed cwm and blahblahblah. I said hmm maybe it's the rom, I then tried to flash this rom (http://forum.xda-developers.com/showthread.php?t=1993934) and when I tried to reboot system now after the process; again the phone got stuck at the black and white Samsung Galaxy SIII screen and did not boot. The phone works fine when I odin it to stock builds but refuses to boot custom roms. Can someone help me here? I haven't been able to find a solution for days. :crying:
PS I'm a noob, don't kill me lol
edit: forgot to include I have the Tmobile variant
Click to expand...
Click to collapse
I was having some of the same issues. I downloaded XquiziT's Superwipe and ran it by installing from external sd card. I ran it three times to clear everything out, then I wiped data, cache and the rest three times.
No probs for me after that.

Will definitely give that a try as well! Thank you! Will post my results when the holiday is over.
Happy thanksgiving
Sent from my SGH-T999 using xda app-developers app

[Q] Android 4.3 hanging on boot

I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.

captican said:
p
I had something that sounds similar when I was trying to update from task's 4.2.2 to 4.3. Kept stopping at the kernel screen ( after the usual wiping of caches and system). Finally, someone recommended that, in addition to wiping data, that I format data as well. This basically wipes everything (i was using twrp 2.3.3.1). After doing this, I reinstalled the ROM and gapps and it works now.
Not sure this is what you experienced but it sounded similar. Before doing anything else, be sure that you have a back up and that you have removed any external sd card, should you have to go back. Good luck.
Click to expand...
Click to collapse
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?

danielhep said:
I have an I747 on T-Mobile.
I recently installed SlimBean 4.3 on it, and it started up and worked fine. But when I went to restart it, it hung on the "SlimBean" screen. Never got to the bootanimation.
I read online that there's issues when coming from another 4.3 rom, and I had previously been running CyanogenMod 10.2, although it was a nightly and it crashed, corrupting my data. I decided not to try that again.
So after that experience with SlimBean, I tried to flash BeanStalk from the T-Mobile GS3 forum. This is also a 4.3 rom, and it ran fine on my I747, except when I went to reboot. It too hung on the logo.
And yes, I have wiped internal storage, and I'm running the latest version of TWRP. I even tried to flash Samsung's stock firmware with Odin, and it worked, but it wouldn't boot (or maybe I'm overestimating how quickly TouchWiz can boot). It overrode my recovery, like I was expecting, so I flashed TWRP with Odin and then proceeded to flash SlimBean 4.3 again. Same problem.
Does anyone have a solution to this? It's been driving me crazy. I will try some other 4.3 roms and see if they're all doing this.
Click to expand...
Click to collapse
I had the same problem since 4.3 came out. It has to do with partition tables... What i've done to correct the problem:
- Odin back to stock
- Format entire phone. (Complete wipe) + Dalvik and cache
- Odin stock with root
- Replaced TWRP recovery for CWM
- Flashed 4.3 ROM and VOILA
- I have tried every 4.3 rom ever since with no problems
Don't (Complete wipe) with Twrp recovery, it seems to mess up the partitions.
Hope this works for you
Cheers

danielhep said:
Yeah, I did that. I wiped everything I could and formatted data. Maybe I should try installing a different kernel?
With your issue, was it stopping on the first boot or did you get it running once then it stopped?
Click to expand...
Click to collapse
It loaded the first time and then rebooted, freezing on the kernel screen. I could get into recovery, and restore a previous ROM but it would hang up on 4.3. I described the steps I had taken when someone suggested reformatting data. I tried again and it is working now.
The method described in the other post may also solve your problem. I say that because I cannot update twrp to 2.6.1, at least via goo manager. I have not tried using Odin to update (yet).

I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app

I managed to load a stock rom back to the phone but again, it hung on the SAMSUNG screen. Took it to "a guy" and he did a
key sequence and got it to boot. Woulnd't tell me what it was........
ANy one know???

Apocalypse487 said:
I have this same as problem. It's annoying. I reflashed the rom 15 times yesterday. I'm gonna try and see if Deathstrings idea works.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This happened to me after I flashed back but formatting data got it to work (but I have had more problems with apps not installing properly but I learned how to deal with that...still cannot update TWRP via goo manager; waiting on trying it with Odin).

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

OMG HELP! Bootloop, download modes works, flashed with Kies and STILL bootlooping

I have the SGH-M919
I've rooted my phone and was running a GE rom
Everything was fine for MONTHS
Got in my car and plugged my AUX cable to my phone for music and the phone froze.
Force rebooted the phone and it started boot looping.
Rebooted to recovery (TWRP) and TRIED to wipe dalvik and cache and it FAILED, said it couldn't mount dalvik
Rebooted to recovery again and wiped all partitions and this time it worked so I proceeded to re-install GE rom, still bootlooping
Came home and tried to use ODIN to flash M919UVUAMDL and it failed.
Tried ODIN to flash M919UVUEMK2, also failed (sorry don't have the error messages right now)
Rebooted phone into download mode again and phone said there was an issue and to use Kies to recover
Installed Kies and started emergency recovery and that went through fine and the phone finished and STILLLLLLL BOOT LOOPS !!!!!!!!!!!
Copied the file that Kies downloaded (M919UVUFNB4) and tried ODIN again to flash that and it flashes fine but STILLL BOOT LOOPS
Obviously my Knox warranty flag is tripped and I don't have the money for the insurance right now.... so PLEASE FOR THE LOVE OF BOB does anyone have any other diagnostic tips or tricks to help me figure out why the F this phone is boot looping.

53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?

avelis26 said:
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
Click to expand...
Click to collapse
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app

I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.

lalec said:
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
1. Samsung WON'T reset my flag... they won't even TOUCH the phone in any way shape or form. I spent almost two hours dealing with them and being honest about the situation. And they STILL won't do anything at all. The rep I was speaking too even said the first thing they do is check that flag and if its popped, they put it back in the box and send it back with no further action. So I will not buy form Samsung ever again.
2. I'm not expecting instant responses at all and nothing I said should have been interpreted at such. I made the comment of 53 views in 4 hours and not a single reply ... I was hoping for a better ratio of responses than that.
3. Where are you getting "Not doing a full wipe before installed a different ROM..." I never said that I didn't... and if you read what I took the time to organize neatly, I specifically state that full wipe was what I tried BEFORE re-installing the SAME rom.
4. Can't try a different recovery if I can't even get the stock factory image to do an initial boot.

cybervyrus8587 said:
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
Click to expand...
Click to collapse
Which one did you flash ?
M919UVUFNB4
M919UVUEMK2
M919UVUAMDL
M919UVUAMDB
I've tried #3 but it gives me an auth failure....

Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love

TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know

avelis26 said:
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
Click to expand...
Click to collapse
Post deleted
☞ Sent from here ☜

baseballfanz said:
Post deleted
☞ Sent from here ☜
Click to expand...
Click to collapse
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.

Ok so .... I guess installing PhilZ... then full wipe, then flashing M919UVUFNB4 TWICE back to back did the trick.... no freaking clue how but it worked

I spoke too soon. Went through first boot. Got all the way to the end setup and then it rebooted on its own ... and now its stuck in a boot loop again

avelis26 said:
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Click to expand...
Click to collapse
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.

TigerDNA said:
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
Click to expand...
Click to collapse
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused

avelis26 said:
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
Click to expand...
Click to collapse
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.

TigerDNA said:
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
Click to expand...
Click to collapse
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?

Yea your Knox flag is tripped alright, you have zero chance if ever getting back to 0x0.... Nobody knows how to do that brother.
Sent from my GT-I9505G using xda app-developers app

avelis26 said:
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Click to expand...
Click to collapse
Just put the phone in download mode. Power off then volume up, home and power. You'll see it when you get into download mode.

TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
Philz's and TWRP both had small glitches on the GS4 4.2.2 Stock Rom.
I downloaded and installed the OUDHS-Recovery-jfltetmo-1.0.3.3.tar and have it all PERFECT now! You can search using exactly that filename and download it for your use. IT IS THE flashable Recovery Version.
I can, using Rom Manager, NAME THE BACKUP before booting into recovery, and it makes the backup just as I named it!
I can also recover using Rom Manager, and visually select what backup file I want to restore to, again, before booting into recovery!
CWM type backups take longer then TWRP backups to complete, but I have not had any instance that a backup I made couldn't be restored.
I did have that problem using "TWRP" and "On Line Backup". (No longer do I trust using those)
Hope this info helps your decision!
Good Luck and Aloha!

d2att won't boot ANY Touchwiz rom, including stock, after having a non-TW rom

At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.

which recovery/version do you have ?
are the touchwiz roms the same android version as the pac-rom version ?
checked the touchwiz md5 to make sure has not been bad downloads ? (i know , far-fetched for them all to be bad DLs. just a thought).
"err on the side of kindness"

First off when you went from CM/AOSP based ROM to TW did you wipe everything but external storage? When going from CM/AOSP to TW & vice versa you MUST wipe internal storage. If you do this & it still fails to boot you'll need to flash the stock recovery wipe with it & install stock. Then Odin TWRP & you're good to go.
You can get the stock recovery from enewman17's NE4 thread.
Just be sure to do your research. d2att is the easiest of all d2's to hard brick thanks to At&t not releasing full firmwares.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk

Chuckles5150 said:
Flashable AT&T Galaxy S3 NJ2 Stock Recovery Zip (Pulled last fall) Google Drive Links
https://drive.google.com/file/d/0B0lfMZeSyJnYT2xFbUxKVUR0RGM/view?usp=drivesdk
Click to expand...
Click to collapse
Nice!
? d2att Oct-M KrAkEn Kernel ?

Jaitsu said:
At a bit of a loss here. I have here a d2att/I747 that was working up until today on PAC-Rom, then I decided to wipe it clean and install a Touchwiz ROM. I tried S3RX, I tried a supposed Note V port, hell, I'm trying stock. None of them will finish booting. S3RX and the Note V port give me a perpetual boot logo, stock gets past the Samsung logo, plays the sound, then gets stuck at the AT&T logo. I've given each one at least an hour to do something, and they're apparently not going anywhere.
I've tried everything I know how to do; I've wiped EVERYTHING (system, data, internal storage, formatted data, the whole shebang) and nothing seems to make a difference. It's on NJ2 and I even just tried reflashing the NJ2 bootloader/modem, but that doesn't seem to have done anything either. Totally at a loss here. What could be causing this? I mean, it boots into download/recovery fine and always -starts- booting the roms, but never finishes. Could I have a corrupted partition or something?
EDIT: Oh, so I put PAC back on it and it boots again. So yeah, this seems specific to TW roms. I don't get it.
Click to expand...
Click to collapse
Flash slimkat ROM and then flash TW ROM. It will work I had same problem

Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?

Jaitsu said:
Oh wow, I didn't mean to abandon this thread. I haven't been getting email notifications 'til today for some reason. Anyway, yeah, I've wiped *everything* including internal storage; I'm flashing from an external SD. Nada. I was really hoping there was some NJ2 Odin-able package I could use that'd guarantee I wasn't screwing anything up, but oh well. Anyhow, I don't have the device on hand anymore (doing this for a family member), but perhaps I'll get it back and try that slimkat idea...? To answer mrrocketdog's question, no, actually. PAC is 5.1, every TW ROM I've found is 4.4. Shouldn't matter if I'm wiping every partition I can first, though, no?
Click to expand...
Click to collapse
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app

BakedOnSomeSour said:
Definitely try flashing the slimkat ROM. I had the same prob as you and read someone's reply about it. It fixed the issue for the touchwiz ROMs. After flashing slimkat go back to a touhwiz ROM. Do this before messing with the phone. I have a slimkat ROM on my SD card ready to be flashed at any moment for whenever I want to go back to touchwiz haha
Sent from my SAMSUNG-SGH-I747 using XDA-Developers mobile app
Click to expand...
Click to collapse
So do I have to flash Slimkat and then dirty flash TW? Seems like that'd have to be the case, otherwise anything it adds would get wiped away, unless it messes with partitions or something... I need to read up on this ****. That's weird.