Database Info

HELP! Tried to root/overclock phone broke phone

Hi Guys,
I checked around but I couldn't find anything. I rooted my phone using the 1 click method provided here http://forum.xda-developers.com/showthread.php?t=1096384 This part went swimmingly. I had my phone rooted and ready to go. I then downloaded CPU set and the program would not let me speed up the CPU past 1 Ghz. so then I downloaded this: kernal netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed which supposedly allowed me to overclock my phone. I then placed the zip file into the root directory of my phone. I downloaded ROM manager and used that to install netarchy-nexus-1.3.0.2-bfs-2.3.3-cm7-compat-signed. When I did this the screen went black and the capacitive buttons at the bottom lit up. I can reach the recovery screen but that is it. There is no USB connectivity with the computer. Is there anyway to fix this or did I just turn my phone into a paper weight.
Thanks,
Cloo

Phone processors are a funny thing. Some can handle being overclocked higher than others. I am assuming that you went all the way up to 1400 and your CPU just gets too hot and everything locks up on you. You need to have a rooted Rom on the root of your sdcard and wipe everything from recovery and flash the Rom from recovery and start over. If you go with Netarchy's kernel again I suggest bumping the CPU up to 1200. If it can handle that bump it up to 1300 and obviously it can't handle 1400. You won't see much of a benefit from 1000-1300 for the most part. I keep mine on 1200 and it runs great. Anything higher for me and the phone starts to get hot and lag somewhat. Your phone is not a brick. If you can get to recover and/or bootloader there is always hope.
Also check out these threads to help you get back to 100% stock and start over.
http://forum.xda-developers.com/showthread.php?t=1072698
http://forum.xda-developers.com/showthread.php?t=1103727

Do you have a NS4G which is what the one- click is developed for or a Nexus S, which is what the Kernel you flashed is for? My guess is that you flashed a kernel which is not compatible with your rom.
Sent from my VEGAn-TAB using Tapatalk

You may not have waited long enough for the phone to boot. His bfs based kernels have a bug that most of the time the phone boots to a black screen captive light shows and no boot animation. It will boot but just takes time of you have right kernel. This is spoken about in his thread.

@housry I never got all the way through the switch to netarchy. Once I used ROM manager the screen blacked out upon reboot and nothing happens now. I managed to get the file SamsungSimpleDL onto my phone but when I try to install it aborts. Any thoughts?
@debh I have the NS4G
@Jerry the phone has been sitting with a black screen for about 10 minutes so I think I screwed something up

According to your op, you flashed a 2.3.3 cm7 kernel. Are you running stock 2.3.4? You need to flash the correct kernel for your rom.
Also, I just read your post above and you aren't supposed to flash the simple.zip on your phone. Download and extract the contents onto your computer and run the .exe from there with your phone connected.
Sent from my VEGAn-TAB using Tapatalk

Deb thanks for the quick reply, am I supposed to have my phone in download mode?

Phone is fixed!!! Thanks to all!

Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App

sh4nk said:
Quick question, im sorry, as I didn't know where to ask. Even checked threads and couldn't find an already posted answer. I have a ns4g, rooted, still on stock rom. Will I still get ota's from google when they push newer software than 2.3.4, which is what I run, and also get ota software bug fixes from goolge when they release it? I really hope so, as I want to stay current with the latest builds from google.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It will be faster to find them on XDA than the wait for OTA

Thank you Plus waiting a little bit will skip any bugs to be fixed lol
Sent from my Nexus S 4G using XDA App

