CWM installation on Odin hanging EDIT: Fixed - Fascinate Android Development

Have appropriate drivers installed. Odin recognizes the phone in download mode on COM3. Run .tar file from PDA box. Process hangs at step 4, initialization... Have left it for as long as thirty minutes, but it never advances or fails unless I unplug the phone. I may have done something very wrong, because it seems to be bricked, now. Phone -!- computer screen when I try to boot up. Can I still salvage the cwm installation somehow, or do I have to use angel's restore? I'm in the process of downloading the .md5 file, just in case. Thanks
EDIT: tried with a different cable and it ran through in 10 seconds! Sorry for asking a dumb question.

Related

Please Help

I was trying to install the stock rom via rom manager and once I got past the galaxy logo after the reboot from recovery when it was applying the update Im stuck with a black screen and the 4 bottons just stay lit up. I tried to flash the stock rom via odin from this video http://www.youtube.com/watch?v=AnY7P14JSWQ but when I put in my device I dont think odin recogonizes the device. The ID:COM box stays empty and when I press start it just says threads complete ( succeeded: 0 / failed:0 ) can anyone please help with how to resolve this issue.
Are the proper Samsung drivers installed? You have to get your phone into download mode, if Odin doesn't detect your phone.. unplug the cable and replug it. Does it detect it there?
I googled samsung usb drivers and downloaded it forget the website and I tried to unplug and plug back in but nothing.
It should be this: http://forum.xda-developers.com/showthread.php?t=728929&highlight=Samsung
installing
first get your phone into download mode. Is adb working? if so power on phone and open adb and type:
adb shell
su
reboot download
once in download mode unhook phone from laptop and
1. Open Odin and set PIT & PDA
2. attach phone back to laptop/pc
3. you should then be able to enter a com port
4. hit start and reflash
I never downloaded adb is it too late for my situation?
superevo89 said:
I never downloaded adb is it too late for my situation?
Click to expand...
Click to collapse
You don't need ADB to use Odin. You need to get INTO download mode as I mentioned in my previous post.
Download mode appears a yellow android digging on your screen.
I am in download mode and the box in odin ID:COM is still empty multiple tries and nothing
superevo89 said:
I am in download mode and the box in odin ID:COM is still empty multiple tries and nothing
Click to expand...
Click to collapse
Then you need to uninstall the drivers you installed to the ones I've linked. The ones I link are the ones that 100.00% works, it works fine for me. Download respective to your OS x86 or x64. Then restart.
FINALLY odin sees it
superevo89 said:
FINALLY odin sees it
Click to expand...
Click to collapse
Did you reinstall the drivers with the ones I linked or did something spectacular happen?
I guess I clicked the wrong download link but it was from the one you linked but right now its at cache.rfs for the past 2 minutes it that normal or is something wrong
superevo89 said:
I guess I clicked the wrong download link but it was from the one you linked but right now its at cache.rfs for the past 2 minutes it that normal or is something wrong
Click to expand...
Click to collapse
Be patient for a little while. Mines only took <1 minute though. What I changed was that.. I would open Odin and pre-set all the files that I'm going to use in Odin and THEN i plugged in my phone then once it was detected by Odin I would just press start.
If i didn't do that, it would be stuck and I'd panic but I pulled out the battery and rewent into download mode. There should be a progress bar that comes up on your phone when it starts. Screen shouldn't turn black.
its still at cache.rfs and nothing changed on my phone still shows the same download screen
superevo89 said:
its still at cache.rfs and nothing changed on my phone still shows the same download screen
Click to expand...
Click to collapse
Give it 10-15 minutes just incase. If it is still stuck, pull the cable out then battery out (pull battery door first). Then redo the process but put the .tar files etc that you're putting before you plug the phone in.
did as you said and nwo I see the progress bar on my phone.
YAY! thank so much for the help and quick replies my phone is back to life now I feel so much more at ease will be confident the next time I have a accident flashing my phone or doing any kind of modifications.
edit: I think I lost my titanium back up so is my phone still rooted or do I have to re-root
hooray! you're welcome. just be sure to do nandroid backups before you apply hacks, at least now you have the tools to perform flashing with odin so next time it'll be easier
titanium said it couldnt get root permissions I had the OCLF did re flashing the stock rom from odin undo everything the lag fix did?

