Develop Bugs

Please help help help!!

i just recently flashed CyanogenMod-7 for EVO tried to flash GAAPS and after did my phone keeps restarting and saying and saying touch screen to being and giving me the option of emergency calls and saying welcome to pc36100 something.. PLEASE HELP ME i dont know whats going on

Did you do a a battery pull and restart?
Also, this should have been in the Q&A...you may be flamed.

go in to recovery, wipe and flash again

phonetec said:
go in to recovery, wipe and flash again
Click to expand...
Click to collapse
i tried that.. it didnt work

Make sure you flashed the right copy off gapps. This happened to me before when I tried to flash the wrong copy of gapps.
Sent from my PC36100 using XDA App

Tiffany84 said:
Make sure you flashed the right copy off gapps. This happened to me before when I tried to flash the wrong copy of gapps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
how did you fix it? and where do i get the right copy of gapps from?

I'm uploading a copy right now. Give me a second.
Sent from my PC36100 using XDA App

U also may not be wiping correly if ur getting bootloops in the setup screen and what not.....grab a format all zip like cualkins and flash that then flash the ROM......tty flashing the rom and the gapps in different sessions.......
Sent from my PC36100 using XDA Premium App

try restoring the nand you do before flashing. is your battery level OK? did you use caukins flash all? Make sure you are wiping data, cache, and dalvik if not using a format_all.zip. With the problems you are having, doing each twice wouldnt hurt (data, cache, dalvik, data, cache, dalvik)

http://db.tt/mKc6tmT
Download these gapps. Boot into recovery and wipe cache and dalvik. Then flash the gapps I just uploaded and see if that helps.
Sent from my PC36100 using XDA App

reverepats said:
U also may not be wiping correly if ur getting bootloops in the setup screen and what not.....grab a format all zip like cualkins and flash that then flash the ROM......tty flashing the rom and the gapps in different sessions.......
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
i cant even get into my phone i can only get into recovery by holding down and power.. i just re flashed again and its still doing the same thing.. im getting very frustrated

Biggie Da Dansa said:
i cant even get into my phone i can only get into recovery by holding down and power.. i just re flashed again and its still doing the same thing.. im getting very frustrated
Click to expand...
Click to collapse
wipe & restore the nand backup

Tiffany84 said:
http://db.tt/mKc6tmT
Download these gapps. Boot into recovery and wipe cache and dalvik. Then flash the gapps I just uploaded and see if that helps.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
i cant even get into my phone because it keeps showing that message and going to the boot screen

Grab the gapps I just uploaded and do what I said in that post and see if it helps
Sent from my PC36100 using XDA App

Tiffany84 said:
Grab the gapps I just uploaded and do what I said in that post and see if it helps
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
it doesnt help if he can't get into his phone

Biggie Da Dansa said:
i cant even get into my phone because it keeps showing that message and going to the boot screen
Click to expand...
Click to collapse
Either do it from a computer or if u have a nand u can restore u could do that and then start over
Sent from my PC36100 using XDA App

tonyh703 said:
wipe & restore the nand backup
Click to expand...
Click to collapse
ok i just restored it..i got one rom to work.. to im gonna whip then reflash the new rom. thanks alot You too Tiffany i really appreciate it

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm starting to love these threads where a newbie has a "life threatening" problem with their EVO and so they post in the wrong section, even after they've seen that it's against the rules...lol
HELP HELP HELP, I turned off my phone and now I can't see anything? WHAT SHOULD I DO.....
A) Turn it back on
B) Freak the hell out
C) Head over to XDA to act like my house is on fire and post in the wrong section
Oh and no need to answer, we all know which one the newbies pick 99.999 percent of the time...hahahaha

