Related
I have a Samsung Captivate and was able to sim unlock nd then root everything was running great, but because i wanted to change the rom and get rid of the AT&T bloatware I decided to install SRE rom from this site but first i had to install rom manager from the market, & install Clockwork Mod which i did so far so good. I go ahead watch the video follow it step by step except i didn't wipe data then install rom. So i decided to kinda start over i booted into recovery wiped data then attempted to install SRE rom again and that's when all hell broke loose phone freezing up on the home screen, not completing its boot process, rebooting by itself, i tried removing Sim card, Microsd, but still not allowing me to reboot into recovery with the key combo or ne other way for that matter. I then tried odin one click to reinstall factory everything but no luck. Sorry for the long story just trying to put it all out there. O yeah i'm a newb incase you couldn't tell. I don't have insurance to try to return to at&t. Thank you in advance for any and all help you may provide.
one_cam_vtec said:
I have a Samsung Captivate and was able to sim unlock nd then root everything was running great, but because i wanted to change the rom and get rid of the AT&T bloatware I decided to install SRE rom from this site but first i had to install rom manager from the market, & install Clockwork Mod which i did so far so good. I go ahead watch the video follow it step by step except i didn't wipe data then install rom. So i decided to kinda start over i booted into recovery wiped data then attempted to install SRE rom again and that's when all hell broke loose phone freezing up on the home screen, not completing its boot process, rebooting by itself, i tried removing Sim card, Microsd, but still not allowing me to reboot into recovery with the key combo or ne other way for that matter. I then tried odin one click to reinstall factory everything but no luck. Sorry for the long story just trying to put it all out there. O yeah i'm a newb incase you couldn't tell. I don't have insurance to try to return to at&t. Thank you in advance for any and all help you may provide.
Click to expand...
Click to collapse
try getting your phone into download mode. If you can do that then use odin to flash everything to stock.
Are you able to get adb to access the phone? You can access recovery from there with the following command:
Code:
adb reboot recovery
Also, are you getting into download mode when trying Odin 1-click? I've found a pretty fool-proof method pull battery/SIM/SD, putting the battery in, holding down the two volume buttons and then plugging in the USB. Works every time for me, and is easier than it sounds.
I was stuck on a boot loop the other night and that process got me into download mode so I could flash with Odin and then restore my backup.
Worst comes to worst, just bring it to AT&T and say it randomly did that. If it's only two days old, and you're under contract (didn't buy it outright) you don't need insurance. I don't even think insurance is available for this phone.
take out the battery, plug in the usb, put the battery back in, hold both volume buttons down, then hold the power button down... the grey/green battery icon will flash to a black screen, as soon as it flashes to the black screen the second time, let the power button go, and download mode should be there.
@rrrrrramos i do not have a contract with them. I obtained this phone through a friend that does have insurance for the handset. Since my computer does not recognize it i am not able to adb.
@magnumrt62 & rrrrramos I have tried these button, usb combos and nothing. I appreciate all the responses i will con't to try and seek psychiatric help...lol.
How would i know i am in dl mode? All it does when i let go of the power button after the second blk screen is nothing but show green battery nd con't to charge then goes to black screen. Computer doesn't recognize it.
Are you using the SRE with voodoo in it, if so that is not playing nice with ROM Manager, it is a known issue that Clockwork Mod dosen't recognize ext4. Sounds like that may be the issue. read this thread http://forum.xda-developers.com/showthread.php?t=784170
It sound like that is the problem.
I am unable to mount/unmount the internal/external sd cards because the phone freezes and does not allow for this. The few times i was able to get odin to recognize phone com3 i hit masterclear left it alone and 6hrs later it had done nothing. I can't even get into recovery mode. I am about to see if this beautiful phone will fly then bounce... O how a grown man wants to cry over his phone... LMAO... Can ne 1 close to orlando, kissimme, poincianna help a fellow Captivate lover out i got beer money, gas money, i'll drive too you. hell i'll even cook a new york strip or two.. HELP ME PLEASE..
To do master clear your have to be in usb debug mode and at the home screen. Fire up odin then plug the phone in odin will see the phone and then hit master clear. It will then wipe the phone
Sent from my Samsung Captivate w/Voodoo using XDA App
Thats where the phone freezes up at on the home screen and just stays stuck there. The last time I was able to get into the phone i switched on usb debugging but still nothing. I just booted up the phone and heard the sweet bing sound but still doesn't show up.. I really appreciate every1 taking time out to try to help me.. Just wanted to put that out there..
So am i one of the unfortunate souls to have "BRICKED" his phone. I will not give up yet.. As long as i see the sweet "S" i will not give up..
I don't think you bricked it. Something is going on with your drivers, if the computer won't recognize it. Obviously your phone has been able to boot into recovery before if you had ClockworkMod on it. Did you get into Recovery using the key combo?
I have not been able to get into recovery using any key combo. Right know i am actually in Android System Recovery by using adb reboot recovery and a lil luck and speed. It is recognized by odin3 0:[com3] but it will not do any thing. I clicked master clear and it states master clear started but that was 53 minutes ago.
You need to use the odin from here: http://forum.xda-developers.com/showthread.php?t=731989 as it is made to specifically use with the captivate. It also includes the jf6 kernael which is critical. I used method 3 for the I-9000 because SRE 1.3 put that kernel on the phone and screwed it up big time, it has different hardware assignments. When you put the battery in, hold volume up and down and plug in the usb, no sim, no external sd when doing this. No other version of odin worded for me, just this one. You can't do a master clear until you are fully booted, I don't care what anyone says, it will never work, besides, you don't need to. You need to hit the "Start" button in odin when it show that you're connected. It will reflash you phone with the proper rom and kernel.
Don't download anything else from there but the odin file, you have the drivers already and don't need the other kernels (what got you here to begin with ). just that version of odin that already has what you need.
Good luck man!
one_cam_vtec said:
I have not been able to get into recovery using any key combo. Right know i am actually in Android System Recovery by using adb reboot recovery and a lil luck and speed. It is recognized by odin3 0:[com3] but it will not do any thing. I clicked master clear and it states master clear started but that was 53 minutes ago.
Click to expand...
Click to collapse
It's great that you can get into recovery mode through adb because that means you can get into download mode: adb reboot download. Then you can flash back to stock with odin.
Also forget about recovery. That's not going to help you right now. You need to be in download mode to use Odin
I'm going to give that a shot when i get home. Why didn't I think about adb reboot download wow guess you can tell i'm a real NEWB.. Thanks i'll let u know how it works out for me..
one_cam_vtec said:
I have not been able to get into recovery using any key combo. Right know i am actually in Android System Recovery by using adb reboot recovery and a lil luck and speed. It is recognized by odin3 0:[com3] but it will not do any thing. I clicked master clear and it states master clear started but that was 53 minutes ago.
Click to expand...
Click to collapse
What is it that you don't understand. Master clear only works when you are at the home screen. You can't evoke it from download mode or recovery. You have to have your phone recognized by odin when you are at your home screen and then you can hit master clear. That is the only way that it will work.
It sounds like adb works so when you are at the home screen and you envoke adb reboot recovery it reboots the phone into recovery correct. If that is working then there should be no reason master clear won't work then. Boot the phone up normally and then run odin 1 click then plug the phone in if odin recognizes the phone then hit master clear and see what it does. It should work.
@ Everyone who suggested things for me to try THANK YOU. I finally got it with the adb reboot download. Didn't know i could do that. @Sparker366 I would envoke adb b4 it got to the home screen as soon as odin recognized it i would envoke commands, because the phone would freeze on me on the home screen Just didn't know about the "download" command. Thanks again every1...
TL;DR - Stuck in boot loop, can't enter recovery mode, but can enter download mode. Odin says it is successful, but the phone is still in the boot loop.
I've had Cognition 2.3 for a few months now and decided to update to Cognition 4.3. I used the AIO toolbox 2.5 to Odin one-click back to stock, rooted, and flashed to 4.3. Everything went well and I restored all my apps with Titanium and loaded some music.
At some point later the screen was completely blank and the only way I could get any response out of it was to hold the volume buttons and power buttons. Instead of going into recovery, though, it would boot to the Cognition boot screen and hang indefinitely.
I was able to get it into download mode by removing the sim and battery and holding the volume buttons while plugging it into USB and replacing the battery. I ran Odin one-click again, it said it was successful, but the phone was stuck in either a battery screen or AT&T screen boot loop (depending on whether or not it was plugged into USB).
I've tried using regular Odin with both the ROM included with AIO 2.5 (JF6*) and JH2 (from http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36) to no avail. Every time Odin shows that it is successful, but it always ends up in a boot loop with no ability to enter recovery mode.
What can I do? Will getting a jig help me in any way?
*Edited for correct ROM
Use the normal ODIN (v1.7 or v1.8), a full stock JF6 ROM and PIT file. Make sure "repartition" is selected and if possible, do a master clear with ODIN first (though shouldn't be critical.........then start over with Cog 4.3 if that's your ROM of choice (good choice by the way).
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
bharden said:
I tried the JF6 ROM again with the same results (using http://forum.xda-developers.com/showthread.php?t=818439#8802897). It looks like AIO 2.5 used this ROM all along.
I can't master clear because I can't boot past the AT&T screen. The only way for me to get Odin (or Windows for that matter) to recognize the phone is by putting it in download mode. From what I understand you don't master clear from download mode.
Click to expand...
Click to collapse
Are you using the PIT file and selecting repartition?
When I get home today, I will upload the ROM and PIT that I use to flash to stock and see if that helps but you do need to use the PIT and repartion which will only help if you have a FULL copy of JF6 that reloads the bootloaders.
Just out of curiosity, what is your build number?
I am using the PIT and selecting repartition. I've done this every time I've tried Odin (besides when using one-click of course) Is the PDA.tar listed in that link not a full copy of JF6?
My build number is 1008.
May sound crazy, but you could try using a different computer. I ran into a lot of problems using odin on my pc. Switched to laptop (more ram and windows 7 64 bit ) with great success. Also make sure you have the right drivers. Your build# should allow you to use odin one click.
Sent from my GT-I9000 using XDA App
I've actually already tried it from both my PC (Windows 7 x64, 4 GB ram) and my laptop (Windows Vista x86, 2 GB ram). In both cases I used the drivers in the AIO toolbox 2.5 (http://forum.xda-developers.com/showthread.php?t=944418)
Are those the correct ones? If not, could you point me to a resource with the latest drivers? There are quite a few versions floating around and I'm not sure which ones I should be using.
Any other suggestions?
Those should be the correct drivers
Also, make sure odin is completely open before connecting your phone.
That'd all I can think of.
Sent from my GT-I9000 using XDA App
I definitely did that.
Since I'm able to get into download mode, I should be able to un-brick it right? I can't figure out why Odin says it's successful but I still can't boot.
Does anyone else have any ideas?
You may have to give it a few minutes or so as I am uploading now but the link for the PDA and PIT is:
http://dl.dropbox.com/u/24576569/ATT%20ROM%202.1.rar
Try using this version of ODIN:
http://dl.dropbox.com/u/24576569/Odin3%20v1.7.rar
Hope this helps otherwise I am out of ideas except flashing a kernel with a recovery included through ODIN, going into the recovery and formatting and wiping absolutely everything and then reflashing JF6. But try the files I linked first.
Good luck.
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
bharden said:
It's been 30 minutes and the ROM link still isn't up. Is it working?
Also, I'd like to change what I said slightly. When using regular Odin 1.81 it says PASS when it's finished. When using Odin one-click it gets to the point of cache.rfs and then says removed. The box turns blue and says Reset. Meanwhile, the phone is busy rebooting indefinitely on the battery screen.
I'll try your ROM and Odin version as soon as the link works. Also, do you have a ROM with built in recovery that you would suggest? Thanks!
Click to expand...
Click to collapse
Drop box seems to be running slow. So the JF6 that I am uploading may take a bit. The version of ODIN that You are running should be fine.
Try this Kernel. It's not a complete ROM just the kernel. If it works, you will have to flash a ROM too. Cognition is a good start. You can find it in the Dev section and actually, even if it's not the recommended way of flashing, I moght try flashing a custom ROM anyway just to rule out ODIN and your phone. If you can successfully flash a custom ROM then it's probably the version of JF6 that you are using.
Anyway, let's start with the kernel first:
Onix by existz:http://forum.xda-developers.com/showthread.php?t=930679
make sure you download 2.0.3 "tar" file for ODIN
you know how to get into recovery after you flash right? From powered off, hold the up and down volume buttons and then power all at the same time for about 5 second......
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
bharden said:
Ok, so there seems to be some progress. I flashed the kernel and the phone rebooted to what I'm assuming is the Onix splash screen and hangs. The power button won't turn the phone off, but at least the softkeys do seem to respond, even if they don't do anything.
Odin now recognizes the phone in both download mode and at the splash screen. Although, to reach download mode I now have to take the battery out, whereas I did not have to before.
I'm still unable to enter recovery. The only way to get any response out of the phone at the splash screen is to hold both volumes and the power button, but the phone just reboots back to the splash. It also does this when attempting to enter recovery from a power off state.
Click to expand...
Click to collapse
The three button combo should work to reset the phone when it's stuck as well as getting into recovery. It sounds like you aren't holding the buttons for long enough. If the phone is frozen, you have to hold the button combo for quite a while to get the phone to reset. Weh trying to get into recovery, push both volume buttons and then hold down the power button and don't let go till yoiu get past the AT&T screen.
If that still doesn't work, then try and load up the ROM and see if at least you can get a working phone back in the meantime. Like I said, I recommend Cog 4.3 but serendipity is a good choice too.
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
bharden said:
Awesome. I must have been holding the buttons for half a second too little. Now I can get into the Onix Recovery, but I'm getting:
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)"
when trying to mount the SD card.
Searching around I've found these two threads:
http://forum.xda-developers.com/showthread.php?t=563298
http://forum.xda-developers.com/showthread.php?t=792708
but I'm not exactly sure what to do with the information. I don't particularly want to go guessing at what to do next and ruin my progress. Could you give me a little guidance on what steps to take next?
From "adb shell mount /sdcard" I'm getting:
mount: can't find /sdcard in /etc/fstab
Click to expand...
Click to collapse
OK, so I've never had to mount SD from those options so not too familiar with this problem but, i am going to guess that we shouldn't have to play with this right now. Onix will let you install a zip from your external SD, so i recomend finding a recovery flashable ROM (almost all custom ROMs come this way....it'll be a ZIP file) Again I recomend using Cog 4.3 or serendipity (both of these may change your kernel but it's ok because they will both have a custom recovery).
Follow these steps:
1. Remove your external SD and insert it into your computer.
2. Remove any files you want to keep and place them somewhere on your computer for future recovery (Titanium backups, music, pics, etc....)
3. Format your sd (FAT32 should be default)
4. Download the ROM of your choice, copy it to the root of your external SD using your computer
5. Replace the SD into your phone power up into recovery
6. From the Onix recovery menu select "advanced options"
7. Pick wipe dalvik/cache and confirm
8. Select go back untill you get to the first recovery menu
9. Select install zip from SD and NOT "install update.zip"
10. Navigate to your external SD (it should look something like "/extsd" in the file menu
11. Pick the zip you put on the external SD and confirm
12. Wait till the recovery indicates instalation done
13. Navigate back to the first recovery menu and select reboot phone
14. Sit back and relax, your phone will likely take 3-5 min to boot up the first time
If after 10 min of waiting you get no response from your phone, use the 3 button reset to get into the custom recovery and select advanced features again, format absolutely everything you can format (you'll have to do it one at a time) and do that. Then repeat the steps above.
Installing a custom ROM isn't normally this complicated but I am trying to eliminate as many variables as possible here that might cause complications with instalation.
Let me know how it turns out.
FYI: Continuum v4 has the Onix kernel in it (recovery is a blue color)
ROM Files
This is the link to the good JF6 stock ROM. You will have to download it and the ODIN version. All you need is the PDA.tar and the PIT that comes with the ODIN package in the thread. You can still use ODIN 1.8 once you get the PIT file out of the ODIN ZIP.
So, after all is said and done. When you feel like trying this:
1. Open ODIN
2. Phone into download mode (with phone off hold down both volume buttons and plug in USB)
3. Make sure phone is recognised by ODIN
4. Select PIT file that you downloaded
5. Select PDA file that you downloaded
6. Make sure "repartition" IS selected
7. Hit start and sit back and relax
http://forum.xda-developers.com/showthread.php?t=818439
Again, let me know how it all works out.......
Ok, I'll try flashing Cog 4.3 after I get off this afternoon. I'll have to buy an external SD, but that's better than buying a new phone.
I skimmed those threads on the internal SD problem and it looks like there's either some corruption on the SD or it's not formatted correctly or something. How can I fix this problem? Doesn't the ROM need that internal SD card space? Or can it use the external SD card as a replacement? If it does need the internal SD card then won't the ROM fail to install if that SD is corrupted?
Thanks for all your help by the way. When Odin wasn't fixing the problem I was afraid it was completely bricked.
Introduction
I've put together a video on how to flash a rom. It includes Rooting, Backing up data, Flashing a kernel, Flashing a rom, and troublehooting bad flashes.
Warning
Before you go and flash a ROM for the ultra-fast speeds, kick-butt graphics and awesome sound upgrades... Realize that the risks are real, it is possible for you to black-screen-brick (hard brick) your phone. Here is a real-world example:phone won't turn on. At this point, only JTAG recovery will be effective. I will be posting a video on JTAG soon enough.
You may feel more comfortable stopping after rooting and titanium backup, and not installing a ROM at all, that's OK.
How-To
If you are installing a ROM, then select the ClockWork Mod flashable zip you want and copy it to your phone's internal memory before you watch the video. I did not cover this in the video as there are many options. Team Komin recommends Andromeda3, but you may select any Captivate ROM.
Here is the video which I have prepared on flashing a custom ROM.
Flashing Toolbox
Windows Drivers - select the proper driver for your setup
32 bit: http://www.mediafire.com/?0b45zo7o75rc5d5
64 bit: http://www.mediafire.com/?3dh4d6up72me9re
Files
*SuperOneClickV1.7 - http://files.teamkomin.com/Andromeda/Tools/SuperOneClickv1.7-ShortFuse.zip or http://www.mediafire.com/?kr649t97dd116cd
*Odin3 1.7- http://files.teamkomin.com/Andromeda/Tools/Odin3 v1.7.exe or http://www.mediafire.com/?dy2ix2icags19qr
*Ursa Minor - http://files.teamkomin.com/Andromeda/Tools/UrsaMinor.tar or http://www.mediafire.com/?a1i0boby6em54eo
*Andromeda3 - http://files.teamkomin.com/Andromeda/Andromeda3-Final.zip or http://www.mediafire.com/?vpu22j478j4542a
Recovery Software
*Odin3 one-click 1.0- use only in case of emergency, this can damage your phone -http://www.multiupload.com/XAZUYNXSC1
Tips, Tricks, Good to know
If you have a standard computer setup and you see your phone connected to a port higher then COM6, reboot your phone and your computer before flashing anything.
Phone--!--PC is just a download mode. If the computer does not recognize the phone, reinstall drivers, reboot and pull the battery out, then try again.
Odin is only used for initial and/or recovery modification. After using odin to flash a new kernel sucessfully, you will only need ClockWorkMod (CWM) to flash most kernels and ROMs. CWM is accessed by pressing and holding the 3 button combo.
If your phone displays Phone--!--PC and does not register a COM port on your computer follow the directions below
1. remove the usb cable, battery, sdcard, SIM.
2. wait 10 seconds, then insert the USB cable.
3. press and hold the 3 button combo while you insert the battery
4. continue to hold until phone's screen goes black twice and release power button.
5. timing is critical, it may not work the first time. Keep going until you see the COM port is connected properly.
Disclaimer: All materials presented are for informational purposes. This video is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.
Thanks for the guide adam, I'll be using this tonight. Could you possibly update this with a section on how to go back to a stock kb1 build? That would be great.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
AdamOutler said:
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
Click to expand...
Click to collapse
Thats JF6, not KB1.....
Stock 2.2 you get from the update using kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dead Links
Hey could you repost the download links because none of them work anymore? Thanks
Sorry, Team Komin's server is down right now, there are other sources on the internet. I will mirror on mediafire as soon as I can
In a boot loop - Moved from Andromeda thread
Hi Adam, Just to get up everyone where we are. I had a flashing issue with Andromeda which resulted in the phone continuously rebooting; i.e. white screen Ursa Minor screen disembodied voice which I now think says missing operation, it definitely doesn't say backup operation, I've listened to it soooooooo many times. . .anyway I put the phone in download mode as you said - BTW this phone with phone off vol+vol then plug in USB and download appears. Holding the power button takes you -when the phone isn't loopiing of course- into recovery mode. I had already restarted the computer, - not a VM - restarted Odin 3 and tried to reflash. Pass! Reset and unfortunately I'm still in that loop can't get to recovery mode.
I removed the battery and USB. Held down all three buttons and with the USB cable connected put the battery back. I held through 2 screen goes black circuits. Second time up the screen shows a gray battery then goes black then I get the ATT screen followed by Ursa Minor and my now less than favorite voice. Doing the same without the USB cable I don;t get the battery but I do get the ATT splash screen between the two black screen and then that darling voice again. So that's where I am. Ideas please
Personally I would One-Click back to Stock. ROOT. Install CWM using Rom Manager. And then install Andromeda via CWM. (I usually skip re-rooting and just install from CWM via the update.zip from ROM Manager) See if that doesn't work... If it does, finish up by installing Ursa Minor #2 (or is it just Ursa Minor now?)
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
^^ It can be tricky to get it into download mode, but there are several ways to do it on all phone. The important thing is that you get a sane COM port like COM8 or less on Odin3 1.7, and that you have download mode activated on the phone. Good to see that everything is working properly.
BWolf56 said:
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Click to expand...
Click to collapse
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
fireboss said:
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
Click to expand...
Click to collapse
OK well I've confirmed that Odin One Click won't restore on this phone unless it is open on the Windows machine when I connect the USB port tot throw the phone into download.
I restored then went through the flashing process again. This time when when it rebooted it didn't loop but it wouldn't go into recovery. I used droid explorer to flip it to recovery mode. Inoted then that there was no adndromeda.zip package on the sd card. I assumed Ursa was supposed to pull that over because in the video it says to find it and install. In any case I drug it from the computer to Droid Explorer and then was able to find it and install the Rom. The unpack looked normal enough the system rebooted. I unplugged USB,gave it the three button fix roputine, and was back in the loop. No matter what I did it looped. The loop was slower this time and the voice clearly said Restore Operation. Not knowing enough to wander farther and unable to get into recovery now because Droid Explorer couldn't see the phone anymore I let Odin restore it. That's where I am now.
Suggestions?
AdamOutler said:
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
Click to expand...
Click to collapse
Thanks! I'll try that out once I get home from work. The only thing I can say is that I wish that would've been up when I got my 1st cappy - would've saved me the trouble of having to Odin3 1 click
Once again, Great work!!
EDIT: This should be Stickied!
fireboss: redownload all links above, it is possible that something went wrong with the download process and a bit is missing somewhere.
-copy the rom of your choice to your SDCard (Team Komin recommends Andromeda3, but any will work)
-put the phone into download mode and flash ursa minor tar file using Odin3 1.7
-let it run though it's operation until it boots normally.
-remove the usb cord, press and hold 3 buttons to reboot into recovery
-select zip from SDCard- Andromeda3.zip
i dont see a link, or file attachment or any mention of 3e recovery in OP
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Might already be in Ursa Minor? (correct me if I'm wrong Adam)
fireboss said:
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after.
Thanks
Click to expand...
Click to collapse
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Right Bwolf
No need to mess with 3e recovery. UrsaMinor.tar overwrites 3e recovery and gives you CWM so you can begin flashing immediately.
mxracer101 said:
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Click to expand...
Click to collapse
That works. The biggest thing is that you are in download mode and you have a sane COM port like COM5 or 6, not COM14. As shown in the video, COM14 lead to Phone--!--PC..
I may do this video again with heimdall. it worked well.
mxracer101, any chance you can generate a pit file? I'd like to make Andromeda3 into a full heimdall flash where you simply put the phone into download mode, select the files, hit start, and let the stock phone boot into Andromeda3.
SOLVED: when having trouble with your computer not making a good connection to the phone, try your USB HUB on the mother board. it totally fixed my problem!
So here it is. I received a cappy from a buddy at work.
Basically, she is running cognition (FROYO BASED) rom, not sure of the kernal, and Cwm.
i can get the phone to reboot into RED CWM recovery, and even into DOWNload mode.
The phone was shut off during a factory reset. the battery died.
(IDK the girl was a dumbass and did it from settings on the phone not in CWM )
The phone will boot, ONLY after a factory reset from CWM but the setup google accs f/c's and the only thing i can get it to do is volume up/down pull the notification bar down and power off recovey dl mode...ect ect.
Task manager say's there are no APPS installed on the phone running? yet when i go LVL 2 RAM clear, the phone says 13 apps closed..
I think the Stock APK's have been deleted, since i cannot get into menu at all.
Since she factory reset the phone, and wiped the SD CARD, ALL CWM recoveries she created are GONE.
I have Cleared the cache, and wiped dalvik code, fixed permissions.....
I'm very familiar with the VIBRANTS, not the cappy's so this is a challenge to me.
my Vibrant has connected with all the usb drivers from samsung, but the cappy cannot. I've even downloaded the drivers for just the CAPPY, uninstalled all others, and Still not recognized, yet my vibrant does?
i've installed i think every driver on here for captivates, kies downloads, even went to the samsung website and Downloaded from there.
STILL NOT CONNECTING.
Even DL'd the AIO cappy toolbox (very nice to have for my VIBRANT)
Still no avail.
THE PHONE CANNOT MOUNT THE EX SD CARD. So that idea's out.
all my drivers are correct for the 32 bit vista OS. even tried on my GF's 64 Windows 7.
Still no avail.
I've installed the drivers with the phone in DOWNLOAD mode even, still not connecting.
Rebooted the computer after removing and also reinstalling drivers.
Changed between 3 diff cords, all work for my VIBRANT,
still no avail.
Any idea's would be greatly appreciated.
Thanks.
PelvicThunder said:
So here it is. I received a cappy from a buddy at work.
Basically, she is running cognition rom, not sure of the kernal, and Cwm.
i can get the phone to reboot into RED CWM recovery, and even into DOWNload mode.
The phone was shut off during a factory reset. the battery died.
(IDK the girl was a dumbass and did it from settings on the phone not in CWM )
The phone will boot, ONLY after a factory reset from CWM but the setup google accs f/c's and the only thing i can get it to do is volume up/down pull the notification bar down and power off recovey dl mode...ect ect.
Task manager say's there are no APPS installed on the phone running? yet when i go LVL 2 RAM clear, the phone says 13 apps closed..
I think the Stock APK's have been deleted, since i cannot get into menu at all.
Since she factory reset the phone, and wiped the SD CARD, ALL CWM recoveries she created are GONE.
I have Cleared the cache, and wiped dalvik code, fixed permissions.....
I'm very familiar with the VIBRANTS, not the cappy's so this is a challenge to me.
my Vibrant has connected with all the usb drivers from samsung, but the cappy cannot. I've even downloaded the drivers for just the CAPPY, uninstalled all others, and Still not recognized, yet my vibrant does?
i've installed i think every driver on here for captivates, kies downloads, even went to the samsung website and Downloaded from there.
STILL NOT CONNECTING.
Even DL'd the AIO cappy toolbox (very nice to have for my VIBRANT)
Still no avail.
all my drivers are correct for the 32 bit vista OS. even tried on my GF's 64 Windows 7.
Still no avail.
I've installed the drivers with the phone in DOWNLOAD mode even, still not connecting.
Rebooted the computer after removing and also reinstalling drivers.
Changed between 3 diff cords, all work for my VIBRANT,
still no avail.
Any idea's would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
First, see if you can find out which version of Cognition she was running (Gingerbread- or Froyo-based).
Once you have that information, I believe you should be able to download the appropriate ROM on you computer and copy it to the microSD card (adapter or whatever method you need to do to get it there). Since you can get into CWM recovery, you could try flashing the ROM from there. Assuming it's a full wipe rom (and you're not concerned about keeping apps installed on the phone), it should reset things to a more workable state. (If you are worried about apps remaining... I don't know what to say at this point, since you can't get to Tibu.)
If that doesn't work, you could try the one-click back to stock (realizing that you're having connectivity issues, I'll get to that in a second).
When you connect the phone in download mode to ODIN, does the yellow COM:# show up?
If you have tried ODIN on your Vista computer, try running ODIN as Administrator.
I've had some luck in the past getting the phone to be recognized (assuming Froyo) by doing this:
1. With nothing connected to computer, start ODIN (one-click to stock would be good).
2. Pull battery on phone.
3. Reinsert battery, but do not power on.
4. Hold Vol+/Vol-/, and insert USB cable.
5. Wait for it to kick into download mode, release buttons, and wait again.
6. See if ODIN recognizes it.
jmtheiss said:
First, see if you can find out which version of Cognition she was running (Gingerbread- or Froyo-based).
Once you have that information, I believe you should be able to download the appropriate ROM on you computer and copy it to the microSD card (adapter or whatever method you need to do to get it there). Since you can get into CWM recovery, you could try flashing the ROM from there. Assuming it's a full wipe rom (and you're not concerned about keeping apps installed on the phone), it should reset things to a more workable state. (If you are worried about apps remaining... I don't know what to say at this point, since you can't get to Tibu.)
If that doesn't work, you could try the one-click back to stock (realizing that you're having connectivity issues, I'll get to that in a second).
When you connect the phone in download mode to ODIN, does the yellow COM:# show up?
If you have tried ODIN on your Vista computer, try running ODIN as Administrator.
I've had some luck in the past getting the phone to be recognized (assuming Froyo) by doing this:
1. With nothing connected to computer, start ODIN (one-click to stock would be good).
2. Pull battery on phone.
3. Reinsert battery, but do not power on.
4. Hold Vol+/Vol-/, and insert USB cable.
5. Wait for it to kick into download mode, release buttons, and wait again.
6. See if ODIN recognizes it.
Click to expand...
Click to collapse
Thats my problem, the cappy does not see that there's an EX SD card there at all? says no files, but i've tried to push a cognition rom to the EX SD and use CWM to flash it to get it to boot, but the phone cannot see that there's an EX SD, but the SD card is fine, even my vibrant used it..
ODIN as ADMIN? tried that and nothing, still no yellow com port,
i know how to use odin, as my VIBE has been "Bricked" a few times lol
the vol up/down button combo does nothing, just shows up as a charging screen, the only way i can get the phone to download mode is through CWM.
the phone is running a FROYO based cognition ROM. or that's what her bf put on there.
This may sound stupid and simple but is the device set on mass storage from the settings menu? If you know.
Also have you tried mounting your sd cards in CWM?
Rhiannon224 said:
This may sound stupid and simple but is the device set on mass storage from the settings menu? If you know.
Also have you tried mounting your sd cards in CWM?
Click to expand...
Click to collapse
lol THATS MY PROBLEM> the phone thinks it boots normally, but i cannot get the settings menu. like the "SETTINGS APK" file was deleted when she formatted the SD!
but i was just playing around and i got google voice search to pop up!
then from there i used my WIFI and setup the google settings, then i went to the market grabbed CWM and used the cognition rom i've already downloaded, and used it!
then the GREEN CWM booted, and it still cannot MOUNT EX SD card. so the flash failed.. HMMMMMM
As of now i am gonna go into the rom i DLed (cognition) and try to DL Root explorer and hard push the Settings.apk file to the system. HOPEFULLY from there i can get my settings back to restore the phone.
Realizing that it's a long shot at best due to connectivity issues, have you tried using ADB?
If so, you could push the ROM you need to the internal SD.
so, used root explorer to move the NEW cognition froyo rom from the EXternal SD to the INTERNAL SD. from there i used CWM recovery to flash the rom, the rom flash was successful, but now the phone is stuck in bootloop on the AT&T world phone screen.
and CWM will not LOAD. FML
Looks like i'm gonna have to take this apart and get to the internal SD card. =/
Can you get to CWM with the Vol+/Vol-/Power combo - hold those past one AT&T screen and when you see the second one, let go?
Adb was not an option at that point, the phone couldn't recognize it even had a phone attached to it.
but now that i'm stuck in bootloop and with no CWM recovery OR DL MODE, yeah the jig isnt' workin... HAHA
i guess its just a paperweight now.. Owell, i tried.
i held it for about 3 mins... lol and the jig i got for my VIBRANT isn't workin either. I didnt know these phone's can lose the 3 button combo reset? i often flash I9000 roms to my vibe, thats why i have a jig, but i didnt think cappy's would do that unless i flashed an i9000 rom to it? lol
Just because I'm not sure if you tried it - have you tried plugging the cable into a different port on your computer? If it's not one directly connected to the motherboard, that can sometimes cause problems getting the phone to be recognized.
Also - does the phone show any signs of recognizing there is a cable inserted (like charging)?
tried every port. No the phone only acts as if it wants to display the batt charging symbol, but does not show, I cant believe it, i actually think i bricked a galaxy s.. haha
Another long shot, but you could try the One-click unbrick. Since it's Heimdall-based, there's always a chance.
Wow, didnt know that even existed. Definately gonna be useful for my Vibrant, haha i'll give it a shot.. THANKS, i'll report back after i try it.
I hope it does something. With the connectivity issues you're seeing it's starting to sound a little like hardware issues.
I'm going to throw out a checklist of stuff, knowing that you are already experienced with ODIN and ROM flashing, simply because I know I usually can use some sort of checklist to make sure I've caught everything.
- Redownloading/reinstalling drivers, rebooting before connecting phone
- Redownloading/reinstalling ODIN package
- Redownloading ROM to flash
- Hold V+/V-, inserting USB cable
- Remove battery, hold V+/V-, insert USB, insert battery
- Hold V+/V-/HOME softkey
- Hold V+/V-/HOME/Power
- If download mode reached, allowing phone to sit connected for long time
- If download mode reached, connecting phone after opening ODIN
- If download mode reached, connecting phone before opening ODIN
- If download mode reached, connecting phone after ODIN, disconnecting, reconnecting phone
That's all I can think of for a checklist of stuff to try/retry.
I appreciate the help but i've tried all of those options several times, The jig did work to get it into DL mode, but from there i'm still in the same **** position, my computer will not recognize that the phone is connected.
Is it possible that the phone somehow lost its drivers? what i mean by that is, the phone acts different with different USB ports, completely.
On one port it says unknown device, another USB android composite device.
Its as if the phone's changing as i change ports. Very FRUSTRATING!
i think it could be a hardware issue myself, but how could a corrupt drive work so well? To the T every time i've used the jig DL mode fired up, but my computer still cannot find the drivers to run it. Hell i've even tried using winusb drivers package to force install the phone, still no avail.
Like i said, I really appreciate the input, I figured if i couldnt figure it out, someone on here had some EXP in doing this lol i've just never had a driver problem give me so much trouble. IDK, bout ready to turn this paper weight into a pile of ash.
If you can get into cwm, have you tried doing another hard reset/factory wipe?
Thats the problem, earlier i COULD get into CWM, and hell i flashed the new rom perfectly!
now it is stuck bootlooping, therefore i just used the Jig, and first few times it didnt work, now its stuck bootlooping, download mode is attainable, and still NOT connecting to my pc via usb.
mrhaley30705 said:
If you can get into cwm, have you tried doing another hard reset/factory wipe?
Click to expand...
Click to collapse
Nvm, reread your post. Have you tried flashing a different rom?
PelvicThunder said:
Thats the problem, earlier i COULD get into CWM, and hell i flashed the new rom perfectly!
now it is stuck bootlooping, therefore i just used the Jig, and first few times it didnt work, now its stuck bootlooping, download mode is attainable, and still NOT connecting to my pc via usb.
Click to expand...
Click to collapse
Try a different computer? also, which version o of odin are you using? I've found 1.3 & 1.82 to work best.
I'm a newbie here and doesn't followed correctly steps for install a theme, so it's completely my fault. Now, I need somebody to help me recovering my device.
I tried to install this theme http://forum.xda-developers.com/showthread.php?t=1808013
I read this thread http://forum.xda-developers.com/showthread.php?t=1551156 I've rooted the device and applied the instructions for "ClockWorkMod Recovery 5 - for use in future custons rom or partial back-up.-" but then, here is when I do wrong, I went to boot recovery mode (not CWM) > apply patch/update and selected the theme zip. Since then, every time I boot the device, it shows me 2 errors: the status bar process has stopped - And then the screen goes black and return again with the same error. At least it loads the background and icons of the main screen.
The device doesn't ask me for the password before the errors prompt. My device has the stock rom.
Can I fix it with recovery boot > wipe data/factory reset?
kalise said:
I'm a newbie here and doesn't followed correctly steps for install a theme, so it's completely my fault. Now, I need somebody to help me recovering my device.
I tried to install this theme http://forum.xda-developers.com/showthread.php?t=1808013
I read this thread http://forum.xda-developers.com/showthread.php?t=1551156 I've rooted the device and applied the instructions for "ClockWorkMod Recovery 5 - for use in future custons rom or partial back-up.-" but then, here is when I do wrong, I went to boot recovery mode (not CWM) > apply patch/update and selected the theme zip. Since then, every time I boot the device, it shows me 2 errors: the status bar process has stopped - And then the screen goes black and return again with the same error. At least it loads the background and icons of the main screen.
The device doesn't ask me for the password before the errors prompt.
Can I fix it?
Click to expand...
Click to collapse
Yeah from what you are describing you can 100% fix it. However if you didn't make a backup of any sort then you will need to reinstall your firmware with ODIN3 v3.07. Go to the same thread that you got ClockWorkMod Recovery from and download Odin from there. Then download the latest firmware for your country/region from here (you have to change the country to your own one in the drop down menu and sign up to download files which is free).
Make sure you download firmware for S5830i ONLY whatever you do! Wipe all user data in recovery just to avoid any further hiccups. Then put your phone in Download Mode (Power + VolUP + VolDown when switched off), connect it the PC and open Odin. Use the PDA section ONLY to put the tar.md5 firmware file in. DO NOT use a PIT file and do not tick any other options than the two default ones (Auto Reboot and FReset Time I think). Just follow that to the letter and once ODIN is done, it will almost definitely be back to normal again.
By the way also make sure you run Odin as administrator and that Kies is not running because they don't agree with each other.
I've downloaded the lastest firmware for my country (s8530i, Spain, November) and now Odin looks like this: i.imgur.com /rZ76d.png (no 10 posts yet, sorry)
I've got the device connected via USB and awaiting in odin mode "product name, custom bin, current bin, etc) "Downloading..." message. Should I use the entry "Wipe data/restore factory" from the recovery boot first?
Now, is everything ok, do I press start?
Very nearly but Odin hasn't recognised your phone yet. Basically you see where it says "ID:Com" with 8 grey boxes above the writing, well when Odin has made a connection with your phone one of those boxes should light up and something like COM:1-9 (number isn't important) will be displayed inside the box.
You probably need to install Samsung Kies (search for it on Google) which comes with the USB driver needed for Odin and then it should work. But as I said just make sure you actually kill/terminate Kies from Windows Task Manager before using Odin. If you've already installed Kies sometimes it's just being a pain in the backside, unplug the phone, pull the battery out, reinsert it, put the phone back in Download mode, reboot your PC, hopefully that should do it.
Everything else in your screenshot is absolutely fine. You don't have to Wipe Data before doing it, I usually do it because sometimes it can cause issues. In the worst case you might have to do it afterwards.
Sorry, my fault. The device wasn't plugged. Now it looks like this i.imgur.com /HJz3B.png
Done, device working, thank you very much and sorry for the trouble.
No trouble just press thanks button if I helped though please.