I have been having issues that i can't resolve. When i flash a rom that is not TW based, my radio starts to have issues. For the first few hours after i flash a cm or asop based rom everything is fine. After that i start having connectivity issues. Usually it starts with no 4g then moves to total loss of data. I lose most roaming ability and have no data when i roaming. I've tried going to a TW rom, updating prl and profile then nandroiding back to CM but with no luck. I've been able to install a TW based rom while in roaming and everything starts working fine. Wondering if anyone has had this problem or if anyone knows a fix. Thanks
Wartouched said:
I have been having issues that i can't resolve. When i flash a rom that is not TW based, my radio starts to have issues. For the first few hours after i flash a cm or asop based rom everything is fine. After that i start having connectivity issues. Usually it starts with no 4g then moves to total loss of data. I lose most roaming ability and have no data when i roaming. I've tried going to a TW rom, updating prl and profile then nandroiding back to CM but with no luck. I've been able to install a TW based rom while in roaming and everything starts working fine. Wondering if anyone has had this problem or if anyone knows a fix. Thanks
Click to expand...
Click to collapse
try to just flash the md4 kernel after the switch to 4.2.2+ not the full rom just the kernel
Still having issues
I have tried flashing different radios while on a cm rom. This seams to have no affect. Even with a older radio flashed I still have connectivity issues.
mrwetwork said:
try to just flash the md4 kernel after the switch to 4.2.2+ not the full rom just the kernel
Click to expand...
Click to collapse
Please DO NOT flash a Touchwiz Kernel on any AOSP ROM. That's just asking for trouble.
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
I've been searching for answers for a while now including blogs and videos on numerous websites, but I can't seem to find any answers. I am typically pretty good at flashing anything on my phone, researching for answers, but I am definitely running into a wall at this point. I will admit, compared to most posts on here, I do consider my self a n00b still, so I will apologize in advance for sounding ignorant.
I have an SGH-I747 stock 4.3 i747ucuemjb stock kernel rooted w/ TWRP 2.6 and busybox installed. SuperSU updated and binaries updated. SuperSU asked to block knox, and by the looks of it (meaning no more error messages of apps being blocked) everything is running great on the phone. My problem is that I can't flash any custom roms on the phone. I've tried just about anything I can think of (from 4.3 to 4.4.2) and TW based, aokp, cynmod, etc.. I'm getting a prop error with either it stating that the rom is intended for d2spr when my phone is obviously a d2att. But mostly all the roms I've tried have been just flat out failing. I can't even do a backup within TWRP, it also fails.
I've had to re-flash my stock 4.3 rom several times this past week b/c if I try to flash anything over the stock rom (keyboard, roms, etc.) the phone buggs out and touchwiz crashes to the point it gives me a black screen with the pop-up indicating that Touchwiz has stopped working and won't let me hit close or ignore. Even after rebooting the phone, that's all I see. At this point, the phone will vibrate in a peculiar pattern (buzz----------buzz-buzz-buzz) and it will repeat that pattern times infinity.
I am desperate for suggestions. I have a strong feeling it's kn*x causing all the problems. I have learned to accept my mistake by installing the OTA 4.3 aka sucker. But I need to be on a custom rom again.
Are there any success stories with specific roms? Are there knox based roms?
Any help will be greatly appreciated.
I had a similar issue this week....this is what I did after trying a number of things. Mine is finally up and working, and I don;t know for sure if this is what caused it to work or not....but its worth a shot. I formatted the internal data, wiped cache, wiped dalvik....I did all of this about three times each. I then flashed the mjb bootloader and modem, wiped cache, wiped dalvik, then I flashed the AOCP ROM.....finally I was able to use my phone. After I got that ROM up and running I then went back and tried flashing other ROMS I previously couldn't..they all work now. I am not sure why, but it worked, could just be coincidence. I used CWM for recovery BTW.
Flashing the boot loader may have done the trick. That's the only thing I haven't tried bc I keep reading warnings about potentially bricking the phone when flashing the boot loader. Are you on a sgh-i747 also? If so, what bootloader did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Castillo2.0 said:
Flashing the boot loader may have done the trick. That's the only thing I haven't tried bc I keep reading warnings about potentially bricking the phone when flashing the boot loader. Are you on a sgh-i747 also? If so, what bootloader did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yes i have the sgh-i747...and I flashed the MJB bootloader...so I can't go back to any ROM before 4.3.
Yeah i had a very similar issue too. I was on TWRP as well but then i switched to cwm and everything works fine now. I too am on the updated bootloader but you can still flash 4.1.2 roms that don't contain a bootloader. I'm currently running hyperdrive which is 4.1.2 based, no problems at all.
Sent from my SGH-I747 using Tapatalk
Hi there, I am not new to installing Roms in any way but I accidentally installed a d2lte Liquid smooth ROM instead of what my phone is, a d2att. So when installing the above ROM I did everything what I was supposed to do (clean install, format system). However, whenever I go on any ROM (Such as Quantum or Omni) I get an error as soon as it boots up, and my signal keeps turning on and off. I wiped data, cache and dalvik twice and go to a new ROM and the problem persists. For some odd reason, Carbon ROM works but I need a different one due to battery drain. I've never experienced this problem ever and I was hoping someone could please help me out?
Have you tried re-flashing the modem?
audit13 said:
Have you tried re-flashing the modem?
Click to expand...
Click to collapse
Yes i tried that earlier but still no luck. It's weird though how there was no problem on carbon rom and yet there was a problem when i went back to the Quantum Rom. Something happened on the LiquidSmooth Rom but i don't know what. I will again try reflashing the modem though thank you.
EDIT: Re-flashing modem did not help
Is it possible to use Odin to get back to a completely stock rom? If you have a 4.3 bootloader, you can't use Odin to flash a stock ROM.
A way to get back to a stock ROM for those on the MJB bootloader has been provided by enewman17. See AT&T I747 UCUEMJB Stock Restore in the development forum.
Ok so here is the deal: I rooted and flashed cwm touch. I flashed PAC man ROM 4.4.2 nightly and after installing like 15 or so apps from the play store, my WiFi stoops working. It won't pick up any access points (I know my WiFi router is fine). So after being fed up I do a factory reset/wipe and flash PAC man ROM 4.4.2 again, this time it works fine. Now I did a full wipe and flashed carbon ROM 4.4.2 nightly and same problem: WiFi works fine and after downloading many appsit spontaneously stoops working. Not wanting to loose all my settings I just did, I reflashed the ROM and wiped the dalvik cache and cache but WiFi still doesn't work. Please help thanks!
Maybe you need a different modem than the version you've been using?
audit13 said:
Maybe you need a different modem than the version you've been using?
Click to expand...
Click to collapse
Its weird I thought that may be the case but I think the modem should work fine with my hardware... And it was working flawlessly for over a month (after I flashed PAC man ROM the second time before I switched to Carbon)
drewstopher said:
Its weird I thought that may be the case but I think the modem should work fine with my hardware... And it was working flawlessly for over a month (after I flashed PAC man ROM the second time before I switched to Carbon)
Click to expand...
Click to collapse
I have seen posts where updating the bootloader required an updated modem. I suggested updating the modem in case you updated your bootloader. All this being said, it is weird that it just stopped working. Unfortunately, I don't what else to suggest other using a stock ROM for a while to see if the problem reappears.
audit13 said:
I have seen posts where updating the bootloader required an updated modem. I suggested updating the modem in case you updated your bootloader. All this being said, it is weird that it just stopped working. Unfortunately, I don't what else to suggest other using a stock ROM for a while to see if the problem reappears.
Click to expand...
Click to collapse
Thanks I just did a full wipe and flashed seems to be working fine now..... But still weird thanks for input!