[MOD] SuperWipe 2.4 for MyTouch 4G (ATTENTION: ROM MODDERS and FLASHERS!!!)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
A simple, single and easy way to wipe and format your Android device's partitions.
Introducing SuperWipe
Many problems can occur when you flash multiple files on your device. Flashing new files from recovery only copies over the existing files, leaving all old files on your device's partitions, which takes up space and hinders the operations and performance of your Android device. Thus facing these problems, The SuperWipe idea was invented by Ohsaka at xda.
His original link for SuperWipe for the G1 can be found here!
Since then developers have ported or use the same concept of SuperWipe to completely wipe there devices. Let this be the base template for all future SuperWipe concepts.
Mission
We have been working on this project to make it simpler to port to different devices. So I have rewritten the script in edify language. This script also carries the same options as the Original SuperWipe for the G1.
SuperWipe will now read it's properties you set up. Say you only want to wipe certain partitions/files, you have the freedom of choice by editing the SuperWipe.prop file that is stored in the sdcard.
I have also made this an open source project using the GPL in hopes that you donate time, code and any ideas towards this project.
Click to expand...
Click to collapse

SuperWipe general information
A simple, single and easy way to wipe and format your Android device's partitions.
SuperWipe is practically a zip you flash through your recovery.
It SuperWipes your partitions so that your next rom install has minimal issues.
It also has extras!
To set up:
You must flash this once and reboot to be able to edit it from inside the rom with a file manager or using the recovery mount sdcard option to edit your SuperWipe.prop file located in sdcard/SuperWipe/SuperWipe.prop to specify what you WANT WIPED! Or you can make a folder on the root of your sdcard called SuperWipe. Then pull a copy of SuperWipe-prop-sample to that folder renaming it SuperWipe.prop with you edits.
A Sample SuperWipe properties edits:
This file is default, you must configure the file to wipe your preference!
#***wipe data/factory reset***
SuperWipe.Userdata=false
SuperWipe.Cache=false
SuperWipe.Sdcard.android_secure=true
SuperWipe.Sdcard.Android=false
#***superwipe extras***
SuperWipe.Boot=false
SuperWipe.System=false
SuperWipe.Sdcard.sdext=false
CheckFileSystems=false
SuperWipe.log=true
MoveRecoveryLog2sd=true
RebootDevice=false
Click to expand...
Click to collapse

This looks awesome, thanks!

Holy crap. . . . This looks awesome. Has anyone tried it? I'm scared. Ha.
Sent from my HTC Glacier using XDA App

Just to be clear, you use this in addition to a full wipe or instead of a full wipe?
Sent from my HTC Glacier using XDA Premium App

This will do it for you.
First: Flash the file through the Recovery.
Second: Once you've booted back up, go to your SDCard/SuperWipe folder, there is the SuperWipe.prop. Edit that (taking false to true) on the selections you want wiped (the next time you need to wipe).
So when you're ready to change ROMS, just flash the SuperWipe from Recovery and this time it will wipe the options you marked True.

If I want to get the same results as a fastboot wipe, what should NOT be set to true? I want to make sure I don't brick my phone here.
Sent from my HTC Glacier using XDA App

estallings15 said:
If I want to get the same results as a fastboot wipe, what should NOT be set to true? I want to make sure I don't brick my phone here.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
All of the selections that are in the script are the ones you would have to do manually from Recovery in order to do a full wipe.
This app just automates it.

Thanks Richie, nice to see some new stuff for the MT4G anytime, i've been using a similar script but it can only wipe data/cache/system, yours does a more so i'll try it out. And no one should be scared to try this, it won't blow up your phone, cause a BSOD, or fix the economy, but will speed up wiping process.

Just tested everything True and it works perfectly... Thanks Richie

stlouie65 said:
Just tested everything True and it works perfectly... Thanks Richie
Click to expand...
Click to collapse
Same here! I'll be hitting the thanks button now.
Sent from my HTC Glacier using XDA App

I assume the reboot option is a reboot back to recovery?

Try SuperWipe Now!
Thank you guys. Sure hope it's useful! And more take advantage of its simplicity...

