Related
i have been having issues using the infinity rom when multitasking. for example when i am using pandora thats all i can do. if i try browsing or anything while on pandora my phone freezes and restarts. and everytime i try to overclock it to 1.3ghz it freezes and restarts as well.. this is the process i am using to flash this rom.
1. coming from teawstock v1.4 (latest build), pb&j kernel, tweakstock is already ext4... right.. but thanks to imnuts, he provided the proper conversion tools needed in case i were to be RFS... lol, thanks buddy for this rom in advance. i have flashed everything available for this phone and your rom is by far my favorite... hahaha. i will post a screen capture of my quadrant standard to show you how much ive tweaked my ****.. lol. i think my last benchmark was around 2360...
2. data foctory reset/ wipe cache/ dalvik
3.mount system
4.flash rom/TSM parts, love the TSM parts by the way!!!!!
5. reboot phone.
Can you OC to that level on a different ROM? Your phone just may not be able to go that high.
Sent from my SCH-I510 using xda premium
I have the same problem. i love this rom but have a lot of freezing and rebooting. i see there is a updated infinity rom but have not tried it yet
YAH BABY
stebomurkn420 said:
i have been having issues using the infinity rom when multitasking. for example when i am using pandora thats all i can do. if i try browsing or anything while on pandora my phone freezes and restarts. and everytime i try to overclock it to 1.3ghz it freezes and restarts as well.. this is the process i am using to flash this rom.
1. coming from teawstock v1.4 (latest build), pb&j kernel, tweakstock is already ext4... right.. but thanks to imnuts, he provided the proper conversion tools needed in case i were to be RFS... lol, thanks buddy for this rom in advance. i have flashed everything available for this phone and your rom is by far my favorite... hahaha. i will post a screen capture of my quadrant standard to show you how much ive tweaked my ****.. lol. i think my last benchmark was around 2360...
2. data foctory reset/ wipe cache/ dalvik
3.mount system
4.flash rom/TSM parts, love the TSM parts by the way!!!!!
5. reboot phone.
Click to expand...
Click to collapse
@stebomurkn420 & @nailem
I guess I can't tell you to use the non-tsm rom then eh? I find TSM to be too buggy and cause more problems than extra goodies, plus theming can edit just about any part of your phone on any Rom, icons, statusbar, you name it.
Anyway whenever I flash a new rom I always revert back to stock with the charge.pit file to make absolutely sure that my partitions are set up correctly. A little more time consuming than just wiping data but I have never had an issue jumping from one Rom to the other.
To make sure I was back to ext4 since I was flashing from stock straight into InfinityRom, I flashed Imosey's kernel (which has lagfix) and autoconverted me to ext4, then once my phone booted with ext4 I just wiped and flashed PB&J kernel again. Nice and quick, flashing the kernels to get me to ext4 took all of about 3 minutes. Now I have InfinityRom, PB&J (w/ the awesome advanced sound tweaks), and no lag. If you wanna give it a shot I can help shoot you some links for all the files I mentioned.
Also be careful not to OC too high, there is a point of diminishing returns.
cliMACtic, yes that would be great. I found the updated infinity rom but have never returned my phone to stock. Links and a little instructions would help. Thank you
nailem said:
cliMACtic, yes that would be great. I found the updated infinity rom but have never returned my phone to stock. Links and a little instructions would help. Thank you
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1560117
look for EP4D stock rom link.
thanks climaktik
thanks for your help buddy.. im going to flash through odin back to stock ep4d anyways to do the fp1 modem update that we had last night... then try to reflash infinity without tsm parts... and give that a go.. i tried gummy charge as well last night and was hving freezing issues... i have resorted back to tweakstock for the time being because of its stability.. lol.
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
jonslaught said:
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
Click to expand...
Click to collapse
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Mr. Apocalypse said:
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Click to expand...
Click to collapse
I've wiped everything multiple times and flashed just the eg rom on its own and it still sends me back to recovery. x.x
i'm using g2x nullifier to see if after doing that, then flashing any rom will make it work.
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
I would a give a shot of this tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize all your partitions.
Sent from my LG-P999 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
ratza66 said:
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
Click to expand...
Click to collapse
was looking around for some tool like this and couldn't find it x.x
I used it and presto! my g2x is alive and kicking again, thanks alot man
And thanks to everyone else that bothered posting, really helps alot
I recently installed CM10.0 (The stable release) on my gs3, and I'm not too happy with the severe battery drain and glitchy lockscreen, so I want to swicth back to a TouchWiz based ROM that will provide a good balance of performance and great battery life. I have two questions. First, is there anything special I have to do with transitioning back to TouchWiz from CM10.0? I know I had to install the gapps package, but the factory wipe should remove that right?
Also ROM suggestions for stable performance with ability to tweak more settings, but at the same time retains healthy battery life? After researching a bit, CleanROM or Synergy seem like my best bet, but I would like opinions from more experience users than myself, I'm still pretty new to this.
Thank you in advance! :good:
i wipe data, cache, dalvik in between roms.
if im going to 4.2 to TW or TW to 4.2 or whatever.
if you like the looks of AOSP but the function of TW flash Beans build 10. you WILL NOT regret it.
xNali said:
I recently installed CM10.0 (The stable release) on my gs3, and I'm not too happy with the severe battery drain and glitchy lockscreen, so I want to swicth back to a TouchWiz based ROM that will provide a good balance of performance and great battery life. I have two questions. First, is there anything special I have to do with transitioning back to TouchWiz from CM10.0? I know I had to install the gapps package, but the factory wipe should remove that right?
Also ROM suggestions for stable performance with ability to tweak more settings, but at the same time retains healthy battery life? After researching a bit, CleanROM or Synergy seem like my best bet, but I would like opinions from more experience users than myself, I'm still pretty new to this.
Thank you in advance! :good:
Click to expand...
Click to collapse
Hey xNali,
I was in a similar position, in which I went from TW to CM10 stable, back to TW. To go back, all I did was, in Clockworkmod recovery, wipe the phone/factory restore, wipe cache, wipe dalvik cache, and then flashed the TW ROM.
As to your second question, I am using CleanROM 5.6 w/ lean kernel. I am only on the first battery cycle with very minimal usage (less than 1 hour of screen time), and I got about 1 day and 5 hours of battery life on it. Thus far, CleanROM seems to be very stable and I have yet to experience any issues - no apps crashing, wifi, BT tether all work, no screen flickering. At the same time, I use my phone primarily for work emails, so others on the board may be able to provide better advise.
In addition to CleanROM and Synergy, Jelly Beans also seems to be very popular (based solely on the # of posts in that thread).
JOLiu said:
Hey xNali,
I was in a similar position, in which I went from TW to CM10 stable, back to TW. To go back, all I did was, in Clockworkmod recovery, wipe the phone/factory restore, wipe cache, wipe dalvik cache, and then flashed the TW ROM.
As to your second question, I am using CleanROM 5.6 w/ lean kernel. I am only on the first battery cycle with very minimal usage (less than 1 hour of screen time), and I got about 1 day and 5 hours of battery life on it. Thus far, CleanROM seems to be very stable and I have yet to experience any issues - no apps crashing, wifi, BT tether all work, no screen flickering. At the same time, I use my phone primarily for work emails, so others on the board may be able to provide better advise.
In addition to CleanROM and Synergy, Jelly Beans also seems to be very popular (based solely on the # of posts in that thread).
Click to expand...
Click to collapse
Thanks for the advice. I'm getting like 12-15 hours with very minimal usage which is pathetic to me. I've never flashed a kernel before, can you link a thread for me?
ddurandSGS3 said:
i wipe data, cache, dalvik in between roms.
if im going to 4.2 to TW or TW to 4.2 or whatever.
if you like the looks of AOSP but the function of TW flash Beans build 10. you WILL NOT regret it.
Click to expand...
Click to collapse
Awesome that is essentially my issue are the bugs which I completely understand, because they are still doing nightlies to perfect it. How's your battery life?
xNali said:
Thanks for the advice. I'm getting like 12-15 hours with very minimal usage which is pathetic to me. I've never flashed a kernel before, can you link a thread for me?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2116415
I can't find the thread, but another thing I remember reading was to install CleanROM and, while still in recovery, flash the kernel (find Lean Kernel here - make sure you download the TW kernel, and not the AOSP one).
Once the kernel is flashed, and before you reboot, someone suggested clearing cache, dalvik cache, fix permissions, and then reboot. No idea what fix permissions does, and how it affects how the ROM and kernel run.
Also, what others have said is to allow the ROM to settle a few battery cycles to see the full effect of the ROM/kernel. Again, I have no idea how this has any effect on battery life, but a lot of people seem to swear by it.
Hope this helps.
I will give that a shot tomorrow. My other worry is I had to revert back to stock when I was flashing CM10 the first time because it was stuck on roaming and on stock you cannot change from NV to RUIM/SIM and it was stuck on roaming. Is there an option in CleanROM to change it or will it be ok when I flash it? I was stuck on roaming and had to flash back to CM10 change the setting then flash back to stock.
Sent from my SCH-I535 using xda app-developers app
xNali said:
I will give that a shot tomorrow. My other worry is I had to revert back to stock when I was flashing CM10 the first time because it was stuck on roaming and on stock you cannot change from NV to RUIM/SIM and it was stuck on roaming. Is there an option in CleanROM to change it or will it be ok when I flash it? I was stuck on roaming and had to flash back to CM10 change the setting then flash back to stock.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You'll be fine when you flash clean ROM 5.6. When you're wiping cache and dalvic you shoul also format system. That will insure that you get a good clean install. Also is your imei backed up just in case? There is a thread on how to back it up if you need to.
Sent from my Nexus 7 using xda app-developers app
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.
what are you doing before flash the new rom?
juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app
Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.
Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.
So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(
I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium
Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.
Hey Guys,
So I decided to be a little bit dangerous at work today and flashed cyanogenmod but I didn't really like it all too much so I tried to flash back to franco's kernel. Now my phone's messed up and wont go pass the google screen. I don't have my usb cords either. What can I do?
Well, you will obviously need a usb cable to push the cyanogenmod zip to your device if it's not there already.
If you have the rom in your sdcard, then boot to recovery and flash cm again. It should boot.
We need your firmware you were running what cyagenomod you flashed what firmware you tried to go back to how you flashed it and what colour of T-shirt you were wearing at the time. ANY info you have. And yes you are going to need the USB lead. Anyway you can prob just fix it with Wugfresh nrt
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
bullsrfive said:
Hey Guys,
So I decided to be a little bit dangerous at work today and flashed cyanogenmod but I didn't really like it all too much so I tried to flash back to franco's kernel. Now my phone's messed up and wont go pass the google screen. I don't have my usb cords either. What can I do?
Click to expand...
Click to collapse
Get back to recovery and flash CM or adb sideload another custom rom or flash the factory image in fastboot. Franco kernel is not compatible with CM atm.
gee2012 said:
Get back to recovery and flash CM or adb sideload another custom rom or flash the factory image in fastboot. Franco kernel is not compatible with CM atm.
Click to expand...
Click to collapse
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
bullsrfive said:
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
Click to expand...
Click to collapse
Or a custom rom based on AOSP (stock) scources like most are, read the OP of the different devs. If CAF is mentioned in a OP Franco kernel is not compatible.
bullsrfive said:
I just flashed CM again to get my phone working. So to get back to franco's kernel I pretty much have to flash my phone back to stock?
Click to expand...
Click to collapse
Yup stock or any other aosp based rom such as paranoid etc.
varuntis1993 said:
Yup stock or any other aosp based rom such as paranoid etc.
Click to expand...
Click to collapse
Thanks for the reply guys! Unfortunately my phone is going crazy right now and every thing isn't work. The internet browser stops sometimes and I definitely cannot download anything. Do I have to wipe anything for the device to start working properly?
bullsrfive said:
Thanks for the reply guys! Unfortunately my phone is going crazy right now and every thing isn't work. The internet browser stops sometimes and I definitely cannot download anything. Do I have to wipe anything for the device to start working properly?
Click to expand...
Click to collapse
Yup, just do a data factory reset, backup first though.
gee2012 said:
Yup, just do a data factory reset, backup first though.
Click to expand...
Click to collapse
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
bullsrfive said:
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
Click to expand...
Click to collapse
First flash PA and straight after that Franco.
bullsrfive said:
Okay I'll do that. I have a question about downloading paranoid rom. If I flash that then flash franco, am I just adding franco to paranoid or am i going back to just franco?
Click to expand...
Click to collapse
You're mixing up roms and kernels. There not the same thing
Sent from my Nexus 5
I think that you urgently need to read here http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
Or will brick your phone as soon as today.
I am a dummy. Basically what I was running before was stock rom with franco kernel. I loved it! Looks like I'll hav to flash back to stock and load up franco. I guess I'll need my USB cable for that.
I'm having major problems with the PA rom though. It keeps saying the process com.android.phone has stopped and I can't really do anything. A lot worse than when I was on CM. Ughh ....
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
bullsrfive said:
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
Click to expand...
Click to collapse
The best thing to do in these situations is to stay calm. When your about to flash something to your device, Always read the OP and then read it again, just to make sure you didn't miss anything or misunderstand something. Your not a dummy and It's not that there's a problem with the ROM's or the kernel's... its the lack of compatibility of the kernel with ROM. Which as you found out will get you stuck on the splash screen or in a bootloop, but its an easy fix.
Also when ever your flashing a completely new ROM, (like going from CM to PA) do a clean install, generally by just wiping the dalvik cache, the cache partition and performing a factory reset in recovery or what the ROMs OP suggests. This will make sure that there's nothing left over from the previous ROM and won't cause weird issues like the com.android.phone has stopped problem.
bullsrfive said:
Never mind it works now after I wiped the data from recovery mode. Man once I get it back to what it was before I'm never downloading another rom again lol. Thanks for all your help guys
Click to expand...
Click to collapse
You don't have to feel discouraged about flashing Roms. All of us were on trouble at lest 3 times during android experience. Now you know what to do if run into the same problem. This is about informing before doing things we are not used too. If you like a new Rom, don't flash it without understanding its features and kernel compatibility. Read threads, they are huge but at least firs pages and last ones too. Ask questions, get answers and evaluate the challenge.
There is a lot of juicy info on the first 4 threads on the general section that will provide almost all you need to know to go safe.