[Q] [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root added - Infuse 4G - Arabic Support

[Q] [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root added - Infuse 4G - Arabic Support
[ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root added - Infuse 4G
I applied the above ROM to my AT&T. So far, all is working well from what I have tested: WIFI, BlueTooth, Phone and GPS. It seems to be very stabel compare to other ROMs I applied in the past.
My delimma is that I correspond in 4 different languages and arabic is one of them. When I applied the Hebrew Arabic Patch I am able to see the arabic letters connected. However when I attempt to write any arabic text, it is all disconnected.
I could not post to the forum where I found the ROM since I am new to the XDA forum. But I believe the answer to this question may help others.
Can anyone please provide me a patch to this ROM so it can allow me to write connected arabic letters? If such a pacth exists, can you please point me to it?
Thx for any help!!!

Some of the Arabic keyboards available on the Android market have settings to connect the letters. Here is a link to one that defaults to having letters disconnected, but it offers a setting to connect them.:
https://play.google.com/store/apps/...51bGwsMSwxLDMsImNvbS5pYnJhaGltLmtleWJvYXJkIl0

This worked!
Thanks jscott30!

Hi Ishedra/ jscott30,
I currently have a Samsung Infuse 4G with the GB 2.3.6 update. I am really only interested in rooting and getting Arabic RTL support.
You mentioned using the ROM [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root.
My questions are:
Which of the options did you go with because there are 4 of them? Or does it not matter which one?
Where do you obtain a Hebrew Arabic patch that works with this ROM. It seems Arabic support is only available in certain custom ROMs. I tried searching for a general patch that works on all rooted 2.3.6 Gingerbread but couldn't find any.
Thanks in advance!

dashrendar said:
Hi Ishedra/ jscott30,
I currently have a Samsung Infuse 4G with the GB 2.3.6 update. I am really only interested in rooting and getting Arabic RTL support.
You mentioned using the ROM [ODIN][UCLB3] AT&T 2.3.6 Gingerbread with root.
My questions are:
Which of the options did you go with because there are 4 of them? Or does it not matter which one?
Where do you obtain a Hebrew Arabic patch that works with this ROM. It seems Arabic support is only available in certain custom ROMs. I tried searching for a general patch that works on all rooted 2.3.6 Gingerbread but couldn't find any.
Thanks in advance!
Click to expand...
Click to collapse
Hi dashrendar,
Here is a link to the patch that Ishedra most likely used. It should work with any rooted UCLB3 base or rom w/ CWM recovery. If you opt for one of the options from my Odin to rooted UCLB3 thread, it sounds like you would most be interested in Option D.
Arabic patch: http://forum.xda-developers.com/showthread.php?t=1467808
Arabic keyboard: https://play.google.com/store/apps/...51bGwsMSwxLDMsImNvbS5pYnJhaGltLmtleWJvYXJkIl0
Let us know if this works, as I've not tried it myself since English is my only language.

Outstanding jscott...u d man
Sent from my SGH I717, Black Star.

Thanks a lot jscott30.
The Infuse is actually my wife's. I have an AT&T Samsung Galaxy SII with stock ROM (2.3.6 GB).
I wanted to make sure that I can do the same patch on my wife's phone so that she is not left out.
I will definitely be following the steps you provided, but I wanted to test on my phone first. Do you recommend a similar ROM for the SGSII similar to what you did for the Infuse--basically, rooted stock software with CWM (to support the RTL patch). The goal is to be as close to stock as possible (can't afford to lose any functionality but I do welcome the ability to uninstall bloatware).
Thanks again!

dashrendar said:
Thanks a lot jscott30.
The Infuse is actually my wife's. I have an AT&T Samsung Galaxy SII with stock ROM (2.3.6 GB).
I wanted to make sure that I can do the same patch on my wife's phone so that she is not left out.
I will definitely be following the steps you provided, but I wanted to test on my phone first. Do you recommend a similar ROM for the SGSII similar to what you did for the Infuse--basically, rooted stock software with CWM (to support the RTL patch). The goal is to be as close to stock as possible (can't afford to lose any functionality but I do welcome the ability to uninstall bloatware).
Thanks again!
Click to expand...
Click to collapse
Glad to help! And I haven't been around the SGSII forums to be able to suggest something similar, but I'm positive that they have similar rooted stock roms. At very least, over there they can show you how to root your phone and install CWM recovery.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Hi jscott30,
Thanks again.
I am in a bit of a dilemma. I stayed up until 4:30 AM this morning trying to resolve an issue I ran into. Sorry, I tried to post in the original thread for the stock image, but because I don't have enough posts I wasn't allowed to.
Anyway, I went with option D as you suggested. I performed the data/cache wipe in step 4 to avoid the potential boot issue. Everything else went okay.
However, after installing a bunch of applications and freezing a couple, the Phone application kept crashing. Basically, when I click on it, the screen stalls for a couple of seconds, the screen turns black with a quick all-screen white flash, then black again. Then after a couple of seconds, I see the pattern screen lock. Then I can go in again. That happened every time I clicked the Phone icon.
I performed the flash again the same way. It went fine. The first thing I checked was the Phone app, and it was working okay. However, now every time I turn on Wi-Fi or mobile network connectivity, the same crash keeps happening periodically every 10-20 seconds, which makes the phone unusable. :crying: I initially thought it was the external SD card, but I took it out and the same symptom persisted. I turned both network connections off for now and no crashes are happening.
Do you have any ideas? I thought I would post this first before I start scouring the forums in case you had any ideas.
Thanks!

I can't reproduce those issues here, so it's hard to say. Try a software factory reset by going to Settings / Privacy / Factory data reset. That may clear what is causing your issue. That package has been downloaded over 2000 times, though, and this is the first I've heard of this issue. Makes me think that something is left from a prior install. Also, do you have this issue before the Arabic patch?
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

Hi jscott30,
I have done the reset as you described and it goes into a loop when it boots. I tried flashing again and this time I wanted to keep track of the order of things. I mean last night I was able to download and install a bunch of apps using WiFi without problems. I think after which I installed the Arabic patch and the crash started happening.
I flashed again about 30 minutes ago following your steps to the word. After that I did the the following:
- Skipped the Setup Wizard;
- Enabled WiFi;
- Launched the browser to ensure data is being transmitted;
- I added my wife's Google Account to make sure it's not a synch issue;
- I asked her to check her GMail on both WiFi and mobile connectivity;
It seems like it's working normally so far. I will try to apply the Arabic patch to see if it's the culprit (which would be disappointing to see it affecting Wifi/Mobile Data).
By the way, I noticed that Al Hosny instructed installing something called Aries. What is that? And do I need this as well prior to the patch?
If the patch is indeed the problem? Could it be an incompatibility with this version of the CWM kernel? (Sorry for any noob questions).
Anyway, thanks for the quick response and I'll keep you updated as to what happens.

If the patch suggested ends up being culprit, I'd PM Ishedra to ask how to apply an Arabic patch. It was a guess on my part that he used the one patch, as I've not used it before. Unfortunately, English is my only fluent language.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2

dashrendar said:
Hi jscott30,
Thanks again.
I am in a bit of a dilemma. I stayed up until 4:30 AM this morning trying to resolve an issue I ran into. Sorry, I tried to post in the original thread for the stock image, but because I don't have enough posts I wasn't allowed to.
Anyway, I went with option D as you suggested. I performed the data/cache wipe in step 4 to avoid the potential boot issue. Everything else went okay.
However, after installing a bunch of applications and freezing a couple, the Phone application kept crashing. Basically, when I click on it, the screen stalls for a couple of seconds, the screen turns black with a quick all-screen white flash, then black again. Then after a couple of seconds, I see the pattern screen lock. Then I can go in again. That happened every time I clicked the Phone icon.
I performed the flash again the same way. It went fine. The first thing I checked was the Phone app, and it was working okay. However, now every time I turn on Wi-Fi or mobile network connectivity, the same crash keeps happening periodically every 10-20 seconds, which makes the phone unusable. :crying: I initially thought it was the external SD card, but I took it out and the same symptom persisted. I turned both network connections off for now and no crashes are happening.
Do you have any ideas? I thought I would post this first before I start scouring the forums in case you had any ideas.
Thanks!
Click to expand...
Click to collapse
When you were installing the app and the OS started crashing, were you trying to install apps that you had backed up previously?
Some times, certain apps restore or apps/data restore from the older OS will cause crash on the newer OS.
When this happens, I would suggest downloading the app new from your source and do not restore them from backed up source.
Not every app/data does this...but if you ran into problems, start new.

Hi qkster,
I was actually downloading and installing those apps from the market. I only backed up/restored their relevant data/settings.
I have some good news though. Before I loaded this Arabic Patch I started looking for another one. I tried and settled on this method whose source steps are in this blog. I see the Arabic text fine, the letters were all connected in GMail, Whatsapp and Facebook. I haven't tried the keyboard because my wife showed no interest.
I apologize for not trying out the previous Arabic patch in order to confirm its functionality. Unfortunately, I didn't have enough time--with my wife waiting and depending on her phone and my baby daughter wanting to play with me, it's hard to find the time.
I installed the rest of the apps for my wife and everything is working solid so far.
This is good practice for when I need to do the same steps on my brother's and dad's phones. I believe my phone will be getting ICS soon (which should have built-in Arabic language support), so we'll see.
Thanks again for the great ROM and advice guys. :good:

Just updated to official ICS from Rogers

hey guys,
hope everyone is having a great weekend, i was so pleased to find out that rogers finally released the official ICS update for my galaxy s2 skyrocket lte, so i get it updated today.. and one the TW launcher is so ugly and non customizable and worthless so i am in the midst of deciding on one that i like, so far ive tried ICS pro launcher. my main problem with my phone after upgrading to ICS is the fact that the swype typing is so slow and laggy you can barley hold on a conversation, it just seems like ICS slowed down my phone a crap ton, and mind you i have not rooted my phone at all nor have i ever installed a custom rom on this phone, what do you think could be the problem? the phone itself is so laggy, anyone have any ideas?
Thanks in advance.
-Davey

just to reiterate i did the update over samsung KIES, am i supposed to do a hard or a soft reset?

Maybe you should give other launchers a go, I use Apex myself, but Nova is also pretty good for ICS.

nthuser said:
Maybe you should give other launchers a go, I use Apex myself, but Nova is also pretty good for ICS.
Click to expand...
Click to collapse
Do you think that would affect my swype lag? also if i wanted to wipe everything and start fresh can i do that with odin without being rooted/

davey818 said:
Do you think that would affect my swype lag? also if i wanted to wipe everything and start fresh can i do that with odin without being rooted/
Click to expand...
Click to collapse
factory data reset is the best way just boot up to the default androdi recovery (same way as you would with CWM) then clear data/wipe. Then you want to disable all that crap rogers installs on our phones (stupid one music, one contacts bs) and other crap that samsung installs on our phones. In my opinion CM9 is much faster and better then the ICS rogers rom.
EDIT: I got a brand new replacement for my i727r so I didn't want to root it yet cause its in mint condition lol so thats what I did to keep the stock at decent speed

When ICS will be available for at&t I will format the whole phone in CWM then flash ICS tar in Odin...That way did a great impact on ICS speed when I was using Nexus s...OTA over the old gingerbread was slow as hell, but when I did a clean install from scratch phone was way faster...and even better battery life ..I never really liked update rather than a fresh install in any software matter...

samsung kies
mahanddeem said:
When ICS will be available for at&t I will format the whole phone in CWM then flash ICS tar in Odin...That way did a great impact on ICS speed when I was using Nexus s...OTA over the old gingerbread was slow as hell, but when I did a clean install from scratch phone was way faster...and even better battery life ..I never really liked update rather than a fresh install in any software matter...
Click to expand...
Click to collapse
True say thank you very much, just one more question is there a section that touches base on kies issues in here? for some reason after the update to ICS my computer no longer sees my phone i tried reinstalling the drivers and kies several times.

davey818 said:
True say thank you very much, just one more question is there a section that touches base on kies issues in here? for some reason after the update to ICS my computer no longer sees my phone i tried reinstalling the drivers and kies several times.
Click to expand...
Click to collapse
Kies is a very stupid software full of bugs and slow ..Why you need it anyway ? you can backup your pics files ...etc... using the USB connection , other things like contact are already on your google account ... So I don't see what kies is important for ...
----------
Grab the official Rogers ICS tar from sammobile.com and ODIN it to your phone...(that's after you wipe/format every partition (cache,data,system) in CWM recovery)...

CRT screen off animation gone with Jelly Bean OTA.

Anyone else noticed it?

Mine works perfectly fine. Make sure your animation for Window is set to x1.

I have the same problem on my Nexus S I9023. It feels weird...

same problem here i9023.. crt not work

Mine works 1 time out of 30 i guess . I9023
Sent from my Nexus S using xda app-developers app

it seems to be a problem only related to 9023 SLCD looking to replies...
(I9023 SLCD here, and CRT animation working 1/30 times)

i got an i9023 aswell

My used to work, now it's nothing.

the problem looks to be only on the I9023 model (which i have) like raducux mine goes once every while.i think we should be able to work on a fix,the problem is probably with "services.jar" i decompiled the "framework-res.apk" and everything looks fine there (i checked the bools) so am gonna take a look at services and will try to work on a fix for this.

i9023 here. same annoying issue

Same here. i9023.
(But sometimes I see it... just not most of the time. I hear "click" though, when screen is already off)
window animation is set at 1.

imbehind said:
Same here. i9023.
(But sometimes I see it... just not most of the time. I hear "click" though, when screen is already off)
window animation is set at 1.
Click to expand...
Click to collapse
I can confirm I have the same problem on my S-LCD screen.

any fix pls ?

tumbHo son
Would be super cool if someone could upload any kind of a fix for this. That's the only thing that's pissing me with 4.1.1

do you also have this bug when you updated 4.0.4 to 4.1.1 OTA via the system update (not manual flashing) ?

asphantix said:
do you also have this bug when you updated 4.0.4 to 4.1.1 OTA via the system update (not manual flashing) ?
Click to expand...
Click to collapse
I always had this bug on any type of 4.1.1. SDK port, AOSP, manual upgrade in cwm from stock 4.0.4 fastboot images. I even tried that "official OTA" from this thread:
http://forum.xda-developers.com/showthread.php?t=1784497
Now I'm on 4.1.1 which I got by installing this update:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip
CRT animation was active for a while, then just stopped working.

working on fix here (can't promise anything though ) i would be happy if someone can provide me with ICS 4.0.4 "framework" odexed or deodexed just to save me some time.as i said before the problems seems to be with services.jar which i deodexed and decompiled in order to start working with it but i still need the 4.0.4 framework to compare with.

i do this step : Stock 4.0.4->Unlock bootloader wipe data->Flash Cwm->Flash 9ZGgDXDi.zip->Boot->Lock bootloader-> After Wipe data and cache from Android Recovery and factory reset from settings .. the first time work i think but after no...

so you think everyone gets the 9ZGgDXDi.zip? Maybe google rolls out a different update for i9023 that's why I asked if anyone updated via the standard google update process.

asphantix said:
so you think everyone gets the 9ZGgDXDi.zip? Maybe google rolls out a different update for i9023 that's why I asked if anyone updated via the standard google update process.
Click to expand...
Click to collapse
no google usually roll the same update for i9020 and i9023 the only difference is the display the problem could be with backlight oe other related screen things,like the problem we had with 4.0.3 recovery.

[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