I've saved a couple i9000 Odin flashed Fascinates with this method so it should work.
First, grab my DI01 All in One. You need an all inclusive package.
http://adrynalyne.us/files/kernels/DI01package3.tar.md5
You will need odin3 v 1.30. Google for it.
You also need Heimdall.
Heimdall – Glass Echidna There is a readme in the windows version zip if you get stuck. Drivers must be installed for it as well.
You also need a copy of the samsung galaxy s usb drivers, because Heimdall will remove them when you use it.
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - xda-developers
You will also need a PIT file from me:
http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Steps:
1. Install Heimdall and drivers.
2. Put phone in download mode and plug it in to usb cable.
3. Unzip the Odin file. 7zip can do this, but will give an EOF error. Ignore the error.
4. Choose each section in Heimdall and add the appropriate file, including PIT. Check repartition. Primary boot loader is boot.bin and secondary boot loader is sbl.bin.
5. Start. Boot once, check for problems. If problems persist, continue.
6. Reinstall Samsung USB drivers for Odin. This may require a PC reboot.
7. Put phone back in download Mode and start Odin, making sure its detected.
8. Load the entire Odin package, not extracted into the pda section of Odin. Include the PIT file. CHECK repartition.
9. Run the process.
If all goes well, you should be back to stock, crappy Eclair 2.1 without force close errors.
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
i went to cm7 from sc 2.4 aswell, and to get back to sc 2.4 i just flashed cwmfroyo edition through cwm, rebooted the recovery then wiped data, re-installed sc 2.4 and bam! i was back.
upsidedownaaron said:
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I wouldn't say you were bricked. Bricked means the phone no longer functions period, no matter what you do to it. But I'm glad this helped you. I'll probably use the DL09 All in One and then flash SuperClean back over that.
When you flash an All In One, you are taking your kernel and your radio (modem) back to that version as well. When you want to go back to Froyo or whatever, make sure you flash the radio along with whatever else your flashing.
Boot looped. Wouldn't get past Samsung logo. Not an uncommon problem for me. I have become very comfortable with Odin.
Sent from my SCH-I500 using XDA App
upsidedownaaron said:
I have become very comfortable with Odin.
Click to expand...
Click to collapse
haha yeah. It's saved me but a couple times mostly anytime voodoo is involved. Tried restoring a nandroid backup of EB01 after flashing CM7 and got force closes from hell. Odin'd back using the EB01 unbloated/deodexed.tar and everything booted fine. Tried to restore the nandroid and couldn't do anything because of the force closes. Think I have corrupt data somewhere though. I also made a backup of the apps and data in MyBackupPro and ended up in the same force close situation upon reboot after restoring all. Selectively restoring a couple apps worked fine. Oh well.
Basically, I can't sustain a data connection for longer than about a minute before my fascinate disconnects. It takes about a minute to reconnect, then it disconnects again. Over and over and over. It never affects phone calls because it's not losing signal, it's just dropping the data connection.
I've been poking around my phone a bit, and in the past week, but I can't pinpoint what I did that made this start happening. I was hoping this thread would save me, but it didn't. I went back to DI01 using heimdall, booted up, still had the same problem. Reflashed with Odin, same thing. Went back to SCv2.4 with EB01 modem, same thing.
I ask this in this thread because I'm wondering what part of the phone remains untouched even with the full DI01 flash? Like some kind of low-level device mode that I triggered?
If there is nothing then it must be hardware related, and I will get a replacement.
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Why does the movinand.bin fail when using Odin?
upsidedownaaron said:
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Click to expand...
Click to collapse
Sounds pretty familiar . I always have to be breaking my stuff to be happy.
I've done the full heimdall DI01, followed by full Odin, to no avail. I think I messed up something with the service programming on the phone, but reactivating it doesn't help. None of the factory reset options I've tried have cleared the activation settings back to stock. Anyone know how to accomplish this?
I suppose I should move to my own thread now.
Related
so i am trying to restore to an old back up but every time i do it it takes me to the Android System recovery. I have tried the following from the system recovery reinstall packages>then backup and restore>restore> and i tried with the following backups: 10-18-10_JI6_Lag_Fix, 10-29-10_Bionix_Voodoo, 11-02-10_Fusion_Voodoo. i even disabled voodoo tried to restore again and nothing it keeps sending me to Android recovery system. i would have to use Odin and start all over again, whats the purpose of a backup if i cant get it to work. any ideas?
p.s. i also took out battery and put it back in and took me back to Android recovery system.
EDITk so i tried to go back to stock (JI6) and no luck, on the Odin i get RESET (in blue) the phone resets and goes back to Android system recovery. i tried to reboot and nothing only goes back to system recovery the only time i get PASS (in green) is when i disconnect the phone.
what am i to do i am freaking out. i am downloading JFD but i am worried it will happen the same thing, any ideas?
Use the all in one ji6. Odin zip in the stickie. Then try to flash a different. Rom.
Is your phone Loki? Use Odin. You'll be Thor!
demize! said:
Use the all in one ji6. Odin zip in the stickie. Then try to flash a different. Rom.
Is your phone Loki? Use Odin. You'll be Thor!
Click to expand...
Click to collapse
was able to finally download JFD and it seems to be working as its taking a while to finish. how long is it supposed to take? its been a while since i last restored to stock.
adinis78 said:
was able to finally download JFD and it seems to be working as its taking a while to finish. how long is it supposed to take? its been a while since i last restored to stock.
Click to expand...
Click to collapse
Usually takes about 10-15 minutes per the readme in the Official Firmware Odin Thread.
edit: I used Odin 1.3 on my machine (Win7 Pro 64-bit) when I went back to stock (instead of the v1.0 in the thread). The newer 1.53/1.7 releases weren't out yet...
~SB
ShinyBuddha said:
Usually takes about 10-15 minutes per the readme in the Official Firmware Odin Thread.
edit: I used Odin 1.3 on my machine (Win7 Pro 64-bit) when I went back to stock (instead of the v1.0 in the thread). The newer 1.53/1.7 releases weren't out yet...
~SB
Click to expand...
Click to collapse
i have been stuck for almost an hour, i think there is something really wrong....
why wouldn't i be able to restore a back up? did i have to disable voodoo?? this is what i don't understand, made backups but i cant restore.......
can't restore old backups - solved well kind of
adinis78 said:
so i am trying to restore to an old back up but every time i do it it takes me to the Android System recovery. I have tried the following from the system recovery reinstall packages>then backup and restore>restore> and i tried with the following backups: 10-18-10_JI6_Lag_Fix, 10-29-10_Bionix_Voodoo, 11-02-10_Fusion_Voodoo. i even disabled voodoo tried to restore again and nothing it keeps sending me to Android recovery system. i would have to use Odin and start all over again, whats the purpose of a backup if i cant get it to work. any ideas?
p.s. i also took out battery and put it back in and took me back to Android recovery system.
EDITk so i tried to go back to stock (JI6) and no luck, on the Odin i get RESET (in blue) the phone resets and goes back to Android system recovery. i tried to reboot and nothing only goes back to system recovery the only time i get PASS (in green) is when i disconnect the phone.
what am i to do i am freaking out. i am downloading JFD but i am worried it will happen the same thing, any ideas?
Click to expand...
Click to collapse
EDIT: after hours of sweating and thinkin i would have to get a new phone i was finally able to get my phone of the Android system recovery by flashing Eugenes Froyo That does not Brick the reflashing JFD. But my original question is : trying to restore to an old back up but every time i do it it takes me to the Android System recovery. I have tried the following from the system recovery reinstall packages>then backup and restore>restore> and i tried with the following backups: 10-18-10_JI6_Lag_Fix, 10-29-10_Bionix_Voodoo, 11-02-10_Fusion_Voodoo what is the proper way to restore a backup and is it worth is cause in my case it did not work.
EDIT: well i got my answer on how to back up, it seems that i need to back up/restore with voodoo disable. That was my mistake, all the back ups i had were with voodoo enabled and when i went to restore i didnt disable it but it would not have matter since i did the back ups with voodoo enabled. It would have been a good idea to advise people that when doing their back ups to disable voodoo first and when restoring them to do the same, this would have avoided a lot of lost time and frustration. Now i have to go back and redo everything again and remember which apps i had and reinstall them. Lesson learned and hope this helps. (thanks to jdkackley for the insight)
I'm a longtime reader, don't post too much.
I'm in desperate need of help. If you're just going to flame me, please save that for a little bit so I don't have to sift through it to find some help.
I have the ROM addiction--I've flashed just about everything available for the Fascinate. I am a novice at best (i've fumbled my way through ADB before), but have never had any serious issues. Tried to flash EB01 modem through Odin (was at DI01 still somehow), and Odin froze. After 20 minutes I closed and disconnected my phone. It wouldn't boot after that. I was running the EC10 Rom and kernel (v2, before it became nameless). And I accidentally flashed the 3.0 clockwork, so I couldn't do anything through recovery.
I was trying Odin 1.3 from a Vista machine (not mine, I run Ubuntu) to begin with. Finally got my hands on a Windows 7 machine and Odin worked great. Restored to DI01, then flashed Superclean 2.9.2, and had the correct Clockwork. Less than a day later, Zeam (which I had as my default launcher) started force closing. Somehow Clockwork reverted back to 3.0, so all i could do was try fix permissions. Tried to odin restore again, and odin froze again, from the Windows 7 machine this time.
I've tried different USB cables and ports on three different computers (Windows 7 and two XP's. I can't get heimdall to recognize it in Ubuntu (might not have the drivers loaded properly there). Odin at least recognized the phone earlier, and it would start to flash. After 4 or 5 minutes the screen on my phone would go black and the flash would just freeze. Restarted the computer, reinstalled the drivers. Kept trying to flash. Then the screen started to change colors when it froze--always a solid color, but changed with different flash attempts. White once, pink once, and i think blue once.
I've been on IRC and received some tips, but it's hard to get sustained attention there. Especially since i'm a n00b. I've read every post I can find.
I NEED my phone. My girlfriend is out of the country right now, and that's how we communicate. Skype, chat, etc. It's killing me not to have my phone right now.
Can someone please help me out? And if you must flame me, how about wait until my phone is working please
Thanks in advance
Well i'm a noob too but... I have read you should use oem cables. I guess people have issues with non-oem ones. I don't know why odin shouldn't run though. Just try flashing the right cwm. You can either try odin or just flash it in cwm itself.
I was hacing the same problem with odin 1.3, i have been using odin 1.7 for months with no problems. Here is a link for the one i use, hope it helps. http://www.mediafire.com/?t093btu771q0bgi
Sent from my SCH-I500 using XDA Premium App
thanks Dale, i'll try that now.
Exzackly--i was able to flash the correct CWM at one point but couldn't install a ROM through it. and now I can't connect to Odin at all.
thatoneguy1983 said:
thanks Dale, i'll try that now.
Exzackly--i was able to flash the correct CWM at one point but couldn't install a ROM through it. and now I can't connect to Odin at all.
Click to expand...
Click to collapse
Because this kind of question has been popping up all over the place, i put together a post with instructions, and links for everything you will need just to help everyone out. hope it helps you. http://forum.xda-developers.com/showthread.php?t=1026746
Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J
Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.
CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.
Thanks given.
Do you know of any method I can do to fix this
You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.
You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.
I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.
Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?