Related
I'm new for Galaxy S and I just rooted yesterday!
It was working fine and today I changed the system font styles.
And then problems have started!
I just rebooted the phone and then when the Samsung logo coming on, it stopped. so I did hard reset but nothing different.
So I searched google and found Odin way.
I followed the steps, it passed, then all I got were bunch of "force close" msg. like loop of force close!
so I tried Odin few more times, and then I was told to try with Vibrant Odin then I might get an error after that try Fascinate again.
So I did it.
Then more probems!!
When I turn on the phone, first thing I see is GT5000 something whatever for the Vibrant model name, and then I see Verizon Wireless.
Sometimes the phone just keep blinking( screen goes on and off and on and off)
so I turn off the phone turn back on, and then Im not able to make phone calls or network (airplane mode is on and I'm not able to turn it off)
I'm so stuck here.
Is there anyone who can help me??? PLEASE!! HELP ME!!! =[
Did you odin with phone or pda
Sent from my SCH-I500 using XDA App
I did it with PDA !!
sounds like you flashed vibrant firmware on your fascinate or vice versa...either way bad move
Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.
RacerXFD said:
Yea, if you can somehow shoe horn the modem.bin, and falling up's fascinate images, you may be able to recover.
But if you flashed a rom from a different device, you may not be able to recover at all...
This is exactly how I would try to fix assuming that you didn't install voodoo.
1. Wipe in stock recovery (not in cwm, for some reason cwm recovery doesn't wipe)
2. Find a modem.bin for the di01. Flash that using odin.
3. Flash the system dump for di01.
4. Flash the kernel for di01.
5. Flash stock recovery as well just to be thorough.
If that works, then you should flash cwm recovery in odin and root again.
Click to expand...
Click to collapse
good luck getting your phone to work again...^ that *should* work for you
but really people this is about the 500th thread on people flashing the wrong firmware on phones...geez
Yep, there are stickies for this. Maybe we should write a guide so that no one does it again. Wait, they already exist...
What's with all these threads? ..
How hard is it to read the instructions first before doing anything drastic?
http://forum.xda-developers.com/showthread.php?t=867648
This should help you. I fixed practically the same problem with this.
It's a magic wand, that'll take you back in time when you had your virgin unrooted fascinate
I have a huge problem.
I rooted my wife's (yea...my wife's...) Fascinate last night. The root method I used worked like a charm. I installed ROM Manager. Again...no problem. Flashed ClockWork Mod no problem as well. I selected "reboot to recovery" to do a nandroid as I've done on numerous other phones. In fact, ALL of this I've done on numerous times on half a dozen different phones.
When it rebooted, instead of it being in Nandroid, it was in the regular stock recovery. My stomach sank...lol
It would just reboot...that's it. Is there a loop with the fascinate? How do I get out of it if so?
At one point, the phone wouldn't do ANYTHING...all that would happen when I plugged it in was a little computer and cell phone would pop up on the screen. No recovery, no nothing. So, after lots of digging and reading, I found the files here that I thought I'd need to reflash the system using odin. I got the /system file, the kernal and the recovery. I flashed the kernal...worked perfectly. Flashed the recovery...again, perfect (and recovery is back but still in a reboot loop...) When I try the .tar.md5 system file, it says md5 is invalid so I changed it to a straight .tar file and it worked all the way up to the very end, then it stops. That's it.
I just need the phone to work again for my wife. I don't care if I even flash a new custom rom (which I can't fine one of that works!) or if it's just simply restoring the stock system files.
ANY AND ALL HELP GREATLY appreciated, guys. Thanks!!
To get to cwm, you have to select "apply update.zip" from stock recovery. This is how fascinate and a few other galaxy s cwm works. Also don't ever delete the update.zip file from sd card.
But to start out....
Step 1: Start with Odin:
http://forum.xda-developers.com/showthread.php?t=782204
A. Flash system and pit together
B. Flash kernel
C. Flash recovery
*Important note: in Odin, always use PDA!!!! Using phone will cause huge issues.
Step 2: Flash cwm:
http://dl.dropbox.com/u/458252/CWMrecovery.tar
*note: this is an Odin file, again flash using PDA
Your phone will end up stock, rooted and with cwm.
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Rooting aside if you want to just fix it, I can help you with that. Nothing more though. Interested?
Sent from my SCH-I500 using XDA App
rmp5s said:
That's very interesting. Here's why:
A) It tried to flash the update and the update failed.
B) My Vibrant didn't require this step.
So...as I was typing that, I had the tar.md5 downloading again. Apparently 4th time was a charm because it worked and I'm back up and running.
Thank you all SO MUCH for the STUPID fast replies. Very very cool!!!
Click to expand...
Click to collapse
What do you mean for the "stupid fast replies"?
tats_06 said:
What do you mean for the "stupid fast replies"?
Click to expand...
Click to collapse
I think he means that your replies were just as fast as geeknik's kernel. The only other interpretation is that although your replies were quite quick, unfortunately they were also stupid. But thats obviously not true, so it must be the former. ;-P
Sent from my SCH-I500 using XDA App
I think some of us are showing our ages, "stupid" is the new "awesome."
Sent from my SCH-I500 using XDA App
Hey dont worry i had same problem
http://www.mobilephonenews.info/and...fascinate-restore-is-it-really-that-easy.html go here and follow instructions!!!
then update phone manually to get latest update!! might take a few times or many times because it failed to get update many times but eventually youll get it!!
goodluck
Sherwood, in his case he needs all Odin files, not just system.
Fallingup was first to put this up, credit to his post!
Download:
Odin: http://dl.dropbox.com/u/458252/Odin%...in3 v1.3.exe
Odin Restore file for /system: http://dl.dropbox.com/u/458252/Odin%...System.tar.md5
Odin Restore file for kernel: http://dl.dropbox.com/u/458252/Odin Files/Stock-i500-VZW-Kernel.tar.md5
Odin Restore file for recovery: http://dl.dropbox.com/u/458252/Odin%...covery.tar.md5
PIT file for use in Odin Restores: http://dl.dropbox.com/u/458252/Odin%...00-VZW-pit.pit
Yea...I mean it's almost stupid how fast I got good, meaningful, educated replies.
In other words, you guys kick ass. Thanks again!!
similiar issue, please help me out.
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
aabfalter said:
spent 90% of the last few days of my life trying to "unbrick" my phone. i kno some of you will argue that its not really bricked but hell, a screen lighting up does not mean its more useful than a brick. anyway my problem is as follows:
the one and only thing my phone will boot to is download mode. absolutely no recovery. i have flashed via odin the stock modem system and recovery files countless times, sometimes successfully sometimes with error. even when doing so succesfullly the phone gains absolutely no functions. still download mode or black screen. only real thing i can mention that may have led to this issue is that i flashed stock kernel over voodoo lag fix without doing anything to it first. Please help.
Thanx
Click to expand...
Click to collapse
sam problem here, i can get to cwm recoery and thats it. someone please help
justin94 said:
sam problem here, i can get to cwm recoery and thats it. someone please help
Click to expand...
Click to collapse
I had the same problem when I flashed the non-voodoo over voodoo and spent hours trying to fix the boot loop. I followed the instruction here http://forum.xda-developers.com/showthread.php?t=782204 but still running into the boot loop (recovery mode) then I flashed with the file from here via ODIN http://adrynalyne.us/files/kernels/DI01package3.tar.md5 and it restored my phone back to factory. From there you would have to do the root procedure again. Hope this helps.
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
The update.zip to get to clockwork??
http://sharesend.com/g2jbl
First time I've ever hosted a file so let me know it if works lol.
Sent from my SCH-I500 using XDA App
This could be one of the rosiest phone ever to unbrick, unless you are a noon of coarse.
Sent from my DROIDX using XDA App
tswtech2 said:
anyone know where to get the update zip besides the dropbox link thsat has been dead forever??? every site i hunt on post that link. is there anywhere else to get it. both my pc get c++ runtime floating point errors when i open odin so i cannot flash with that. so i want to use the update zip but cannot find it
Click to expand...
Click to collapse
There is no update.zip method to unbrick. You will need to re-download a working copy of Odin or figure out how to make Odin work to do a factory restore with it.
Download the di01 complete package and use pda in odin to restore it.
http://forum.xda-developers.com/showthread.php?t=867648
borked up the fascinate whilst trying to update to the devs 2.2.
i know exactly what i did wrong. i was running voodoo5, and i clicked to disable lag fix, but i forgot to restart to let it *actually* disable before trying to load the new stuff. STUPID!
when that happened, it hung on samsung screen, then after battery pull all the phone will do is boot loop.. samsung screen, then goes to robot and screen says says "wiping cache, data, ect.." and then back to samsung screen to reboot and reboot.
i have literally 30 tabs open with articles from here and other forums, nothing seems to be working. here is what i have tried.
1. tried booting back to red cwm and playing with the lagfix (enable and disable again) to see if it would work, no go. i ended up losing red cwm - had to ODIN red back.. i cant get green to flash.
2. tried flashing DL09 both the full package and each individual part via ODIN
3. tried flashing the stocki500system.md5 (from the board) and kernel via ODIN, and nothing.. same boot loop. everything i have flashed via ODIN still gives me a boot loop..
4. tried to connect via ADB but it wont let me access the phone.. NOTE: i just downloaded ADB as a last resort and know nothing about it..
the only thing i can seem to do is get to red cwm. i have several backups in the restore section, but none of them seem to work - either i get a "no file found" even though i can see the file(s), or i get an error after it does load that says ".android_secure.img not found. skipping restore of /sdcard/.android_secure"
any ideas?
Okay follow these steps. Make sure you follow them step by step. Even though you have the lagfix installed this removed it for me.
http://forum.xda-developers.com/showthread.php?t=782204
Place the PIT file where it belongs. Then ODIN the system, kernel, and recovery in that order. Don't restart the process every time. Just ODIN them one after another.
thank you very much for taking a moment to answer. i did follow that thread, however
i managed to get the stocki500 recovery but the other files (recovery, PIT) are all 404 not found errors.
ive tried that stock md5 and it still boot loops. i actually have that tab open from when i tried that route..
any other ideas and thanks again
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
BSayre18 said:
Thats why its not working. Try this restore by adrynalyne. The file is there and everything is in one. Just ODIN in the PDA section. This should work.
http://forum.xda-developers.com/showthread.php?t=867648
Click to expand...
Click to collapse
downloading now.. thanks for the point to this file.. i hadnt found that one yet
no problem. it should work out good.
mailaliasgar said:
I got myself into a bit of pickle too. Kept getting errors on the new_cwm file. After numerous attempts. I figured out the file hadn't downloaded correctly and the archive was damaged. Folks who havent installed Froyo yet, do yourself a favor and check the files before you save it to your sd card.
Click to expand...
Click to collapse
i soft bricked doing that with a corrupt file before.. however that time i was able to restore using my backup.
this time, every time i try a method, it kicks me back to boot loop. if the file that im downloading now doesnt work, i will have to try and figure out ADB as a last resort..
thanks much for the help!
BSayre18 said:
no problem. it should work out good.
Click to expand...
Click to collapse
problem
thank you for all your help
mrjake1970 said:
problem
thank you for all your help
Click to expand...
Click to collapse
So this worked for you? You just re-rooted as normal?
def
Thank you all for your help. i applied all the info i got here, and one of them worked it finally took the ODIN flash to stock and i recovered into FROYO from there.
seriously thank you all.. its great that the community is so supportive
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Joe T said:
I did the exact same thing a couple of days ago, and recovered a similar way, odin back to D101, flashed DL09 & superclean, then restored a backup, then disabled voodoo and finally flashed DL30. I've got a couple of questions.
1: Is voodoo completely off my phone or is it just disabled (is there a difference)? When I apply update.zip from the blue recovery I get green cwm.
2: Each time I backup, restore, flash a different rom I apply update.zip, then from green recovery I flash "new_cwm.zip". Is this necessary?
Click to expand...
Click to collapse
i followed all the hints i got, and i think that the one i got about formatting helped me get out of the boot loop from hell.. it finally took my flash from ODIN, it wouldn't until i did the format(s)..
mind you i am NOT an expert, however from what i read and talked about offline, voodoo is still resident on your phone but disabled (check to see if you have the voodoo file still on your card).. if DL30 is running fine, you are ok..
from what i have read, yes.. the new cwm is required in order to get it to mesh properly with 2.2 leak.. i havent had any issues and i loaded that as well.. from one of the posts i read, if you are a serial flasher, then you need to make sure that not only you download the new cwm zip, but also should have deleted the entire clockworkmod folder from your card for best results..
I love this threadd.... I did the same damn thingg...
Sent from my SCH-I500 using XDA App
You guys are not alone. I'm just glad the peeps that know what's going on have the patience to put up with us.
Sent from my SCH-I500 using XDA App
adrynalyne's di01 odin package covers a multitude of sins.
upsidedownaaron said:
adrynalyne's di01 odin package covers a multitude of sins.
Click to expand...
Click to collapse
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
godihatework said:
It will literally bring any phone back from the dead as long as its a software issue. I recommend keeping the di01 package, samsung drivers and Odin 1.3 on your computer at all times...
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
ABSOLUTELY!! I have those on my computer at all times, adrynalynes d101 brought me back a few times.
Sent from my stock 2.1
unrooted, fully bloated (for now) Fascinate
I rooted my fascinate, flashed CWM with Odin, and installed one click lag fix. Everything was working fine for a few days, but today I started getting a lot of force closes, and then it just stopped booting. I can't even boot into CWM recovery, it won't access the update.zip file on the sd card. It won't boot to the OS, and just reboots to the stock recovery whenever I try to do anything. I have backups on CWM, but I can't access them. I'm trying to restore it to stock, and start over, but as I said, I can't access CWM, or get to the OS at all. Please help me get this thing running again.
Thanks,
Anthony
Flash one of the All in One Odin packages from the Development forum and you should be good to go.
And never touch OCLF again.
Any particular one I should be looking for? I was looking around, but the only one I saw had a busted link, and I couldn't download the package.
Downloading the DI01 and DL09 Odin packages. We'll see how that turns out. Use PDA option in Odin correct?
diesel43078 said:
Downloading the DI01 and DL09 Odin packages. We'll see how that turns out. Use PDA option in Odin correct?
Click to expand...
Click to collapse
Yes
And only PDA
Sent from my SCH-I500 using XDA App
DL09 flashed with Odin. Seems to be working great. Thanks for all the info fellas.
Hi,
I have been searching and searching. I tried to install a kernel to my phone, its been forever so i don't remember which one.
It just reboots every 5 seconds without any screens coming up. I can not get into recovery mode
I can get into download mode and have flashed stock I337UCUAMDB_ATTAMDB_I337UCUAMDB with odin, but it doesnt fix anything.
What can I do to get to stock recovery and fix my phone?
What happens if you put it on download mode and then cancel with vol down
It falls back into the bootloop of restarting every 5 seconds with no screens coming up. No entry into recovery.
And if you pull the battery and put it back in does it try to boot?
What firmware were you on and was it loki'd if you were on mdl?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
megatilter said:
I have taken the battery out and replaced it. It does not automatically try to boot. After pressing power it goes into the same boot cycle. Also, thank you for your quick attention!
Click to expand...
Click to collapse
When did it start doing what's it's going. Did you do anything before hand? Do you know what firmware you where on before you tried odin? Was it mdb?
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
megatilter said:
"What firmware were you on and was it loki'd if you were on mdl?"
Previous to my obvious blunder with the kernel download, I was using goldeneye rom from android develepment, sucessfully.
Dont know if that answers the question but i have also tried to flash AMDL with odin but have the same results.
Click to expand...
Click to collapse
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
jd1639 said:
When you used odin did you only have f.reset and auto-reboot checked and flashed the md5 file in PDA
Click to expand...
Click to collapse
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
I think you've broken it too. Sounds like you flashed the wrong kernel and at that point you were more or less hosed. Look into jtag, mobiletechvideos.com. They can probably fix it. It'll cost you $60.00 +
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
i've never seen a kernel hard brick a device or corrupt the recovery partition. i also rarely see a user flash a file and not remember what they just flashed. he/she possibly flashed an incompatible kernel or flashed a non-loki'd kernel without flashing loki-doki. either way, recovery would still be accessible to correct this issue. i feel that there is more to this.
OP, see jd's jtag post above.
megatilter said:
I have done it multiple times, perhaps panicking, I checked the re-partition button. I have tried to get a PIT file downloaded and tried to use that.
However, this behavior was happening before I did that. It started boot looping as soon as i tried to use TWRP to flash the kernel (I know i am an idiot, and didn't read first). As soon as this started happening, that's when I immediately tried to flash AMDL (exactly as you described with only those options checked) through odin and it didn't do anything different. That's when i tried other options. I fear i may have broken my phone. Again thank you for your attention.
Click to expand...
Click to collapse
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Great news! You got lucky, make sure you read and learn on xda. And always know what you flash.
megatilter said:
Well I finally was able to get Kies working and did a firmware update. That gave me back regular recovery. Now Im stuck at bootloop att screen.
I then re flashed AMDL stock via odin and VIOLA!
Im back to stock baby!
And from there ill probably go back to Goldeneyes Rom and never think about this ever again. Thanks for your time. My phone is working again!
Also
Thank you for helping me at least by giving this thread attention. So much appreciation to the fine people here at XDA
Click to expand...
Click to collapse
Care to share how you got Kies working? I have a similar problem and I can't get Kies to recognize my phone.
Fix!
So What you gota do
1. Pull Out Battery Put back in
2.Go To Download Mode
3. Download The TWRP.tar For Your Phone
4.Run Odin as Admin, Tick Pda, for pda select the TWRP.tar
5. Hit Start, Then Pull Out battery put it back in
6.Get A Micro Sd And Put The Cyanogenmod Rom, and the gapps the ones for your phone
7.Insert microsd in phone
8. Boot Recovery and go to mounts and mount the microsd
9, Go Advansed, file manager, ext sd, And Copy the cyanogenmod and the gapps to internal storage
10. Flash the cyanogen mod and the gapps. DO THIS PART CAREFULLY OR MIGHT HARD BRICK!
11. Reboot And youl boot to cyanogenmod! OH yeah! Replay if this helped or if you have any problems