johnson8cyl said:
I assume the reboot option is a reboot back to recovery?
Click to expand...
Click to collapse
Yes it will

Reboot option reboots into recovery.
johnson8cyl said:
I assume the reboot option is a reboot back to recovery?
Click to expand...
Click to collapse
A simple, single and easy way to wipe and format your Android device's partitions.
Yes! So that you can reflash cleanly your ROM.

stlouie65 said:
Yes it will
Click to expand...
Click to collapse
Good, then I set everything to true and let it ride......
Sent from my HTC Glacier using XDA App

Used this on the G1 forever as a solution to wiping problems for Sense roms. Does this still do as clean of a job as that one? If so this is like super toilet paper!

Thought so. Thanks Richie.
Sent from my HTC Sensation 4G using XDA App

RichieDaze said:
A simple, single and easy way to wipe and format your Android device's partitions.
SuperWipe is practically a zip you flash through your recovery.
It SuperWipes your partitions so that your next rom install has minimal issues.
It also has extras!
To set up: You must flash this once and reboot to be able to edit it from inside the rom with a file manager or using the recovery mount sdcard option to edit your SuperWipe.prop file located in sdcard/SuperWipe/SuperWipe.prop to specify what you WANT WIPED! Or you can make a folder on the root of your sdcard called SuperWipe. Then pull a copy of SuperWipe-prop-sample to that folder renaming it SuperWipe.prop with you edits.
sample SuperWipe properties edits:
This file is default, you must configure the file to wipe your preference!
Click to expand...
Click to collapse
So, wheres the link?
Sent from my HTC Glacier using XDA Premium App

chipis said:
So, wheres the link?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
A simple, single and easy way to wipe and format your Android device's partitions.

TWRP update

So it looks they initiated a feature freeze and will focus on ironing out bugs, so I don't think we're too far from a release.
Got boost?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Nice! I have been waiting for TWRP. I rooted but refuse to put on CWM with all the issues. Plus my battery life is so much better with the stock kernel right now.

stangdriverdoug said:
So it looks they initiated a feature freeze and will focus on ironing out bugs, so I don't think we're too far from a release.
Got boost?
Click to expand...
Click to collapse
Not yet, but I'm looking to be pushing about 12 lbs in the coming year.
sent from my Epic 4g Touch

Could someone please explain to me what TWRP is.
Sent from my SPH-D710 using xda premium

amwworks said:
Could someone please explain to me what TWRP is.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It the recovery that teamwin were building for our phone, its a touch base recovery. search for it from android central or google.

jedwardmiller said:
Nice! I have been waiting for TWRP. I rooted but refuse to put on CWM with all the issues. Plus my battery life is so much better with the stock kernel right now.
Click to expand...
Click to collapse
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App

TWRP is touch screen capable. Also they figured out how to keep it from changing when you flash other kernels.
Got boost?

tpike said:
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.

housry23 said:
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.
Click to expand...
Click to collapse
The good thing us we don't have to worry about 4g keys.
Sent from my PC36100 using xda premium

Hit a bump in the road!
From Twitter...
This, folks, is why #TWRP 2 isn't released yet. It just magically s-on'ed my EVO 4G! Stupid phone. >_<

cordell12 said:
Hit a bump in the road!
From Twitter...
This, folks, is why #TWRP 2 isn't released yet. It just magically s-on'ed my EVO 4G! Stupid phone. >_<
Click to expand...
Click to collapse
I saw that! I was like wtf? S-on really?
Got boost?

stangdriverdoug said:
I saw that! I was like wtf? S-on really?
Got boost?
Click to expand...
Click to collapse
Lol he bricked his evo4g on the newest tweet
Sent from my SPH-D710 using xda premium

