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

[Q] Can't flash back to stock

I've downloaded the stock image directly from the Motodev site for my MZ604. It successfully flashes boot.img. When I try to flash system.img, it just hangs. I thought maybe I was rushing it before giving up but I left it going for a couple of hours this morning with no luck. I'm happy with cwm and running ics roms but this is puzzling me as to why I can't get back to stock. My stock recovery img got trashed last month so recovering back to stock isn't an option. Any suggestions?

More specifically, I get a successful send of system.img, the hang up happens while writing.

I know this may not help you but have u tried downloading the file another time and compare the md5 between the file.. If they are the same then i have no idea mine was able to write correctly.. If they are different download it a 3rd time and see which one is truly correct.?
Sent from my mind control device

Downloaded from another site and got the same results. I kept rebooting the xoom and repeatedly tried flashing and it finally went through. For some reason, I had to do the same thing for recovery and userdata. It's back to stock and working normally now.
ps now i'm about to root again and flash a nightly lol. I just couldn't understand why it did the same thing last month when i tried to revert to stock and gave up. I was determined to figure it out today.

Awesome to hear! Flash away lol
Sent from my mind control device

[Q] Stuck in Recovery?

Hi all,
As the title says I am currently unable to boot past (red) CWM recovery on my Infuse. I figure it might be easier to get help if I explain everything I've done:
The other day I tried to flash Uniporn build 37 only to soft-brick my phone because I didn't have the GB bootloaders installed (I had previously been on CM7). I managed to nandroid back to CM7 and decided I'd give it another go today.
Since I was told that flashing bootloaders is very risky I decided to flash something easier first with Heimdall to make sure everything was working right. I ended up flashing the ICS kernel in qkster's thread (one-click)... mistake #1. That bricked my phone once again and gave me rainbows in recovery.
So then I decided to try a Heimdall flash to stock 2.3.6 UCLB3 (once again, the one-click Heimdall from qkster's thread), which did give me a bootable OS despite some rainbows while booting up. However, here I made mistake #2 and tried to recover from the CM7 backup I made earlier today with the Infuse Toolkit. This completely soft-bricked my phone; I couldn't even get into recovery at this point.
So, I tried to reflash the stock 2.3.6 with bootloaders this time, only (and this may be important, not sure) it tried and failed to flash a PIT. At this point I flipped because I thought I had hard-bricked the phone. After I calmed down and came back a while later, I discovered the phone wasn't hard-bricked at all and I was able to get it into download mode after all!
I then flashed stock Froyo (I'd had enough of that rainbow ****) and it seemed to go fine... only now it wouldn't boot past 3e recovery, despite me wiping data and cache multiple times. So I flashed the community kernel... same problem, only now with red CWM instead of 3e.
So... what can I do now? I'm relieved I don't have a hard-brick on my hands, but this isn't that much better... could that PIT be the problem? I hope the info I gave is enough to help (and isn't too much either!)
Screw ICS, now I just want my CM7 back
EDIT: I should also probably note that after I managed to get CWM back I tried to flash the UCLB3 ROM in the Infuse toolkit; it said it installed but when I rebooted the phone still went straight to CWM.
EDIT 2: Another weird thing I just noticed: the phone apparently refuses to stay turned off while it's plugged into the wall to charge. If I plug it in, it turns on and goes into recovery mode. This also can't be good, since IIRC the battery won't charge while in recovery.

Just heimdall or Odin again...I've had this happen soo many time when I had my infuse...I just simply run heimdall again and its good...if you ever get recovery after heimdal or Odin...do not hit reboot...wipe everything then hit reboot...
And gingerbread bootloaders are not required for ics...I keep hearing people say they brick there phones because they don't have gb bootloaders...that is not the reason...yes with out the bootloaders you get rainbow recovery and boot up but that is it!!!
Remember if you are going to ics from gingerbread...YOU HAVE TO double flash...the first flash will not work...just three finger back to recovery and flash again from.blue/rainbow recovery depending whether or not you have.bootloaders...
Look at my infinitum port thread...it has great instructions on how to flash ics roms...as well as how I flashed gingerbread bootloaders when I had my infuse
Sent from my HTC PH39100 using XDA

Nah, I've tried that, it's more broken than that. I think I need to reflash the PIT, which Heimdall doesn't like for some reason. I followed qkster's advice in another thread but still no dice. I might have to try using a different computer.
All fixed now, I used the Heimdall one-click on a Windows machine; the PIT and everything else flashed without a hitch and I'm up and running again.

just keep trying flash different stable stock roms thru odin until u can boot..i had it happen twice nd even couldn't get computer recognize my phone for a bit thru odin but it finaly workd now I'm back on cm9
Samsung Infuse ICS 4.0.1(cm9)

Soft brick/boot loop

I was running the latest tweaked ROM yesterday when it rebooted itself into a boot loop. Iets stuck at "Samsung"
I attempted to restore using Odin following the instructions in the how to fix your phone thread. Though i've been successful with that in the past, this time it didn't fix the phone. Its still stuck on Samsung, but will randomly display the stock boot ani with sound, or even get to the lock screen, but then immediately go back to displaying Samsung.
Any ideas would be greatly appreciated, and yes, i've followed all instructions correctly with wipes and loading things in Odin, etc.
Thanks!

Hmm... was there anything going on at the time of reboot? Very curious.
Beyond that - assuming all went as it should with ODIN, if you are still having issues then the problem is a bit beyond the rom. It seems a scapegoat but perhaps a hardware error is underlying things...?
Anyhoo - what file (or files) have you tried to ODIN? There are a few to choose from, and they all can be found here (just be sure to only DL and use the charge-specific ones of course). I would try each one and hope at some point something sticks to where the phone is usable again. Sorry for the troubles!

Thanks for your reply! Phone was just sitting on my desk, I was text messaging...it may have been plugged into a non Samsung charger. I doubt its the fault of your ROM tho, as it had been running great since I installed 2.1 a few weeks ago. Its always run hot so that might have just caught up with it.
I'll try all those files this time on fresh downloads, might have been something corrupted.
thanks again!
UPDATE: Successfully loaded ED1 on, and it boots. I can unlock the phone, begin the setup process, but then it reboots. I'm so confused...

Find the most current OTA file and flash it instead of working your way all the way from Froyo to Gingerbread.
Sent from my SCH-I510 using xda premium

I had something similar happen to me just a week ago. I was on stock debloated deodexed and odined to tweeked and it bootlooped, Odin said successful but nothing was happening just Samsung logo. I knew there was no problem with tweeked cause I used the same file b4 and it worked fine. Tried to Odin back to stock ep4 same Samsung logo Odin still said it was successful. So I changed cable and made shure I was not moving phone or cable while it was doing its thing. It worked. Then updated to fp1, cwm superuser then Odin to tweeked. Everything ok. I figured the only problem of my was that the cable was a bit loose when I plugged it in the phone, the connections in the phone I guess were not getting the full contact as they should have. So try making shure you connect/plug in cable all the way and don't touch it while Odin is doing its job. You might also need to flash the stock ep4 file. Sorry could not help more. This worked for me, now on tweeked 2.2 n no problems.
Sent from my SCH-I510 using xda app-developers app

[Q] Lost camera after AOSP flash and even ODIN to stock won't work

So I finally took the plunge to AOSP since I have my note 2 to run stable. First thing I noticed was that the camera got a "can't connect to the camera" error. Fixed permissions, wiped multiple times, tried a couple different AOSP roms and nothing, so I looked deeper and found some file replacements for the data folders, tried that and still nothing. Wiped again flashed a stock rooted image and still nothing, so last resort was 2 different stock rooted and not-rooted images through ODIN. Successful flashes of both and still no camera.
I am stumped i thought my fail safe ODIN would work but it didn't if anyone has any suggestions I would greatly appreciate it.
p.s. my bootloder is unlocked.

::UPDATE::
Ok so after continuing the troubleshoot finally stumbled upon something. After restoring a stock ODIN of ICS from when i first got the phone I let Verizon run through and do its update and after it finished VOILA my camera's working. I honestly don't know how it happened but nothing else had worked, now i have to go through and unlock root and get a custom ROM again. hopefully this can help someone if this happens to them.