[Q] no matter what i flash ? - Samsung Infuse 4G

i posted something with regards to battery life shortly after ZTR and have flashed to other since, but now it seems no matter what i flash battery just gets swallowed up regardless nd even phone seems to run liiil bit slower.
any suggestions?
different modem?
different driver?
return to stock and root again?
not like i am on phone all the time and its like i dont want to use it cause of the drainage.
ideas???

i would Odin or Heimdall back to stock to clean anything out then
flash again and see the result
if problem persist it can be a faulty battery or hardware
do Odin/Heimdall first tho

Related

Used to be able to flash any ROM, now I have problems with every rom!

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.

Constant Loss of Single/Odin 1 Click Boot Loop

Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766

Horrible battery life - FIXED!!!!! Does this make sense?

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

[Q] - Ruined for all other ROMs?

So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
frankxanders said:
So I have a little bit of a strange issue.
I had flashed the AOKP Milestone 5 on my TF, and although I managed to fix the CWM bootloop, it doesn't appear I'm able to install any other ROM.
Since I've flashed it, any other ROM I attempt to flash either fails to complete it's first boot (watched a few different ones try for hours yesterday) or wifi will not turn on. The wifi issue is also present in my backup from stock.
Perhaps for the ROMs that are booting for me there is a different kernel I may have better luck with? Thoughts, anyone?
Click to expand...
Click to collapse
What recovery are you using? might pay to try another (Recommended: http://forum.xda-developers.com/showthread.php?t=1759452)
You may want to obtain a kernel compatible with the ROM you want to try and flash both the ROM and kernel at the same time. The wrong kernel could definitely cause both the booting problems and the wifi not turning on.
I think about a kernel problem too, go to your ROM thread and you'll see the best kernel to flash with it...

Firmware question after bad flash

So I had a completely stock Galaxy s 4g, on gingerbread. I had the bright idea of rooting to try out different builds. I was in the middle of flashing when I noticed that what I was flashing was for the Vibrant. Well, it was either let it flash with that or stop the flash, so I stopped it. After searching for hours, I couldn't find a working link for a download to flash a custom build. I was able to find a "stock" flash, but for some reason I don't think it's right. I have problems with low call volume now and have to power the phone off and on to fix it temporarily. Everything else works fine, so far. Another thing I noticed is everyone shows firmware of 2.3.6, mine says 2.3.4????? Here's my info: sigh-t959v, baseband T959VUVKG4, kernel 2.6.35.7-t959vuvkg4-cl385158, build gingerbread.vuvkg4.
Any thoughts on what I should do?
Thanks in advance
This thread has heimdall one clicks that will get you back to stock kj6. Remember to flash once then after booting until you hear the t-mo jingle pull battery and put it back in download mode and check the flash bootloaders and flash it again.
http://forum.xda-developers.com/showthread.php?t=1358498
If you want root in the second post is a one click created by me. You can flash it instead of the plain stock one by bhundeven. But you need to flash the bootloaders to make sure you get rid of all the vibrant stuff.
Ok, thanks a lot. I will flash your build tomorrow when I get home from work. I'll let you know how it goes. Thanks again.
So I flashed your build and everythingis working great, even seems to be running faster. However, the wifi says "error" when I try and activate it. Is that a rom problem? Should I start over and try again?
It is because the kernel uses a different module then what is in the rom itself. That is why it is suppose to be used as a stepping stone to flash to a different rom.
Gotcha.

Categories

Resources