tpike said:
haven't rooted this device yet, but will soon. I have never had issues with cwm on my tab or my original epic. I haven't read any complaints yet with cwm on this device. Can you share some links or specifics you know about?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
No links or anything. Going on personal opinions onlyy. I actually used and liked CWM in the past. I have also used and liked AmonRA. I did put stock with cwm on a while ago and battery dropped from going to bed with over 50% to going through the entire battery in a day.
I know it most likely had nothing to do with CWM, so no need to correct me. This is only personal. Plus after seeing TWRP in action I can't wait to try it.

housry23 said:
A lot of people are afraid of CWM because on the OG EVO 4G early builds were wiping out people's RSA keys which are needed to connect to 4G. It was fixed shortly after, but for some it was too late. Once you restored from a nandroid, your 4g abilities were gone. That is really the only issue I have ever heard of with CWM. I have heard of issues with Rom Manager, but not CWM itself. I prefer TWRP, but if the only custom recovery is CWM, then that is what I'll use. There are no issues with CWM on our phone.
Click to expand...
Click to collapse
There was also another issue of CWM not wiping properly so when people would wipe and then install a ROM, it made the ROM appear to not be functioning properly, ie force closes and such. That and the RSA keys issues were the only ones I was aware of.
The solution to that was to just switch to AmonRa recovery, which was a lot better anyway.

I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.

true but with Calk's "format all" that SHOULD put you at ease
spencer88 said:
There was also another issue of CWM not wiping properly so when people would wipe and then install a ROM, it made the ROM appear to not be functioning properly, ie force closes and such. That and the RSA keys issues were the only ones I was aware of.
The solution to that was to just switch to AmonRa recovery, which was a lot better anyway.
Click to expand...
Click to collapse
phatmanxxl said:
I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.
Click to expand...
Click to collapse

phatmanxxl said:
I never was a fan of CWM, its too buggy. If teamwin comes through in separating the kernel and recovery partition I will be very happy, this is much needed.
@spencer88 I also had a feeling that CWM does not wile properly, I'd install a ROM and get boot loops. Usually that only happens with a ROM when you don't wipe and flash.
Click to expand...
Click to collapse
Agree. That happen to me just recently. I can't wait for a new recovery, I'm looking at you twrp
Sent from my SPH-D710 using xda premium

xlGmanlx said:
true but with Calk's "format all" that SHOULD put you at ease
Click to expand...
Click to collapse
It does, thanks Calk.

xlGmanlx said:
true but with Calk's "format all" that SHOULD put you at ease
Click to expand...
Click to collapse
I only used his format all on the EVO and had issues with getting loops and force closes. I haven't used it since then. It sounds like all are loving it though, which is good to hear.

[Q] backup question - TWRP, CWM, and RA

ok, maybe this is stupid but i don't know. i recently was able to get my evo hboot back down to 0.76.2000 and i'm like all excited and stuff. it works and i'm happy.
here's the potentially stupid question... when creating a backup in the mentioned recoveries, they create a backup of BOOT. does BOOT mean HBOOT?
Second question... in the backup recovery is listed. is that the recovery such as twrp, ra. cwm?
the reason i ask is i'm planning on restoring a backup and i don't want to lose my hboot. the recovery was done on hboot 2.16
i have three oreo cookies for the first person who know, answers, and doesn't call me a dumb-ass.

That's your boot image, not your hboot. And yes that backs up your recovery.Now where's my oreos
Sent from my IdeaTab A2107A-F using Tapatalk HD

CRIME INC. said:
That's your boot image, not your hboot. And yes that backs up your recovery.Now where's my oreos
Sent from my IdeaTab A2107A-F using Tapatalk HD
Click to expand...
Click to collapse
ok. so if i make a back up with CWM and then install RA and use RA to restore the CWM backup, it will put CWM back on my device?
and here's your three Oreo's. real deal, not some of those cheap ass wal-mart fake crap cookies! :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jsp254 said:
ok. so if i make a back up with CWM and then install RA and use RA to restore the CWM backup, it will put CWM back on my device?
and here's your three Oreo's. real deal, not some of those cheap ass wal-mart fake crap cookies! :good:
View attachment 1625464
Click to expand...
Click to collapse
I do believe that's what would happen, I've never used that option when making a nandroid though.
Sent from my IdeaTab A2107A-F using Xparent ICS Tapatalk 2