[Q] No download mode?

I recently used Odin to update to froyo 2.2 from my eclair 2.1, and it "pass"ed but now my phone goes into recovery mode. Boot screen then recovery, even when its off and begins charging goes straight to recovery.
At recovery it says:
"update media, please wait
E: Cant mount /dev/block/mmcblk0p1
(Invalid argument)
E;copy_dbdata_media: Cant mount SDCARD:
your storage not prepared yet. please usee UI menu for format and reboot"
But UI menu doesnt work, doesnt let me select anything, and download mode wont load so Odin gets stuck at "Setup Connection".
Help?
Thanks!
- try different versions of Odin's this is the most common issue.
- Make sure your using the correct Eclair 2.1 files the ones by Eugene the unbrickable one.
Mostly, try a different ODIN, and the one that works, don't switch from it.
Odin is the only thing keeping my phone good as new, and i dont need any updates on that.
xrider is correct, I would recommend the 1.7 Odin. You can then Odin back by first flashing Eugenes Froyo that does not brick, then back to JFD2.1
you can get all you need in the Stickies
From there you can root and then flash away
good luck,
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Dark619Cloud said:
Thanks for the replys.
But for Odin to work, wouldn't the device need to be in Download Mode? Which would explain why it doesn't go beyond "SetupConnection". I used the same Eclair rom as I did for my previous recovery. But it fails now, I also tried different versions of Odin from 1.0 to 1.7. Oh an Odin recognizes my phone as a COM6, if that means anything.
I might just go ahead and call Tmo and get a new one. I still have insurance and a warranty.
Hmmm...
Click to expand...
Click to collapse
Wait, if you can't get into Download mode, then how are you getting COM6 on ODIN?
I have no idea. Phone just sits in recovery, I plug in USB and it says
<ID:0/006> Added!!
But when I try flashing anything, it stays at SetupConnection.
When I WAS able to get into download mode, it was COM8.
Wait for more replies, idk the solution. Sorry
Maybe new version of odin?
I really appreciate your help though.
I think it's just bricked. The froyo which I had updated to was probably faulty, causing this to occur. I mean, even the recovery menu is messed up. Up and down are inverted, and power button does nothing. Phone doesn't show charging screen(well it does for a second then go straight to recovery).
I'll just call T-mobile tomorrow. I wouldn't get charged right? I tried updating to THEIR firmware, had they made it OTA this wouldn't have occurred, right?
The fact it sees com 6 or com8 or com 4 really isn't important, sometime mine say com2 sometimes it say 6......... this is unimportant.
Follow this ...this should work, the only other thing I can think of is to get into factory recovery and wipe, cache, and memory, go into advanced and wipe the dalvik, then back to Odin and perform the following:
1. Odin 1.3 or higher I use 1.7 but not real important
2. Have the original JFD Vibrant rom
3. You will need the .pit file (this is for mapping)
4. You will Eugene froyo that does not brick rom.
The order is as follows:
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! You will have flashed back to the original software. From there, you can do anything !!!
Next root the phone if you are confused about this go to youtube and look up the video by unlocker.com they do a great job showing how it is done.
After all this you can now flash a new rom.
The reason he's getting a COM port without being in D/L mode is because of the secondary bootloader in the sbl.bin. You may just be able to flash JI6.tar without a pit file and get past the Setup Connection
Whoa, nice feedback.
Downloading both Eugenes "Froyo that does not brick" and the JI6.tar.
Will try both methods and reedit my post.
Thanks a lot.
I can't press "Thanks" more than 5 times a day...
UPDATE:
Eh still nothing...Odin gets stuck at SetupConnection.
I believe this will persist until I find a way into download mode. Odin recognizes phone, hence the COM6, but doesn't fully connect since it does not go beyond SetupConnection. The recovery menu also isn't functioning properly, since I can't select anything.
Losing patience with this phone...
I called T-mobile and their sending in a new one.
Told them I was updating and this happened. Do you think I'll get charged?
Well, while you still got time with it...try a different version of ODIN and see if that works... 1.0, 1.3 or 1.7 dunno if there are more
All three versions get stuck at SetupConnection.
I looked into making a JIG, but I only have one USB cord and don't wanna go through the hassle. A JIG would put my phone into download mode, right? Even though it's not really bricked, just completely messed up.
Just now I was messing around with phone, and I got to a different screen!
RST_STAT = 0x1
PMIC_IRQ1 = 0x0
(and some other stuff like that)
Then " POWER RESET OR UNKOWN UPLOAD MODE"
It shows up as COM7 in ODIN But still stuck at SetupCOnnection...grrr
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Dark619Cloud said:
I FIXED IT.
I got the android SDK, and did "adb reboot" which rebooted the phone, and I have froyo and everything.
But ONE problem. T-mobile is sending me a new phone already....what the hell do I do? I can't send this one in, because it's working now.
Nevermind, everytime I rebooted phone it stayed in recovery and I had to always do "adb reboot".
So I did abd reboot download which took me into download mode, but ODIN still stayed at SetupConnection, i took out battery, now I have the indigenous PHONE ! PC error.
NOW I HAVE NO POSSIBLE WAY TO GET INTO DOWNLOAD MODE, Nor have adb connect to phone. No devices are shown when I do "adb devices".
I also tried every variation to get into DL mode, USB, VOl +/-, Battery...etc. Now I think the phone is completely bricked, honestly.
Click to expand...
Click to collapse
if you look at ODIN while you plug the phone in with that screen you'll notice it giving you a COM port....weird...but you can still ODIN the phone while on that screen. Flash back to JFD from there.
Yeah I know ODIN should recognize it, because it happened before and it did. But this time it's not. I tried different versions of ODIN as well.
tsk tsk ;P lol
u fixed it? or it remains broken ?
I did fix it, partially. It loaded and everything, but sound wasn't working, and volume rocker was inverted, I guess the rom I flashed was corrupted. So I did "adb reboot download" which took me to download mode to go back to JFD stock, and I did ODIN and everything but it stayed at SetupConnection again. I removed battery to put in download mode manually, and now it's bricked. PHONE /!\ PC. PC doesn't recognize it, and I tried every combo to get into download mode.
So no, it's not fixed.

