Database Info

[GUIDE] GUIDE to get the official US T Mobile OTA

If you were impatient and flashed a leaked SBF like and still wants to get the official update, here is a shord guide for you. I examined the 6.36.0 sbf and the code groups for CG31 and CG39 are the same as the leaked froyos so i flashed it on my phone running CM7 and it booted After it i downloaded the OTA let it install and now i am on the official 2.2. I can change it with the CM7 anytime i want and if i have to take the phone to the service restore it to stock 2.2 So step by step
1. If you are on any leaked froyo download the latest us eclair sbf(JORDN_U3_6.36.0) from http://www.and-developers.com/sbf:defy
2. Boot into the stock recovery and wipe
3. Boot into the bootloader and install the SBF from point 1
4. Let the phone reboot then go throught the motorola blur registration then setup a wifi connection.
5. Download the OTA (settings->about) and if the download finished let it reboot and install the update.
6. Enjoy stock untouched 2.2 T mobile froyo

hi is this only for US people or will it work in UK as well?

It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App

Does it supports 720p video recording!!

vick33 said:
It will work but it does not worth it. It is the same version as the one was a month ago... the nordic 177 or CM7 is better.
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
What is the version number after the update?

Anyone can upload nandroid and sbf ?

It came out as OTA so no sbf available. Every version is the same as it was with the test update... it is android 2.2.1 34.4.9 they did not changed anything from the test update so i am not satisfied at all...
Sent from my MB525 using XDA App

Can i send in my defy for service with this rom?
Edit: I guess this rom is official. Read this thread. http://forum.xda-developers.com/showthread.php?t=1044980 .Cool stuff. Thanks for the heads up!

I tried flashing this and now my phone wont turn on i needed this so i can return it to T-Mobile with a stock ROM, but now my phone won't even turn on. Tried removing battery and putting back in, no matter how long i press the power button, it wont even turn on. help plz

On which rom were you before? Did you wiped before flashing the sbf? I have done it myself many times.

i was on CM7 and i wiped and flashed like u said. it might be my phone.
EDIT:
well nevermind, looks like the screen is fried. it seems to have flashed but the screen wont display anything cause when i plug it in to the computer, i hear the little beep and the LED notification appears, but no display.

you cant burn the screen like that. If it beeps then you are ok. You should try flashing the nordic sbf for example, fom it i have gone fortth and back to the us froyo the way i described.
so what should you do:
1remove your battery and while putting it back hold volume up.
2 start RSD lite and connact your phone
3 if it is connected flash the sbf.
If the PC does not sees the defy then your battery is flat. Charge it with an external or try mcgyver, you cant brick defy with flashing.

Will this work if you flashed the 2.2 OTA then used a custom froyo ROM. I basically want to take this phone back to stock.
I thought we couldn't downgrade.
Sent from my MB525 using Tapatalk

i was on nordic when i did the things i written. Got back the official now i have done it from other custom roms like CM7, but wipe in the stock recovery before trying it. I dont have any problem but seems like someone had so be careful.

I'll give it a shot because my nandroid restore is buggy.
Will post results.
Sent from my MB525 using Tapatalk

It would be interesting if it wont work for you. Cg-s for the us eclair are same as for the froyos
Sent from my MB525 using XDA App

Finally a way for US users to return to FULL STOCK regardless of firmware
It worked!!!
I was on barbones 1.5.1 then went to a backup nandroid version of my original stock rooted. Was kind of buggy so I decided to try this
1. Wiped everything using the stock recovery
2. Bootloader and flashed nordic 2.2.2 and "skipped" the automated setup until the phone desktop appeared then waited until RSD said the phone "passed".
3.Wiped everything using the stock recovery again
4. Bootloader and flashed 2.1 JORDN_U3_6.36.0 then pressed "start" at the motoblur screen and waited until RSD said the phone "passed".
5. I then entered my motoblur info and "skipped" everything until I was at the android desktop. After syncing was finished (waited about 5 min) I proceeded to "Download the OTA (settings->about->system updates) and after the download finishes let it reboot to install the update"
Thanks "vick33" nice find!
Note:
I could not update the kindle app without it giving me unsigned package errors. My solution was to root and uninstall the oem kindle app.
Then unroot and perform a factory reset. The oem kindle app did not restore and I was able to install the latest kindle without errors.
No other issues have been found.
*** CONFIRMERD TO WORK ***Another solution maybe to update the kindle app prior to updating the phone to 2.2 via OTA. Possible the better way to go considering it does not require rooting or removal of a system installed bloatware.

