for those who used stock att 2.3.6 on there rogers like me. and tried to go back to rogers and most likly got the rainbow screen upon boot up. this method i used by staying up and trying to get rid of that eyesore of a screen. even tho i dont turn my phone off. i knew it was there. here is what i did after i flashed 2.3.6
1. used gtg ultimate unbrick pit,pda, and phone..flashed
2. used Odin_Infused_Gingerbread_Kernel_v1 just to get root and cwm
3. got rom of choice i used 3 of them already and same result. (skips the first boot screen) goes right to samsung. i used miui 2.2.24, infused 2.2.3 and zeus total final.
no more eyesore upon startup of phone
im glad i found a solution. im tired from staying up and getting couple hours sleep for a week. cause i hate broken stuff.
Also I found on Zeus don't install add-ons. As it makes my phone lag and loop
Sent from my SAMSUNG-SGH-I997 using XDA
Related
Background. Was using 2.2 for the longest time, loved Firefly. Went ahead and bit the bullet and decided to go to 2.3 and use Gingerbread. Solid week of great success. However I started notcing my antenna saying no signal. Several Reboots and still nothing worked. Decided I would One-Click Back to 2.1 and start fresh. Well I never had issues with Odin 1 Click before, but now I get in a boot loop (ATT SPlash Screen) I have noticed when its unloading the package after , the last thing i see is CSC and that it boots into the loop. Would love to get my phone back to stock so i can see if its a hardware or software issue with my antenna. I have looked at this link, http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36 but was afraid I possibly might still have GB bootloaders on my phone. I would think not if Odin finished, but I just want to double check with the community so I dont brick.
Thanks guys.
Can you get into DL mode? IF so, i would try and Odin again. ALthough I looked at the link in your OP, unless your heart is set on 2.1JH7, i would use the Odin3 one click downloader. That will restore your phone to 2.1JF6 as well as flash the correct bootloaders. I have gone back and forth from continuum to cm7 a few times now using that method.
Thanks for the quick reply. however this is the 3rd time trying Odin-1 Click tonight and I still end up in a boot loop. I have redownloaded the file just to make sure I didnt have a corrupt one. I just want a stock system and see if the constant antenna issues continue. (Trust me Ive tried different modems and all those possibilities.) Is it safe with that link? I noticed when i do Odin they flash a sbin and bootloader. I am assuming that puts it back on 2.1
which Odin are you using? Are you using the one click program that gives you stock firmware... JF6 firmware?
It is here:
http://www.megaupload.com/?d=SBSMALFJ
Yup thats what I have. It looks like it doesn't load the android system. Soon as it says installing Multi-CSC its done and rebooting. It would seem like its not unpacking the files. I have no status bar at the bottom. I have no idea why its doing this. Here is the crazy part. If i go back to the ginberbread stock, its not a problem to get to boot.
while I'm no expert.. seems like a bootloader thing. Try downloading it again from the link i put up and see if it was maybe a corrupted download.
The bootloaders are the first thing flashed in odin. It stopped after that then you have stock bootloaders. Also if all you see is the white AT&T screen and then it reboots, that indicates stock bootloaders as well. The gb bootloaders have a black galaxy s I9000 screen as the param.lfs image.
I would bet money you have stock bootloaders, use that link you posted that work be perfect. If you go back to gingerbread and want to return to stock bootloaders you'll have to use one click again even though you got a problem from it this time, if you get the same problem you know this worked to fix it.
And lastly usually problems with cell signal are modem related ... Which one were you using, did you even try another one? That would've been my first move instead of going all the way back to stock.
Hey studacris,
I have been using Mosaic (Love the work you guys do over there). I did try and use the other method to get back to Stock Last night and it did the same thing. Just a bootloop. If its plugged into the USB cable it goes directly to the Battery Symbol, if its not the Att 3G bars loop. I can flash to Gingerbread stock and then apply Other Roms. I tried GR-2 and Mosaic again, but still nothing with the signals. I just dont like the fact I cant get back to Stock with those 2 different methods. What I think is odd is when I load Gingerbread, it seems like items are being unpacked and loaded. When i try to go to Stock, everything happens super quick, making me believe nothing ever gets installed on the Internal Card during the unpacking sequence. I am no pro, but thats just something i noticed. Here was my original post on the Mosaic board. http://forum.xda-developers.com/showthread.php?p=14043766&highlight=Rizz67#post14043766
Forgive the title, I need it to make it interesting to get some views. Now that's said, let me get to it.
I recently tried to flash MIUI onto my Samsung Infuse. I had Infused ROM v.2.2.3. I must have messed up because now I'm having trouble getting my phone to start. When I power on, it briefly shows the Samsung logo (for about 3 sec); then for split second an alternate screen flashes on my screen just before my phone shuts off. Now, I've tried to load CWM(red version) with the 2/3 button technique; however, I haven't been able to get into that GUI.
I have been able to get into the Download screen, for Odin. But, I was hoping there might be some sort of way to solve this problem without resetting my phone to stock.
Questions
1. Can I utilize the Download screen to re-implement or re-flash my ROMs on my phone; without loosing data
2. Is there a way that I can force my way into the CWM GUI?
3 If none of the above are possible, where can I get information Odin for the Infuse; and where can I download the program?
Thank you for reading, and thanks for the help in advance!
Joaquin
I wasn't going to reply to your thread but you caught me in a good mood. head over to the dev forum and you will find everything you need to get your phone back. That's all I'm goin to give you. the more you search and experiment the more you will learn
Already found somethings that are helping...
I didn't post for as a resource, just thought that if someone knew where to look they'd point me in the right place.
For anyone who might need a nudge; this link will direct you to complete recovery http://forum.xda-developers.com/showthread.php?t=1092021
Did you follow the directions exactly as it says? Did you ever get into blue cwm and flash miui a second time?
Sent from my SGH-I997
I wouldn't recommend MIUI to anyone who isn't atleast a little experienced in flashing ROMs, and are sure won't panic if they find their system soft bricked.
went to http://galnetmiui.co.uk/landing/weekly-builds/ downloaded infuse rom using miui build 112230 wiped data,cache,dalvik applied installed galnet miui rebooted does not load stays on samsung logo wiped data,cache,dalvik reinstalled galnet does not work, used blue cwm, returned phone to stock froyo, using odin reinstalled galnet using green cwm, still doesnt work, dont know what im doing wrong, please help, do i need to install gb bootloaders?
Sent from my SGH-I997 using xda premium
getting to be far too familiar a scenario lately....
lately EVERY time i reboot my phone (running ics build 2, 3 and 4, stock kernel) it gets stuck on samsung logo.. somehow my phone will only boot into the frigging cm7 recovery which as im sure youre all aware is rather useless to fix any problems im having in ics and leaves me unable to flash, backup, or restore anything. it's quite frustrating and i have no idea how to fix it but by going back to bml, re-partitioning, then odin ei20 modem, cm7 fixed recovery, then flash back to ics but doin this every reboot it getting very tedious..
ive read about recovery loops, but the fix doesnt work for me as i cant mount the ICS /system partition in cm7 recovery...and ive been all over trying a zillion things to get it to work and havent pulled dmesg or logcat but if someone thinks it would be useful ..i wish i knew why EVERYTHING is great, then BANG, reboot and it's FML city.
i should add this phone is a replacement via insurance and that the entire time ive had it, i've been having this problem to varying degrees of intensity,.sometimes if i rebooted enough the ics boot animation would finally come up and freeze part way through, and in the first week with this phone is seemed fine. the first few times i rebooted and battery pulled until it started but this is the fourth time in two weeks ive found myself going back to repartition from odin and then back to ics.. the phone is only mine for a month,.
if nobody has any ideas ill be getting it replaced tomorrow in store. i have the no fee insurance replacement plan, but i would prefer not to have to use another as it's not under warranty and this would be my second replacement and this mes has to last me until the gnex hits uscc in hopefully april if it ever does because i'd rather switch to vzw than take any of usccs other offerings currently.. if they dont get the gnex it'll be time for me to move on...
anyway please advise.. thanks
You're asking this at the wrong forum dude. You wont get any support here. Everyone's moved to Rootzwiki
http://rootzwiki.com/topic/15859-ics-b4-was-100-rebooted-and-bootloop-on-samsung-logo/
Yep but when fishing it helps to have multiple lines in the water...
Past experience
From what ive found out, once you have ICS flash on ur phone, ur not going to want to use the three finger salute. If you want to boot into recovery, only do it by rebooting into recovery through ics
Hey all, I recently rooted my atrix 2 about 3 days ago then decided I wanted to run ICS so I went back to 2.3.5 then OTA'd to 2.3.6 and got my phone on ICS following Jim's guide. Everything went fine and I was running ICS fine until I downloaded ROMtoolbox and tried to change my font to the DROID font. the screen flashed and everything went to chinese and then my phone reboot itself but now it keepts getting stuck on the white AT&T screen, I've tried running through recovery and rebooting but everytime it just freezes on that screen.
Nevermind guys I got it all back up and working by just reinstalling ICS from recovery menu.
J9993 said:
Hey all, I recently rooted my atrix 2 about 3 days ago then decided I wanted to run ICS so I went back to 2.3.5 then OTA'd to 2.3.6 and got my phone on ICS following Jim's guide. Everything went fine and I was running ICS fine until I downloaded ROMtoolbox and tried to change my font to the DROID font. the screen flashed and everything went to chinese and then my phone reboot itself but now it keepts getting stuck on the white AT&T screen, I've tried running through recovery and rebooting but everytime it just freezes on that screen. Please help
Click to expand...
Click to collapse
Can you get into bootmenu? If yes, do you have an ICS based backup?
If you don't have a backup or bootmenu the only thing you can really do is fkz back to GB 2.3.5 and re-update...
And for future reference... don't use rom toolbox.. it usually doesn't end well... as you might have figured out.
PEOPLE! Stop goofing around with things using ROM Toolbox, it does nothing for your phone other than cause headaches. I've soft bricked using it, others are having similar problems. It's not worth the hassle. Seriously...
Sent from my rooted Mayan Calendar
Apex_Strider said:
PEOPLE! Stop goofing around with things using ROM Toolbox, it does nothing for your phone other than cause headaches. I've soft bricked using it, others are having similar problems. It's not worth the hassle. Seriously...
Sent from my rooted Mayan Calendar
Click to expand...
Click to collapse
Yupp, even i bootlooped trying to change the font.
Sent from my MB865 on rooted ICS leak
so it would be better to have the individual apps themselves instead of toolbox or stay away from those apps in general? also is it still possible to do the wifi tethering with the ICS leak?
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