Database Info

[Q] Stuck In Android System Recovery

OK...I think I did it this time.
I tried to install a new ROM and now when I reboot, all I get is the i9000 screen.
The "good" news is that when I take the battery out and reinstall it and press both UP and DOWN, I am able to get into System recovery (makes me think it is salveagable).
The yellow text below simply says:
upload media, please wait...
# MANUAL MODE #
-- Appling Multi-CSC...
Installing Multi-CSC
But the problem in this mode is that I only have 4 options:
1) Reboot System Now
If I select this, all I get is the phone restarting and then getting stuck in
the GT-I9000 mode (not too helpful)
2) Re-install Pacages
Just kinda reboots to the Android Recovery screen. Nothing really happens.
Same yellow font as what was described up top.
3) delete all user data
Useless for rebooting the system.
4) delete cache data
Useless for rebooting the system.
I am thinking that Option #2 has to get me somewhere...but it isn't really doing anything once I select it...the phone just sits in the Android System Recovery screen.
Any help to get me outta this predicument is certainly worth a PayPal donation!
What's the secret? HOw do I get out of this mess?

Use adb to get into download mode and flash back to stock using Odin.

majinzen said:
Use adb to get into download mode and flash back to stock using Odin.
Click to expand...
Click to collapse
What he said.

My phone did this to me 2 days. Just go into DL mode then go back to stock. then reflash whatever you was flashing

Use adb? Can you provide me steps...or a thread that details this? .i am not sure how to do this.
How do i get to "dl" mode?
Sent from my HTC HD2 using XDA App

Can't Get Into Download Mode
So my latest problem is that I can't get into download mode! Only recovery mode. I tried the tricks posted (power with volume button down) (plug in USB cable), to no avail. Then I tried a "power button/back button/volume buttons" combo and I got a picture of the Android logo shovelling something...it said "Downloading" do not turn off target!!!! But it just sits there....I can't do anything on that screen. Is that the "Download Mode"?
I am lost...anyone know how to get me into a download state and successfully re-install a ROM???? $20.00 to the person who gets me back up and running (er, via PayPal).
One other thing: When I plug the phone into my computer, I do not see it in my computer...but it seems to acknowledge parts of the phone. I get the USB plug in sound and get the Driver Software Installation which says:
SAMSUNG USB Composite Device Ready to use
SAMSUNG Mobile Modem #2 Ready to use
But again...I don't have access to the phone through the computer.

Any Suggestions?
I am still quasi-bricked...any suggestions on what I should do when I get to that Download splash screen? I can't seem to do anything once I get there.

dinohaven said:
I am still quasi-bricked...any suggestions on what I should do when I get to that Download splash screen? I can't seem to do anything once I get there.
Click to expand...
Click to collapse
dude.
this is why you dont flash anything without understanding what the hell you are doing.
where did you get the rom? the development section?
go there and READ. there is a ONE CLICK ODIN that contains the stock rom. instructions are in that thread....
for crying out loud...when will the stupidity stop?

dinohaven said:
I am still quasi-bricked...any suggestions on what I should do when I get to that Download splash screen? I can't seem to do anything once I get there.
Click to expand...
Click to collapse
Use Odin one click back to stock. Make sure Odin is running first, plug it in, it should show up as COM:# and then click Start and let it do its thing.
Sent from my Captivate

Dude, if you're still having problems PM me and I'll help you out. I don't feel like typing a bunch of instructions if you're already fixed.

Still Not There...
I am not yet fixed (think I am getting closer)...I have downloaded Odin (and drivers) since my last post and tried to run it in Admin mode.
Using: Windows Vista (32bit)
Steps:
1. Plugged in phone to computer (only way to get to "Downloading...Do not turn off target!!!!" screen)
2. Start Odin in Admin Mode
3. Press "Start"
4. System immediately says, "<OSM> All threads completed. (succeed 0 / failed 0)"
That is where I am at the moment...any help will be appreciated.

