The other day, I got a text from AT&T indicating that an official 2.3.5 kernel was available for my Captivate. Great, so I fire up Kies mini and install it over my rooted stock 2.2.
Update goes well, I have Gingerbread. All of my apps remain in place. Re-root (SuperOneClick) and my Titanium Backup works like a charm.
However, I can't get my WiFI to connect to save my life. IT scans for about 15 seconds then shuts back off. I can't even enter WiFi settings manually, because it shuts off and "fail to save" the settings.
IS anyone else having issues with WiFI on the AT&T stock Gingerbread kernel? (No, I don't feel the need to upgrade, since I just want to be able to use TiBU)
hurricanedad said:
The other day, I got a text from AT&T indicating that an official 2.3.5 kernel was available for my Captivate. Great, so I fire up Kies mini and install it over my rooted stock 2.2.
Update goes well, I have Gingerbread. All of my apps remain in place. Re-root (SuperOneClick) and my Titanium Backup works like a charm.
However, I can't get my WiFI to connect to save my life. IT scans for about 15 seconds then shuts back off. I can't even enter WiFi settings manually, because it shuts off and "fail to save" the settings.
IS anyone else having issues with WiFI on the AT&T stock Gingerbread kernel? (No, I don't feel the need to upgrade, since I just want to be able to use TiBU)
Click to expand...
Click to collapse
I just updated to stock GB and have no issues with Wifi, although I am not rooted. I thought that rooting with SuperOneClick didn't work with this 2.3 stock.
Hogan773 said:
I just updated to stock GB and have no issues with Wifi, although I am not rooted. I thought that rooting with SuperOneClick didn't work with this 2.3 stock.
Click to expand...
Click to collapse
I'll have to check that when I get off of work. That's what I used to root the unit when on 2.2. I wonder if the root just carried through the upgrade?
Anyway, I am probably going to flash back to froyo and update GB again, sans root to see if that helps.
For the life of me I couldn't get Superoneclick to work on 2.3.5, or 2.3.3. I flashed the rooted kernel with Odin.
No questions in General, post them in Q&A.
Related
My phone originally came with 2.1 Éclair and I upgraded it with Kies Mini the official AT&T way. Then I rooted it with Shortfuse's SuperOneClick method. I was not satisfied though and I wanted to get Cognition 4.3.1 but later found out that you needed to have 2.1 to do that. So I used Odin to go back to 2.1 and then I rooted my phone again with the same method as before. Then I installed Cognition 4.3.1 with Rom Manager FREE version. When my phone booted up, it had Cognition on it but it was not rooted anymore. I still had SuperUser on it but when I opened apps that needed root like TitaniumBackup Pro, it wouldn't allow me saying I wasn't rooted. So then I tried to root my phone with SuperOneClick again and it would work. It said it was successful but it still wouldn't work. I tried to root it with the OneClick and SuperOneClick and both wouldn’t work. After countless times of failing, I tried using my phone to call someone and it wouldn't let me and would start vibrating every 1-2 seconds. So now, what I did was put it in download mode and used Odin again to go back to my original 2.1 and did a master clear with Odin and a factory reset through my phone, and cognition was gone and all I was left with was 2.1 stock firmware, non-rooted, and I was mad.
Now my question is:
Can your phone be rooted and be running Cognition 4.3.1 at the same time? Is that possible or can I just have Cognition 4.3.1 only and not rooted? Is there a possible way to have both?
If there is a way, can you please give me some step by step instructions on how I can do it?
I understand how to root my phone and install Cognition on my phone but when I installed Cognition, the root was lost. Any ideas would be appreciated please.
Samsung Captivate Cognition 4.1.3. w/ Odin 3 flash
Hey Daniel. I had the same problem & trust me they happen. I went to the tube & found a
3 part vid on cognition install with Odin flash & at first it didnt work for me. So I reflashed to
2.1 stock with Odin & followed everything to a t.....having patience watching the vids. I kinda
enjoyed it & was able to effectively flash my Samsung Captivate to Cognition 4.3.1 that is based
off of froyo 2.2 (by the way). Cog is smooth & fast & works great with home launchers!
Enter Samsung captivate rom & look for the mobile tech vid of Cognition. (older firmware used
in vid but all works the same). My phone is way faster than 2.2 stock and I grabbed a ADW from
the market to change the home launcher and all my buds want me 2 do there phones now!
Just be patient,its worth it. You will glad you were when your phone is better than new.
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.
It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.
I am going to give this a try and see what happens, I will post results.
Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.
Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7
I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?
The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
pammiecaykz said:
The other day I updated my phone to 2.3.4 using odin. after that I had a horrible wifi signal and i kept losing my data connection all together. So I flashed back to Froyo 2.2.1. I am so confused because my phone kept force closing, I did a factory reset and it stopped but it says my kernal version is 2.6.32.9...is that normal? Also how do I go about flashing a good rom to my phone? The way it is now it is soooo slow which is why i updated to the 2.3.4...any information would be helpful as I am ready to throw my phone out the window.
Click to expand...
Click to collapse
Which 2.3.4 ROM did you flash via ODIN? KG4/KG6 both show less wifi signal but I actually haven't seen a difference in speed. I'm on this one right now:
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
The way to properly get to that is by doing the following:
1. ODIN
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4
http://forum.xda-developers.com/showthread.php?t=1183413
2. Then boot up like normal and wait for it to load up into the system.
3. Turn off your phone again (shutdown) and put it back into download mode.
4. ODIN this to get CWM+Root http://forum.xda-developers.com/showthread.php?t=1194032 (use the ODIN version)
5. Keep lagfix disabled via the voodoo menu in recovery after you flash the CWM+root+Voodoo EXT4 package in the link in step 4.
6. Boot into the system. It's up to you, I flashed this
[ROM] Stock Deodexed T959VUVKG4 with Root [Gingerbread 2.3.4][7.26.2011]--Whitehawkx
http://forum.xda-developers.com/showthread.php?t=1187293
Which is a deodexed build which allows you to theme etc.
Some people have had issues getting onto EXT4 partitions while on a gingerbread ROM. I had a few issues myself. Needless to say there are several places to read about how to get EXT4 working on all partitions if you want to.
Best of luck, hope this helps.
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
pammiecaykz said:
Well to be completely honest, I don't know anything about partitions. All I know is that I updated my phone and then all of a sudden I had a horrible wifi connection and my data connection would just drop out all together and say "searching". I would have to reboot my phone 2 or 3 times to get it working again. What is a good rom to update to? Is have the kernal build that I do going to be an issue?
Click to expand...
Click to collapse
Please read the post above and follow the steps and links and you will be fine
Hello everybody,
I rooted and upgraded my T-mobile(US) SGs4G from Froyo to ICS, currently:
model sgh-t959v
firmware 2.3.6
baseband ver t959vuvkj6
kernel ver 2.6.35.7-t959vuvkj6-cl694130
build # gingerbread.vuvkj6
since this upgrade i have 2 bugs:
1. usb(mass storage mode) is not working in my car (read error), worked before OK. it's still working when i connect phone to computer. We got another SGs4g in the family (not rooted, just upgraded to GB), it's stop working in USB mass storage in the car too. Any ideas? could i replace usb driver in ICS or do i need to go back to Froyo?
2. I worked in the building with poor reception of GSM signal, so if phone could not connect to the cell, then even if i go outside later it's still "searching" and could not find signal, so i need to turn phone off/on in order to get signal.
Could it be fixed? again it was OK with Froyo: 5-10 sec and reception re-established.
Thanks in advance.
You don't have ICS. You have Gingerbread. Try a factory reset for your problems.
I did
Thanks, my bad, sure it's not ICS, its GB. And i did HW reset in the begining, do you think it's the number of resets that counts? BTW i did not back up my Froyo, do you know where i can get one?
When did you do the factory reset in relation to your problems? How did you upgrade?
Depending on your answers my recommendation is follow the guide in the second link of my signature. GB is worth having.
I can find you a link for Froyo but it is not as simple to downgrade to Froyo as you might think. You will need to make sure to flash Froyo bootloaders also.
first i did root still with froyo
then updated to GB with keos
did reset, and re-installed all applications.
I did figure out how to "trick" lost connection due to no signal:
turn on flight mode and turn in off. so definitely it's a bug.
still no luck with USB
I know that downgrade to froyo is not easy, and i like GB, this is why i'm asking if there is a way to patch usb driver only
regards
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help I can't seem to find a working link for CWM-UXKG3-rooted-de-odexed-update-v2.zip maybe if I install the cwm the light neon blue screen will go away?
crayzze said:
Hello I rooted my i997r infuse rogers but the com# in oden was in the wrong box and it saied succesful /failed one but I didn't think much of it I was so exited that it worked I upgraded from 2.3.3 to 2.3.6 AT&T firmware thinking i have to in order to install ics I then installed cms 10 J.B 4.3 my phones runs great better than ever before execpt for the fact that my screen takes about one minute to turn on with lines I think its called rainbowing im not sure I think it has something to do with my original root that messed up my screen so I want to downgrade to stock using odin and reinstall and hopefully my screen won't be messed up so I used http://forum.xda-developers.com/showthread.php?t=1193927 it was successful I used the Odin_UXKG3_rooted_no_bootloaders_v2.zip then Odin_Stock_Rogers_UXKG3_Kernel.zip and my screen now has a shade of gray with this shade of blue this blue shade that covers the screen right when I turn it on it keeps getting worse it goes away after a couple minutes in recovery mode but now I just don't know what to do I can't even use my phone now help me please! How do I fix my video driver I guess this is whats going on help
Click to expand...
Click to collapse
Read this:
http://forum.xda-developers.com/showthread.php?t=1613523
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
crayzze said:
Thanks I read the part about the bootloaders I flashed to gb 2.3.6 and then flashed the bootloaders hoping it would fix the blue screen i always get and have to wait 5 minutes to go away every time turn m screen on it just isin't when I power my phone on its whenever I turn my screen on I can't see anything when someone calls me I have to wait, im on a rogers infuse and I hope this isn't a permanent bug. I went back to 2.3.3 gb stock I don't have a rogers boot logo anymore but it runs fine execpt for this light neon blue that covers the screen does anyone else ever have this problem please help.
Click to expand...
Click to collapse
rainbow screen on recovery = no gb bootloaders
blue screen on phone ...maybe bad cable connection or corrosion at contact
you might have to open it and check the connections
Working and tested CWM 1.2 ghz
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Fullmetal Jun said:
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install the usb driver for your Samsung galaxy. The link is on the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged into the computer but disconnected from your phone. shut off your phone. When the power is off press Volume up and Volume down simultaneously, after the buttons are pressed plug in the usb cable at the same time, which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a stock kernel which contains CWM. use "2013.04.30-CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow Enthropy's CM9 guide for your first ROM!
Click to expand...
Click to collapse
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
crayzze said:
Thank you but it's not bricked... are you suggesting this will take away the screen issue?... k so it's been a while since I used my infuse the screen was getting so annoying that I put it away for a month last night I turned it on and the screen seemed fine, I was very pleasantly surprised I re rooted it and put on the new cm10 jellybean and noticed the longer I kept using the screen the more the lines/screen problem came back I left it untouched overnight after modding it and this morning it's fine again until continued use of the screen... I have taken it apart and unplugged all the screen plugs reattached looked around everything seemed fine so I dunno... I have a really newbie question for the way I went about getting to jellybean from stock... first I rooted it with Odin_Infused_Gingerbread_Kernel_v1 and noticed that cwm was installed so is this all I need to proceed with installing ics? because I kept thinking I needed to install 2.3.6 and that is not firmware meant for my phone and thats what I think might be the cause of my screen issue sooo do I just need to root it first then go straight to ics or do I need to put 2.3.6 then ics?
I am on a rogers infuse.
Click to expand...
Click to collapse
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Help!
qkster said:
Re-reading your thread, I realized that you have a i997R - Roger's. These come stock GB 2.3.4 - unlike the i997-ATT that started with 2.2.1
The difference is that the i997R has already built in bootloaders from the start. That means that Roger's phone do not get the distorted recovery with flashing we termed as "rainbow." The rainbow is fixed with a bootloader flash. Roger's phone do not need this step.
I think the color distortion you are seeing could be due to a heating issue, the screen or the graphics chip. More likely than not, this may be hardware related.
If you have opened and cleaned out the connections and such, and have not noted any difference, then the problem may be deeper situated. Further testing may require another Infuse and swapping out parts to see where the issue lies.
gl
Click to expand...
Click to collapse
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol... My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear... my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
crayzze said:
Yes I bootloader flashed it in desperation with an at&t bootloader and now lost the rogers bootloader lol...
Click to expand...
Click to collapse
no big deal..same phone..same hardware..different version of firmware..it's the APN for providers that makes the difference
crayzze said:
My phone came stock 2.3.3 gb and I desperatly wanted gb 2.3.6 so I rooted it and did so, then after discovering ics and then after jb... I believe that installing 2.3.6 might have damaged the hardware being that its only ment for at&t i997's or possibly a combination of 2.3.6 and then installing ics then jb or whatever the case may be my screen needs 1 to 5 minutes to fully appear.
Click to expand...
Click to collapse
yes..you are right. Rogers came with 2.3.3 not 2.3.4 as I previously stated.
the earlier versions of gb came with Carrier IQ that track users. It was taken out later.
I doubt Installing 2.3.6 or ICS or JB will cause any prob with the phone. I suspect your phone may have some hardware issues.
After the first flash, the os (esp ICS or JB) may need time to build cache and dalvik..sometimes it may take a few minutes. Blue or distorted screen, however, is not typical from my experience.
crayzze said:
my question is if I ever happen to root another rogers i997 do I need to upgrade to 2.3.6 before installing ics or can I install right after root? Because I also might re root the phone back to stock and root it then install the newer version of ics then jb cm 10.2... I am currently running on jb cm 10.2 do you think it would make a difference if I rerooted to stock then install newer ics then jb with upgrading to 2.3.6 for at&t phones??? Thank you.
Click to expand...
Click to collapse
IMO, it doesn't matter how you get to CM10.2. Rooting is just one method. The idea is to get insecure recovery...ie..cwm.
from stock rom, you can odin or heimdall a custom kernel without rooting. boot into recovery and flash what you want.
it doesn't matter if its rogers or att. same phone..same hardware. years ago, it only mattered when a user had to return or exchange the phone for warranty...after the warranty period ended..it's not a big deal.
flash away at any method you want. it doesn't make any difference in my mind. get some practice..the infuse has many restore methods via odin or heimdall
rooting gives one access to the root directory
insecure kernel or custom recovery allows one to flash firmware without manufacturer signature