well since i know now it wont screw up my hboot... i think i'm about to give it a shot and test it.
enjoy those cookies, they were my last ones.

jsp254 said:
well since i know now it wont screw up my hboot... i think i'm about to give it a shot and test it.
enjoy those cookies, they were my last ones.
Click to expand...
Click to collapse
Good luck, post back and let us know how it turns out.
Sent from my IdeaTab A2107A-F using Tapatalk HD

It won't revert recovery but you need to use a special setting to restore a CWM backup from ra or twrp.
Edit: at least not from my experience..
Sent from my SPH-L710 using xda premium

i never even tried it. i had been running the latest TWRP, but went back to RA. i like the keyboard ability in TWRP and being able to name my backups as i create them. but, i like the 3x wipe option in RA. if i knew how to mash them together to get a touch responsive, keyboard equipped, triple wiping recovery... i would just be someone else people could ***** at for bricking their ****.
i may go back later.
i'm like a ***** with shoes.
"what to wear today...pumps, heels, or jungle boots..."

I believe you will have to reflash whatever Rom or kernel you had after you recover your backup, since you changed Hboots. Usually it will not boot into the operating system, but will go directly to Hboot instead.
Sent from my SAMSUNG-SGH-I747 using xda premium

shortydoggg said:
I believe you will have to reflash whatever Rom or kernel you had after you recover your backup, since you changed Hboots. Usually it will not boot into the operating system, but will go directly to Hboot instead.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Not the case. Hboot has nothing to do with it. I ran a ROM on 2.18 then downgraded to 2.10 and the ROM still worked.
Sent from my SPH-L710 using xda premium

ROMs have nothing to do with hboot, they are contained in the /system and /data partitions while hboot is located somewhere esle. The only interaction between the two is that hboot is what tells the how to start up and that is what then loads up the actual ROM on the Android VM
Sent from my PG06100 using xda premium

death-by-soap said:
Not the case. Hboot has nothing to do with it. I ran a ROM on 2.18 then downgraded to 2.10 and the ROM still worked.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
2.10 yes, but I've had Hboot 0.76 after downgrading from 2.10, 2.16, and 2.18 and that was the case. I always had to reflash the kernel to get it to boot into the operating system, or else it would go directly to Hboot. It's an old engineering bootloader unlike 2.10.

I use a zip called superwipe. i'll have to get back to you on where i found it, but i think it would be a good solution to your TWRP/RA dilema lol. all you do is flash in recovery the superwipe.zip, and it automatically deletes cache/dalvik cache/data, three times, then sends you back to the recovery menu, where you can just simply flash your desired rom zip. sorry if this was already mentioned... i didn't read all of the reply pages
its called ZZZVR_SUPERWIPE.ZIP, im sure google will point you to the download location
also, im running MIUI ROM and RA 2.3 recovery

jsp254 said:
i never even tried it. i had been running the latest TWRP, but went back to RA. i like the keyboard ability in TWRP and being able to name my backups as i create them. but, i like the 3x wipe option in RA. if i knew how to mash them together to get a touch responsive, keyboard equipped, triple wiping recovery... i would just be someone else people could ***** at for bricking their ****.
i may go back later.
i'm like a ***** with shoes.
"what to wear today...pumps, heels, or jungle boots..."
Click to expand...
Click to collapse
Twrp factory reset/data wipe wipes 2x in one click everything except dalvik which its wipe option wipes 2x as well as a matter of fact I think every single wipe option in twrp automagically runs 2x it jist formats the partition and then reformats it again everytime you swipe the slide
Sent from my SPH-L900 using Xparent ICS Tapatalk 2

[Q] gapps process has stopped after restore

