Develop Bugs

CM10.1 Freezing issue and message not sent error.

Hey guys,
First post here,
i was searching around for my problem, and i haven't found an accurate answer so thought to share my problem and hopefully find an answer.
i am from Canada, Edmonton, and i am with Rogers.
First problem,
i run CM 10.1 and Most the NIGHTLY updates they were butter smooth and works great, until Update number CM-10.120130317 till the current update. All the updates i download, my phone freezes LOT! example of how it freezes , i try to unlock my phone, it freezes . I try to write something it freezes . and sometimes when its on sleep it freezes i can't turn the screen on again! so i always downgrade to CM-10.120130316 to have that stable ROM.
I did the wipe date /factory reset from the ROM manager, and wipe cache and dalvik. and yet the problem is not solve.
So my question is, dose anyone facing the same problem? or it's just me?
Second Problem
am having this beyond annoying notification, where it says my message has not been sent! but my message get's sent and all acts normal. But i always get notification and its never gone. I have screen shoot the problem. Is there a way i can fix this? i've have attached in the thread.
if you guys have any questions or want me to provide some information please do ask.
Looking forward to hear the feedback.
Cheers,

for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.

There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747

xBeerdroiDx said:
for starts, you're running nightlies and you need to remember that. i'm not an advocate of these, but thats just my opinion. you generally cant run a non-perfected piece of software and repeatedly dirty flash layers of updates on top. you will generally begin to experience bugs that can only be fixed with a full wipe and clean install.
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
Domoo said:
There's a warning that these builds are unstable and use them at your own risk. I use cm10.1 20130317 build and it is extremely stable. A few quirks but nothing major. I plan on sticking with it since the 3.4 kernel on the newer nightlies isn't optimized yet, which result is lower battery life.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thank you guys for the time to post in my thread. Alright, i will stick with update that runs well in my cellphone..
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Thanks in advance!

xBeerdroiDx said:
that being said, i would either 1) commit to these cm10.1 nightlies and perhaps even just stick with 1 of them thats working well for you or 2), find a stable 4.1 or 4.2 rom and install after a full wipe. backup first.
Click to expand...
Click to collapse
MH_91 said:
However for my second problem, do you know how i can fix that problem? i am talking about the message not sent notification.
Click to expand...
Click to collapse
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well

xBeerdroiDx said:
assuming you have a stable backup to rely on, i would wipe data/factory rest, wipe cache, wipe dalvik cache and reflash either your current update or (preferably) the one you were running with no problems before. perhaps flash the one listed by a user above that seems to be running well
Click to expand...
Click to collapse
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..

MH_91 said:
Yes, i am have backed up all my stuff. oddly, i did all that you have mentioned last weekend, and still i got those glitches and the text matter it was gone at the start, but i got it back again.
Noob question, what dose "Flash" exactly means? maybe i know what flash step is, but i didnt know it was called by that term lol..
Click to expand...
Click to collapse
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.

xBeerdroiDx said:
and you tried flashing a different (previous) version of cm10.1 when you did that? there's always a full wipe. that includes formatting /system in recovery.
flash = install.
Click to expand...
Click to collapse
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?

MH_91 said:
Interesting.. i have got an idea i will try to do it hopefully by tonight or tomorrow. and i will share the results.
i was thinking to manually download the latest update nightlies instead of my phone update it for me, and then do the wipe thing and then i install it manually, maybe that will fix my problem.
am using G cloud for my backup and it dose his job pretty well. I wanted to use the Titanium backup but it kinda was too complicated for me.
Why they just don't call it "install" instead of Flash then lol?
Click to expand...
Click to collapse
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps

xBeerdroiDx said:
avoid using the OTA update feature on your phone. i didnt know you were doing things that way. you'll notice many more bugs and problems that route.
you are on the right path when you say download the actual update (latest release) yourself. make sure you have the gapps to go with it. boot into cwm, wipe data/both cache, flash rom, flash gapps
Click to expand...
Click to collapse
Will do mate! Thank you so much for your kind help! i really appreciated it. i will for sure share the results with you very soon.
Have a good one.

[Q] Any JB 4.3 (or other JB) roms with working ringtone?

Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!

