I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
mooter said:
I have to post here because I'm a massive lurker and haven't got the post count for the development forum!
Firstly, excellent to see Task back in action for ICS! I was considering going back to stock for the OTA following today's ICS release but figured seeing as I was already rooted I might as well stick with custom roms.
I installed Infamous 2 (1st Aug) no problem at all, smooth as silk for a day 1 release! I used it for a bit before seeing Task was back with his first ICS so thought I'd stick with what I know best and completed the process again for his rom.
Install went fine, factory reset/wipe everything, install from .zip and booted first time no problems. I didn't go through the Google setup, or wifi, in order to let the rom settle, then I rebooted after 10 mins and the problem started. I got the following error on screen every 10 seconds:
android the process com.android.phone has stopped working
It would hang every time (unsurprisingly) and I couldn't access files via PC either, despite MTP connection showing. I've now restored back to Task14 from recovery backup and I'll wait for some more mods to be done before trying again, but thought I'd share my experience here in the hope it might help others/Task sort things out if it happens to them.
/refreshes the forum over and over again impatiently waiting for the real goodies to start flowing
Click to expand...
Click to collapse
logcat or it didnt happen.
task650 said:
logcat or it didnt happen.
Click to expand...
Click to collapse
I see some logs in the root folder, is that what you're referring to? I'll happily help you investigate if I can but it'll help if you point me in the right direction. Actually, maybe I'll try again and see how I get on? Restoring from backup was pain-free so not much to lose but 20 mins
Regardless, I very much look forward to seeing your work progress on this one over time! I know you're busy but superstars have obligations dude haha ;D
edit - trying again now with logcat reader installed - I'll report back!
do you have Ti backup installed? I would first try to see if there is some kind of phone apk in there. If there is try to clear the phone apk data and cache. If that doesnt work maybe try freezing it. Its strange that you have this error since tasks rom is a stock galaxy tab 10.1 ics build. Maybe try to wipe everything again and follow tasks instructions one more time step by step. sometimes weird things happen and a reflash might fix that. And just a stupid question but you have the wifi p7510 tab right
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
abc.mikey said:
Hi,
Not sure where to report this kind of thing but I seem to be getting frequent lockups on my S2 with the Resurrection Remix 3.1.3 that I wasn't getting with the previous 3.1.2.
Click to expand...
Click to collapse
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Donnie Sins said:
You mean freezes and/or fc's? You actually have to ask in the RR-thread, but I understand you only have posted 8 posts for now.
Remember RR 3.1.3 is still very new and under development, and isn't as stable as 3.1.2 is. If you want more stability, flash the 3.1.2-version.
And did you flash it with a full wipe? It's a must.
Sent from the Matrix
Click to expand...
Click to collapse
Thanks for the replies!
It freezes as in apps start becoming more and more unresponsive, sound if playing starts to stutter more and more until it ceases playing at all and phone us completely unresponsive except to a long hold if the power button. Sorry but I don't know what FC is.
I upgraded because the notifier informed me that there was a new ROM; I see now that it's a good idea to wait a bit now. I've downgraded to 3.1.2 which I've been very impressed with the responsiveness and stability of.
My first attempt at installing 3.1.3 was an attempt at an upgrade but didn't work very well as I think I followed the wrong procedure. But the issues I was having were with a wipe and reinstall following all the steps in the manual plus an undocumented one to install the keyboard patch for the S2 to make the keyboard work at all.
TheATHEiST ok will try reporting there next time, hopefully my post count will allow it by that time
TheATHEiST said:
The normal procedure would be to first read through the posts on the roms dev thread and see if others have had same issue and what (if any) solution is. if you dont see any comments then make one of your own explaining issue (You wont be able to do this until you have 10 posts).
Before leaving any replies on topic you should try doing a wipe/factory reset in recovery then boot to system see if you have same issues. Its advised to wipe recovery before each rom flash (Unless you have stock kernel, If you have stock rom/kernel you need to flash custom kernel before wiping. You can mostly ignore wiping if you are updating to new version of same rom however its still advised as somtimes can lead to issues.
You dont need to worry about apps/appdata and sms etc as you can easily backup them with Titanimum Backup Pro and SMS Backup etc. Get pro version of TB as you can batch backup/restore app/appdata in one go.
Click to expand...
Click to collapse
I can confirm that I have followed all the procedures (flashed at least 20 differet roms by now) and can also confirm that I have been facing a laggard and slow responsiveness throught out the rom, with couple of FCs and lockups as well. At least thrice I had to force reboot. Also I have done an extensive search and the only thread I could see on the similar issue was this.
I am posting here because of same reason as OP as I have a low post count but I have been following xda for over 2 years now.
I know the obvious answer is to downgrade to 3.1.2 or not install RR at all. This is "just reporting", you know!
Thanks!
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Nevethen5 said:
Hey, I am also experiencing the same thing as the OP and 7mojo. My S2 would randomly freeze and the only way to get it working is a hard reboot. It happens randomly but quite often, I would say atleast 3 times a day. I have done a full wipe and re-install but no luck. Like 7mojo said, I too have searched the web and the only thing relating to this issue is this thread. Anyone else having this problem? any solutions? I hope there is an update soon.
Click to expand...
Click to collapse
I've had similar problems.. am guessing its due to bugs in the unstable rom. Will have to wait for the dev to release an update. For the time being, better stick with 3.1.2.
As for me, I switched to JellyBAM. And then to CM10.1. And then to Omega.
"To err is human, to forgive is divine"
Sent from my SGS II
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hello first of all I would like to thank all the great developers for the great ROMs out there.
Second I would like to warn everyone that this is a "first world problem rant" that I'm about to write up with a legit frustration I have.
I have a rooted Samsung Galaxy S4 from ATT and the only reason I got this phone over any other Android phone is the great camera and the screen.
I absolutely hate TouchWiz. It's bloated, slow and painfully ugly (to me). For this reason I decided to try out Flashing roms.
For the last couple of weeks (months maybe?) I have been using Cyanogenmod 10.1 stable with not many problems. Mostly camera issues but no biggie.
My frustration is the following: CyanogenMod has had two stable updates for my phone to go from 10.1 to 10.2 and, though it flashes perfectly, every time I reboot the phone the phone gets stuck on the "Samsung Custom (lock)" screen and I am forced to go into TWRP and reflash 10.1+Gapp from my SD carfd.. This happens EVERY TIME. With CM10.1 I can restart the phone just fine by the way. It's 10.2 and other Roms that make get stuck on the Samsung Custom (lock) screen.
So i decided to try out Gummy ROM because Kit Kat
I put the ROM in my SD card, Formated, Wiped and Installed. Worked like a charm until the camera wasnt working that well. I read the forums and said to restart to fix the camera.. Guess what?...AGAIN....Stuck on Samsung Custom (lock) screen.
My frustrations is that pretty much EVERY Rom that I have tried minus CM10.1 has done this to me and I have no idea what I'm doing wrong.
I have tried battery pulls, waiting 30 seconds, wiped dalvik, cache, etc. Fixed Permissions....everything and I have to reflash the ROMs almost 99% of the time unless I use CM10.1. I am tired of reading forums to fix this so here I am asking for your help.
/endrant
I have no idea what else to do so any help would be great.
INFO:
Current ROM: Gummy 1.1-11-21-13-UNOFFICIAL
Android 4.4
Baseband version
I3377UCUAMDL
Kernel Version
3.4 g0-Elite-Kernel-ga719cb
Build Number:
KRT16S
Google Apps:
Gapps-Kk-20131113.Zip
TWRP Version
I have no idea and I'm not about to restart phone and go through the pain of reflashing the ROM again as I just did. I will punch so many babies if I have to do this again!'
Thanks for listening.
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
9859834534
prsterero said:
First, if you have an ATT phone then you should be posting there. Have you tried hitting the home button and waiting a few seconds? If you're flashing Verizon stuff to an ATT phone that could also be causing issues.
prshosting.org
Click to expand...
Click to collapse
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Speedsterspeed277 said:
Oh man! So sorry, just realized this was a Verizon Forum, I got a bit lost in the tabs and thought this was the General forum for Samsung Galaxy S4.
And I have installed mainly ATT ROMs in my phone and usually stable ROMs as well.
Do you think it's TWRP causing the problem?
Click to expand...
Click to collapse
It could be. There have been people that get weird issues with twrp so you may want to test out a different recovery to see if the issue persists.
prshosting.org