Hey guys, I seem to be having a problem on my phone recently.. Every time I start it up, or try to load an app or something, I get a message saying the process ends. This happens with Google Apps, Gingerbread Keyboard, Etc. I've tried wipe x3 then reflash, but it doesn't do anything.
I'm running
Genocide Kernel, Firmware 2.2.1, And Simply AOSP v3.1.2
I believe it's still on SFR 1.2 , but it's not saying that in the build number so I'm not sure..
someone please help.
If you have a good nand backup you can do a factory data reset and then restore advanced data. That will clear up any of the FCs. Or clear data in each of the apps giving you problems in settings>applications>manage applications>all and scroll to google services framework and click it and clear data. Do the same for the Gingerbread keyboard and any other app FCing.
kennyglass123 said:
If you have a good nand backup you can do a factory data reset and then restore advanced data. That will clear up any of the FCs. Or clear data in each of the apps giving you problems in settings>applications>manage applications>all and scroll to google services framework and click it and clear data. Do the same for the Gingerbread keyboard and any other app FCing.
Click to expand...
Click to collapse
I will try this, but the other problem is, it just started having problems with the android processor. Like, I did a restore, and all the sudden, I'm getting all the errors I was getting originally, and like the core & android processor thing is failing.
JWhitez said:
I will try this, but the other problem is, it just started having problems with the android processor. Like, I did a restore, and all the sudden, I'm getting all the errors I was getting originally, and like the core & android processor thing is failing.
Click to expand...
Click to collapse
Sounds like you did not have journaling enabled. The Factory Data reset and a reflash of your ROM should fix it. Find out how to enable journaling for your ROM and do it.
kennyglass123 said:
Sounds like you did not have journaling enabled. The Factory Data reset and a reflash of your ROM should fix it. Find out how to enable journaling for your ROM and do it.
Click to expand...
Click to collapse
I'm sort of new to this, so just one more question. Now, I had Syndicate Frozen Rom 1.2 on originally, then I flashed Simply AOSP 3.1.2 . Which one would I reflash, Simply AOSP or SFR?
JWhitez said:
I'm sort of new to this, so just one more question. Now, I had Syndicate Frozen Rom 1.2 on originally, then I flashed Simply AOSP 3.1.2 . Which one would I reflash, Simply AOSP or SFR?
Click to expand...
Click to collapse
I believe Simply AOSP is a full ROM including kernel so that would be what you would reflash.
kennyglass123 said:
I believe Simply AOSP is a full ROM including kernel so that would be what you would reflash.
Click to expand...
Click to collapse
EDIT: Thank you very much. I just did it and it's working very well. I think it might have messed it up because I was trying to load 2 kernels without knowing it. Thanks for all the help.
JWhitez said:
So theres no need to flash the Genocide Kernel I used for SFR?
Click to expand...
Click to collapse
When you install a new ROM like AOSP all of that is gone. If you want to do SFR and Genocide instead of AOSP then go ahead. We should get you up and running first though and then you know the steps to take when it screws up again.
kennyglass123 said:
When you install a new ROM like AOSP all of that is gone. If you want to do SFR and Genocide instead of AOSP then go ahead. We should get you up and running first though and then you know the steps to take when it screws up again.
Click to expand...
Click to collapse
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
JohnCorleone said:
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks John, welcome to the party. I think what you suggest is exactly what he needs. He just PMd that after selecting another theme in Simply AOSP it started FCing again.
JohnCorleone said:
Yeah Kenny is right, as usual. If you decide to try SRF 1.2, flash the ROM, then journal on zip, then the kernel you want to use then reboot and enjoy.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Thanks, I'm back on SFR 1.2 with no problems, but I didn't need to flash jounral on, so I don't know. Would you know what to do to get on Simply AOSP 3.1.2 , because it has a kernel built in.
JWhitez said:
Thanks, I'm back on SFR 1.2 with no problems, but I didn't need to flash jounral on, so I don't know. Would you know what to do to get on Simply AOSP 3.1.2 , because it has a kernel built in.
Click to expand...
Click to collapse
Well, if you already have the ROM downloaded and it includes a kernel, all you should have to do is wipe everything 3x and flash it
Sent from my SPH-D700 using Tapatalk
JohnCorleone said:
Well, if you already have the ROM downloaded and it includes a kernel, all you should have to do is wipe everything 3x and flash it
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Whenever I do that, I get all those FC's...
I'll give it a go again if I don't decide to go to EG22..
JWhitez said:
Whenever I do that, I get all those FC's...
I'll give it a go again if I don't decide to go to EG22..
Click to expand...
Click to collapse
I would suggest either pming or posting on the AOSP thread what setup you're on and how best to convert to their Rom. Sometimes they've heard of conflicts or tricks that they can walk you through. I love SRF, but if you want to explore, you should know what works best to transition. You'll get it going, just keep toying. Worst you have to do is Odin and that's not terrible for the phone now and again.
The Root said:
I would suggest either pming or posting on the AOSP thread what setup you're on and how best to convert to their Rom. Sometimes they've heard of conflicts or tricks that they can walk you through. I love SRF, but if you want to explore, you should know what works best to transition. You'll get it going, just keep toying. Worst you have to do is Odin and that's not terrible for the phone now and again.
Click to expand...
Click to collapse
I gave up on it.. Went to EG22. Still debating on whether or not to go back to SFR / Simply AOSP.. because the battery life on RandomROM is absolutely amazing. But I'll PM him.
Related
Every non-Aosp rom I've ever flashed (Acs, bonsai, midnight, simply aosp, viper, et..) have always ended up freezing and forcing me to remove the battery to re-boot, I've followed instructions, re-downloaded the roms etc. CM7 and MIUI, both Aosp, have never had that problem, always flashed right the first time, never had to flash twice. I guess I'm just curious if anyone can explain why aosp roms work fine (minus mms, 4g, and the other aosp bugs) and every rom based off of official releases always seem to end up failing?
Sent from my Samsung-SPH-D700 using XDA App
wrong section man, this is not development (it will be moved soon).
If you are following instructions to the point in ROM guides, I have no idea. Sorry. But more specifics on your problems would help us help you
Its because most of the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.
djbacon06 said:
Not to sound like an ass, but that's not entirely true. I have never had to flash non-aosp roms more than once.
Click to expand...
Click to collapse
Even after an odin? Cause I've had to every time. If I'm just going between two roms I don't. Maybe my phone is just picky
GituSum Epic 4G
GituSum said:
Maybe my phone is just picky
Click to expand...
Click to collapse
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact
djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
But yeah, even after clean ODIN installs it works fine first flash. Did that today as a matter of fact
Click to expand...
Click to collapse
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G
GituSum said:
Then ya mine is picky. I flashed EE03 last night and used odin to go back to froyo today and had to flash twice before it booted up. No big deal just an extra couple minutes to flash and boot up
GituSum Epic 4G
Click to expand...
Click to collapse
Haha you're not the only one! On DK28 I had to flash twice everytime! And then for a little while on EB13. I don't know what changed though. But I havent had to do it for a longtime. Maybe it's because I never boot into stock before flashing?
It mainly jas to do with us having a crappy recovery.
Sent From My Evo Killer!
djbacon06 said:
I think that's it for sure. This phone literally has a mind of its own and every one is different. Just like people???
Click to expand...
Click to collapse
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha
Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App
Flash srf and then vision 1.1 over it. Post in the right sub-forum.
Sent from my SPH-D700 using XDA App
Skimp Killah said:
Even from a fresh odin, all other roms end up freezing, CM7 or MIUI I can flash over anything, and they always work, everytime.
Sent from my Samsung-SPH-D700 using XDA App
Click to expand...
Click to collapse
I experience this to an extent as well.. w/ SRF 1.0.2 it flashes first time and works flawlessly..
What I've found is that all devices aren't created equal. Some work really well others are finicky.
What I've found that works for me is immediately after a flash, I can tell if it's gonna be wonky or work. After the flash, if it 'delays' before popping back up to the recovery menu, it's gonna fail. If the recovery menu pops up right away I'm good.
When it 'fails'.. I'll reboot system.. on the white samsung screen, pull the battery. boot back into recovery, then re-flash. boot system if it doesn't auto boot and you're good.
Not sure why it's like this, but it works for me. MY device doesn't always play nice w/ every version of every ROM and rather than whining in all of the ROM threads about why the rom sucks and I can't use it.. I've figured out a way to use them through troubleshooting and process of elimination using some of the 'fixes' that are posted in the different threads.
all Epics are not created equal. Just gotta figure out what works for yours.
EDIT: now that I think about it, (not that it's a big deal) I'm gonna go find noobnl's thread about checking for bad blocks on the ONEnand... just curious if journaling is trashing my NAND (I don't think it is, but ya never know)
EDIT: Still only 3 bad blocks. Nothing to worry about for me
spyder09 said:
UH OH are you ACS guys developing AI and secretely putting it in our phones? hahaha
Click to expand...
Click to collapse
LOL, I am by no means developing anything for ACS. I'm not a developer, just an advocate
And knowing how k0nane does things, there would be absolutely no trace of something like that in ACS roms
Try ec05plus its an odin tar, and it will work from the first boot...
Sent from my SPH-D700 using XDA App
GituSum said:
Its because the non aosp roms are backing up and restoring your data. If your coming from a clean flash you have to flash the rom twice before it will boot up properly.
And yes this belongs in the q&a forum
GituSum Epic 4G
Click to expand...
Click to collapse
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time
Still not sure why this is in development.
k0nane said:
Still not sure why this is in development.
Click to expand...
Click to collapse
Won't be for long, about to pm impaler unless you already have.
Sent from my SPH-D700 using XDA App
TheDub said:
That's not true. He mentioned Simply which I know for a fact doesn't backup/restore data.
1.) Odin back to EC05
2.) Re-root and Install CWM3
3.) Let it convert you to EXT4
4.) Upgrade to CWM 3.0.2.5
5.) Wipe data.
6.) Go to Advanced/Mounts and hit Format /system
7.) Flash the rom of your choice
8.) If it fails again wipe data x3 and then system x3 for good measure, try try again.
Hope that helps.
Pst make sure to use the proper section next time
Click to expand...
Click to collapse
Iv'e tried everything listed other than upgrading to the newest CMW, I'm thinkin I'm just gonna have to wait for CM7 or MIUI to have mms and what not.
Sent from my Samsung-SPH-D700 using XDA App
Moved to Q&A.
Hi there!
I have had an s3 for a few days now and love it!.
Any TW rom and my camera works just fantastic.
Any cm10/aokp/miui/etc rom and I just cant use the camera no matter what app I use to try it, whether it be the built in app or camera360/etc.
Driving me nuts and would love someone to help me. Anyway research I have done hasnt told me what I'm doing wrong.
I wipe cache/dalvik/factory reset/system before each rom. I have tried different kernels but nothing has helped.
Any gurus out there have any ideas on what I can do to fix this?
Your install process would be and please link the files you are flashing... I'll try and help you. I've seen a few people mention this the past couple days.
The most recent I tried to flash was Illusion v1.1.18 - (d2tmo, d2att & d2vzw) - 1|18|13 from this thread:
http://forum.xda-developers.com/showthread.php?t=2037028
I downloaded Illusion-v1.1.18-d2tmo.zip and gapps-jb-20121212-signed.zip.
I went into recovery which is twrp and the most recent version. I installed it with the goo.im app.
When in recovery I did:
1) Factory Wipe
2) Wipe Cache
3) Wipe Dalvik
4) Wipe System
I would then click Install and select the rom file, and after it succesfully flashed I would then flash the gapps file. All were successful.
I would then reboot and the rom would boot up fine. I setup my google account and all that then for the heck of it I would reboot.
I then would try the camera app and it would complain that it couldnt connect to the camera basically. I went into the play store and tried a free version of camera 360, puddle camera, etc and all would not work.
I went back into recovery, wiped cache and dalvik again, hopped on one foot, faced east, and clicked my heels together. Upon reboot the camera does not work.
I have wiped all that and tried to install [Kernel][JB] Leankernel: Minimalistic Kernel for D2TMO/D2ATT (AOSP) v2.3 [1/17/13] which flashed fine. Upon reboot I could change voltages to undervolt, mess with governors but cameras still do not work.
I have a backup of two TW roms (one stock) and both of the those roms work beautifully with whatever camera I try, including the built in/stock camera.
I hoped I didn't leave out something. If there is something I missed than I'm an idiot because it seems like I am really missing something.
Thanks for your help.
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery... Are you using the same Gapps over and over on each try? Might wanna try a different set.
mt3g said:
I don't see any reason your steps lead to that, the exact steps I take every time to flash. I'm researching but in the mean time, go to app manager and wipe cache and data from gallery.
Click to expand...
Click to collapse
I did that earlier with no luck.
I just force stopped on gallery, wiped cache/data, rebooted, and I tried the camera only to get the same message.
Thank you for that tip but I will continue my research also.
Just because I looked at about phone.
Model of phone is SGH-T999 (just in case someone thinks I'm in the wrong forum"
Baseband version is T999UVDLJA
Kernel is of course 3.0.59-leanKernel
AOKP Version is Illusion v1.1.18 d2tmo
Build number is aokp-d2tmo-userdebug 4.2.1 (I truncated the rest)
mt3g said:
Are you using the same Gapps over and over on each try? Might wanna try a different set.
Click to expand...
Click to collapse
I have downloaded this gapps twice for the last rom http://goo.im/devs/itsmikeramsay/gapps-jb-20121212-signed.zip.
For the miui rom there was a gapps that was specific to miui and had miui in the name. The miui rom's camera didnt work.
I'll look for a different gapps if that might be the problem but since I have tried a couple roms and a few different gapps I feel that might not be the issue.
I still will give it another try though. Just have to find another gapps to try.
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
mt3g said:
try these just in case they're corrupted. http://d-h.st/dtk these are the ones I use
Click to expand...
Click to collapse
I redid the entire install process from scratch using that gapps and the camera is still not working.
Ugh. Thanks for the link.
WIll keep trying :/
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!? Shots in the dark right now, just trying to help as I've never seen this issue before solved.
mt3g said:
run a log cat and post it. Other then that maybe bad firmware...
did you update your phone to stock JellyBean via Over the Air or Odin? it updates the partitions which could be the issue, mmayyybbeee???!?!?
Click to expand...
Click to collapse
It had JB on it when I got it almost 2 days ago. I tried to do an OTA when I got it but it said I was up to date.
Let me do a restore to stock and see what version it is.
Edit: Restored stock. Says android version 4.1.1, Kernel 3.0.31-370274se.infra, Build number JR003L.T999UVDLJA
Was it already rooted?
Sent from my SGH-T999 using xda premium
mt3g said:
Was it already rooted?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It was new, out of the box. I watched the guy unrap it. It is one of the newer grey metal color looking ones. It was not rooted. I did that. Should I do an Odin to bring the device back to complete stock and start from scratch?
Will take a while since I have no idea where to start with all that
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
mt3g said:
Thats the best suggestion I have. Maybe someone else will step in with an idea.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
You have been helpful. In a bit ill reflash a cm/aokp rom and logcat it.
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
mt3g said:
This is happening a couple of threads above you haha http://forum.xda-developers.com/showthread.php?p=36899130
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
dccoh said:
Hey thanks again for your help. I ended up falling asleep but installed Wicked V6 (tw based rom) and liking it enough that I will wait on a aokp/cm10.x rom until I get up the motivation to try again.
I'm sure I'll get an itch for a different rom in about a week though
Click to expand...
Click to collapse
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
mt3g said:
All good, just hope the thread I pointed to will work out once you do want to give it another go.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
dccoh said:
I backed up Wicked and loaded up my original rom that I wanted to try.
The fix in the said thread fixed me right up, camera works fine.
All this trouble because of one 350ish kb file
Thanks for checking on my issue.
Click to expand...
Click to collapse
Most definitely sir. I don't understand why that file was getting screwed over. Glad it all got worked out for you.
Sent from my SGH-T999 using xda premium
Hey guy's I recently reflashed JellyBomb on my phone due to some problems. For example when I boot my phone up it get's stuck in landscape on the lock screen and sometimes when I'm texting it get's stuck in landcape again and I can't press anything. For I don't know how long cause I usually just pull out the battery and reboot. I also have to clear cache and davik then it works. Until have I have reboot my phone Does anybody know the problem is.
Are you flashing bad addons? Did you do a full wipe when you installed? Did you make system / kernel tweaks?
teh roxxorz said:
Are you flashing bad addons? Did you do a full wipe when you installed? Did you make system / kernel tweaks?
Click to expand...
Click to collapse
Yeah I did a system reset, and wiped cache and davik and cleared internal, and it still happens.
RobTheHuman said:
Yeah I did a system reset, and wiped cache and davik and cleared internal, and it still happens.
Click to expand...
Click to collapse
Have you changed kernels?
teh roxxorz said:
Have you changed kernels?
Click to expand...
Click to collapse
Nope, I barley know about kernals to change so I don't even bother hahaha I usually keep the ROM the way it is. I forgot to mention if it could be the problem I changed the font from ROM toolbox.
RobTheHuman said:
Nope, I barley know about kernals to change so I don't even bother hahaha I usually keep the ROM the way it is. I forgot to mention if it could be the problem I changed the font from ROM toolbox.
Click to expand...
Click to collapse
That shouldn't affect the system too much; I would try flashing the kt747 TW kernel, and see if your system smooths out.
teh roxxorz said:
That shouldn't affect the system too much; I would try flashing the kt747 TW kernel, and see if your system smooths out.
Click to expand...
Click to collapse
Fasho thanks I'll download it now. Like it said I don't know to much about Kernels I don't know which one to download. I have sprint by the way. http://forum.xda-developers.com/showthread.php?t=1800576
RobTheHuman said:
Fasho thanks I'll download it now. Like it said I don't know to much about Kernels I don't know which one to download. I have sprint by the way. http://forum.xda-developers.com/showthread.php?t=1800576
Click to expand...
Click to collapse
Yurp, that'd be the one.
teh roxxorz said:
Yurp, that'd be the one.
Click to expand...
Click to collapse
Fasho thanks man, hopefully this works.
any word if that smoothed out? I had an issue where i guess i flashed a rom prior to flashing the upgraded firmware/modem and it caused a ton of odd issues. So make sure the rom you are using also is using the same radio/firmware you are. If it isnt, the main thread of the rom should have a DL link for the modem/firmware, or there are a couple AIO modem/Firmware dls out there.
My note has been laggy as hell lately it started a few days ago and I'm not sure why I was on goodness rom the went to Jedi x16 and am now on pacman as of today and every last one of the ROMs have the same problem force closes and freezing a lot no matter what I'm doing and YouTube is choppy also my battery doesn't charge like it used to I'll be getting the note 3 whenever it comes out in the next few months but I want this phone as my backup and as of now its the only phone I have and I need help any would be much appreciated thanks in advance I'm pretty much a noob just throwing that out there
Do you do a clean wipe every time you install a new rom? Clean wipe cache, dalvik, data, system, internal sd? Try downloading rom thru pc then transfer to your sd.
POWERED by the MASTER!
Craniotomy said:
Do you do a clean wipe every time you install a new rom? Clean wipe cache, dalvik, data, system, internal sd? Try downloading rom thru pc then transfer to your sd.
POWERED by the MASTER!
Click to expand...
Click to collapse
Yeah its weird I always do a clean wipe even when they say its unnecessary but the phone started acting up a few days ago I think it may have been after I restored to one of my old ROMs and from there the phone has just been acting really crazy its very annoying it happens most when I try to use internet app though I noticed
WzrdCuD said:
Yeah its weird I always do a clean wipe even when they say its unnecessary but the phone started acting up a few days ago I think it may have been after I restored to one of my old ROMs and from there the phone has just been acting really crazy its very annoying it happens most when I try to use internet app though I noticed
Click to expand...
Click to collapse
Only thing i could suggest is total wipe and clean and start from new downloads
POWERED by the MASTER!
Craniotomy said:
Only thing i could suggest is total wipe and clean and start from new downloads
POWERED by the MASTER!
Click to expand...
Click to collapse
Yeah I've tried that a few times with no success but thanks for your help anyway
WzrdCuD said:
Yeah I've tried that a few times with no success but thanks for your help anyway
Click to expand...
Click to collapse
What kernels are you using? Are you using set Cpu? Trickster mod? At the same time? I use set Cpu for the power profile. But for undervolt i use trickster. Or try to just use one and uninstall the other.
POWERED by the MASTER!
Craniotomy said:
What kernels are you using? Are you using set Cpu? Trickster mod? At the same time? I use set Cpu for the power profile. But for undervolt i use trickster. Or try to just use one and uninstall the other.
POWERED by the MASTER!
Click to expand...
Click to collapse
I'm currently on PAC man ROM which I believe is the cyanogen mod kernal
WzrdCuD said:
I'm currently on PAC man ROM which I believe is the cyanogen mod kernal
Click to expand...
Click to collapse
Ok. Have you tried a different kernel? I tend to stay with T-Mobile based roms.
POWERED by the MASTER!
[QUITE=Craniotomy;44367932]Ok. Have you tried a different kernel? I tend to stay with T-Mobile based roms.
POWERED by the MASTER![/QUOTE]
No i haven't actually but yeah I'm usually on Jedi x but no matter what it does the same thing
WzrdCuD said:
[QUITE=Craniotomy;44367932]Ok. Have you tried a different kernel? I tend to stay with T-Mobile based roms.
POWERED by the MASTER!
Click to expand...
Click to collapse
No i haven't actually but yeah I'm usually on Jedi x but no matter what it does the same thing[/QUOTE]
I would definitely try a different kernel. Maybe your phone can only handle stock kernels or something which Jedi doesn't use. Having a CM kernel still lingering through a flash while running Jedi can't be too good either, it's possible that's what happened? Go back to just stock rooted and see if the problem remains.
tony yayo said:
No i haven't actually but yeah I'm usually on Jedi x but no matter what it does the same thing
Click to expand...
Click to collapse
I would definitely try a different kernel. Maybe your phone can only handle stock kernels or something which Jedi doesn't use. Having a CM kernel still lingering through a flash while running Jedi can't be too good either, it's possible that's what happened? Go back to just stock rooted and see if the problem remains.[/QUOTE]
Its really weird because this has never happened before I've also never flashed a kernel my friend always scares me saying that its the most dangerous thing to do when rooting but do you have a suggestion thanks in advance
I already made a suggestion, go back to stock rooted.
tony yayo said:
I already made a suggestion, go back to stock rooted.
Click to expand...
Click to collapse
Lol sorry about that I'm really not sure what stock rooted would be is there a ROM for it like I said I'm extremely noobish and don't really know Mich beyond flashing my friend rooted my phone for me again I'm sorry
I think your better off letting your friend handle it. I dont want to suggest anything at all if you don't know what you are doing.
tony yayo said:
I think your better off letting your friend handle it. I dont want to suggest anything at all if you don't know what you are doing.
Click to expand...
Click to collapse
Sorry for the late reply but my friend is in the army he doesn't really have much time to help me with this so any suggestions I wouldn't blame you in the least if something went wrong
http://forum.xda-developers.com/showthread.php?t=2102380
That's where you will find a stock ROM. Flash the factory image with Odin. If you don't know what stock is or how to flash a kernel it's best to go back to stock and don't run custom ROMS. Just read the thread I linked and post any questions about the process in that thread.
You can flash the factory image using Mobile Odin from the Play Store and there's an option to keep root.
Sent from my SGH-T889 using xda premium
Rhiannon224 said:
http://forum.xda-developers.com/showthread.php?t=2102380
That's where you will find a stock ROM. Flash the factory image with Odin. If you don't know what stock is or how to flash a kernel it's best to go back to stock and don't run custom ROMS. Just read the thread I linked and post any questions about the process in that thread.
You can flash the factory image using Mobile Odin from the Play Store and there's an option to keep root.
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
Ok thanks so much
I hope it works for you.
Sent from my SGH-T889 using xda premium
Are you running custom kernels that are overclocked? Maybe your phone can't handle the overclock anymore.... it happens
Sent from my SGH-T889 using xda premium
Tried IRC, so I'm going to try here also.
Anytime I use a ZVB or ZVC based ROM, the kernel crashes within 10-15 seconds of being flashed. No matter which of those based ROMs I use, I get the kernel crash in the same time period. I've tried different kernels as well, but none have worked. I've use Awesome's Kernel Cleaner each time before flashing the kernels, but get the same result.
Here's the kicker though, if I use any of the AOSP ROMs it will run fine. My only problem is there was no EFS backup, so I get no service, which pretty much makes using the 4.3.x+ ROMs useless. Basically, I'm trying to get back to stock ROMs so I can get service and save the EFS to use on the later ROMs. If I can even just get the ZVC ROM working that would be great too.
I'm not sure if there is a AOSP kernel stuck in there or something, and it's not clearing it out, or what is going on. I'm doing a complete wipe with data everytime I flash.
I appreciate any help, and thank you for taking the time to read!
Jxt. said:
Did you flash a radio ?
Click to expand...
Click to collapse
When flashing the ZV ROMs? I did the ZVB radio when I did the stock ROM. I might have done it after instead of before though.
Jxt. said:
you only flash a radio once, have you been doing it everytime you flash a rom?
Click to expand...
Click to collapse
Only when I went from ZVB to ZVC just to be sure. Would the radio cause the kernel crashing?
Jxt. said:
yes could be, can you give me the that you got the radio from
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40169203
HyphyCus said:
Tried IRC, so I'm going to try here also.
Anytime I use a ZVB or ZVC based ROM, the kernel crashes within 10-15 seconds of being flashed. No matter which of those based ROMs I use, I get the kernel crash in the same time period. I've tried different kernels as well, but none have worked. I've use Awesome's Kernel Cleaner each time before flashing the kernels, but get the same result.
Here's the kicker though, if I use any of the AOSP ROMs it will run fine. My only problem is there was no EFS backup, so I get no service, which pretty much makes using the 4.3.x+ ROMs useless. Basically, I'm trying to get back to stock ROMs so I can get service and save the EFS to use on the later ROMs. If I can even just get the ZVC ROM working that would be great too.
I'm not sure if there is a AOSP kernel stuck in there or something, and it's not clearing it out, or what is going on. I'm doing a complete wipe with data everytime I flash.
I appreciate any help, and thank you for taking the time to read!
Click to expand...
Click to collapse
Are you wiping /system too? If in TWRP 2.5.0.0, wipe>advanced click all 4. If 2.6.x.x all BUT internal data
He told me in irc that this originally happened after the screen broke and he replaced it. After that anything stock gives a kernel crash but aosp doesnt.... if that helps anyone trying to help him.
engine95 said:
Are you wiping /system too? If in TWRP 2.5.0.0, wipe>advanced click all 4. If 2.6.x.x all BUT internal data
Click to expand...
Click to collapse
Using 2.6.3.0, and wiping everything but SD card. Wiping 3x before installing ROM, gapps and kernel. Tried multiple stock based kernels. Can install CM or Slimbean and it will boot no problem, and work fine. It's just the stock ROMs, and tried Lifeless as well.
Guess this has everyone stumped huh?
HyphyCus said:
Guess this has everyone stumped huh?
Click to expand...
Click to collapse
There's always LGNPST. Only other option to see if it'll fix it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
There's always LGNPST. Only other option to see if it'll fix it.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that with the stock ZV9, ZVB and ZVC. Even used LG flash.
Here's an idea that came in my head. Maybe it's crashing when it tries to connect to the Sprint network. Since the AOSP ROMs never attempt to connect to it, they don't crash. But the stock ROMs do, so they crash when attempting.
If I'm not rooted, I get just a reboot. If I run SuperSU from TWRP before rebooting, then I get the Kernel Crash screen when it reboots.