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
Related
So today i have had nothing but problems with flashing roms. I was on the PAC rom nightlies, but decided to go back to touchwiz roms due to the wifi calling. I tried flashing wicked v4, booted fine but once i reboot, got stuck at the samsung boot logo. tried reflashing/wiping/flashing other roms, including PAC again, all would result in getting stuck at the samsung boot logo. so i used odin to go completely back to stock. That wouldnt boot at first, so i tried wiping data in stock recovery, luckily that got it to boot. I then re-rooted and tried to flash infamous 2.5. same thing, got stuck at the samsung boot logo. finally, i was able to get infamous google edition to boot, but isnt what i want (since it doesnt have wifi calling), but is the only thing i could get to boot.
So does anyone have any idea why my phone is being so moody, or am i just having a bad day?
edit:i will attempt to try and flash infamous 2.5 when i get out of work to see if my phone is in a better mood, but right now i just need a working phone
edit 2: if its relavent, before i used odin, i was using twrp recovery, but after odin, i used clock work mod touched
I also having the same problem, by just rebooting on jedi it goes into bootloop. My guess is either the kernel or the recovery (no expert). On my friends ATT it bootlooped only because I didn't flash the required Ktoons kernel. As for Tmobile I'm not sure of the bootloops, but to fix it i just dirty flash a rom and it works but it happens usually after i flash some add ons.
Both of the problems here are kernels, change to another kernel, should fix these problems.
Good luck
If that does not work, come back here, we will figure something else out.
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
TheAtheistOtaku said:
just tried flashing infamous 2.5, this time with ktoonz kernel, same result, stuck at samsung.
Going to try wicked v4 this time
Click to expand...
Click to collapse
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
mgbotoe said:
You tried infamous with it stuck kernel?
But I know what you mean been experiencing that with some Rom as of late not sure what's the deal...
Famously Infamous
Click to expand...
Click to collapse
yes i have tried it with the kernel it comes with, same result.
still downloading wicked.
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
mgbotoe said:
What recovery are you using? I know twrp latest is very buggy for most people...also I heard its not fully cleaning people phones for a flash and what not..Im quite sure its a recovery bug for you
Click to expand...
Click to collapse
ive used twrp before i odind back to stock. but now i have been using clockwork mod touch, still having the same problem
after flashing kernal wipe cache,dalvik and fix permissions that should work
LIL_ROOKIE said:
after flashing kernal wipe cache,dalvik and fix permissions that should work
Click to expand...
Click to collapse
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
TheAtheistOtaku said:
i have been doing that after every new flash.
anywho, wicked v4 is booting with ktoonz kernel, and after a reboot its continuing to boot, so im not going to press my luck and stay on wicked. though i still would like to know whats going on.
Click to expand...
Click to collapse
You're not "formatting data" correct? Should only "wipe data". Not format.
norml said:
You're not "formatting data" correct? Should only "wipe data". Not format.
Click to expand...
Click to collapse
no im not formatting data lol i know the difference
TheAtheistOtaku said:
no im not formatting data lol i know the difference
Click to expand...
Click to collapse
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
norml said:
LOL, I'm sorry, just that I have seen soooo many ppl getting bootloops or stuck samsung screens, because of that and also not knowing exactly what to wipe. Just trying to help.:victory::highfive:
Click to expand...
Click to collapse
its no problem
Check SD card
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Wow, SanDisk sd cards have been really sucKing lately. I'll try taking out my sd card if it ever happens again
Sent from my SGH-M919 using Tapatalk 4 Beta
31337_haxer said:
I had a similar issue where my S4 just decided to go into a bootloop on the way to work. A coworker of mine's wife's S3 did the same exact thing and we were finally able to pin it down to both having a SANDISK 32GB micro sd card. Once I pulled the card (after having ODIN'd back to stock and pulling my hair out my desk =/) the phone booted right up. Since all I had on there was music I stuck it in after the phone booted, reformatted it from the stock odin restore (MDL), and I haven't had any issues since. Just figured I'd let you know what caused me to go insane for a few hours since it wouldn't boot after flashing anything at all and only occasionally boot from a clean odin restore or fresh wicked flash. After talking to another guy at work that has a note II, S3, and S4 apparently I'm not the only one that's had this issue pop up.
Since I fixed it I've been running Infamous GE (Infamous Kernel) and The leaked GE 4.3 build without issue.
Click to expand...
Click to collapse
I'm using a PNY SD card... just flashed the 7.2 version of infamous, and out of 20 boot attempts, 2 or 3 booted past the GS4 logo.
seems to work if I go back into recovery and factory reset, boot again, and that's the only way I've gotten past the GS4 screen.
Im using TWRP
I've since figured out the problem. For whatever reason when you wipe the cache & dalvic with twrp, sometimes something happens where your internal memory fills up completly, leaving you with no space. Formating the internal from twrp fixes that, but of course you loose everything not on your sd card. Can confirm this problem in twrp 2.6.0 also, since it happend a few times for me
I now just use clock work mod touch, and haven't had the problem since. Pity though,I prefer twrp
Sent from my SGH-M919 using Tapatalk 4
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).
Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:
emili0estavez said:
Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:
Click to expand...
Click to collapse
Which 4.3 ROM(S) are you having trouble with?
Please update us also what provider you have along with more info about your phone.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Bruce Lee said:
Which 4.3 ROM(S) are you having trouble with?
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right now im on the quantum v2.20. This problem happens with any 4.3 rom though Tasks,PA,Liquid smooth they all give me this error. Tried wiping the phone over and over nothing. I even installed clean without restoring data or anything and can never reboot properly. In order to reboot properly I have to go back wipe memory, factory reset, wipe everything else and install Rom again.
emili0estavez said:
Right now im on the quantum v2.20. This problem happens with any 4.3 rom though Tasks,PA,Liquid smooth they all give me this error. Tried wiping the phone over and over nothing. I even installed clean without restoring data or anything and can never reboot properly. In order to reboot properly I have to go back wipe memory, factory reset, wipe everything else and install Rom again.
Click to expand...
Click to collapse
Well, from what it sounds it could be the recovery, so make sure that it is the latest version and also make sure that your bootloader is updated to one from the 4.1.2 OTA update. There's a post on the Quantum thread about how to update your bootloader (something necessary to flash any 4.3 rom). Just please make sure to read a lot BEFORE flashing so you don't end up with a paperweight. I assume your on AT&T, correct? If this is the case and your phone is a SGH-I747, the update should go fine. If this doesn't work, I would try asking super nicely on the official thread and explain everything with as much deatil as possible, and they'll be able to help you, since it's not one of those threads that get furious at asking questions in the dev thread. Hope this helps.
emili0estavez said:
Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:
Click to expand...
Click to collapse
or you can go back to 4.1.2 which is mostly stable and works fine with no issues or problems compared to 4.2.2 or 4.3 AOSP/CM Roms
I'm having the same issue, but for me my phone gets soft bricked and I have to reformat internal storage for anything to work. I bought my phone with 4.1.2 already installed, and my recovery is twrp 2.6.30, which is the latest one
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey everyone,
Greetings from Jamaica!
I've had my e980 OGP for about 2 months now
When I got it, it was running the 10p firmware. After a while, I realized that i'm having random mobile network drops, sometimes I get a good signal, sometimes I don't, sometimes it goes and comes. I was advised to flash a custom rom, I rooted using the VROOT method, installed freegee from the play store and flashed cwm. I then flashed cm11. When I flashed cm11, it worked perfectly! after about 5-10 mins of first-time-use setting up, it froze, then started rebooting, after that it randomly rebooted constantly for the remainder of that day. after trying various custom roms, I decided to flash back to stock, but I flashed the kit kat stock firmware using the Flash Tool and the TOT file. Once v20g was up and running, the reboots stopped, but the signal issues came back, I'm clueless as to what would cause my issue, but I'm confident I can get some answers from the geniuses here, so plz, help a brotha out?
Any help? :fingers-crossed:
YOu could try changing the modem/baseband, there are a few floating around that you could flash.
luisoman2000 said:
YOu could try changing the modem/baseband, there are a few floating around that you could flash.
Click to expand...
Click to collapse
Ok Thanks much. Is there a possible diagnosis for the random reboots in cm11? maybe a custom kernel could fix, or is there a flashable version of the e98020g kernel that I could flash on cm11 to make it... stop rebooting I guess? I'm kinda noob with this phone
blazin876 said:
Ok Thanks much. Is there a possible diagnosis for the random reboots in cm11? maybe a custom kernel could fix, or is there a flashable version of the e98020g kernel that I could flash on cm11 to make it... stop rebooting I guess? I'm kinda noob with this phone
Click to expand...
Click to collapse
Dunno, i don't use AOSP based roms, prefer the stock look.
Any fixes?
I realize that no matter which custom rom I try, I still end up with random reboots. @madmack is there anything that could be done to stop the reboots? I tried flashing that stock kernel you made for kitkat onto PacMan but i'm stuck at the LG Logo. Any help? Please?:crying::crying::crying:
blazin876 said:
I realize that no matter which custom rom I try, I still end up with random reboots. @madmack is there anything that could be done to stop the reboots? I tried flashing that stock kernel you made for kitkat onto PacMan but i'm stuck at the LG Logo. Any help? Please?:crying::crying::crying:
Click to expand...
Click to collapse
Any Ideas?
blazin876 said:
Any Ideas?
Click to expand...
Click to collapse
When you install custom roms, do you make a complete wipe of your system,including factory reset?
blitzkriegger said:
When you install custom roms, do you make a complete wipe of your system,including factory reset?
Click to expand...
Click to collapse
Using CWM, I wipe data/factory reset + Wipe Cache + Wipe Dalvic Cache
Use hacked twrp and make sure you wipe it clean ..completely clean. Install ROM .. Gapps.. And boot up ... Run build m8 or m9 cm.... But I run stock kk due to deep sleep issues for a lot of our Roms... Some get deep sleep and some don't ... But stock kk is where its at for me
2SHAYNEZ
Since day one I had this , well..., phone, I had signal drops to-noservices.
AT&T and rogers, I barely use this phone, since I had it, only problems.
To double-down on what Shayne said, wipe SYSTEM as well, when jumping between AOSP/LG sources or JB and KK. Have you altered preferred network or APN at all? Leaving the defaults delivers the best stability if you're on AT&T. Finally, if you click settings--> mobile data --> menu, there are background data/auto-sync data options buried in there.
Sent from my Nexus 7 using Tapatalk
JCred said:
To double-down on what Shayne said, wipe SYSTEM as well, when jumping between AOSP/LG sources or JB and KK. Have you altered preferred network or APN at all? Leaving the defaults delivers the best stability if you're on AT&T. Finally, if you click settings--> mobile data --> menu, there are background data/auto-sync data options buried in there.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ok, Thanks for the tips, I just flashed the most recent CM11 release using all the directions I got here so hopefully it works. I'm in Jamaica and so I dont have access to AT&T lol. CM11 gives perfect stability as it relates to mobile network tho...
[EDIT] I still get random reboots, apparently less frequent tho
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.