I am rooted and was using CWM to flash Cyanogenmod. I did a factory reset and then did a restore. The restore went through, but upon reboot the message "Unfortunately, the process com.goog.process.gapps has stopped" appeared. Pressing "ok" only made more dialogs appear. A selection to use Nova Launcher and Touchwiz was also there but I was only able to launch Touchwiz. I don't have any service on the phone and it seems to have locked me out of my Samsung and Google account. I went back into recovery and did another restore and wiped the cache and the dalvik cache based on another thread I saw. Upon reboot, "Android is upgrading" appeared and acted as if it was reinstalling apps or something. Once I got to the home screen the same thing was happening though. I am at a loss and would greatly appreciate help.

I just realized I forgot to install the gapps.zip I had downloaded and was hoping that would fix it. It did not and is still doing the same thing.

rvlution said:
I just realized I forgot to install the gapps.zip I had downloaded and was hoping that would fix it. It did not and is still doing the same thing.
Click to expand...
Click to collapse
you only need to flash the gapps package once right after you flash the rom.....when you make a back up of the rom it also backs up the gapps....so when you restore you get what you backed up so you wont have to flash the gapps again

I had this exact problem when I restored my stock ROM with CWM. The only thing that solved the problem was a factory reset.
Then I discovered Philz recovery. I've don't literally dozens of nandroid backups & restores since, without a single issue. Hopefully installing Philz touch recovery will do the trick for you, too.
Sent from my SPH-L710 using XDA Premium 4 mobile app

Darkside920 said:
I had this exact problem when I restored my stock ROM with CWM. The only thing that solved the problem was a factory reset.
Then I discovered Philz recovery. I've don't literally dozens of nandroid backups & restores since, without a single issue. Hopefully installing Philz touch recovery will do the trick for you, too.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This makes me feel a little better. I am still pretty fresh to this world so could you point me in the direction of an idiot proof guide to do this? Am I able to do this with my phone already in this weird state?
EDIT: Or should I do a factory reset, download and install Philz, and then do a restore?

rvlution said:
This makes me feel a little better. I am still pretty fresh to this world so could you point me in the direction of an idiot proof guide to do this? Am I able to do this with my phone already in this weird state?
EDIT: Or should I do a factory reset, download and install Philz, and then do a restore?
Click to expand...
Click to collapse
First: http://forum.xda-developers.com/showthread.php?t=2446393
[d2lte/d2spr][CWM ADV.] OFFICIAL PhilZ-Touch Recovery 6.48.4[7.06.14]
Second, I would install Philz and try to restore your CWM backup with it before starting over with a factory reset. You may get lucky.

Darkside920 said:
First: http://forum.xda-developers.com/showthread.php?t=2446393
[d2lte/d2spr][CWM ADV.] OFFICIAL PhilZ-Touch Recovery 6.48.4[7.06.14]
Second, I would install Philz and try to restore your CWM backup with it before starting over with a factory reset. You may get lucky.
Click to expand...
Click to collapse
Sorry if I sound clueless, but put Philz on my external and then flash using CWM recovery? And is flashing just installing a zip? Everything I have seen hasn't been too specific and seems to be focused on people who already know what's going on.

rvlution said:
Sorry if I sound clueless, but put Philz on my external and then flash using CWM recovery? And is flashing just installing a zip? Everything I have seen hasn't been too specific and seems to be focused on people who already know what's going on.
Click to expand...
Click to collapse
1. Yes but then you have to reboot into recovery to get into philz
2. Yes
Sent from my SPH-L710 using XDA Free mobile app

sevenpioverthree said:
1. Yes but then you have to reboot into recovery to get into philz
2. Yes
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
Reboot into recovery meaning one of the advanced options in CWM? I just want to to make absolutely sure before I accidentally do something I shouldn't.

rvlution said:
Reboot into recovery meaning one of the advanced options in CWM? I just want to to make absolutely sure before I accidentally do something I shouldn't.
Click to expand...
Click to collapse
Press and hold the home button, the power button and volume up button to get into recovery. Once there, find the philz zip and install from within CWM...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