i mean the screen doesnt show anything. screen is black, idk whats wrong with it. im not saying the sbf had anything to do with it, just saying the screen went out. i just turned it in anyways, so ill be getting a new one soon.

[Q] Help me please!

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

[Q] Cant update 2.3.4 OTA

Hey guys, Ive been a lurker for a while, didnt really need to be a member since I found answers to all of my questions most of the time. But now I must say I am a little stumped. I have a Google Nexus S from WIND Mobile, I believe it is the i9020xxKD, I am currently on the 2.3.4 Gingerbread version, and I have rooted the phone with Mr. Superuser. Everytime I try to update to 2.3.6 OTA, I get the 10 sec before reboot and install, but once it reboots it does not install, instead it freezes with showing a Yield Sign with the android dood inside beside an exclamation mark. I have to remove the battery to get it to restart. Now Im assuming it has to do with me rooting the phone, and thats why it doesnt work. So is it worth to update to 2.3.7, or should I just wait for the Ice Cream thing to come out in December and get that?

10cheesecakes said:
Hey guys, Ive been a lurker for a while, didnt really need to be a member since I found answers to all of my questions most of the time. But now I must say I am a little stumped. I have a Google Nexus S from WIND Mobile, I believe it is the i9020xxKD, I am currently on the 2.3.4 Gingerbread version, and I have rooted the phone with Mr. Superuser. Everytime I try to update to 2.3.6 OTA, I get the 10 sec before reboot and install, but once it reboots it does not install, instead it freezes with showing a Yield Sign with the android dood inside beside an exclamation mark. I have to remove the battery to get it to restart. Now Im assuming it has to do with me rooting the phone, and thats why it doesnt work. So is it worth to update to 2.3.7, or should I just wait for the Ice Cream thing to come out in December and get that?
Click to expand...
Click to collapse
I believe u have to be stock everything... =\
Sent From In between Your Moms Boobies

10cheesecakes said:
Hey guys, Ive been a lurker for a while, didnt really need to be a member since I found answers to all of my questions most of the time. But now I must say I am a little stumped. I have a Google Nexus S from WIND Mobile, I believe it is the i9020xxKD, I am currently on the 2.3.4 Gingerbread version, and I have rooted the phone with Mr. Superuser. Everytime I try to update to 2.3.6 OTA, I get the 10 sec before reboot and install, but once it reboots it does not install, instead it freezes with showing a Yield Sign with the android dood inside beside an exclamation mark. I have to remove the battery to get it to restart. Now Im assuming it has to do with me rooting the phone, and thats why it doesnt work. So is it worth to update to 2.3.7, or should I just wait for the Ice Cream thing to come out in December and get that?
Click to expand...
Click to collapse
Flash one of the stock ROM's from here in recovery,
http://forum.xda-developers.com/showthread.php?t=1063664
Then check for updates.
---------- Post added at 10:53 AM ---------- Previous post was at 10:51 AM ----------
YourMainDude said:
I believe u have to be stock everything... =\
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
I think as long as you have the stock ROM and kernel , Your fine.
I rooted my stock 2.3.4 and installed SU and it updated to 2.3.6 without any problems,
You'll just lose root and recovery.

Im still kind of lost with the stock rom and kernal stuff. How can I install them, I get to the recovery menu but nothing happens when I try to install anything.

bro , just wait for few weeks , and then directly update it to 4.0 ...
-------------------
download a 2.3.6 STOCK ROM , and then flash it via recovery , reboot, you are having 2.3.6 then ..
how to :
go recovery --> wipe --> first and third --> back to main menu --> install from zip --> select zip file you download (which has to be put in SDCARD) --> yes , flash it ---> reboot ---> android 2.3.6

Yea Ill just wait till 4.0 ^_^