Alright. I have a lot of experience with this rom stuff I fkashed at least 5 different ones and 2 of them were failed (I deleted the rom off once and didn't worj at all kept vibrating and the other time I unplugged the phone while odin was working)
Start odin3 jh6 (the stock one click odin flasher)
Then take the battery out
Plug in the usb in and hold all three buttons (power and volume up/down)
Put the battery back in and when you put it in take your finger off the power button
Go to odin and hit download
I used this method when I got the connect phone to computer screen a semi brick. Good luck!

And don't listen to all the idiots calling you stupid.... I had no clue what to do either. akl I have to say is google and a night with barely any sleep are always a good thing for putting on roms.

dinohaven said:
I am not yet fixed (think I am getting closer)...I have downloaded Odin (and drivers) since my last post and tried to run it in Admin mode.
Using: Windows Vista (32bit)
Steps:
1. Plugged in phone to computer (only way to get to "Downloading...Do not turn off target!!!!" screen)
2. Start Odin in Admin Mode
3. Press "Start"
4. System immediately says, "<OSM> All threads completed. (succeed 0 / failed 0)"
That is where I am at the moment...any help will be appreciated.
Click to expand...
Click to collapse
and yet you are still doing it backwards.
ODIN has to be running BEFORE you plug in your phone in DOWNLOAD mode...

Suggestion try it on a widows 7 PC. I was having the same problem untill I restore it using my friends windows 7 laptop.
Sent from my SAMSUNG-SGH-I897 using XDA App

Yepper....Odin Helped
WHOO HOO!
Finally worked..thanks to individuals on this board...Goos, Majin & Curti...I owe you a beer so PM me with your PayPal email address...
Odin truly worked...the problem was that I couldn't do it in the order everyone was saying...I HAD to plug the phone into the computer to get to the Download mode for some reason (screwy). I also used this tutorial, which helped even though it is a little out dated...pictures are always good:
http://www.ponack.net/flashing-captivate-stock/
Ultimately, I just turned the phone on and simultaneously plugged it into the USB...
Thanks to everyone that truly helped...I am wiser now...

dinohaven said:
WHOO HOO!
Finally worked..thanks to individuals on this board...Goos, Majin & Curti...I owe you a beer so PM me with your PayPal email address...
Odin truly worked...the problem was that I couldn't do it in the order everyone was saying...I HAD to plug the phone into the computer to get to the Download mode for some reason (screwy). I also used this tutorial, which helped even though it is a little out dated...pictures are always good:
http://www.ponack.net/flashing-captivate-stock/
Ultimately, I just turned the phone on and simultaneously plugged it into the USB...
Thanks to everyone that truly helped...I am wiser now...
Click to expand...
Click to collapse
I'm glad we were able to help. As far as the paypal goes just donate to designgears for me.

curti.nogg said:
I'm glad we were able to help. As far as the paypal goes just donate to designgears for me.
Click to expand...
Click to collapse
Im assuming "goos" is me... anyways glad I can help! If you ever need help again don't be afraid to ask. We got you!
(P.S. good news I don't have a paypal guess what that means! You don't loose any$$$ )
Sent from my SAMSUNG-SGH-I897 using XDA App

Bricked, need help.

So, I bricked my Infuse last night at work when I tried installing MIUI from ROM Manager. I've been trying to unbrick using gtg's Ultimate Unbrick method, but no luck. I believe it's something to do with the Samsung Drivers since my phone is not recognized in Odin. Tried to redownload the Drivers from Samsung's website, but still doesn't work.
Any ideas?
BTW, running Windows 7 32bit

why would you install a rom that's for a different phone?
can you boot into recovery mode? did you try the "jig"?

Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.

the reason other roms pop up in rom manager is because you are using the galaxy recovery. unless it says "for infuse" (there is only one, gtg's rom) it wont work. bummer dude. im all out of ideas, never had this happen. hopefully someone who's been through this can chime in and provide some info that will help you.
on a side note, why cant you take it to an att branch and have them exchange it for you?

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
I hope u have USB debugging turned on. If yes, u cud try this:
1. Download and install android SDK (search google for this if don't know how to).
2. Open a command prompt
3. Type in "adb reboot recovery" without quotes, and don't hit enter
4. Connect phone to PC
5. Turn the phone on
6. Wait for "samsung" to appear, and hit enter in command prompt
7. If it says "device not found", use the up arrow to get the command from history, and hit enter again. At some point, it should issue the command to the device.
8. If u can get to recovery, well, u have a way to now try to flash any other ROM.
Don't give up. Samsung has strong phones that could be got out of soft bricks most of the time.

Delete/reinstall the drivers.
Infuse 4G

Just tried Diablo's method, and it tells me command not recognized...

Download Kies on your pc to have it recognize ur phone. Run odin. Put ur phone in download mode (pull out battery, put it back in, hold both volume buttons down, plug in ur usb) and use gtg's unbrick.
Sent from my SAMSUNG-SGH-I997 using XDA App

Tried Kies before and it would never recognize the Infuse. Should I pick Galaxy?

UPDATE!!
Redownloaded Kies and installed the drivers (for the 500th or so time) and now Odin is recognizing a device. It's showing [COM3] instead of COM## but I'm letting Odin do its thing. Seems to be working... Crossing my fingers!
EDIT::
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
****in A! Thanks for the help guys!

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251

Misterjunky said:
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Click to expand...
Click to collapse
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D

Pat713 said:
Just tried Diablo's method, and it tells me command not recognized...
Click to expand...
Click to collapse
That means u do not have android toolkit installed on ur system. You should install it first for the adb commands to work.
I would recommend downloading and learning the basics of adb. This could be a life saver in many no-so-happy situations.

Pat713 said:
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Click to expand...
Click to collapse
Had this same problem and it turned out to be a hardware problem. There was no gix for it. Also youll notice that gtgs recovery includes a preroot. If you need to send your phonr back like i did youll need to get that off. It was tricky for me because the hardware was so screwey. I got it off after a few reboots of the phone and a couple of trys with superoneclick.
Sent from my SAMSUNG-SGH-I997 using XDA App

Searched/Bibled/Need help w/brick please

I updated to Whitehawkx's Valhalla, and flashed successfully, although when booting I would get a fuzzy/snowy screen.
After reasearching, I found that I needed the GB bootloaders. So, I went to the Bible post, found the "updated bootloader" GB ROM, and attempted to flash it via odin.
Here's where I think I went wrong. I put the phone in download mode. In Odin, which I've used extensively in the past, I checked the "Phone Bootloader Update" checkbox, then attempted to load the PIT, Phone, and CSC files from that GB ROM linked in the Bible post.
It hung.. I let it sit for well over an hour, and it was just stuck on zImage, in the "Message" area of Odin, where it shows progress.
I unplugged the usb, replugged, tried again.. same thing.
I rebooted phone, and it no longer goes into bootmode. I get an active screen, that displays a small handset icon connected to a PC icon, with an orange warning triangle between..
Again, cannot get into download mode, even with every method posted. It always just displays this same graphic.
Since the display is functioning, I assume it is not hard bricked.. but hoping for something to help!
Thanks mucho in advance. I have many hours into trying to recover, before coming to the community with tail between legs.

hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
I wonder if you might need a jig to be able to get it into DL mode again? There is a post about that somewhere, but I can't seem to find it at the moment.

mike-y said:
hmm, I've never checked/unchecked anything in ODIN, I just let it decide on its own (if a box came up checked, I left it).
Click to expand...
Click to collapse
Yeah, as I mentioned, that's where I think I went awry as well. Figured that since I was primarily wanting to replace the bootloader, I should check it. Probably my big downfall though.

Odin should still be able to pick up your phone with that screen. It might take a bunch of tries as well as switching between 1.7 and 1.85. Just keep trying. Flash kg4 then Honks kernel. Should give you cwm access then reflash valhalla

You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App

CozzaFrenzyy said:
You can still odin at that screen. Re install the usb drivers. Also try conecting your usb to a different port and monitor with odin if it picks up the phone. If you have adb installed run adb devices to see if yiur pc recognizes the phone
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.

Bimboy said:
Thanks! That's what I am continuing to do. I cannot get it to be a recognized device, but i think my PCs (tried 3) have messed drivers now, as my wife has an SGS4G, and I cannot even get her phone to be recognized as a device any longer.
Keepin' on though. thanks for the encouragement and ideas.
Click to expand...
Click to collapse
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App

farwek said:
Use a program called usbdeview to uninstall old faulty driver copies assuming that you are on windows. Then when you plug your phone in again it should work just fine after it reinstalls the drivers for the phone. The you should have no problem with your comp recognizing your phone.
My comp did that to me last night and I had to use the same process.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Excellent help, that allowed me to get the phone connected. Appreciate it.
However, I can get Odin to see the device, but do nothing with it. I've tried flashing the KG4 as recommended, then I tried a few others, including going back to KC1.
I can never get past "Setup Connection" in the log, which looks like this:
Code:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
So, I'm connecting, starting the process, getting MD5 validation, and then not connecting. So, I think I am VERY close, but I can't get past this.
Greatly appreciate more thoughts, even if it's unrecoverable. You guys have got me this far, and I appreciate it.

I had this happen the other day and had to go back to KC1 "fix", found here.
That link 3/4 of the way down on the first post will give you like 3 or 4 files to put in odin. Before you try it restart your comp and phone. Good luck!

Hey golmar.... ... Did you use your own bible thread to find that link?

FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
List of dangerous ODIN stuffs.
1. Repartion with wrong pit(wrong means never able to boot again even with bootloader fix)
2. Check "bootloader update"
3. "EFS clear"
4. Put a file with bootloaders in the "bootloader" section. You have to put it in PDA.
5. flash wrong bootloaders. ( you can unbrick using a few methods)
6. flash the wrong rom.

airfluip1 said:
FB, your are quite funny! Anyway, you should have never checked "phone bootloader update", that is probably the second most dangerous thing you can do in ODIN.
Click to expand...
Click to collapse
Yes, I knew it, as soon as I did it, as I stated.
I got it to start to flash, and then hang.. for hours. I saw probably 5mm of a progress bar on the phone. From there, I can now go into download mode via battery pull/usb/volumes/battery insert. However, I can never get past "Setup Connection.." in ODIN.
Luckily, I have had a work holiday to day to "labor" over this less-then-optimal situation. Still nada though. I continue to get messed up drivers, and when I get the correct ones loaded, I only get to "Setup Connection..." on the ODIN flash.
Over the years, I've gotten into many "close to paperweight" situations, when cooking early WM ROMs. I've never been this deep in time to recover.. without results.

You must use heimdall to insure optimum results, also there is a different driver. Just follow my post on heimdall. It is in the development section. Also, I would suggest using version 1.1.1 instead of 1.3.x or whatever. It should be on the heimdall site. Just google it. All the archived versions are still there. 1.1.1 is easier, as it has a more easy to use GUI for some people and you don't need to use a pit file. Primary boot loader is boot.bin and secondary boot loader is sbl.bin. Make sure you have C++ 2010 redistributables on your computer and navigate to the "drivers" section in the folder you download. Open zadig, and then go to options and list all devices, you should then see Samsung composite USB or something like that, click install driver, when it is done, just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.

Thanks airfluip1! I'll give it a shot tonight. I already had tried Heindall, from you post, so I have it all downloaded already (1.1.1), along w/C++.

airfluip1 said:
... just use heimdall. It may fail giving you a message like failed to find phone or failed to retrieve config descriptor or something like that. just force off your phone and put it back into the computer and if you get to the phone ---> computer screen, you should be fine.
Click to expand...
Click to collapse
Well, with Heimdall, I get consistent, replicatable failures. I can flash the primary bootloader, but it always fails at 20% on the secondary bootloader (even tried the "backup secondary bootloader" flash with the same result:
Code:
c:\heimdall>heimdall flash --primary-boot boot.bin --secondary-boot-backup sbl.b
in
Heimdall, Copyright (c) 2010, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Claiming interface... Success
Setting up interface... Success
Beginning session...
Handshaking with Loke... Success
Uploading primary bootloader
100%
Primary bootloader upload successful
Uploading backup secondary bootloader
20%
Failed to send file part packet!
Backup secondary bootloader upload failed!
For some reason, it will not let me flash it.. So close, I can taste it. FWIW, MD5 checks fine on the SBL file. Also, I started with the heimdall_frontend, but prefer the feedback the commandline offers.

Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App

Light-라이트 said:
Im not a pro at this. But if youve been doing.it with the pit file included, try without the pit file. Worked for me. :x.
P.s. The kg4 files.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Thanks! That was something I tried immediately. I may be looking at something I need a jig for. I wonder if partitioning got hosed, and it is not allowing me to write to disk, where it thinks it should be. Also, not sure if it is worth my time, compared to buying the next latest and greatest. Kind of a good news/bad news scenario.

Just wanted to thank everyone for this thread... I ran into the same problem as the OP did when I tried flashing Valhalla.... Somehow I manged to completely overlook the giant red bold message about needing the GB bootloader. So, I got the boot loop and the fuzzy screen mentioned, but what I did was go into download mode and Odin flashed Krylon's stock+root per this extremely detailed tutorial.
Tomorrow I'll probably entertain flashing up to GB, but for now I'm just glad not to be bricked....

Try this DL mode method
Get the KG4 leak and load it into Odin.
Leave everything as-is (including re-partition).
Pull the battery from your phone.
Plug the phone into the PC.
Hold Vol+Up and VOL+Down while connecting the battery.
Once Odin picks your phone up, hit start.
You *really* shouldn't have any problems at that point. I've encountered the exact same issue, and entering DL mode using this method worked for me.
Once your phone is up and going on KG4, use Odin again to flash Valhalla, and you're good to go
[ROM-Leak][ODIN] Gingerbread 2.3.4 T959VUVKG4

Thank you! This thread saved my bacon. I had the snow after a failed Heimdall. Odin 1.7 and a different USB port enabled me to get back.

[Q] Serenity KK4 questions

So i have been looking through the pages, and cannot find anything pertaining to what i am looking for. I am new to ROM's and i cant find a explanation on how to install it, or flash it rather. I saw the part that said installation which has:
- Make sure you're on Gingerbread I897 Bootloaders
- If you are on EXT4, convert back to RFS (disable lagfix)
- Flash a CWM KK4 kernel
- Flash serenity zip file
- First boot takes some time
My phone is a Captivate rooted, and have tried installing roms with ROM manager, to no success because it says to reboot into ClockworkRecovery, but i have followed every instruction in the book to get to CWR but it still takes me to the stock recovery menu.
I have been at this for about two weeks looking at forums and everything to figure out how to do it on my own, but i really have given up because i have no clue.
Thanks in advanced for any advice.

So rooted & stock? Some thoughts
You need Samsung usb drivers.
adb for PC command line controls:
http://www.xda-developers.com/android/adb-easy-tutorial/
In Settings>Applications>Development toggle USB debugging on.
Use ODIN [1.85] once you put it in Download mode:
http://forum.xda-developers.com/showthread.php?t=1365805
Download mode: use adb command: adb reboot download
Bootloaders via ODIN [has its own odin copy]:
http://forum.xda-developers.com/showthread.php?t=1129821
Flash a tar of Corn 6.0.3 kernel via ODIN. This comes with its own CWM version:
http://forum.xda-developers.com/showthread.php?t=1294477
Always have a way to get back to stock if things go wrong:
http://rum.xda-developers.com/showthread.php?t=731989

Ok, so got it into download mode.
I open ODIN, but im not exactly sure what to do from there, so i tried opening ODIN then using the bootloaders.
I ran the bootloader program, went through that, it said:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
dont know if im doing something out of order, but clicking start in ODIN itself doesnt do anything.
Thanks in advanced!

Buckli39 said:
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
sequence:
1.Run the Odin with built in bootloader code.
2. Phone in DL mode
3. Attach to USB. Odin will then get a yellow box indicating some com port.
Yellow com port box or it will do nothing! Perhaps you ran Odin with the phone already in DL mode & usb connected?
Sequence matters: If you used adb to get into DL then with Odin already open it should recognize it [20 seconds?]. I use a jig from MobileTechVideos $7 to get into DL, only then I usb connect to PC with Odin already running/waiting. Using adb is functionally equivalent. As the phone reboots it is not actually "connected". Once the reboot to DL happens the connection to PC is restored.
My Odin/Bootloader one-click program reports: " <ID:0/012> Added " with a yellow box with " 0:[COM12] "
4. choose Start. A green bar progress will indicate the 'progress'. It will reboot the phone.
5. You can close Odin after the "all thread completed", it will indicate a reset. Safest to wait for the reset/reboot.
It should have read: <OSM> All threads completed. (succeed 1 / failed 0)
This is just as directed on the link to the Bootloader one-click program [odin variant]
You only need the basic Odin[1.85] when flashing the Corn 6.03 tar file. In theory if one had the tar file for the bootloaders one could use the basic Odin for it, but here the bootloaders are already packaged in with an Odin executable.

okay, so i did exactly the sequence you told me, run odin/bootloader, phone into DL, then connect to usb.
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!". i go back into DL mode and it says its disconnected ( i also waited 20 min just to make sure it didnt come back as added )
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.

Buckli39 said:
I do not get the yellow com port until after i turn my phone off, out of DL mode, and back into reg mode. then it recognized it and says "Added!".
And you had said "Once the reboot to DL happens the connection to PC is restored." it is exactly the opposite, once it reboots to DL the connection seems to be severed.
If i hit start when it is present and not in DL mode but has the yellow com, it just fails anyway.
Click to expand...
Click to collapse
Connecting when in Normal use mode will always have Odin responding Yellow/ComPort. And yes Start will do nothing unless in DL.
I tested my sequence. Odin/Bootloaders running, PC: adb reboot download, and it did fine giving YellowBox/ComPort. Never usb disconnecting physically, only functionally as it reboots. So I dont know. I do know that sometime DL mode goes stale. Phone unresponsive if one does not take fairly prompt action. That is I cannot put in DL and put aside for 5min. If I had to do this then I would need reboot into DL again.
For the Kernel you can transfer the Corn6.03 [zip CWM version] file to some directory in the internal SD card [ not the one inserted by "you"]
Then you could use "adb reboot recovery" but the stock recovery is very limited, and it wont let you flash the kernel in recovery. Unless you first save a CWMR 3 file as update.zip on the internal sd. This was how you rooted? There is some reason stock recovery forces you to do the flash from update twice, the second time puts you in the CMW3 program[green menu, no longer blue?] where you can then flash the kernel. Look for old links/threads to the old CWM zip file.
Let me get back to you on the BLs & perhaps a link to the old CWM3.

i will keep on trying to get the DL mode to be connected, and I rooted via the super one click root program, was told it would be the easiest and fastest way
Okay so i was digging around and found some reasons why it wasnt reading my device, and i got it. i got odin to flash the file, waiting for it to start my phone back on, atm it is stuck on the att screen. i shall wait a bit and report

okay i have let it attempt to reboot by itself for about 20 minutes, all it is doing is loading to the att screen, staying there for a sec, then the screen goes black, the the att screen pops up again.. it has just been repeating that since my last post

so something messed up. i wanted functionality until you could help me out, so i was doing the last link you sent me to restore it to stock. Did that, and now it wont even turn on or get into DL mode, the only thing i can get onto the phone is:
RST_STAT =0x1
PMIC_IRQ1 =0x3c
PMIC_IRQ2 =0x0
PMIC_IRQ3 =0x0
PMIC_IRQ4 =0x0
PMIC_STATUS1 =0xc0
PMIC_STATUS2 =0x2c
Moden booting...
End modem booting.
Now start usb upload.
*
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom

Buckli39 said:
...
okay maybe i should wait to post, i finally got it into DL mode and installed stock rom
Click to expand...
Click to collapse
DL mode can get scary. So many threads warn the user "I'm not responsible for your bricking your phone". Early on I spent a couple of days stuck, "soft bricked". Here too I only tell you what has worked and still works for me.
As you used the link/thread for flashing to stock that I listed perhaps you will have an easier time now.
Then select Settings >> Applications >> Development and tick "on" USB debugging [must disconnect usb cable first]
Now perhaps you can do the Odin work. I looked for where [link/thread] I had found it to no avail so I attach BLs and what I use for CWM3 and rooting. Until now I had preferred passing a thread where you could use others vetted sharing, rather than 'just my copies' of these. BL file can be used in normal Odin. The other two should be named update.zip and placed in the internal SD and flashed in Recovery. [adb reboot recovery].
On to Corn6.3 [CWM safer?] and Serenity 6.0 and subsequent & extras in Recovery.

Help! My tab is bricked, cannot be started. [New Thread]

Ok guys, long story short, here are the symptoms:
1) Still shows charging status.
2) Can enter download mode ONLY after being charged and the charging status is shown even for a short duration. Else, it will not react to any button I push.
3) Cannot enter recovery mode.
4) Somehow I can boot up to the SGT-2 logo which is rare. (I tried to start more than hundred times).
5) While in download mode, my PC wont discover the tab. In other PC, it simply says "device descriptor request failed". Which is code 43.
What I've tried:
1) Heimdall
2) Changing USB (3 times)
3) Different PC (2 times)
4) Removed the battery and put it back
5) Kies and drivers of all sorts I found on forums.
6) Swearing and threatening to kill the tab (numerous times)
I really need assistance. I maybe need to bring it to the service centre, however it will be very costing I presume. So does anyone have ever encountered the same problem as mine or know how to solve it? Please and thanks.

