Hi guys, i swear i searched! for like days! i still haven't found out how to solve this issue. problem started when i tried hellybean a few weeks back, and then i heard someone on the thread said to try and use the latest beta uber kernel at the time, and i did. What end up happening was that my hardware keys are dead, the lights still works but very dim, i think this is because of the swipe to wake thing where it leaves your hardware keys on 24/7 as long as the phone is on, which is not that bad because i'm now used to using the nav bar. but the real problem is that now every time I install a rom that is not JB 4.1 (haven't tried 4.2 though) i.e. 4.3, 4.3.1, it gets stuck at the app optimization screen, it would go about half way through optimizing the apps, and then just reboots itself, and it'll do that over and over, like boot loop but it can actually go into the rom. So i think this is not as bad as a situation as soft bricking or hard brick, but i just really don't know what the heck is going on to even try and fix it. I've tried odin, thinking that there may be something wrong in the boot file, nada, factory reset, nada, the only thing that worked was installing the 4.1 roms, i think it is because the 4.1 roms don't require app optimization.
If anything maybe anyone out there can help me find a way to disable app optimization? maybe that'll let me get into the rom.
btw, i dont really mind using 4.1, but i really want to try the jedi rom, but having my hardware buttons dead and jedi rom being TW and it doesn't seem to have a nav bar make it impossible for me to use the rom, so i've only been able to use cyanogen 4.1, which are great but they are pretty outdated, so if there are anyway to fix that, lmk too.
Anyways, any help would be appreciated thanks a ton guys! sry for essay!
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
krazierokz said:
have you used the infamous cache wipe? http://forum.xda-developers.com/showthread.php?t=2235141 try this and it should fix your issues its because your going from AOSP/AOKP to TW they dont like each other lol follow those instructions and you should be good. also what recovery are you using to flash these?
Click to expand...
Click to collapse
Lol actually the problem started when I was on 4.3, and then upgraded to 4.3.1 helly bean, in which i tried to use the beta uber kernel, that was when the problem started. So the only roms that allows me to get pass the optimization screen were the 4.1.2 roms, which were TW, pananroid, like i tried a bunch, like super old ones, they all worked, just that when i try to get any rom higher than 4.1.2, it keep going back to that. And yeah when i tried to upgrade from jedi to aosp, to tried using infamous cache and it didnt work :/ because i've heard that's what would fix it... and lastly, Im using twrp 6.1 i think, not the latest one.
Thanks alot for the reply!
PS. I see you running slimbean 4.2.2, how is it? any probs? maybe i can try a 4.2.2 if this doesn't work out, i havn't been able to get any 4.2.2 roms cause the links are all dead, so idk if i'll have problems with 4.2.2. if there's anyway you can link it for me that'll be great! thanks!
PSS: also i've tried odin, but idk if that actually wipes everything, i'm having a feeling that it might be a script problem or something because it goes into the rom once, but it just refused to work and after like 10 seconds it reboots.
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
krazierokz said:
quick question are you trying to restore 4.1/4.2 apps on your 4.3 ? apps dont play nice like that sometimes .. also your not restoring any system apps are you? Personally i love all the ROMs/Mods the devs put out for us but im one who likes it really stable with very few bugs so i like to stick with stable ROM's so thats why im still on 4.2.2 its nearly perfect no issues here brother . When you flash the rom what are your actual steps in detail please from the time you boot into recovery until you finish so i can get a better idea here
Click to expand...
Click to collapse
Ey thanks for the reply, ok so first, I did not try to restore any apps or system apps, I even odin so everything were wiped cleaned. So really dont know whats going on. After I updated to a newer hellybean, not newest by now, and a beta uber kernel, this happens. I see two other people having the same problem too. Also I tried to use 4.2.2 roms, did not work
Anyways any insight would be apreciated!
Thanks!
One more thing, I tried twrp 2.6.1.0 to flash as reccomended by all devs and still no results. :/
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
krazierokz said:
Damn sorry brother that's pretty frustrating try dirty flashing helly bean and just wipe dalvik and cache and see if using the stock kernel helps first then see what happens :banghead:
sent from my t mobile S4
Click to expand...
Click to collapse
oh well, thanks for the reply then, im trying 4.4, hopefully it'll help... somehow... lmao idk haha
Related
Stock my Gnex was a rocket, but after I started ROMing it is a laggy MESS. I do a clean wipe on each ROM install, but even before I load up any apps it stutters like crazy. The nav buttons can take seconds to respond, swiping through home screens jerks really bad.
Currently I am running the latest CM10 nightly JB rom, but it acts this way on any ROM I have tried. It seems to be a file system issue...the lag feels like the lag you get when you update a lot of market apps all at the same time...except all the time. Opening Google now can take up to 30 seconds on a clean install.
Any ideas on what may be going on?
Grims said:
Stock my Gnex was a rocket, but after I started ROMing it is a laggy MESS. I do a clean wipe on each ROM install, but even before I load up any apps it stutters like crazy. The nav buttons can take seconds to respond, swiping through home screens jerks really bad.
Currently I am running the latest CM10 nightly JB rom, but it acts this way on any ROM I have tried. It seems to be a file system issue...the lag feels like the lag you get when you update a lot of market apps all at the same time...except all the time. Opening Google now can take up to 30 seconds on a clean install.
Any ideas on what may be going on?
Click to expand...
Click to collapse
Suggestion-1: Flash stock once again and check whether the same happens. If the same happens again you may contact for phone replacement.
Suggestion-2: Try Wiping cache and Dalvik cache in CWM and reboot. Many times this has helped my phone to work fast.
Suggestion-3: There are many other ROMs around. Try them out.
I am not an expert to suggest you. But hope above works. Hope any more suggestions come up for you.
I have tried every popular ROM out, and wipe data and all cache on every install. They all act exactly the same. I really think there is some kind of bandwidth issue on the system partition. Maybe the flash storage has degraded? I will try flashing it back to stock to see if that would makes aay kind of difference.
I had been planning to RMA it anyway because of some major screen burn in issues...but was trying not to because I bought it through Letstalk, so I need to deal directly with Samsung for a replacement...which means being without a phone for a week or two.
I believe prior to flashing you should do data wipe cache and wipe System also :/ don't know if you've tried that it's under mounts and storage in CWM =)
I just setup a Samsung RMA for the screen issue. Hopefully they simply give me a refurb instead of repairing it.
logcat, df, dmesg and in this case, maybe a 0xbench math/vm test or it didnt happen.
not sure how a custom rom would be slower than stock.
i dont think its hw issue, or stock would suffer from the issue.
sent from my i9250
bk201doesntexist said:
logcat, df, dmesg and in this case, maybe a 0xbench math/vm test or it didnt happen.
not sure how a custom rom would be slower than stock.
i dont think its hw issue, or stock would suffer from the issue.
sent from my i9250
Click to expand...
Click to collapse
My apologies, I wasn't clear. I meant that the device worked great while it was stock, but now it runs like crap. Custom ROMs may or may not have anything to do with that which is why I mentioned it. I will say that the stock-ish JB leaks ran flawlessly, while the ICS custom ROMs I was running before ran like crap. After I moved off the JB leaks to custom JB ROMs it started to run like crap again.
Grims said:
My apologies, I wasn't clear. I meant that the device worked great while it was stock, but now it runs like crap. Custom ROMs may or may not have anything to do with that which is why I mentioned it. I will say that the stock-ish JB leaks ran flawlessly, while the ICS custom ROMs I was running before ran like crap. After I moved off the JB leaks to custom JB ROMs it started to run like crap again.
Click to expand...
Click to collapse
I thought I'd update this in case anyone else has ever had a similar issue. As I was preparing the device to be sent back to Samsung for a screen defect, I flashed the stock 4.1.1 factory image, and locked the bootloader. It feels like a completely new device..flying faster than I have ever seen it go.
I do not know why this resolved my issues and a wipe data/clear cache never did. Maybe encrypting the bootloader did something to the file system a normal wipe data doesn't? But then again the JB leak seemed to run well too if memory serves..so I just don't know.
Now that it is running properly for the first time in months...I really cannot stand sending it back and being without it while waiting for the repair.
Cm10 issue same happens to me
Enviado desde mi Galaxy Nexus usando Tapatalk 2
coldrazor said:
Cm10 issue same happens to me
Enviado desde mi Galaxy Nexus usando Tapatalk 2
Click to expand...
Click to collapse
It did it on ICS ROMS too, but now that i think about it every ROM I have tried was based off CM9 or 10. Either way it's on the way back to Samsung now (for screen problems) so hopefully the next one doesn't have this odd issue.
I recently have spent a decent amount of time trying to get my inc2 to boot JB without extreme lag(maxed out CPU). I've ran JB quite a few times until one day I overclocked to 1.5GHz and my phone boot looped and could never get JB or ICS to run properly. Its been reported that over clocking over 1.3GHz can break the partition on your phone and even lose root. If u have similar problems this is what I did -
Put the stock ruu GB 2.3.4 on the root SD card as pg32img.zip
Boot into boot loader and click vol up to accept update.
you are now on the latest stock gb without root but s-off will b preserved
download super one click and htc drivers to gain root.
reboot
I flashed twrp thru goo manager cuz that it's what I prefer. Wipe and flashed dkstunna's build 3 with 4.2 gapps and boom BACK TO FAST JB in under 30 min.
hope this helps someone! hit thanks if it did
next I hope to help on the main thread one day, Ive flashed almost every ics jb Rom and would luv to help
Sent from an incredibly running JB inc2
Can anyone verify this works? Not that I doubt you OP, just wondering if this has worked for anyone else?
Quick question.
I have been rooted for so long I've almost forgotten how it is done but I don't remember Super One Click supporting the DInc2. Does this mean it does root 2.3.4?
yes super one click works for inc2, and yes it will root 2.3.4. s off is the hard part on 2.3.4 if ur not already, so be s-off. I'm sure this will work differently for everyone cuz god knows why ics jb stopped working right in the first place. I bet kernel source would fix this too...
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
I'm running PA for months now and it hasn't locked up or lagged. I came from Venom before. I wiped everything except SD card, installed CM10 10/3, booted, flash PA, booted, flashed gapps and kernel. It booted up just fine for me.
I also flashed the firmware in the Venom thread. I don't use v6supercharger, 1024MHz smartassv2, and I undervolt -50.
TheAtheistReverend said:
Well,
Tried it, and it didn't do the trick.
Still no JB for me.
Frustrating!
Click to expand...
Click to collapse
I was in a bit of a panic cause i was using viper, went to aeroevans 11/13 jb, it worked for about 6 hours and then the massive lag and boot loops started. I couldn't flash any ics/jb aosp rom, I tried mimicry, dkstunna, and aeroevean's cm9/10. all non usable, crazy lag and boot loops. viper seemed to flash fine though.
I did try the solution in this thread and it didn't seem to work so I reflashed viper formatting using aroma. I let it boot and settle. then i formated all partitions in 4ext and reinstalled viper without formatting in aroma and i let it boot and settle, finally i reformatted all partitions in 4ext, installed aeroevan's 11/13 with latest jb gapps and all has been great for the past few days. fingers crossed.
I have tried just about everything. I can't think of anything else to try. I wish we knew why some phones were doing this.
The first thing I remember not going as usual on my phone was MIUI was not installing properly. It would hang on "updating boot" during install. I couldn't for the life of me get it any farther than that. The next thing was a JB NAND wouldn't boot properly, and then it was all down hill.
Back on the same bull**** of bootlooping on cm10. There should be a warning on the viper thread to not install it if you ever want to use another rom.
I don't know why but I'm not having any problems after viper...
I'm so fresh you can suck my nits...
None of us know the answer and that's the only common denominator. I'm just lucky that Miui works or i'd be sol
Uhh so yeah, tried this and it didn't work. Never had any problems with the phone before I got rid of ViperInc. I was on the latest firmware, every ROM flash was a totally clean one, followed the instructions in the OP and CM10 Global is just sitting here bootlooping. I know the dev isn't responsible for what happens to our phones, but multiple cases of the same seemingly unsolvable problem says there's something wrong with that ROM, imho. ****ing bogus.
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
chillybean said:
Does anyone know if.the devs will try n make a fix or maybe implement one in the next build?
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
It's not the cm10 devs' problem
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
chillybean said:
Didn't say it was cm10s dev problem its the viper dev problem ..its an awesome.Rom but when some problem as bad as this with many ppl affected ..in my opinion I think the team should at least help ..when ppl start seeing this they aren't gonna want to flash this Rom...then there would be no point in developing it unless for the ppl that WANT to stay on sense...all I asked was if the team was aware n if they plan on a fix or a disclaimer that this Rom may poison your phone so it does happen to anyone else ..no need to be a smartassv2 lol I'm just asking and I'm sure a lot of ppl are too
Sent from my HTC Droid Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
I don't think it is ViperROM dev's problem, nor is their responsibility to help. They make it very clear they hold no responsibility for what happens to your device when you flash their ROM. They are also not making any money from the free rom they put out for us to enjoy, so their is no driving force really behind their desire for "fans" if you will.
That being said, it would be nice if they could help and did. Has anyone directly, and nicely asked Nitsuj or any of the Viper team for help?
fen0m said:
after getting JB to work for awhile I decided to flash the .312 radio, booted and 5 min later I get jelly beans to the face... now I'm stuck on viper again. I tried multiple times to recreate whatever fixed it the first time and I get nothing. I remember reading somewhere awhile back that going stock s-on then going s-off root might solve the problem
Click to expand...
Click to collapse
Doubt it. I went all the way except for S-off and re-rooted but it still will not load any JB rom I try. But by all means, it might be worth trying if you're so motivated. Seems like some things work for some, but not for others at this point.
Just got back onto CM10. Was on Viper, did full wipe x2, formatted partitions to ext3 in 4ext Recovery, fix permissions, then formatted cache.
Then...here's the weird part....since Mimicry was the only non GB Rom I could get to at least boot, I tried a clean flash of it. Used only the baseline items in the Aroma installer (only things I installed were the jb animations, trebuchet, v6, and daemon). Booted into Mimicry and let it settle without signing in to Google. Profit!
Next phase was a full wipe x2, flash newest CM10, flash GApps, then format cache.....double profit! Hopefully this will hold up. Will report back once its had time to fully settle.
Sent from my Incredible 2 using xda premium
Sry didn't mean to say it like that but I know its not their responsibility..I just asked if they try to figure this out..I'm gonna try this mimicry method...I hope I profit like twice
Sent from my HTC Droid Incredible 2 using xda app-developers app
I wouldn't call it a method really....I think I may have just gotten lucky
Sent from my Incredible 2 using xda premium
Okay, so I have been a flashaholic for the past couple of years and been on the AOKP nightlies for a very long time.
However, since the last month or so, every time I try to flash (clean and dirty) a new ROM or upgrade to a newer nightly, the flashing process goes on pretty smooth as expected. But, here is the thing.... after booting up fine, it starts to optimize the apps and I see it going through the entire cycle of apps. When all the apps are optimized, it says "Starting apps" and this is when I feel a vibrate and the phone reboots and does this over and over. My only way out of this is to boot it back into Recovery (TWRP 2.5) and restore my backup and sadly continue using what I had before this exercise.
I have tried various combinations of wipes, fix permissions, kernels, radios, etc. and am totally stumped here!!
Help please as it bugs me to no end when I see crazy new features the newer ROMs are dishing out and I cannot taste them
by clean what are your actual steps you mind elaborating a bit more of your steps, and with which ROM this happens on have you tried a stable as oppose to a nightly to see if it will fix your errors, as far as flashing do you ever format system in mounts and storage when you flash ROMs ???
Clean: Wipe Cache, Dalvik, Format System, Data. I haven't tried formatting the Internal SD or Preload partitions yet.
This happens with quite a few ROMs... I have tried SlimBean, CM 10.1, AOKP M2, PA so far. See the same behavior on nightlies or stables. I haven't tried Stock ROM yet... maybe should give that a try as well.
Let me know if I can give you more information to help me out.
since it seems to be happening on every ROM for you i would suggest you try going back to stock and re-root and try again, it doesn't take that long it just really sucks to do everything from scratch, but its the only way you are going to know where this problem is coming from also if you are on TWRP 6 that might be the problem everyone has been having lately it sometimes works sometimes doesn't have you tried opening ROM MANAGER and fixing permissions only from within the app...see if that squashes your bugs just trying to give some ideas ....
I would hate to go back to stock and re-root all over again. But if all else fails... I guess that remains as my only option.
I am on TWRP 2.5 for quite some time now and have successfully flashed using that numerous times before this problem started... not sure what you mean by TWRP 6 (you mean 2.6?)
I do not have ROM Manager on my phone, will give that a shot as well before resorting to the "Stock" option.
Thanks for your help!
yeah i ment 2.6 lol DOOHH!! and yeah you def sound like you know what you are doing so im sure you will figure it out just wanted to give you some ideas ... and for the record its always nice to take a break but good luck bro sorry i couldn't help you more
It was an issue with the Kernel I guess!!
Flashing SlimBean b8 + gapps followed by the UBER Kernel after wiping the hell out of everything as my last ditch effort I went past the "Starting apps" while I was feverishly holding onto the Vol UP + DN to get into recovery if it fails again.... to my surprise, it went past that screen and there was the start screen I have been looking forward to.... what drama )
I guess will follow all my flashes with the UBER kernel going forward.
awesome man!! glad you got it fixed - Like i said i knew you would figure it out good stuff man, now you got more knowledge and can help others if they run into the same issue happy flashing ! take care
I was running liquid smooth, which was running nice and smooth.. but then the back camera just stopped working. it was always black and would just crash. So i wiped app data.. still didnt work. I factory wipe / wiped cache and everything, still it didn't work. I flashed a ton of new 4.3 roms like the new aokp, slim bean 4.3 , PA 3.99 , and still the camera didnt work..I dont know what else to do. I'm not super experienced so bear with me, please help me out.
try restoring your stock back up or flash the stock Rom and root again
chiefsfan645 said:
I was running liquid smooth, which was running nice and smooth.. but then the back camera just stopped working. it was always black and would just crash. So i wiped app data.. still didnt work. I factory wipe / wiped cache and everything, still it didn't work. I flashed a ton of new 4.3 roms like the new aokp, slim bean 4.3 , PA 3.99 , and still the camera didnt work..I dont know what else to do. I'm not super experienced so bear with me, please help me out.
Click to expand...
Click to collapse
Restore a completely 100% stock ROM. If it works, then there's a problem with the ROMs your trying to flash. If it does not work then you have a hardware issue.
I'm trying, but when it asks me to enter the S / N into kies it keeps saying that its incorrect even though im reading it right off the darn sticker..
cheifsfan645: Ive never learned about flashing with kies but try searching for "flashing stock rom with odin" This is the method I use and there is no serial numbers or any info needed. Make sure you use the correct image, it has to be for your carrier and phone or you could end up with troubles, even in some cases, bricking your phone. An even more foolproof method is to use "Samsung Toolbox" because it comes with detailed instructions and is a mostly automated process. I hope I may have pointed you in a helpfull direction, Im still new to this stuff.
Sent from my SGH-I747M using XDA Premium 4 mobile app
chiefsfan645 said:
I'm trying, but when it asks me to enter the S / N into kies it keeps saying that its incorrect even though im reading it right off the darn sticker..
Click to expand...
Click to collapse
Whoa, I've never heard of that one. I'm assuming you flashed a stock odin image? Maybe try to download the stock image from another source and see if that helps. I've never had that happen to me before.
What recovery are you using? If its TWRP make sure you have the latest. If its not then make sure you update to the latest. I got a replacement device. Rooted it and Rom'd it and my camera broke just like you are describing. I want back to full stock and camera worked. I then rooted it and camera worked. I then talked with friend and he advised me to flash the newest TWRP. I did and my camera came back.
Download TWRP from here http://techerrata.com/get/twrp2/d2att/openrecovery-twrp-2.6.3.0-d2att.tar
Download odin from here. http://forum.xda-developers.com/showthread.php?t=2189539
Install odin and run it. Reboot the phone to download mode make sure you have usb debugging checked in settings. Then check the PDA box and browse to that tar file and load it and then hit start it will flash your phone will reboot and the camera should be working.
ok, i just got a captivate glide from my gf, ive been looking into flashing and rooting for about 3 months, but i JUST got an android (ik so behind) but originally i was looking into sidekick 4g for keyboard but this worked too in my eyes and it was free so i figured why not, but either way i wanted to root and flash, but now im at a barricade that im not sure if to continue or not, i rooted using one of the threads directions
this one to be exact
http://forum.xda-developers.com/showthread.php?t=1378082
i ran into a barricade here at first, the initial set up wouldnt run, i fixed that by doing the Vol. Down plus Power recovery mode i think its called, and clearing memory then rebooting and it worked fine, i was rooted and had the super user app as well (some boxes from widgets were invosible like accuweather and the android assistant thing but, thats ok).
ok next step i knew if i was supposed to try to flash a rom i should back up EFS which i did with some difficulty (such as figuring out i needed busybox lol)
ok now my next step was installing ROM manager by clockworkmods
NOW onto the actual part i need help with that i couldnt figure out myself (and excuse me for being newbish here too as i dont know much but im not bad with tech either but i felt i damn near bricked the phone in the process already so i WANT to continue with guidance before i do anything else)
now that im rooted, now that everythings backed up on my computer and ive got rommanager and everything
what now
will i still be rooted once i flash a rom? will i still have busy box, super user, all of that stuff? (as the thread i rooted with clearly said that was flashing a rooted rom)
and theres some other personalization questions i need help with too but thats more towards once ik what direction im going in
and uh.. not sure if it matters but im on metropcs service, so occasionally i get issues if i have to reset the phone at all as i have to change the ANP or ADP cant remember the acronym but ive got to change it from some t-mobile one to the metropcs one, i dont see why that would matter but, its a just in case emasure, also im using the ATT one not rodgers (not even sure what rodgers is tbh)
EDIT: OH one last thing. the rooted rom is gingerbread.. thats my main reason for wanting to change it.. i want kitkat, or would prefer kitkat, but id like some opinions as well on what perhaps the best ROM would be, im not sure between omni-rom and cyanogynmod which are the main ones im looking into, but, again, get more into that later
ok now
now im looking through the Rom info.. and.. im starting to wonder.. is it even worth it?
what sacrifices am i going to be making if i flash a custom? what all can i change without flashing a custom? and can i still get kitkat without screwing up my root (KIES?? or ODIN??) its just the things like this that make me wonder... i want the root, that much i DO know, theres so much i can do with rooting im seeing this and enjoying this, but i just need some type of guidance as to what to do, and if theres a better place for this thread please feel free to move it as i do see that it might be ok to have under general ndroid questions, but, i wasnt all too sure on it as this isthe phone im using so any issues deriving from the phone type might screw someone up
Most of the custom roms are rooted already.
There is only 4.0 official, no kitkat. We dont have odin custom images, nor KIES. You must wipe your data, system, boot parition, install KK means clean phone for you.
I think KK is better then official, but it has some limitation.
bubor said:
Most of the custom roms are rooted already.
There is only 4.0 official, no kitkat. We dont have odin custom images, nor KIES. You must wipe your data, system, boot parition, install KK means clean phone for you.
I think KK is better then official, but it has some limitation.
Click to expand...
Click to collapse
ok.. im confused then, cause i had kitkat on it when i used kies to update firmware, or atleast i thought i did, perhaps because both had 4 and i was sleepy i was confused lol, and sorry but if KK doesnt mean KitKat then what does it mean. and how high will a custom Rom take me in terms of lining up with official, just to ice cream sandwich?. and.. cyanogenmod, ive been tempted to get it but.. im not sure exactly which one to get because when i was on the site i only found captivate in the devices not captivate glide
EDIT: one more thing, as far as wiping the phone clean and starting over, what do i use.
and of course if you say the rest are rooted, then whats one of the best kernels and roms to use then, its true i want atleast ICS on here, so.. if im right i looked up KK, do you mean KKlauncher the app?
well...
ok i soft bricked my phone, it just shut down in middle of installing some fonts, and for some reason i cant restore it even tho i created a back up as it advised me to do so, i get errors in CWM recovery,
now im about to just do this
using this as a sort of reference so people can keep track of me if something else happens that i mess up..
http://forum.xda-developers.com/showthread.php?t=1890125
miseryvein said:
ok.. im confused then, cause i had kitkat on it when i used kies to update firmware, or atleast i thought i did, perhaps because both had 4 and i was sleepy i was confused lol, and sorry but if KK doesnt mean KitKat then what does it mean. and how high will a custom Rom take me in terms of lining up with official, just to ice cream sandwich?. and.. cyanogenmod, ive been tempted to get it but.. im not sure exactly which one to get because when i was on the site i only found captivate in the devices not captivate glide
EDIT: one more thing, as far as wiping the phone clean and starting over, what do i use.
and of course if you say the rest are rooted, then whats one of the best kernels and roms to use then, its true i want atleast ICS on here, so.. if im right i looked up KK, do you mean KKlauncher the app?
Click to expand...
Click to collapse
I mean KK is kitkat. I dont know what did you read, but there is ICS the last official.
Cyanogenmod and other custom roms has own official support, that what you can download rom their site. We dont have official support from them, you cant download those roms from there. You can found download link in rom's threads.
Start reading here: http://forum.xda-developers.com/showthread.php?t=2623635
I preffer CM11, but yon can found many other KK roms.
If you brick you randroid, just reinstall same you had.
bubor said:
I mean KK is kitkat. I dont know what did you read, but there is ICS the last official.
Cyanogenmod and other custom roms has own official support, that what you can download rom their site. We dont have official support from them, you cant download those roms from there. You can found download link in rom's threads.
Start reading here: http://forum.xda-developers.com/showthread.php?t=2623635
I preffer CM11, but yon can found many other KK roms.
If you brick you randroid, just reinstall same you had.
Click to expand...
Click to collapse
hell i got it back on default ICS now lol, i screwed it up XD and yea ik you guys dont have the downloads your selves but the links and guidance of what i should be doing is basically what i was after ill look at the link you gave me, i think im going to chill out with the flashing right this second, but ill pick it back up later im sure, i atleast liked the cpu setting apps. made my battery last much longer and for what time it lasted i loved it
ok another thing im concerned with is alot have bugs that are deal breakers for me, such as messing up the keyboard (the whole reason i have this phone)
and looking through it i do like CM11 too
but looking at your post
http://forum.xda-developers.com/showthread.php?t=2588304
can you explain what you mean by the fixed rotation and skype issues,
and perhaps is there a full feature list somewhere? thats one big thing i want to look at if possible, i usually just keep seeing bug fixes on any ROM
Voip apps (skype,vibert etc) have strange sound, only temporaly fix exists.
When you take a picture with camera, it has fix rotation, I dont remember witch position is the fixed one, but you make photos with different rotation, the picture will be rotate 90/180/270, and you must fix the image.
Most importan bug are: phone call sound doesnt work with BT devices, and voip sound is buggy.