[Q] How to downgrade From ICS to Gingerbread?

I have a Nexus s with 4.0.3 flashed via bootloader.How can i downgrade to 2.3.x without root,cwm or debug(cause it isn't working) ?
i've tried several methods but none of them worked(Odin,Heimdall)
They all requires me to enter download mode with debug enabled.My debug mode is enabled but as far as i read on xda,the degub is not working in this version of ICS.
my question is : how can i downgrade to ANY firmware from this ICS version
P.S. Entering recovery mode is not an option...the phone simpli enters in a recovery/download mode - loop and keeps restarting.
Please respond fast.10x

The way I did it was to download Clockwork Mod app and scroll down to where it says stock... then 2.3.3. Once u flash that you'll lose root and an update to 2.3.x will be prompted to ya. If it doesn't then Google (Download) 2.3.4(x) and manually update. What model do u have btw?
- Google

You need to root is the basic moral here. Nothing else is really worth the effort of getting it done.

Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.

tsam19 said:
Hi
If the procedure for the nexus is the same as it is for the S2.
It should be straight forward.
Download your ROM, if its Orange you want here is a good link, I used it myself today:
http://androidromupdate.com/2012/02...-i9100p-firmware-updates-list-and-stock-roms/
The ROM I used was the NON WIPE type - I9100BVKJ4_I9100ORAKJ4_ORA
I include a picture of what I did.
I was initially on a custom ICS 4.0.3 XXLPH and have gone back to Orange stock rom.
Load the integrated Rom just into the PDA window - connect your phone in download mode and start, and that should be it!
Don't check re-partition or anything else.
Keep trying it will work.
I also had an initial prob whereby I installed the wrong kernel and the phone screen was messed up and seemed to be bricked and to get it back I loaded odin up.
Put phone in download mode.
Checked re-partition - unchecked 'auto reboot and f.reset'
Used a PIT (partition file)
Used a kernel file suitable for the S2 in the PDA window and pressed 'start'
This seems to have repartitioned and wiped the mistake and unbricked the phone.
This loaded and the phone booted - no messed screen.
Then I continued to accomplish the ROM switch over.
Click to expand...
Click to collapse
Don't do this. The method for the Nexus S is definitely NOT the same as the SGS2, or even the SGS. Although it may be possible to use Odin or Heimdall, it is not recommended. We already have enough freedom to do as we please.

I thought all android / samsung phones would follow the same procedure for flashing new roms or unbricking via Odin?
Kies is useless for updating as we all know.
So what other methods beside Odin or Heimdall can be used on the samsung nexus?
Cheers for clarifying though, I was only tying to be helpful

galaxy 2 ics to gingerbread
dear all
i am much upset that i upgrade my galaxy s2 to ics 4.0.3 , it is much laggy i want to downgrade it to gb 2.3.5 or 2.3.6 , can anybody help me to do this , with the all the steps and downloading links of the exact files , i tried alot many times and when it is done on odin with pass message , cell restarts and with error screen .
thanks in anitcipitation
Regards
Shoaib Hassan

i've just downgraded to 2.3.2 i used the rom wiper from bm and then simply flashed the oxygen rom over it

the only way and easily is odin.just go to downloading.make sure to download the correct modem ,baseband and needed files by cheking your nexus s version.ex.i9020t,i9023 .there are not the same version,and will use different modem,baseband ...

I also want to downgrade from ics to gingerbread too, by pure luck i managed to upgrade to ics (i'm completely new to this) but having had this on my phone for awhile, I want to return to gingerbread...
I'm currently grabbing kernel_I9100xwkj3 (couldnt find xwkj1 anywhere)
and
gt-i9100_o2i_i9100xwkj1_i9100o2ik11_i9100xxk14
to use with odin?
question is... is this all i need and is there anything i need to be aware of?

You need to make use of fastboot and flash the stock GB rom from factory images provided by google, then you can flash cwm and then flash any rom you want
it is because cwm can flash roms with android version up but not down means that you can flash 4.1 if u have 4.0.4 but if you are on 4.0.4 then you cannot flash 2.3.x
Hope it helps

[Q] Help i'm a noob and need help please!

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