Related
Any suggestions on the best sense rom and kernal on the EVo 4G? Currently running Fresh 3.3 with Netarchy 4.1.9.1cfs themed with Riptide9. I get alot of battery life drain rapidly. Any ideas?? Curious if I should also switch to Amon recovery instead of clockwork, completely wipe and start over. Thanks.
What Rom is Better in Terms of Battery Life Myn's Rom RLS 3 or 4?
i tried running RLS 4 with Netarchy's 4.2.1 Nohavs and Collin's Tweak but no luck in battery life,it was horrible.
4. it is newer, which sort of spells out better. netarchys is not very good. it only works for a select few. i would ditch battery tweak and go with htc 17 or ziggy made for rls4. both are good.
Does the battery tweak work for those kernels?
Why ditch it? I thought it suppose to increase it. Battery life for me is bad.
Sent From My HTC EVO
just try ditching it. it doesnt work on htc 17 (not sure about ziggy) but just run a week without on one of the kernels i suggested. just make sure you give the kernel enough time to settle, and that you calibrated your battery correctly. i would flash a kernel with a fresh install of myns.
dkdude36 said:
just try ditching it. it doesnt work on htc 17 (not sure about ziggy) but just run a week without on one of the kernels i suggested. just make sure you give the kernel enough time to settle, and that you calibrated your battery correctly. i would flash a kernel with a fresh install of myns.
Click to expand...
Click to collapse
How do I callibrate my battery before I run it? How long would it take to settle in? What do you mean flash a kernel with a fresh install of myns? How would I properly flash a kernel?
Sent From My HTC EVO
you would flash a kernel through recovery. i mean fresh install as in wipe and reinstall myns first. it comes with htc 17 so try that first. google on the calibrating stuff
RL 4 .. but I used ziggy's beta kernel with it.. awesome battery..
tenniech said:
RL 4 .. but I used ziggy's beta kernel with it.. awesome battery..
Click to expand...
Click to collapse
How's the battery life?
Sent From My HTC EVO
dkdude36 said:
you would flash a kernel through recovery. i mean fresh install as in wipe and reinstall myns first. it comes with htc 17 so try that first. google on the calibrating stuff
Click to expand...
Click to collapse
Yeah I know how to flash a kernel but do I wipe everything? Reinstall the same rom over it?wouldn't that brick me or not make me get passed my boot animation. Really? Can you just tell me how to calibrate it please?
Sent From My HTC EVO
you would need to flash the rom, boot up, go through setting up google, then flash kernel. to calibrate, charge to 100%, unplug and replug a few times to make sure its full, then go into recovery and wipe battery stats. then reboot phone and let it sit until battery goes all the way down until phone shuts off. then while still off, charge until light turns green. then unplug/replug to make sure its full, and reboot. takes a while but you will be happy. well worth it.
dkdude36 said:
you would need to flash the rom, boot up, go through setting up google, then flash kernel. to calibrate, charge to 100%, unplug and replug a few times to make sure its full, then go into recovery and wipe battery stats. then reboot phone and let it sit until battery goes all the way down until phone shuts off. then while still off, charge until light turns green. then unplug/replug to make sure its full, and reboot. takes a while but you will be happy. well worth it.
Click to expand...
Click to collapse
But if I flash a new kernel do I just wipe dalvik cache? When do o callibrate the battery? Before flashing a new rom and a new kernel?
Sent From My HTC EVO
after flashing. it helps a lot. i would reccomend doing it every couple of months. when you flash a kernel, wipe cache and dalvik cache.
dkdude36 said:
after flashing. it helps a lot. i would reccomend doing it every couple of months. when you flash a kernel, wipe cache and dalvik cache.
Click to expand...
Click to collapse
Soyour not suppose to do everytime you flash right? Because I e been doing that this whole time..
How do you calibrate it after flashing and flashing what?
Sent From My HTC EVO
Installed MIUI ROM yesterday and just flashed Kings 11 CFS kernel but after it rebooted my touchscreen doesn't work! The phone is working but I can't unlock the phone. Tried rebooting and taking out the battery but it didn't help
What do I do?!
Kings 11 CFS is a Sense kernel. MIUI is an AOSP ROM. You need to flash a kernel that is meant for AOSP ROMs. This is flashing 101. Methinks you need to do a bit more research before you flash anything else, before you do some damage to your phone.
Okay thank you for that...but how do I un-freeze my phone? I tried going into recovery to restore one of my backups but it says there are no files found. Is there anyway I can remove the Kings kernel and go back to the original from the recovery mode? Like I said I can't access ROM manager or anything bc my screen is frozen
NM I figured it out...
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
losphn said:
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
Click to expand...
Click to collapse
Strange indeed my friend. There have been many reports of bootlooping with cm7, and many can't recover. See the thread titled bootloops and no recovery. Its odd that older cm builds and sense work fine for you, and newer ones don't. Its interesting, your observation about the HDMI kernels. I wish I had some suggestions for you, but it appears as though you've exhausted all the things I would've suggested to you already. You've even ran ruu and rerooted. If that didn't work, I'm not sure what will...
Sent from my PC36100 using XDA App
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
losphn said:
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
Click to expand...
Click to collapse
Sounds like you tried everything before you even posted! At least you can run sense roms and older cm in the meantime, while you try to figure it out. Do other newer gingerbread builds flash and run for you? Or is it just cm7? I wish I had more to suggest, but like I said, it seems like you've covered your bases..
Sent from my PC36100 using XDA App
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
losphn said:
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
Click to expand...
Click to collapse
I will also say that I had good experiences with cm. It always ran smooth for me, and as you stated, everything worked. Same with all the other recent gingerbread roms have been flawless for me too. All the boot loop and no recovery issues, take it for what its worth. To each his own. I like all roms, but ill be on sense for a little while.
Sent from my PC36100 using XDA App
Have you tried flashing the FORMAT_ALL.zip from calkulin?
housry23 said:
Have you tried flashing the FORMAT_ALL.zip from calkulin?
Click to expand...
Click to collapse
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
From the OP ^^^^ He's wiped with calk's format all, used different recoveries, he's gone as far as unrooting and then re rooting. wiping again. He's tried everything I could think of. Reflashing recoveries(different versions), ran RUU's, re rooting....what's left?
thanks buckley
Sent from my PC36100 using XDA App
Guys, this is all over the forums now. Something in CM is causing these major problems that people are not able to recover from. One theory is that it's causing a bad block in the internal memory, which apparently, the Evo can't recover from.
I think I got lucky when it happened to me last month, where I suddenly white screened for no reason, while running a CM ROM, and I RUU'd my way out of it, but the problem has gotten much worse, obviously.
I loved CM, but at this point, I'm not stupid enough to try and run it anymore.
I hate to sound rash, but I'd lose any CM Rom's you guys are running until the Dev's can figure this one out.
White epic touch (fwiw)
Rooted with Team rogue CWM (green)
Performed a Calk's format all on the phone and installed Blazer 4.1 .zip in CWM.
Installed successfully. > Flashed hitman 1.5 kernel immediately after that. no boot up no nothing.
Phone turns on, gets to Galaxy S II screen. Auto Power Cycles....but it stays off.
Turn phone back on, same thing.
*Tried taking battery out and holding the power button down with no battery in for 30 seconds
*Tried getting back into CWM to do another Calk's wipe
Now, Phone wont even boot into CWM and tells me to hook up to Kies via recovery mode....
ideas?
If you'd have read it, it specifically says on the front page, "Don't use hitman kernal."
Get it into odin mode and reinstall the el29 kernal/modem etc.
Use this.
http://forum.xda-developers.com/showthread.php?t=1433101
It's a one click so it's impossible to screw up.
EDIT: Difficult to screw up, I should say.
That is a soft brick and can usually be recovered from. Do as the person above stated. If that doesn't work(I've soft bricked 3 times and that didn't work for me) try to just Odin this kernel: http://db.tt/0QJkleJR and hold power/volume+ to boot into recovery and wipe data/factory, wipe cache/dalvik, flash ROM and gapps if rom requires.
Sent on Slim-n-Trim 1.9 using Tapatalk
I did read it, It says dont use hitman to flash. Not to 'dont use hitman kernel'
I have it on my black E4GT. 1.5 hitman kernel and blazer 4.1 no issues....
maybe i mis understood that? Am i supposed to flash a different kernel when flashing the ROM? Power it on.....then flash the other kernel? I dont remember how I did it on my black one, but there's not an issue there.
But im still working on connected it to odin while bricked...
Just odin the el26cwm kernel and boot into recovery. Wipe everything(data, cache, an dalvick) and flash ROM. Reboot and try to stay away from Hitman if possible. There are a few good custom GB kernels that are alot safer. My first soft brick came from flashing that kernel (2nd time I flashed that kernel).
Sent on Slim-n-Trim 1.9 using Tapatalk 2
I went into best buy and claimed my insurance, had them order me a new one . Problem fixed...
But out of curiosity how come my phone didn't soft brick when putting hitman on my phone?
& what kernel would you say offers the best battery life.
thanks
Sent from my SPH-D710 using XDA
xjs1200x said:
I went into best buy and claimed my insurance, had them order me a new one . Problem fixed...
But out of curiosity how come my phone didn't soft brick when putting hitman on my phone?
& what kernel would you say offers the best battery life.
thanks
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Why dont you use desperado? it's the same has hitman minus the touch recovery
In my experience, blazer 4.1 with el29 kernal had outstanding battery life and speed. When you flash from any cwm after el26, you run the risk of bricking. The reason that is, is because el26 was the last kernal with legit cwm custom recovery. Everything after has a rogue repack of cwm.
I very well may have my information a little twisted. If I do, please correct me, anybody.
Sent from my SPH-D710 using XDA