try odin ...
kukuru said:
Ok guys, long story short, here are the symptoms:
1) Still shows charging status.
2) Can enter download mode ONLY after being charged and the charging status is shown even for a short duration. Else, it will not react to any button I push.
3) Cannot enter recovery mode.
4) Somehow I can boot up to the SGT-2 logo which is rare. (I tried to start more than hundred times).
5) While in download mode, my PC wont discover the tab. In other PC, it simply says "device descriptor request failed". Which is code 43.
What I've tried:
1) Heimdall
2) Changing USB (3 times)
3) Different PC (2 times)
4) Removed the battery and put it back
5) Kies and drivers of all sorts I found on forums.
6) Swearing and threatening to kill the tab (numerous times)
I really need assistance. I maybe need to bring it to the service centre, however it will be very costing I presume. So does anyone have ever encountered the same problem as mine or know how to solve it? Please and thanks.
Click to expand...
Click to collapse
if u cannot go to recovery ,well it may be a problem which you need to show in service centre.
the problem you have occurs often if you messed up with the bootloader or the kernel.
so if u want to solve this problem in your device the only way is flashing the md5 file for your device aka the flashing of stock Rom without using recovery.
so the following are the steps you need to do .
1.go to sam mobile site(this only my 3rd post so i cannot add link)
in that site search for your device and download the md5 file.
2. install odin in your pc .(it is an application for windows,search on google or xda you can get the link.
3. you are lucky that you can go to the download mode. So you can charge your device and and go into the download mode.
4. now in odin app in your pc you should open the app.
5.connect your device to your pc
6. dont cahnge anything except you just click on pda in the app and select the md5 file you downloaded before.
and click start.
7.it will take some time .
HURRAY! YOU HAVE SUCCESFULLY SOLVED THE PROBLEM OF YOUR DEVICE.
If you are stuck in the samsung boot logo after this process try going to recovery mode and do a factory reset.
if this does not work please ask me.