Database Info

Constant Loss of Single/Odin 1 Click Boot Loop

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

strange ns4g issues

I used odin when the 4.0.4 official leak was posted here. I since uses the one click software restore back to 2.3.4. At first it gave an issue with the radio. On my phone while restoring it said "radio fail" but the phone seems to be working.
Now I manually updated the unrooted Sprint official 4.0. And my phone since the very first thing I said, has been randomly rebooting, I tried a different battery and it does the same thing. It's also real laggy. Any advice? Are there stock 2.3.4(7) files I can odin? I want it completely factory. Or suggest the problem? Thank you.

Bumping

[Q] Would Samsung fix my bricked phone?

I bricked my unlocked Captivate (bought on Amazon for $240 - I was avoiding a data plan) trying to get Ice Cream Sandwich on it. The phone was rooted.
Initially, the phone was only loading a Samsung splash screen when I tried to get it into normal mode. However, recovery mode was working; it would boot into Clockworkmod. Which is a bad thing considering they would easily tell I had messed with it!
So, I loaded the phone into Download mode and tried to flash the stock ROM using Odin. Odin said "failed" and now my phone was completely soft bricked, and the infamous "[phone]-----/!\-----[computer]" screen was showing up. Download mode worked though. I tried to flash all types of stock and custom ROMs to no avail. Now, recovery and normal modes don't work while Download mode does.
So, I called Samsung and told them it wasn't working; they told me it was still under warranty and I could send it in for repairs.
My question would be: will Samsung repair my phone, or will they find out I messed with it and refuse to do so? Also, if they find out, how much will I have to pay them to fix it?
Getting a new phone is out of the question... I might just buy

If there is an odin flash counter on download mode, they will figure it out if you have messed with it. If there's not, make a good story. Was it on 2.3.6 already when you bought it?

If you can get into download your not bricked. The screen you see is kernel panic. You will have to flash a proper kernel to get it to boot back up.
Sent for a corner cell in Arkham

Yeah, you can still fix it. No need it to bring to samsung

Has anyone sent a bricked phone in to Samsung before?
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?

random_person1308 said:
I tried flashing stock Captivate Gingerbread kernels to no avail. I googled and googled, and I tried everything I found. Including Odin and heimdall.
It was running Gingerbread 2.3.5 when I updated it myself to Ice Cream Sandwich 4.0.3. It was running beautifully. Then I tried to recover my backed-up data, which worked, but then I tried to reboot the phone and it wouldn't boot.
And no, I don't remember seeing any "flash counter." Would they still be able to tell?
Has anyone sent a bricked phone in to Samsung before? If so, what were the results?
Also, how much do you think Samsung would charge me to fix it if they found out and voided the warranty? Hopefully less than $50? And they would charge me for shipping too, right?
Click to expand...
Click to collapse
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.

cessprin00 said:
You recovered your apps thru TB? If yes, Didn't you read that you're not supposed to restore apps from titanium from GB to ICS? Might cause problem like this. No flash counter, they're not gonna notice this. Have you tried flashing again stock GB rom?(not just a kernel but a rom) And when you flashed that GB kernel, was that after you flash an ICS rom? Remember, when you're on ICS, you must use ICS kernel and not GB kernel. If it didnt work Just make a good story! Tell them you updated it through kies and updating was interrupted. Im pretty sure 2.3.6 is out on captivate. If they tell you its your fault for updating it, ask them why did they put update on kies when you can't even use it. Plus, they didn't warn you not to update it.
Click to expand...
Click to collapse
No, I used Clockworkmod to recover data. It worked, and then I hit "reboot system now," and the phone wouldn't boot.
I already shipped the phone off, but thanks for the help, I really appreciate it! If Samsung doesn't fix it I know what to do now!

Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!

random_person1308 said:
Ok, so I've been doing some research over the past few weeks and I figured out what I did wrong. I inadvertently tried doing a Nandroid restore (i.e. - restoring the whole system) instead of just apps. And I didn't wipe data first. That's why it was failing to boot. Why I couldn't flash the stock kernel from Odin; I have no idea.
As for the phone; Samsung fixed it free of charge (all they had to do was a reset...) and sent it back to me.
After getting it back, I rooted and installed Clockworkmod recovery using Corn kernel version 7.05. Geeve420 has an excellent guide over on androidforums.com. Then I flashed Cyanogenmod9 RC2, then Slim ICS version 4.2. It's running smoothly, though in 24 hours I have had 1 freeze (I did a battery pull and restarted) and a few force closes.
I also installed that Google Now app (the thread on XDA is called "The Google Now for ICS Project"). In other words, I went from being a complete n00b to getting JellyBean software on my phone! All I did was follow the directions, step-by-step, and it worked.
Thanks to all who helped!
Click to expand...
Click to collapse
Good for you then Try not to mess with it again. Haha. Do a lot of reading if you're a little hesistant. Plus, asking before doing so is not problem. We have a lot of helpful xda members here to guide you. Goodluck!

Galaxy s2 att help

I have a galaxy s2 that I tried rooting, it sorta worked then it did not. So I followed the instruction to put it back to stock with gingerbread .uckh7,
kernal version 2.6.35.7
The phone seems to work fine. The issue is I cannot put it back to ics which is where it was, I tried reloading Kies, I tried just using the update. Nothing. And the phone now seems to once in awhile go into airplane mode by itself, or to restart itsself.
I would love to root my phone, and have it work well. I know enough about computers to be dangerous I am sure. But baring that I would just like to be able to have it back to where it was.
Thanks for the help.

[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