rvlution said:
Reboot into recovery meaning one of the advanced options in CWM? I just want to to make absolutely sure before I accidentally do something I shouldn't.
Click to expand...
Click to collapse
yes or you can just pull the battery put back in then use the 3 button combo to get into Philz recovery.....i forgot to mention that's the one im using as well

Darkside920 said:
First: http://forum.xda-developers.com/showthread.php?t=2446393
[d2lte/d2spr][CWM ADV.] OFFICIAL PhilZ-Touch Recovery 6.48.4[7.06.14]
Second, I would install Philz and try to restore your CWM backup with it before starting over with a factory reset. You may get lucky.
Click to expand...
Click to collapse
Installed fine, tried doing a recovery and after reboot, same issue. Just did factory reset and restoring again. Will post results when done.
EDIT: After second restore I am getting the same issue. Am I skipping a step after the restore that I should be doing?

Sigh, after Philz didn't work I tried the factory reset. While it "worked" and I was able to link my Google account back, I don't have any cell service. Is there a way to reassign my Sprint account to the phone?

rvlution said:
Sigh, after Philz didn't work I tried the factory reset. While it "worked" and I was able to link my Google account back, I don't have any cell service. Is there a way to reassign my Sprint account to the phone?
Click to expand...
Click to collapse
##72786# in the stock TouchWiz dialer.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v6.3, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

rvlution said:
Sigh, after Philz didn't work I tried the factory reset. While it "worked" and I was able to link my Google account back, I don't have any cell service. Is there a way to reassign my Sprint account to the phone?
Click to expand...
Click to collapse
when you did the factory reset did you wipe cache and dalvik cache? and since your on the stock ND8 rom you can flash KToonsez kernel for 4.4.2 touchwiz then flash the NDC Modem and see if that fixes the signal

roirraW "edor" ehT said:
##72786# in the stock TouchWiz dialer.
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v6.3, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Tried that, I just get a black screen that says "SCRTN" at the top.
6th_Hokage said:
when you did the factory reset did you wipe cache and dalvik cache? and since your on the stock ND8 rom you can flash KToonsez kernel for 4.4.2 touchwiz then flash the NDC Modem and see if that fixes the signal
Click to expand...
Click to collapse
Yes I did. I've been seeing something about a corrupted efs partition and that seems to lineup with what is happening to my phone. It doesn't easy or even very doable to fix without a backup of the efs.

rvlution said:
Tried that, I just get a black screen that says "SCRTN" at the top.
Yes I did. I've been seeing something about a corrupted efs partition and that seems to lineup with what is happening to my phone. It doesn't easy or even very doable to fix without a backup of the efs.
Click to expand...
Click to collapse
So you tried to flash the stock ND8 via Odin? which deletes everything including the custom recovery and makes everything stock
Sent from my SPH-L710 using XDA Premium 4 mobile app

6th_Hokage said:
So you tried to flash the stock ND8 via Odin? which deletes everything including the custom recovery and makes everything stock
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Haven't tried that yet. Where can I download that? And is that the same process as rooting?

rvlution said:
Haven't tried that yet. Where can I download that? And is that the same process as rooting?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2738533 follow instructions on that post and you'll have stock ND8 running in no time just YOU MUST USE DESKTOP ODIN 3.09 to flash it
so you'll be on stock 4.4.2 Touchwiz......if you want to get custom recovery use Philz and flash through Odin as well just make sure the Philz is .Tar.Md5

I really appreciate all the help guys. I ended up going to Best Buy (we have Geek Squad insurance) and they initially sent me over to Samsung who I knew wouldn't do anything about it since it was rooted. I went back over to Geek Squad and they filed a claim and a new one is on the way. Once again, thanks and sorry for anticlimactic conclusion haha. I'm going to wait a while before trying anything on this one and will probably test stuff on the old one first.