Phone stuck on Phone-!-Computer screen.

So, I just got my phone back from Samsung for this issue. Start my newly returned phone up, it's running 2.2. I turn it off, hold volume buttons and plug in my USB cable - I get download mode instantly. I start up Odin 1.7, select the files and click start.
Nothing happens. Hangs up SetupConnection. I unplug the battery, then the USB cable, plug everything back in and I'm back at square one with this ****ing screen.
Last time I tried every single ****ing button combination posted on this website. I know my phone isn't hardware locked because I've never had a problem getting in to Download Mode before. Hell, I'd never had a problem with Odin not working properly before. What the hell is wrong? I have all the proper drivers installed. Why is this happening?
Now, Odin still sees my phone when I plug it in. If I click Start, sometimes it hangs on SetupConnection, sometimes it hangs on Initialization. I've read that you should still be able to flash while on this screen? Is this true? Either way, I think I'm ****ed again. Any help?
Also, I've read that maybe a jig will help get me in to download mode? Where can I buy a jig from?
you can go to stock jfd from that screen, it acts like download mode.
Once on jfd, download mode will work fine.
try the files in my going back to stock... also make sure to remove any other usb components (they can cause odin to hang).
I love you.
Something must be wrong with the files on my desktop, or perhaps the other USB cable I'm using is ****ed.
This is a bit embarrassing. For some reason I can't get root. I can get in to recovery and select reinstall packages, but every time it boots right back in to the OS. Any hints? Never had this issue before.
EDIT: So it looks like I have Superuser installed but since I can't get into Clockwork I can't flash any roms. What's going on? I can't find any other links where people couldn't get in to Clockwork.
EDIT2: Well, I installed ROM Manager and used it to "flash" CWM. Reinstall Packages worked this time it seems. Weird. Anyway, thanks for the help!
Cool, glad you were able to get it all sorted.