brettbee said:
Having only dabbled with rooting and upgrading a Evo View tablet, I jumped into the deep end with my Incredible 2.
I got it to S-off and rooted and have been trying a few different ROMS (mostly chillybean's) and have what seems to be a common problem:
Sound works fine until a call is received. The ringtone fails to play and then sound doesn't work at all until its reset. I have had success resetting the sound by activating Google Voice Search with a long press of the search button. This seems to be true for CM10.2 and PAC. I didn't test this on an Evervolv because 3G never comes back on after Wi-fi has been turned on.
Has anybody had better luck with a particular 4.3 ROM? Does this sound issue affect pre-4.3 JB roms?
Thanks!
Click to expand...
Click to collapse
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.

try beanstalk 1.300
brettbee said:
I answered part of my own question:
I confirmed that the Evervplv nightly 2013.09.24 has a working ringtone. But once WiFi is turned on, 3G is off until reboot.
Click to expand...
Click to collapse
I have been using beanstalk 1.300 with the b-team CM kernel.it has 4.2.2 and everything works! its fast and smooth with great battery life the 4.3 roms have some issues so I am gonna stick with this one

AFAIK everything in the newest Evervolv works.

phillibl said:
AFAIK everything in the newest Evervolv works.
Click to expand...
Click to collapse
Are you using a nightly? Which one?
Does 3G come back after WiFi is turned on?

Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.

kahlil88 said:
Chillybean updated his CM10.2 ROM -- the 20130929 build has the sound issue fixed.
Click to expand...
Click to collapse
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Thanks!

brettbee said:
The 929 rom is not working for me and I know at least of couple of other folks in the same situation.
Are you using the 929 ROM with sound successfully? What - exactly - did you do to install it? I'm wondering if it's a I'm-doing-something-stupid/wrong thing or maybe a hardware revision thing.
Click to expand...
Click to collapse
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.

kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....

kahlil88 said:
Flashed it like any new ROM. Backup important data and reboot into recovery mode. Once in recovery mode:
Factory reset
Wipe cache
Advanced -> wipe dalvik cache
Mount/unmount -> format system
Format boot
Install AntiVenom SDW
Flash a ROM
Flash GApps
Wipe dalvik cache
Reboot and you should be golden. I've had it hang at the boot screen a few times, had to start over and skip installing GApps until I was sure it would boot.
Click to expand...
Click to collapse
brettbee said:
Thanks! I'll give that a try. I wasn't quite as thorough with wiping/formatting as you were. Fingers crossed....
Click to expand...
Click to collapse
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?

brettbee said:
Well, that didn't work for me. The only thing I didn't do was "Format boot." I couldn't find that in Revolutionary CMW.
I'm thinking there's something different about my phone. Hardware? How I rooted it?
Click to expand...
Click to collapse
What version of gapps are you installing? Try flashing the ROM without installing gapps and see if it will boot, then if you're successful go back into recovery mode and flash gapps-jb-20130813-signed.zip from here.

funny question, does docking mode work with these roms?

Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app

flinzak said:
Check Chilly's forum. The Inc S Dev posted a flashable fix for the sound problems. I flashed it and all is fine.
EDIT: Damn autocorrect...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks - found it and downloaded it! I'll give it a try when I can have my phone out of service.....

I flashed Evervolv 10/30 nightly yesterday and it looks like they have the 3G/WiFi toggle issue resolved. The quick settings were missing but, I'm guessing that'll be corrected in the next build. Also, flashed B-Team Kernel. 4.3-s2w version resulted in bootloops but, the 4.3-v2 version worked just fine. No sound issues as far as I can tell.

Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks

jonatcer said:
Does the latest Everlov nightly work? Also what are you all referring to when you say Chilly's forum, the "Inc S dev fix", and AntiVenom SDW? I went through 5-10 of the most recent pages on Everlov and didn't see any of these things, so would someone mind providing links?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6

ArslanQureshi said:
http://forum.xda-developers.com/showthread.php?t=2049902 this is chillybean's thread you can find AntivenomSDW in the other section of the OP (first post) the inc S dev fix can be found here http://d-h.st/1h6
Click to expand...
Click to collapse
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.

jonatcer said:
Alright thanks a bunch. One more question though - what exactly is AntivenomSDW? Where can I find more information on it? Google is little help here.
Click to expand...
Click to collapse
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean

ArslanQureshi said:
its an flashable zip that completely wipes your device it is highly recommended to use whenever you flash a new rom it is developed by Chillybean
Click to expand...
Click to collapse
Alright thanks a bunch.
Would you, or anyone else still reading this thread, care to weight in on whether Evervolv or CB's rom (Which? Beanstalk?) is more stable?

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

Boot loop at Samsung welcome screen when attempting clean install.

I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk

ojai00 said:
I am currently running SkyNote Air and want to do a clean wipe and start fresh. I've done this before without a problem but am having trouble this time around. After a clean wipe and ROM install, the phone will boot but after seeing the "Android is upgrading, Starting Apps" screen and momentarily displaying the Welcome screen the phone will go into a loop. Seems to happen after the phone connects to the network. I can interact with it to reboot into recovery if I'm quick enough.
From the searches I've done, I've already tried clearing cache and Dalvik and factory reset without any luck. I used Philz to wipe for a new ROM and TWRP to wipe internal storage as well without any luck. I've tried installing the ROM twice before rebooting recovery. Fix Permissions from TWRP also hasn't helped. I already had the 43paramtz.tar flashed and reflashing it does not help either. I have not tried the One-click method yet. That seems the only thing left to try. Just want to see if anyone else has any suggestions. Thanks in advance!
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Are you on T-mobile ?

dicksteele said:
What bootloader are you on ??? Did you do the 4.3 OTA ?
Click to expand...
Click to collapse
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.

ojai00 said:
I believe I am on a 4.1.2 bootloader (I317UCAMA4). I have not restored to stock or done a 4.3 OTA.
Click to expand...
Click to collapse
And you're on T-Mobile ?

dicksteele said:
And you're on T-Mobile ?
Click to expand...
Click to collapse
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.

ojai00 said:
Yep. Using an unlocked i317 on T-Mobile with the AWS Mod. My first instinct was to remove the SIM since the phone seemed to be restarting once I was connected to the network but that didn't work either.
Click to expand...
Click to collapse
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?

dicksteele said:
Ahhhh.. Like it says in your signature.... :cyclops:
Yea I'm awake.
Have your ever flashed anything else besides Sky Air ? That's the one you have reflashed after Philz/TWRP wipes right ?
Click to expand...
Click to collapse
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!

ojai00 said:
SkyNote is the only 4.3 ROM I've tried. Yes, that was the ROM I reflashed after the full wipes. I've been flashing SkyNote from version 8 onwards and am now running the N3 version. I've seen some people have issues with the N3 version but not the Vanilla version. I haven't tried that one. I've been following MeanBean but I'm worried if I can't even get a reinstall of SkyNote Air working my chances of another ROM will probably be the same!
Click to expand...
Click to collapse
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....

dicksteele said:
MeanBean is pretty sweet. You have to remember to run the fixdata.sh.
I'm thinking you should give this a try, a stock ROM.
http://forum.xda-developers.com/showthread.php?t=2589891
It's still flashing from a custom recovery.
You've done everything short of sacrificing a chicken.
Gotta run to a mind numbing meeting.....
Click to expand...
Click to collapse
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:

ojai00 said:
I'll give it a shot. Good luck with the meeting. Thanks for your help! :highfive:
Click to expand...
Click to collapse
Good luck.... Hopefully it works.

Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.

ojai00 said:
Tried flashing the stock deodexed ROM in Philz and still the same result. I can at least make it far enough to the home screen but am still getting the same reboots. I also upgraded to the 4.3 bootloader from seanz thread here (http://forum.xda-developers.com/showthread.php?t=2502464) without luck. I wonder if flashing the ROM in Odin will be any different? I have my doubts but want to hear it from someone else.
Click to expand...
Click to collapse
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.

dicksteele said:
If you're game you could try this
http://forum.xda-developers.com/showthread.php?t=2618447
If you do sections 1 and 2, and don't get boot loops, you can flash that stock/root/odex ROM.
Click to expand...
Click to collapse
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.

ojai00 said:
Thanks again. I'll try that next. Attempting the Odexed version of Zen's package first.
Click to expand...
Click to collapse
Sounds good. Good luck.
Not sure what is residual and causing the boot loops.

So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.

ojai00 said:
So I dirty flashed the odex version and that seems to be stable. I then factory reset to wipe it clean and that came up fine. Going to try wiping completely and installing Stock Odex again.
Update: Rooted Stock Odex seems to be the only one that is booting up fine. I then flashed SkyNote Air without any wipes and it was fine again. Once I tried to factory reset to defaults after Air is installed (wiping cache and Dalvik in the process), the boot loops begin. Guess this is what I'm going to have to do if I want to start fresh on any ROM.
Click to expand...
Click to collapse
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.

dicksteele said:
Too wierd. At least you found a path.... Not optimal, but functional.
I'm fighting why I can't flash a custom recovery now.
Click to expand...
Click to collapse
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.

ojai00 said:
Just a thought even though I'm sure you verified. You're sure you're trying to flash the proper recovery for the device? I know TWRP and Philz make a specific version for the i317 with t0lteatt in the file name.
Click to expand...
Click to collapse
Yepper. They live on my machine and phone. Thought it was an ODIN thing, just rooted my phone.
I do so much crap to it maybe that's was I was missing .... We'll see.
EDIT : And that was it. Interesting .....

[Q] Issues with my G Pro

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