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.
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
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!
Hi there, my friend is coming round soon and I was planning to give it a custom rom
Now, I've done this type of stuff before (on my nexus) I just want to see how you would do it for this samsung phone
Now, what recoveries can you get? I use 4EXT on mine
And, can anybody send me to a stable and up-to-date rom that can be used everyday and has nearly no issues? I need one without all the samsung stuff, just a normal default android one
And, how would I go by rooting the phone?
On mine, I used the zergrush exploit, does it work for this phone??
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
ak700 said:
If you want one with everything working, then use the Froyo roms. CM7 is under development. The major bugs are bluetooth and youtube hq. Leaving that, even thats useable. It's even better than Froyo.
I suggest you to try either Kyorarom or Kyrillos v9.6. Both of them are froyo based, pre-rooted, and have other mods to make it even more faster than a stock one.
Happy flashing!
Click to expand...
Click to collapse
Thanks, and how do I go about flashing the rom, would I have to root it first?
No need.
This is something to good to read http://forum.xda-developers.com/showthread.php?t=1372414
BTW to root the phone use super one click root (or sth like that )
Ah, I get it now, thanks
Just one more question, does ODIN delete the phones data before installing the rom?
You have to wipe all your data after flashing(or not if from Froyo to Froyo)
I mean from recovery. ODIN don't delete user data
I exactly I don't know the working of odin, but after flashing you are directly taken to the recovery and advised to wipe data and factory reset.
I've done everything correctly, followed every tutorial, and I'm still not having any luck. I started on stock rooted Lollipop, and all I was getting as installation aborted errors with using Lollipop Autorec. I've since flashed back to stock rooted Kitkat, which I've got the closest with. I've been trying to flash one of the newer nightly updates from Cyanogenmod (20150709 specifically). I've also tried using the first stable release, to no avail. I used one click root to root, which worked fine, and Autorec Kitkat installer for TWRP, which also installs fine, and I can get into recovery no problem. I wipe, I flash, and it boots up, but then it never loads. It ends up being stuck on a boot loop, and it's very frustrating because of how close I'm getting. A Cyanogenmod 11 snapshot flashed correctly, but I'd like to figure out the newer update problem. I'm on LG D800. I'm a complete noob at this stuff, and need a sensei to guide me, please. Thanks in advance.
(Update): I've just now tried installing the newest Resurrection Remix for LG G2, and that sticks me in a boot loop as well, so I have no idea what I have to do. Will update again in a moment because I'm going to try downloading stock Lollipop and the newest TWRP.
(Update 2): So, I've just done what I said I'd do earlier. I flashed the LP bootstack, then Resurrection Remix, then Gapps, and I'm getting a bootloop for that, as well, so I'm calling it a night, and going to bed. Someone please respond. I really need help.
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Yeah, I ended up trying that, and flashing Resurrection Remix, and I was still getting a boot loop on that, as well.
Really now said:
Did you update TWRP? You need to be on the latest version, 2.8.7.1 to flash the newest roms. http://blastagator.ddns.net/twrp.html Put this on your phone and go into recovery and flash it. No wipes needed. Don't reboot when it's done, back arrow to the first screen and select reboot and then select recovery. After that reboots you'll be on the latest TWRP and can flash the LP roms and necessary files or just reboot system and you'll boot up the rom you currently have installed.
Click to expand...
Click to collapse
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
(EDIT): Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
I just read what you said again, and no, I didn't actually try that version. I'm on TWRP normal version 2.8.6.1. I will probably try what you said, soon, and report back when I do.
Click to expand...
Click to collapse
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Really now said:
Yeah, from what I'm reading in all the latest LP threads you have to be on the latest TWRP. I am and I've had zero issues flashing the different roms. Follow the OP of each one exactly and you'll be fine.
Click to expand...
Click to collapse
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Wezurii4694 said:
Alright, man, thanks a lot! I'll report back when I test this out. Also, am I supposed to flash a baseband and/or a different bootloader? I'm really new to this stuff, and I don't 100% know everything to do, and some tutorials aren't 100% clear, because I guess they're assuming the viewer knows what they're doing.
Click to expand...
Click to collapse
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Really now said:
No baseband, just the bootloader the OP specifies. You just need to read, read and read some more. It may be confusing at first but you'll figure it out. A good thing to have on your computer is here, http://forum.xda-developers.com/showthread.php?t=2663369 . It makes it very easy to go back to KK and start over if you need to. I've used this a number of times and have gone back from LP without a problem. Once again, read the OP until you understand what you need to do.
Click to expand...
Click to collapse
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Wezurii4694 said:
What if the OP doesn't specifie? Because I didn't even know I needed to flash that, till this point, haha. Yeah, I've used that, and have that. This past weekend I soft bricked my phone, probably around 10 times, and I used that each time, haha.
Click to expand...
Click to collapse
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Really now said:
I don't know of any of the caff LP versions that don't state that you need to flash the correct bootstack. If in doubt, don't flash it. If you were trying to install cyanogenmod 12 it doesn't require a bootstack flash but 12.1 does. You have to be sure of what you're trying to install. You might try running this http://forum.xda-developers.com/att-g2/development/rom-stock-lollipop-30b-stripped-t3144195 . Same dev that builds TWRP that I sent you to put this together. It's an all in one flash! And since it's in the at&t section it's not bloated with issues from users of different G2 variants. Just a thought.
Click to expand...
Click to collapse
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Really now said:
I'm assuming that you're on stock rooted LP and you've only tried flashing the RR rom. I haven't flashed that one in a long time but I see on the last few pages of the thread that there are several people getting stuck in bootloops. Is it the rom or their installation? I don't know but I'd seriously try a different rom. The latest Cloudy G2 3.3 is an excellent rom and everything works. It's my go to backup rom. The least confusing way to install it is to follow this,
http://forum.xda-developers.com/showpost.php?p=61396344&postcount=465 although you'd be flashing the 3.3 version not the 3.1. On the aosp side, I've been using Vanir https://androidfilehost.com/?w=files&flid=28988 with TK Gapps https://www.androidfilehost.com/?w=files&flid=31524 and this bootstack https://androidfilehost.com/?fid=24052804347760740 . Right now I'm running Slim Saber http://forum.xda-developers.com/lg-g2/development/rom-slimlp-alpha-0-4-t3135141 . It's a very nice rom too. Other than that I don't know how else to help.
Click to expand...
Click to collapse
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Wezurii4694 said:
Alright, I'll try it out. You've been really helpful. I'll let you know how it goes. I had to reflash Kitkat, so I'm about to update to Lollipop again.
Click to expand...
Click to collapse
Really now said:
Good luck! One other thing I was going to say is that if you want a great camera/video and a stock like experience with a lot of features then go with the Cloudy G2 3.3. It's based on the LG firmware so it's a good place to start and get rid of all of the at&t bloatware.
Click to expand...
Click to collapse
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Wezurii4694 said:
Oh, in what order do I do everything? Just to make sure.
Edit: Never mind.
Click to expand...
Click to collapse
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Really now said:
One other thing that occurred to me, are you doing full wipes in TWRP? You have to select Wipe-Advanced Wipe-then check off Dalvik,System,Data,Cache (DO NOT check off Internal Storage) and then swipe the slider. I always do it 3 times, press the back button and Factory Reset 3 times. Probably overkill but it works for me. Then go back and do the install.
Click to expand...
Click to collapse
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Wezurii4694 said:
I've always only ever done the advanced wipe. I'll do the three times thing, this time.
Click to expand...
Click to collapse
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Really now said:
I do it 3 times because on my old Galaxy Note I noticed a few times that when I flashed a new rom a few things that I hadn't installed were still there. So I got in the 3 wipe habit.
Click to expand...
Click to collapse
Oh, okay. Oh, when do I flash the kernal?
Wezurii4694 said:
Alright. I got around to trying what you suggested. Still a boot loop on Resurrection Remix, and I don't know why. I flashed the bootstack for my phone, that the post said to, then the rom, then Gapps. So I have no idea what I have to do to get this to work.
Click to expand...
Click to collapse
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Really now said:
Well you're bound and determined to keep flashing the same rom over and over and it doesn't work. If it were me I'd move on to a different rom.
Click to expand...
Click to collapse
I meant on Cloudy. I'm trying that out.