Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
lourivellini said:
Ok so for the last few months, I have been switching between roms, looking for something with good battery life.
Every rom i tried, the battery life often was awful (10-12 hours light use) until pinnacle came around. With pinnacle, the standby drain was around 1% per hour, and it just kicked ass.
After pinnacle i went and tried cyanogenmod again, and to my dismay, the battery life still sucked. So back to pinnacle i went.
Then someone said to me that i dont have to go through all the hassle of flashing back to jf6 and having old bootloaders and all that crap was unnecessary, so i decided to see if i got better results in CM coming from pinnacle.
Well IT WORKED!!!!!!!!!!!! Battery life is on par with pinnacle as far as i can tell.
My previous method was:
flash back to jf6 via one click odin
root phone and install rom manager
install cwm for captivate
then choose mtd 2xx
then boot into recovery
wipe data, cache, and dalvik cache
install cm7 zip and gapps zip
My new method:
follow pinnacles instructions to install pinnacle
boot into recovery
wipe data, cache, dalvik cache, battery stats
install cm7 and gapps
So my possible conclusions are:
-That one click jf6 package sucks, theres no reason to every flash back to it. I plan on finding a different one click if i ever need to flash back to stock. Ill probably use a 2.2 or 2.3 one click
-CM is not completely wiping everything when it installs, and somehow performs better when coming from a gingerbread rom, than coming from eclair.
-I have wiped the battery stats in the past, but maybe doing it right away helps?
-cm7 build 181 is wayyy better than 179 - (not likely)
Not sure what else it could be. The same apps are always installed. I tried both the stock kernel and glitch v12 last time and both had bad results. This time im using stock with great results, and i havent had the urge to switch, because i dont wanna mess it up.
Hopefully this helped someone, or at least shed some more light on way some people get terrible battery life with some roms. I bet using this same method, I would get better results with roms I've tried in the past (APEX, MIUI, any other i9000 based roms)
They should really change the directions to CM if this is the case. Maybe this isnt the best for everyone, but the gingerbread bootloaders that come with pinnacle seem to work fine with CM, so why make people waste their time.
Click to expand...
Click to collapse
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
minduka said:
Under what usage conditions are you getting 1%/hr?
With data and wifi off I get about 1%/hr
all on 10%/hr
Click to expand...
Click to collapse
everything on connected to wifi. I will post screenshots when i get home. I dont install too many apps, but i use facebook, twitter, beautiful widgets, and doggcatcher - which are apps that may possibly run in the background.
10 percent seems like a lot.
KreepyKen said:
The big battery killer for me seems to be when the phone is searching for data signal. I had my phone at a customer site with no AT&T 3G coverage and no wifi to tap into. My drain was about 22% an hour. I almost crapped my pants when I checked the time about two hours into my day and I was at 55% (first time I looked at the phone in two hours).
When I get to work, if I forget to connect to wifi, I get around 10% per hour drain because the 3G signal in my building isn't that great. That's with minimal use.
If I get to work and connect to wifi, my battery drain is about 5% an hour with minimal use.
Click to expand...
Click to collapse
yea i would definitely try reflashing. Try my method, and let me know if you get better results with that. Mine has been worse in the past, but never that bad.
alecao said:
That´s great news!
Wich Pinnacle version were you in before flashing CM7?
Click to expand...
Click to collapse
I was running pinnacle 1.2. I never felt the need to update to 1.3, and didnt want to risk it with the results i was getting.
Anyone who thinks the captivate sucks on battery should definitely try out pinnacle. And from there try out cyanogen again.
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Mr. Dr. Prof. Sean said:
Hmm... I'll have to try that. I've been getting pretty terrible battery life with just about everything recently. Thanks for the tip.
Click to expand...
Click to collapse
yea please try it and do exactly the same thing as i did. I would like to see if people get the same results as i did.
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
The only difference between both methods is the bootloaders, which may or may not be the reason for the results you're seeing.
studacris said:
What ROM you're on before a flash does not matter. The script completely wipes the OS before the flash. So either way it's writing to an empty partition...
Click to expand...
Click to collapse
thats exactly what i thought, so why should it even matter if i was on stock jf6 or not? (like it says in the instructions)
Somehow it is affecting it though, and i definitely have experienced better results. If i get a chance i will try flashing back to jf6 and doing it that way, and then doing it my way again. But im just listing what i did, and what my results were.
Thats why i was asking if it made sense.
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Jf6 one click doesnt suck, its just pointless and potentially harmful now.
I have been using uckf1 /w pit file to flash back to "stock" (if i need to repartition) but i removed the bootloaders from the package to avoid cataclysmic destruction.
Generally you don't need to flash back to stock at all anymore because most ROM's are full wipe.
studacris said:
Isolate the variables and test them individually. Like I said, the only difference is the bootloaders...so when you flash cm7 from jf6 again after you find out what the drain is like, flash JUST the gingerbread bootloaders while still running cm7 and see if it changes...
Click to expand...
Click to collapse
will try it out probably this weekend.
Question though: Should i just flash the gingerbread bootloader included in the pinnacle install, and then never touch the bootloader again? Ive heard the 2.3 bootloaders work universally, and that its a bad idea to flash bootloaders.
I used to always use the odin one click to jf6 whenever i would change roms. From now on i may use the 2.2 hemidall package i found. The only problem i see with that is it doesnt delete the data partition, and i think the last time i used it, it didnt delete apps i had installed, and i had force closes that made my phone unusable.
Why is flashing a rom on a phone more difficult than installing a OS on a computer.
Basically, i just want to completely format and do a fresh install everytime i put a new rom on. I dont see why things like data and cache arent wiped by default.
I personally like the odin one-clicks that end up erasing EVERYTHING and changes it exactly how it should be. Why are more roms available as odin one-click?
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
studacris said:
You only need Odin or heimdall as a recovery option from a soft brick, or to go back to a touch wiz based ROM from an aosp ROM (cm7/miui) as you need to repartition.
Just flash the Ginger boots and leave them alone, corrupted bootloaders from a bad flash is the only way to hard brick, so to minimize that risk flash bootloaders as minimally as possible (I only suggested that earlier as a suggestion for to to figure out if that was what helped), unless you have done the unbrickable mod then by all means flash your boot loading butt off with no worries.
So if you are on a touch wiz ROM, I897 or I9000 all you should have to do to is just flash over it. And if that goes sour and you can't boot back into cwm then, and only then, should you resort to Odin.
Think about it, if a ROM can flash over a stock ROM what is different about flashing over a custom ROM? Nothing.
If you want to make extra extra sure it's a "clean flash" you can wipe data/factory reset, wipe cache and dalvik cache and then flash, but the ROM should do that.
Click to expand...
Click to collapse
So if i decide to go back to pinnacle - i shouldnt one click jf6? But i at least need to hemidall - which doesnt flash bootloaders. And going from cm, i really dont even have to go back to jf6, i should probably at least go to one of the newer stock froyo roms.
Or even better - i should flash to a rom through odin that is already rooted and has cwm installed, so when i flash to a new rom, i dont have to manually root, and then install rom manager/cwm everytime. Right?
There are Odin packages without bootloaders...and heimdall ones with them.
Yes from cm7 you need to use Odin/heimdall. If using a non 1 click Odin you must place a .pit in the pit slot and a .tar in the pda. Which ever you use is up to you.
Serenity 6.1 seems to have a long life, contrasting with OR5 or Continuum6.2.1
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
alecao said:
Are you using the same modem that comes with CM7 (JL3) or did you flashed another one?
Click to expand...
Click to collapse
Everything stock.
Sent from my SGH-I777 using Tapatalk
Related
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
boardsportsrule said:
used to be able to flash any combo...even I-9000 roms(darky's...) with proper kernel and modem combos.
Had no problems ever!
Now, ANY combination kills my signal. Paragon; perception, pheonix, the list goes on and on.
The only ROM i can run is Cognition. If i flash to a different kernel/modem combo,(even while running cognition) I have problems.
Now atleast I am stuck with a good ROM, but I would love to fine-tune with a different kernel/radio and I have NO idea why my phone is acting this way. I am thinking maybe it's a SIM card thing(I pulled the SIM out one timebefore the phone was fully shut down...
other than that I cannot think of anything weird I have done.
In between flashes I have ODIN'd back to H2 and then Master Cleared.
Flash via CWM. Root with 1-click.
PLEASE give me some idea of what I have done?!?!!?
Or is it warranty time for the phone due to 'GPS' issues..
Thanks
Click to expand...
Click to collapse
Find the modem cognition uses that gives you the least problems. Are you flashing to stock before each ROM?
Sent from my SAMSUNG-SGH-I897 using XDA App
Yep, back to stock & master cleared between(only once problems arised..back in the day I could just flash to what I wanted and never really had a problem. Went back to stock once when the new flash responded strangely.)
Looking at cognition, I get minimal information, I THINK it's stock radio/kernel..
http://forum.xda-developers.com/showthread.php?t=912657
Any one???
I would..check your usb plug/cable/port first..make sure it isn't bad and effecting your data transfer..Make sure your not plugged into a external port and plug into PC directly..
Re down load your roms and kernels again..keep them separate from what you have already used..
Flash back to stock..master clear delete all data on your internal and your data
Re-install everything over again..cause it sounds like something got corrupted along the way
Mac
Mac11700 said:
it sounds like something got corrupted along the way
Click to expand...
Click to collapse
Thats how I am leaning, but i dont think it's with the roms/kernels/radios i have downloaded...since I have tried so many damn copies that wouldn't make sense. also tried downloading directly to phone, eliminating the "3rd party" computer, and have used drop box in the past...
I have flashed to stock and master cleared, i could do it again, but i am tempted to go back to stock and try to exchange it for a new one due to either random shut-offs or GPS(both of which mine are effected by..) but i would like to avoid this hassle...
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
boardsportsrule said:
If something did get corrupted, any idea how I'd solve that? I am at a loss as to what could have gotten corrupted that a odin'd stock + master clear wouldn't solve...?
Click to expand...
Click to collapse
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
opcow said:
It's possible that your phone has a hardware issue making it more finicky. Try stock for a bit and see if the problems go away. Maybe try Andromeda 1.0 and see how the KP1 modem works (or just flash KP1 on some other ROM).
Click to expand...
Click to collapse
hopped back to Stock... Gonna run things here, see which problems arise, and go from there. Can you flash a different kernel onto the stock ROM? I'd assume you need a 2.1 kernel, and i don't think many are retrofitted to 2.1, but the KP1 modem is a good idea, ill let things pan out on stock and see what happens if/when i flash kp1 modem.
funny fact: fire fly made problems for me... it's based on rogers 2.2, same as cognition. that seemed odd to me.
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
nvertigo said:
so my sgs4g was rooted and got on gb with the gb starter pack thread, after which i jumped around between a few roms and am currently running octaneGB.
however, it has always had stability problems, and i can't figure out why. possibly because i messed up bootloaders? i'm pretty sure it can't be the fault of the roms i flashed.
from here, all I want is a stable phone.
can i wipe the phone as it is and then use the oneclick heimdall SMS kj6? would this put me on rooted GB with CWM and good bootloaders? could i simply cwm flash a rom like valhalla after that?
any advice would be appreciated, thanks!
Click to expand...
Click to collapse
Yes, you can use the one-click to put KJ6 on there then flash a different ROM via CWM.
Personally I've had the best experience with Valhalla ROMs. Last night I just flashed RAVERX3X latest Valhalla Black build. Its low profile so it's quick and responsive, and even better, not a single instability issue.
Sent from my SGH-T959V using XDA App
thanks for the advice guys!
I did the first flash step, which worked successfully and rebooted my phone. then i tried to flash the bootloaders that came with it, but uploading PIT 1/10 failed, and it froze trying to end session. i pulled the battery and the phone seemed bricked, but i connected the cable and oneclick said it was connected (no download mode screen, no lights at all). so i did the initial one-click flash and let it reboot again, then flashed valhalla black.
nothing SEEMS to be wrong, but i'm a little scared. can anyone weigh in on what happened?
You're ok. I can't explain what happened but people have reported similar issues, nothing on the screen but it can be seen in ODIN, and were able to recover (as you did) just fine.
Sent from my SGH-T959V using XDA App
This section of XDA is small, but good in terms of quality.
I just flashed Raver's Cyanogenmod/Valhalla hybrid and it is smooth and stable.
One-Click...
At the beginning of the week, I still had Froyo on my device.
I used Bryan's one-click (SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar)...
(I had a scare, too... which involved the so-called "Rainbow screen" -- but FB suggested I run the one-click, again and also to do the Bootloaders -- and everything turned out ok).
But, I needed to get CWM 5 (and, that particular one-click had CWM 3.0.2.8x)
So, I flashed an update of Bryan's kernel (sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip)
And, because I was feeling overjoyed at all the goodness that I'd seen so far, I flashed RaverX3X's rc3.zip (from Team Acid's Source Forge site)...
And, life is really, really, really... good.
yep
+1 Valhalla black edition! Installed today and love love love.
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
nvertigo said:
ok... my phone is now crashing and rebooting all over the place after flashing valhalla black. it seemed fine for the first hour. should i try the one-click again? or did i not wait 10 minutes after flashing the rom, maybe?
anyone know what could be the problem?
thanks in advance!
Click to expand...
Click to collapse
Not sure about the crashing but I experienced reboots because of the kernel Valhalla Black uses. There are fixes out there for that part of the problem but what you should really is perform a factory data reset, do the one to get a ROM with CWM on it, then use CWM to install Valhalla Black per the instructions on the page for it. I've a feeling you'll be much more stable after that.
As for the 10 minutes, that's basically to allow your phone to rebuild the Davlik cache (cache with optimizations for your apps). Definitely let it sit while it does that just to be safe.
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
nvertigo said:
thanks yet again. will try this asap!
can i assume that my bootloaders are correct after the weird issues from the last page? you mentioned that it happened to several people, but it still bothers me that technically it never got past 1/10 uploading PIT file :x
also, regarding the problems with the kernel, can anyone point me to a kernel that works with valhalla final and is known to be fully stable? i want to try to do everything to get the phone usable.
Click to expand...
Click to collapse
If it was fully booting and you weren't getting the "rainbow" screen, then your boot loaders are fine. If in doubt, go check out bhundven's one-clicks, and run one of them - twice. The first time it doesn't let you check the boot loader box but the 2nd time it does.
Valhalla Final comes with bundven's beta 2c kernel. I believe people are running that without issue. Keep in mind Valhalla Final and Valhalla Black are two different ROMs with two different kernels.
I did a one-click back to stock (factory reset, cache wipes, etc.) & am running bhundven's latest beta kernel with no problems (thus far).
I have come to the conclusion that something is wrong with my phone. I have tried to install ICS....a lot. I am not exagerating when I say that I have tried every Odin install, and every ICS ROM that has more than a few positive results. Nothing will work. I am not new to flashing, I have had a Captivate, Inspire, Tab and have had no issues with those, even created a few themes and build.prop tweaks. I know what I am doing and I follow the OP instructions perfectly. The damn thing just wont take. I get the white Samsung screen, a black screen, a vibration, and a reboot. So at this point I think I am just going to stick with GB for right now and hope that either the offcial ICS update works (when available) or maybe 5.0 later this year.
Two weeks of try to make this work has run me ragged. Outside of the ICS issues though this is by far the best device I have had in terms of performance and reliablility.
Rant over.
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
icenight89 said:
Did u flash the uclc5 radio at any point in time?
If not what radio did u install, and did u install it before u flashed ics rom?
What recovery were u using?
Did u odin back stock in between each ics attempt? Did u use dark side wipe at all?
*#* Google dropbox, its useful.
https://www.dropbox.com/referrals/NTcwNDE0ODUyOQ *#*
Click to expand...
Click to collapse
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
mahausrath said:
Personally, I haven't had anything but trouble with superdarkside. Its an excellent tool, but for me, hasn't meshed well with ICS. You should try following seans op for Sky ICS UCLC4, without using darkside at all to change from where your at now.
Also, the modem (aside from UCLC5 for some) has no effect on the installs, I sat on Sky ICS UCLC4 with the UCLC3 modem for a couple weeks without any issues at all.
I have tried all of the CWM mods posted here, and to be honest, my favorite is the CWM touch when installed from rommanager. Seans roms seem to take better with it more than the rest. The CWM touch that is posted on the sky UCLC4 OP is good, but it has a couple minor bugs.
Are you using SuperSU or superuser? Supersu has backfired on numerous occasions for me, I always stick to superuser (and I'm sure I'll be flamed for the comment. Every skyrocket reacts differently, remember)
Click to expand...
Click to collapse
I will give it a shot. I would really like to get back to ICS, I got so used to it on my other phones.
I have been using superuser, haven't had a problem yet from that.
lacer4576 said:
I have not tried the uclc5 radio. I saw a bunch of posts about it being for the Note, however the ROMs I was looking at all used ucld2 and ucla4 radios, so that is what I have been trying. Even the ROMs with the radio included as part of the install didn't work. And yes, I installed the radios (when applicable) before attempting the ROM install.
Recovery is the same, most ROMs suggested a particular recovery and I attempted using the suggestion in each OP, then attempted with the newest recovery when they didn't work, so I bascially did each ROM I tried twice. I did flash back to stock before each attempt.
I do have the dark side wipe and ran it before every attempt, then followed the OP instructions to perform the normal wipe\format and dalvik wipes when directed.
What kills me is that I get the same bootloop when trying an Odin ICS. The only version of that I have not tried is the version that was extracted from the oneclick.
I even had problems getting a GB ROM to install. I did manage to get superlite 3.1 installed after several attempts. You better believe I have nandroid backups of this working install....in several places.
My other concern is that even when the official update gets pushed out that I won't be able to install that either.
I appreciate your suggestion to use uclc5 radio. If I try to install that I suppose I need to try and flash a ROM that does not come with a radio as part of the package?
Click to expand...
Click to collapse
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
^^^ this makes sense. Also I was asking about the note radio to advise u against it, or u may end up screwing up ur phone even worse, and have to make a visit to my corrupt efs fix thread lol.
hcyplr29 said:
I know this may be silly but have you tried to re-download the one click leak your using? Maybe you have a bad download or a corrupt file. And, or try to use a different usb port when you flash. It seems you've tried everything and maybe you have a defective device. I started having a lot of issues recently after going from ROM to ROM so I just flashed the one-click to get back to a clean state and then carefully chose which ROM I wanted to use and carefully install it. I've always used Darkside Superwipe but since I've quit using it, things have been much smoother. What I do now is what most Devs are saying now is to wipe/factory reset multiple times and format/system multiple times. If thats not working maybe go all the way back to stock GB with k0nanes stock tar and go from there. As far as the uclc5 radio, be careful!! I'm sure you've read that it can corrupt a partition and cause issues. I did flash it once and it did work for 48 hours but I noticed signal loss so I flashed back to uclc2. Maybe I got lucky it didn't mess me up, who knows? And if you have an issue not receiving an official update, IF you do go back to the stock GB tar, do a nandroid and flash that when it comes out. Just make sure you flash the stock recovery before you take it. I have a stock GB backup on my SD, so IF and WHEN it does come out, I'll just flash the backup, flash stock recovery and take the OTA. With your constant bootloops, it seems to me its a bad download or a defective device. It seems you've tried everything. Good luck...
Click to expand...
Click to collapse
I will try to get a different download, but I do not think that is it. The only reason I say that is because my phone had the exact same response for EVERY ROM I have download. They can't all be bad files. I have tried on two different PCs with three different USB cables. Good thought though, I have had bad downloads before. I am going to keep trying as the ROMs are updated and hope that I figure out what is going on, and hope that I can get the official update at some point. Then I will just root it and get rid of the bloat myself if I have to
I am going to stay away from the L5 radio, not worth the hassle.
On a side note, if installing a rom from the site, remember, most will work with the "base"
But need to reset/full boot before "updating".. dont just flash rom and flash update then reboot
I had a hard time with ICS as well with different problems, all I can say is it disproves the definition of insanity. Trying the same things over and over again will eventually make it work!
Hang in there, it's worth it. Whenever you do get the ODIN one click to work I highly recommend flashing Raider03's SMOOTHIE ROM. Awesome battery life and extremely "SMOOTH"! But be prepared for a few FCs and bugs with all of the ICS ROMS for now!
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
kintwofan said:
You can just keep flashing until you find a ROM you like. Odin is just basically when things are messed up and you need to go back to stock. I think it was RSD on the Droid 1.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Click to expand...
Click to collapse
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
xsteven77x said:
You can flash it just to go back to stock. Doesn't have to be cause you messed the phone up. I think it's also good to do it occasionally with a pit file to wipe/fix all partitions (not just /system and /data, but ones like the hidden radio/GPS partition etc.)
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well of course you can use it to just go back to stock, but the average user only does it when they mess up. I do agree though I personally even I find my daily driver like to start fresh then flash the keeper ROM.
Sent from my Galaxy S3 running Eclipse ROM V2.1
Have been rooted since day of pre-order delivery. Have flashed multiple ICS/JB TW roms. I stay away from AOKP/CM roms just because of loss of features so can't report on those. I have never lost wifi or GPS. Never had sim card error. Had no problems with TWRP and haven't used CWM since worked with Koush on Tbolt problems. We worked those out and I still run CWM touch on Tbolt. Used Amon on Rezound. Recoveries are what you feel comfortable with. I use whatever works best for the device although that is irrelevant to this subject. I still use the old school clean wipe of data/cache/dalvic cache/system for all flashes on all devices and all recoveries. Ultimately have never had a reason to use Odin or go back to stock since initial root. Only bugs I have seen are rom related and nandroid back to working rom fixed it. There are differing opinions on what I have just posted but I have had no problems with flashing anything on my last 3 devices and have never bricked a phone even though I may flash 10 times a day for multiple devs on multiple devices. Maybe the old school recovery devs were on to something. Beats me.
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
takota6 said:
Kool..I'm catching on., slowly..
Now If I do an Odin with pda can I use a rooted oem Rom to accomplish this newest leak that is said to have killer batt life?
Click to expand...
Click to collapse
Yes you can but they all have killer batter life. No need to Odin you can flash it in recovery. Only have to Odin stock RUU to get firmware update. If you do it could loose root and ability to unlock boot loader. You will have it as long as you keep it. As soon as you flash another rom it will wipe that one and you will be on the base that the rom is based on. This is why the devs update to latest bases whether they be leaks or official. Best you can do is flash newer radios and kernels unless the ROM Gods tell us to update firmware and then it will be checked and deemed safe. Never Odin/flash an OTA/leak unless it has been cleared by the Android Gods. I have only used Odin once and that was because that was only way to root on original pre-order. :laugh:
be sure to back up internal sd card
takota6 said:
I'm a little lost, I've been reading for days and can't seem to find my answer..here goes
Coming from droid1 were I could flash new to old and vice versa..had the s3 for a couple of weeks, I'm on beans 13 kernel lean1.0 and hd radio..the other day I was on clean 2.5, and before that on synergy..can I keep bouncing around like that, our do I need to do Odin thingie? I see were root'ers are Odin then taking this new update and looks like killer battery life..I don't really have a preference on roms , just nead a little help on doing it proper..txs
Click to expand...
Click to collapse
Don't forget to back up internal sd card. Odin will wipe it when you flash.
Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip
xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565
Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!