[Q] Endlessly boot loop...

So this phone is really frustrating me...
I tried this method:
http://forum.xda-developers.com/showthread.php?t=849028
I think I make all the step correctly.
1. Installed drivers on my pc.
2. Downloaded 3 files: ODIN, PIT and PDA.
3. Put the Vibrant on Download mode.
4. ODIN detected it, I selected the 2 files... I tried with RePartition check and uncheck...
5. Then hit start, everything runs fine and ODIN indicate PASS.
But... Still boot looping...
When I boot to recovery I have the original recovery (2e).
Can someone help me please? Im really frustrated.
All of this begin because I made a mistake and used a Samsung Galaxy S 4G rom to flash it using ODIN...
I know it has solution because its boot looping.
Best regards,
Omar
I'll link you to some files that may do a better job. I can't tell for sure if you're actually using the right files to flash your phone back to stock or not. Chances are, you're not. Check your messages, and I'll link you to the files in my Dropbox to download.
can you show links here or link me as well. I am having the same problem and i have tried flashing a whole bunch of vibrant roms/kernels but cant stop the phone from boot looping. Thank you.
I would also like to get these files, having the same problem and tried the same methods to fix it and nothing...
Once you got to the point to boot up, did wipe Dalvik, cache and reset first and then try to boot? This is ususally the reason for bootloops.
For some reason I can't get into recovery (holding the 3 buttons) now... I can get to download mode, though.
This phone was bricked and could restore the bootloader with a Riff Box. Now, after the Vibrant screen, the phone turns off.

[Q] Bricks on reboot!

Hey everybody. I bought a fascinate from CL, which was soft-bricked, thinking I could fix it. Guy told me it froze updating to 2.3. It had been stock the whole time. Phone would not boot at all, no display, only four bottom buttons would light up on touch. No dl mode, recovery, or anything.
Odin somehow would still recognize the phone (comm port turns yellow) but fails during flashing of modem. I tried all stock .tar packages with atlas pit too. I tried to flash superclean with no modem, Odin said success, but phone did not do anything.
Now, I moved on to Heimdall to flash. I successfully flashed stock 2.2. When reboot command was sent, I heard the verizon startup sound, but still nothing on display. I waited a little until the phone vibrated when touchwiz force closed. Then, I locked/unlocked screen with power button and the display came back! Yay, I thought until I saw no internal storage, cannot install app, blah, blah.
Now, every time I turn off the phone, it returns to bricked state. Odin still fails, only Heimdall one click unbrick can successfully restart the phone, but again the display is off until it finishes loading and i can lock/unlock the screen.
Sooo, am I just stuck with no internal storage and cannot ever turn it off or does anyone have another suggestion? Thanks for hanging in there and reading all of this too.
So it seems that the phone powers on into dl mode, maybe? The screen is blank but Odin will see it when I plug it in the computer. This is no key combos or usb, just power button.
It also connects right back to Odin if the flash says success. The phone will reboot (I guess, no display), then Odin beeps and com port added again.
Sorry for double post, just thought that was weird.
BYOBret said:
So it seems that the phone powers on into dl mode, maybe? The screen is blank but Odin will see it when I plug it in the computer. This is no key combos or usb, just power button.
It also connects right back to Odin if the flash says success. The phone will reboot (I guess, no display), then Odin beeps and com port added again.
Sorry for double post, just thought that was weird.
Click to expand...
Click to collapse
follow the steps in section 5 of my guide in general section.
I was using your guide from the beginning. I tried both the Froyo and Gingerbread but Odin fails at the modem.bin every time.
Tried all usb ports, reinstalled drivers, rebooted computer...
The heimdall one click is the only thing that kind of works. Are there any other heimdall packages to try?

Categories

Resources