Related
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.
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
dssheeley1 said:
Ok...I'm at a point where I had no other choice but to get another replacement. I looked just about everywhere my patience would take me, and decided to give up. I hope someone could/would have a solution for me or others like me.
I had EH03 deoxed rom and decided I wanted ICS build5. So I installed CM7, I whiped cache, DLVK, and system data. Then flashed ICSb5 and GAPPS, Rebooted and stuck on ICS splash screen.
At this point USB ports wouldn't recognize fascinate. Downloaded all Fascinate drivers from Samsung, drivers for Nexus S, ADB, Android SK. You name it I got it. Nothing worked for USB detection. I even followed YT videos on turning Vista/PC off and unplug. Nothing.
After messing with data cords,(numerous ones,trying another PC), PC ports, I happened to pull plug and battery out of Fascinate at the same time, not sure what version of CWM, it was blue, came on. Luckily I had two Nandroid backups on SD.
I flashed Nandroid back to CM7 successfully. Rebooted fine and hooked to USB but still not recognized. At this point I was able to get into recovery using ROM. So, I did something stupid...lol...I tried to flash earliest Nandroid which was performed when on EH03 deoxed. Once I did this, I wiped all needed data and rebooted. Now Fascinate shows Samsung logo. It doesnt reboot, just that the logo stays until I pull battery. Now if I have battery in wth phone off and plug in, the charging battery comes on but doesn't show battery level. Doesn't go away till I pull battery.
The funny thing is that I can get into Download mode but USB is still unrecognized/malfunction on PC/Vista. I only wish that I was able to link phone and PC just to use Odin with PIT file and stock EDO5 or EH03.
Any advice?
Click to expand...
Click to collapse
In the op of ics and also droidstyles guide you have to flash build 1 before you can flash build 5
Sent from my SCH-I500 using XDA App
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
I bootlooped when i went from stock EH03 to Build 5 so i did 3 first then 5.
But this doesn't help our poster here.
OP:
you get into DL mode but odin wont see your phone?
What i suggest is to try: Move the usb cable to a different port. see if your pc can see it then. Second thing try a totally different computer. Chances are your PC is trying to use borked up drivers.
Once you get odin going flash a stock image [i recommend eh03] then cwm then build 3 and now the new build 6. good luck!
if you need any links or a more detailed guide I STRONGLY suggest Droidstyles guild, it is by far the best and most up to date for the fassy!
OhioYJ said:
I've never flashed version 1 before flashing.build 5. In fact I've had the least amount of problems going back to stock (ED05) then flashing ICS.
Click to expand...
Click to collapse
Consider yourself lucky....going from stock to build 6 causes me problems and many others. Going from stock, to build 1, then build 6 works flawless.
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
dssheeley1 said:
MOD please close thread due to lapsed timeline and no longer support of this model.Ty
Sent from my SGH-i717/GT-N7005 w/phMOD_beta2
Click to expand...
Click to collapse
You realised you just bring a a old thread back yourself and no longer support of this model wtf you realise people.still use this phone everyday Right?
Sent from my SCH-I500 using Tapatalk 2
This is what happens when you have too much info with waaaay too little experience.
Bought an unlocked Vibrant from Amazon a year ago after the original tmobile one got stolen. It had issues like freezing up, tons of apps running all of time, etc. I finally tried installing froyo and it made the phone SO MUCH BETTER! Everything ran 1000% faster. I should have stopped there. But, it was pretty addictive I started reading about the new ice cream roms and somewhere, before I even got into it, I messed up the internal sd card. I have been working on this for a week, reading, downloading, flashing, etc. I feel like I have tried everything and have gone around in circles.
I can get into download mode with no problem. The furthest I have gotten after that was getting the "pass" in Odin. The phone does the boot up, then stay on the Galaxy S screen. Now, my computer won't recognize the phone (which has already happened) but now I am soooo confused and frustrated about where to go next. I have used AIO toolbox, Eugene's no brick, installing new drivers, new usb cord, etc.
Sorry so long. Thanks again.
bump...hope someone can help.
Could you give a clearer explanation/timeline of what you did? How did you mess internal sd?
Did you Odin stock jfd?
Sent from my GT-I9000 using XDA App
nolamom said:
bump...hope someone can help.
Click to expand...
Click to collapse
Is Clockworkmod recovery installed? If not, google: Samsung_Vibrant:_Full_Update_Guide and go to the Cyanogenmod wiki entry. Read through the "Installing Clockworkmod recovery" section.
In addition, from Addictivetips, to start recovery mode using the hardware buttons:
"Using hardware button combination on most Android devices:
On most Android devices including ones by HTC, you can enter recovery by powering your device off and then powering it back on while keeping either the ‘Volume Down’ or the ‘Volume-Up’ button pressed, depending on the device. This will enter the bootloader from where you can select the ‘RECOVERY’ option by navigating to it with the Volume key and entering it with the ‘Power’ key.
Sorry, but I'm not allowed to post links yet.
On most Samsung devices specifically Samsung Galaxy S series devices, you must keep both the ‘Volume-Up’ and ‘Home’ keys pressed while powering on the device, to directly enter recovery."
Thanks so much for the help. Ascallop: I tried to run Heimdall suite 1.3.1. The first time the drivers installed but I could not get passed the "run as administrator" on the next step. I have Windows XP professional even though I am on a home computer. It is automatically checked off to do so. When I tried again later that day, my computer again only recognized the vibrant as an unknown device. I just followed your link to Cyanogenmod's wiki and downloaded the older version and the same thing happened with the unknown device. I can't get passed that. Trailblazerz11, I think when I got to clockwork mod recovery, I hit repartition (if I am explaining that right). I was able to get into download mode and use Odin to get to the bootloader loop. I can't get into recovery. I was getting the message about the internal sd error. Now, I am stuck with the unknown device issue. I have tried a couple of different versions of Odin, the AIO toolbox, different usb ports, a new samsung cord, etc. Thanks again for helping this noob.
update: Used heimdall frontloader and installed cmenard overstock. Now I am stuck at the overstock screen. I am searching through different posts to find out more. But if you have any advice or can point me in the right direction, I'd appreciate it. Thanks again.
Have you tried repartition on odin?
sent from the xda app on my android smartphone.
Do you have an external SD card installed? If so, then remove it during the entire recovery process. I had lots of trouble recovering and flashing new kernels/roms while it was installed. Probably should have mentioned this earlier... sry.
No. It was already taken out. I am having trouble still with the vibrant not being recognized. I used the zadig, it recognized the samsung, did the next step, frozen at overstock screen. Now, after unplugging cable, Vibrant pops up as unknown device. Can't do zadig again.
I'm travelling until Friday, when I get back to my home PC, I'll odin my Vibrant back to stock Eclair and will list the steps that I took some months ago to install CWM/CM7. I once was at the same point as you are now, I just can't remember the steps verbatim regarding the recovery process. One question though: have you updated your phone via Kies at any point? If so, was the last update to Froyo?
BTW, I'm currently running (quite happily) ICS Passion V12 on my T-Mobile Vibrant.
The Vibrant is a pretty hard device to truly brick. Don't worry too much, yet.
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
nolamom said:
Thanks so much ascallop! I think I tried Kies when froyo was offered as an update through Samsung. But, it wouldn't work. I thought it was because my phone came unlocked so I came here and was able to update to froyo and I loved it. I haven't used Kies since. The ICS Passion looks awesome. I think the ease of using froyo made me ridiculously overconfident. As of right now, I have gotten the drivers to download in Heimdall and used the frontend to flash the kernel. I'm not sure what to do next because it seems that if I reboot to get into download or unplug the usb, the computer won't recognize the phone again. I'm sure I'll be happily running ICS when you get back on Friday. Kidding, kidding.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Let's get your phone back to Stock first. I just did this to my own Vibrant
I am officially back to stock!!! Thanks so, so much. After all of the reading and researching, you actually jumpstarted my recovery! Thanks again!!!
You're welcome
BTW, I flashed ICS V12r1 with Nelson's new kernel today. I love it. GPS works great for me, although others have reported problems. Same old deep sleep issue for them.
I wonder if flashing back to stock first is the key to fixing the prob. Don't really know though...
After the stock flash, the steps I took were:
copied kernel and rom to the internal sd card
One-click rooted the phone
odin (1.3) the Overstock kernel just to get cwm installed (instructions on the cm7 wiki)
reboot to cwm
wipe data/factory reset
wipe cache/dalvik
flash rom
reboot, let settle
reboot to cwm
flash kernel (I used: ICS_Passion_sunset_with_nova)
reboot, let settle
---------- Post added at 05:29 PM ---------- Previous post was at 05:24 PM ----------
One more thing: I flashed the Gingerbread bootloader as well. After you do this the key combo for cwm is: Vol-up + power. Let go when you see the boot splash.
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
You shouldn't need an external card to root. Try One click root:
http://forum.xda-developers.com/showthread.php?t=1125414
nolamom said:
Sounds sweet! Although I'm back to stock, I can't root because I can't access the internal drive. A message comes up about E: no such file, etc. I can see the phone storage memory amount and the phone holds data. I don't have an external card in right now. So, here I go again....
Click to expand...
Click to collapse
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------
cashmundy said:
When I've seen that E: error, it has been because of a mismatch between the CWM version and the filesystem layout on the device. CWM for CM7 doesn't work for ICS, for example. At least not for me.
Click to expand...
Click to collapse
And of course the stock recovery won't work with anything else. Different partitioning, different filesystems.
Okay. I was able to root with the one click root app. Now, I need to figure out what to do next. Ascallop, I was reading about your latest updates. I have to go through it a few times so that I can understand it all. I had froyo before and it blew away stock. I can't imagine what ICS is like Thanks again for all of the help. I HATE being back to stock.
The only reason I'm not running ICS is that I'm waiting for CyanogenMod permissions management to appear in anyone ICS rom. I'm really tempted to try Passion. ICS is markedly better than the best GB in various ways. Just remember to take a nandroid backup before upgrading, and that if something doesn't work and you need to downgrade, you will have to get the downgrade done successfully before you can nandroid-restore. Good luck!
Thanks Cashmundy. I saw the video for the root and install ice cream sandwich by Eddie West (I think that is his name.) He is a dj also. It looks like everything I would need so I may go with that.
Last night I went to reboot into recovery and my phone now sits at the Galaxy S2 splash screen and won't boot up. Tried plugging it in powered off and it won't even go into charging mode. The battery picture just comes up and the little spinning wheel keeps going.
So Ive been trying for the last hour to reflash the phone back to stock using both Entropys return to stock guide as well as the 'How to return your phone to the store' guide too and no luck.
Heimdall of course as always just flat out doesn't work so I hooked it up to my laptop and ran Odin. Odin connects to the phone fine and the box turns yellow, but the minute I hit start, it just gives me this:
<ID:0/008> SetupConnection..
<ID:0/008>
<OSM> All threads completed. (succeed 0 / failed 1)
I even tried the one click ICS leak from Rootzwiki and the same thing.
I can get the phone into Download mode no problem but man I cannot get it to flash ANY of these rome!!
Any advice or should I just take it to an ATT store on the way home from work??
I got it around the second week of February so hopefully worst case scenario I can still exchange it..
Im at my wits end here, can't do anything with it!!
I had same problem with my sprint Gs2, I took it into the store they told me since I rooted they couldnt help me. But the guy said go into download mode and root it again, it will remove anything and everything off it. Idk if that's what you want though. It got my phone back up and running
Sent from my SPH-D710 using xda premium
Ahh forgot to add I can't get into Recovery anymore.
No clue what happened. I can get it into Download mode but not Recovery.
If I could've gotten into Recovery I could've just flashed my Nandroid last night and fixed it hehe..
ODIN requires Download mode, not recovery mode. If your phone can indeed go into download mode as you claimed, you should be able to flash any ODIN flashable ROMs.
Try flashing just a kernel with recovery
Sent from my GT-I9100 using Tapatalk 2 Beta-2
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
creepyncrawly said:
You didn't say what you were running before the problem occured. Or if you did anything just before. Need more information to be able to troubleshoot the problem.
You might try flashing Entropy's DD kernel only with odin. He has at least one tar in his DD thread OP.
It may be that one of the components, such as param.lfs is screwed, but it would be better to have more information first before just randomly trying to flash things.
You can find most everything you might need in the Download Repository.
Click to expand...
Click to collapse
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Slavestate said:
Yeah sorry about the lack of info hehe! I made the thread about 20 minutes before I had to go to work and spent the hour before that trying to fix it hehe.
Anyways, I WAS running the ATT ICS leak that Task and Fenny packaged up with CWM. I WAS going to get everything backed up and attempt to move over to CM9 when it went to crap.
So far what Ive attempted to flash with Odin was the following with no luck:
Entropys 'Return to Stock' PDA.tar (the UCKH7_stock_odin with root)
ATTGalaxyS2Unroot_SGH-i777.tar
The leaked ATT Odin one click flasher from Rootzwiki (same results as using regular Odin with any of the above)
I did in fact also download the I777UCKH7-CL503881-Parts-NoBL.7z from creepys 'How to prepare your phone for return to the store' thread BUT..
The instructions tell you to unpack the 7z and then run the one click .exe inside but there is no .exe in the archive. Just the modem.bin, cache.img, image, factoryfs.img, and hidden.img. This would've been fine to try but of course Heimdall is every Mac OS users enemy and anytime I try to use the front end I get a 'missing firmware.xml' error and running it via command line just never connects to the phone.
Since Entropys return to stock package only has the factoryfs.img and zimage, sounds like I need to find a complete tar file that has all the other parts that creepy's has in it..
Last thing I did before going to work was updating the USB drivers on my Win 7 laptop to see if that would help, but since I can only use my laptop via Remote Desktop Connection from my Mac (display is dead) I had to do a Windows Update so I could get the laptop to restart (which I don't think you can do through RDC unless I missed it), and I had to run to work before it finished..
And I was STILL 10 minutes late hahaha!
So the laptop JUST got rebooted now that Im home, Im going to go see if theres also a newer version of Odin, and Im gonna go dig through the Download Repository and also check that Samsung Firmwares site to see if I can find myself a complete tar ball of the stock 2.3.4 firmware..
Ive got Saturday off finally so if I can't get it flashed and fixed by then I think Im going to bite the bullet and just take it to an ATT store and see if they'll swap it. Hopefully theres no 30 day policy, because Im pretty sure my Blackberry crapped out on me about 2 months in and they had no problem sending me another in the mail.. I REALLY wish I had my MyBackup done on my external SD card and not the internal one.. Gotta put another 40 hours into grinding in all my Zenonias to get back to where I was hehe..
Click to expand...
Click to collapse
Add me on gtalk and we can see what we can do [email protected]
At this point I don't know if anything will help heh.
All it will do is either sit on the GS2 boot screen, or it will go into Download mode.
Download mode though, no luck so far. Odin just won't flash it for some reason. It sees it, the COM port box lights up yellow, but the minute you hit Start, it just goes right to that error message I posted above. After this, I have to close both Odin and disconnect the phone and reboot it into Download mode.
I went through the Download Repo. Tried I777UCKH7-CL503881-Full.7z, and even the param.ifs by itself but everything just gives the same result. I didn't try Entropys DD though since I was running the stock ICS and didn't want to really mess anything up. Only thing I can think of left to try is flashing Task/Fennys CWM modded stock ICS kernel but after all this I doubt its going to work. I tried the stock rooted GB kernel earlier and it didn't bother flashing either.
Am I maybe connecting it wrong? I have the battery pulled and am going into Download mode by holding the vol buttons and connecting the usb cable to the laptop. I don't want to kill the battery power I have left as it won't charge now either. Basically I just fire up Odin, connect the phone and put it in Download mode, select my tar file and put it in the PDA slot, hit Start and go.. Should I be doing anything differently??
Whenever I've had a problem with Odin like that, it has always been that some partition got flashed wrong/partially/corrupted, and the only fix was to reflash the damaged partition. As long as Odin is seeing the phone, then it must be either a software/firmware problem or a hardware problem. I'm still thinking it is firmware, but it seems to be outside my experience.
I havn't been playing with ICS yet, but I have noticed that there have been a number of reports similar to yours, where people have flashed some flavor of ICS. This supports the idea that it is firmware. I have always understood that if the problem is firmware, and if the phone can boot into download mode, it can be recovered.
Yeah Im wondering if I should try flashing the PIT file I have for the phone, but I don't know crap about partitioning these things and didn't want to really mess it up.
Guess at this point its worth a shot. I was about to go sit and chat with the warranty folks at ATT (mines a refurb so Ive only got til the end of the month before warranty s up). Maybe Ill try the pit file and let Odin repartition the thing. I can't flash a firmware back onto it anyways.
EDIT: Holy crap progress.. I flashed the stock secondary boot loader with Odin (in the Bootloader slot) and that actually flashed. Now I just reconnected it and decided to try the ATT ICS leak one click from Rootzwiki and it appears my phone is now flashing!!!!! As long as my crap is still on the internal usb storage today is gonna be a good day hehe! Yep all is well so far! Phone just rebooted and its now at the ICS setup screen! WOOHOO!!! Crisis averted!! Thanks guys for the comments and help! Creepy thank you for reminding me we have that repository!!
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.