So i was trying to flash a new rom onto my vibrant and the instructions told me to mount card and format SYSTEM, after doing so my battery popped out (lid was off) i placed the battery back in but it wont boot up. STAYED AT VIBRANT PAGE
i thought of using odin to recover to eugeune froyo bit its not doing anything...its stuck on set pit file...
any suggestions??
thank you!
Reparation
Sent from my SGH-T959 using XDA App
Had the exact same problem. Went to Tmobile and everything to get the phone exchange but it was out of warranty. Then i did this and it worked like a charm: taknische.com/2011/12/14/how-to-unbrick-a-hard-bricked-samsung-vibrant/
What rar file u flashing? Stock or the j16 rar
Sent from my SGH-T959 using xda premium
I was using Bionix and it was so freaking slow, so I attempted to flash stock on it and forgot about the different filesystems, and that hardbricked my phohe like in the article. So I did the instructions in the article and then I flashed stock deodexed Froyo, choosing "Re-partition". Then I rooted it and flashed a kernel with lagfix to make it a little faster.
So long as you can get it to turn on in ANY fashion (anything on the screen) it will flash.
If you can't get Odin to recognize the phone or flash it (e.g. it fails during operation and hoses you) either use Heimdal or turn OFF your computer and start from zero with it. Samsung's USB drivers are flaky and will flip out on occasion which hoses your flashing attempts and leads to soft "bricks."
I've actually managed to recover from what I THOUGHT was a hard brick this way -- I couldn't get ANYTHING to come up on the screen for a while -- but eventually did manage to get the computer --> phone icon back up, and from there was able to flash.
Note that ALL of the flashes other than the ORIGINAL T-Mobile code are non-formatting, non-wiping flashes. If you flash one of those over something incompatible (e.g. a custom rom) you will get a boot loop back into recovery that will not start. The solution is to flash back to the ORIGINAL T-Mobile code and then go from there.
Make sure you are using T959UVJFD.tar and 512.pit file when you flash with odin when having these types of issues. Just be ready for the really loud and annoying t-mobile chime upon bootup.
Man I hate that chime with a passion.
Sounds like the issue may be on Odin's end. Did you plug your USB cable into your computer and open Odin before plugging into your phone?
Related
had my epic rooted for a while then went to install clockwork with the "all-in-one" epic.aio.v1.13 file. It successfully installed Clockwork but I couldnt not boot into clockwork. So in the vain effort to try and keep the files i have i tryed flashing the SPH-D700 kernal, bare-min and odin hung, Now im trying to get the full factory reset files to flash with odin. are their any other ways to do this other than going all the way back to SPH-D700-DG27-8GB file? BTW when i start now the phone comes up with a phone dash dash yellow ! dash dash Icon. Im guessing I completely trashed this thing. Some one help me?
metalblaster said:
had my epic rooted for a while then went to install clockwork with the "all-in-one" epic.aio.v1.13 file. It successfully installed Clockwork but I couldnt not boot into clockwork. So in the vain effort to try and keep the files i have i tryed flashing the SPH-D700 kernal, bare-min and odin hung, Now im trying to get the full factory reset files to flash with odin. are their any other ways to do this other than going all the way back to SPH-D700-DG27-8GB file? BTW when i start now the phone comes up with a phone dash dash yellow ! dash dash Icon. Im guessing I completely trashed this thing. Some one help me?
Click to expand...
Click to collapse
You can still get into download mode. There us a d18 tar floating around. Flash that the odin
Sent from my SPH-D700 using XDA App
If it powers on then you still have hope. Hold qwerty 1 and the power button to boot into download mode and use this thread to flash back to stock. http://forum.xda-developers.com/showthread.php?t=773032
Epic 4g/Rooted/Epic Experience 1.2.02/Phoenix 1.45/Androdena-Galassia Theme
No problem just do this
metalblaster said:
had my epic rooted for a while then went to install clockwork with the "all-in-one" epic.aio.v1.13 file. It successfully installed Clockwork but I couldnt not boot into clockwork. So in the vain effort to try and keep the files i have i tryed flashing the SPH-D700 kernal, bare-min and odin hung, Now im trying to get the full factory reset files to flash with odin. are their any other ways to do this other than going all the way back to SPH-D700-DG27-8GB file? BTW when i start now the phone comes up with a phone dash dash yellow ! dash dash Icon. Im guessing I completely trashed this thing. Some one help me?
Click to expand...
Click to collapse
I have had your same problem my friend just hold 1 while pressing power on and get in download mode then just do odin again
This nice yellow arrow has happened to me bunches of times so don't worry!
When you get the dash yellow icon situation, the only way to recover is to flash back to factory with Odin3.
In case you haven't gotten it yet, here's the download link for the di18 stock tar:
http://www.multiupload.com/X9AB1U56JV
You can get back into download mode by doing the following:
* Close the Odin program
* Pull the USB cable and battery out of the phone
* While pressing both the 1 key and power button with one hand, replace the battery with the other. Download mode should immediately appear.
* Open Odin first, then reconnect the USB cable
* Load the di18 stock tar into PDA, reboot should be the only thing ckecked. Press start.
I wrote the all in one script, and would like to know what happened when you installed the clockwork mod. Tell me what OS you were using and what messages came up. The script should have detected if the install wasn't successful.
Sent from my SPH-D700 using Tapatalk
thanks for the help
Being the resilient person that I am, (as well as the impatient one). I found a stock Tar for DG26 and Flashed it to my phone using odin... it fixed it. Then i manually updated it... Had i waited for a response i would have known there was a .tar file with the DI18 update floating about... Thanks for the help though. This is a good forum with a good community.
metalblaster said:
Being the resilient person that I am, (as well as the impatient one). I found a stock Tar for DG26 and Flashed it to my phone using odin... it fixed it. Then i manually updated it... Had i waited for a response i would have known there was a .tar file with the DI18 update floating about... Thanks for the help though. This is a good forum with a good community.
Click to expand...
Click to collapse
At least quite a few people came to your aid... glad you've gotten it sorted. Feel free to post again in the all in one if you still want to install clockwork mod, I do my best to help as long as I'm online. You know what to do now in case something doesn't work out... It's happened to us all.
Interesting enough, I don't think I actually bricked the phone when I first installed Clockwork. Seeing as this is my first smartphone and my first foray into the Android universe, I am a bit of a noob when it comes to how things are done. Not realizing that clockwork Mod used a different button to engage items than the normal Samsung recovery platform, I had thought I had some how overridden the start up files to eclair with the All in one program.. After re-upgrading the phone back to DI18, I rooted then installed clock work again using the "AIO" program. (great program BTW). I encountered a similar error to what I had before, When I was in clockwork I was unable to leave by using the home button or even removing the battery, but I hit the back button and then figured out that the camera button acted like the home button would in the native Samsung recovery client. I think this was the case from the start. Just keep this as a story of warning if you ever are in my position, ask people before you think you've completely "bricked" or screwed something up, because there may be a simple solution. Anyways thanks for the help, I'm still learning all of this, though I've been using linux platforms for years (no ubuntu or mint, more Red hat and Debian.) so you'd think id be ok at it....
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
My brother and I both have a Vibrant. He broke his so I loaned him mine for a week. While he had mine (which I've upgraded to 2.2), he installed Android 2.1 Voodoo 4 on it. Little to say, after rebooting, the phone wasn't booting past the boot screen.
I've now followed some instructions from the forum, and have reflashed my phone with Eugene's non-bricking ROM through Odin. The phone boots up just fine now. However, I am trying to install ROM Manager on the phone, so I can reflash my recovery ROM (non Voodoo) - and the Android market tells me it can't install the app due to not having enough free space - though I have over 1GB.
I am guessing this is because the internal disk is still setup in the Voodoo file system, and just enough space was repartitioned for the OS to go back on.
Can anyone help me restore my phone?
EDIT: I've also tried flashing a different recovery ROM through ODIN (with repartition), which also wouldn't let me get past the bootup screen.
I'm taking a wild guess here, I seriously don't know, but did you click repartition in Odin? I think that's would work, but like I said, I'm not completely sure.
I didn't repartition for the Eugene rom fix (as per the instruction I read), but did when I tried to load another version ontop of that.
I was in the Voodoo chatroom, and was able to get some help. It sounds like I need to download a stock ROM and then reset my file partition to get rid of the EXT4 partition, and reset it all to the default.
I have Eugene's "non bricking" rom, but I don't think that's what I need. Can anyone point me in the right direction of what I need and how to do this?
Just search for the stock Odin images and flash back. They should be in a sticky. I would repartition as well.
I am trying to find a stock version I can ODIN flash. Do you know where I can get one?
http://forum.xda-developers.com/showthread.php?t=848737
I've gone through ODIN, done a reflash to the stock firmware, and repartitioned the phone as well.
Now, when I boot the phone up, I get the T-Mobile screen and the Galaxy S screen, and then the phone goes black (with no lights on) and doesn't go any further. My phone has been sitting on the desk like this for 20 minutes now.
I am wondering if this is like when moving to Voodoo, it takes a while to change the format to EXT4, is the phone having to go back to the default?
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
this thread might help
http://forum.xda-developers.com/showthread.php?t=848737
fatboy547 said:
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks fatboy, but I can't even flash back to stock. The phone won't boot up.
Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.
Have you tried restoring to DL17 and then re-upgrading to 2.2?
And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App
wait wait, is this on a Continuum or Fascinate?
Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out
okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.
Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.
huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.
So I was mucking about installing ICS on my fascinate and I've managed to thoroughly brick the device. It will not power on in any form from my perspective. No Download mode, no recovery nothing.
The steps that I took to get myself here
Installed Teamhacksung ICS Build 2 (Everything was wokring fine except calenders so I had to do a reinstall)
Did a Full wipe of all mount point via CWR and fresh reinstall including Google Apps v.5.
Booted fine went through initial setup.
Downloaded Glitch kernel 14 preview 2 for the i9000 ( Yes I know in retrospect it is the obvious wrong kernel )
Flashed Wrong kernel via CWR
Booted phone ( It started up just fine. But I had no Wifi and no 3G not panel buttons only physical worked. This is when I looked at the kernel filename again and discovered my mistake.)
Booted to CWR via power button menu
CWR was modified along with th glitch kernel install. ( It is unable to mount sdcard of any local resource.
I figure okay my bad lets odin
I put the phone in download mode
I flash the atlas_2.2.pit and the CWM4 tar designed to work with CM7 with the following options.
----Odin 1.83
Re-partition
F Reset Time
Atlas_2,2.pit in PIT section
CWM4_for_cm7.tar in PDA Section
-----
Flash is successful I power down phone by pulling battery and unpluging from usb
I put the battery back in to boot into recovery and the phone will not power on.
It will not enter download mode via volume-down method or via 301k jig
This phone is dead as far as I'm concerned.
Any help / ideas are appreciated.
I would try a new cable. If that doesnt work i think your only option is the Unbrickable mod.
http://forum.xda-developers.com/showthread.php?t=1288093&highlight=unbrickable+mod
Not that it will help but I believe your mistake was in using the pit file without flashing a rom. You repartitioned your device and then did not install an os essentialy.
Edit: you should also pull the battery while flashing with Odin.
On a possibly helpful note, have you tried connecting to Odin since then. I know on the Charge people have reported entering download mode but having no visual conformation of it (ie: blank screen but Odin recognizes the phone). Might be worth a shot.
We all make mistakes, I hard bricked my wifes Charge because I keep all my Odin files together, clicked through to quickly and ended up flashing stock i500 files to it instead of i510 files.../facepalm
Sent from my SCH-I500 using xda premium
Ya I've tried connecting to Odin even though not visual representation for Download Mode is there. The Fascinates do that as well from time to time. The thing that gets me is that even if the partition structure is totally hosed the phone "should" be able to get into download mode. I disassembled it last night and will be attempting the Unbrickable mod once a new tip comes for my soldering iron.
I have no clue why you used Odin and repartition v2.2 pit without flashing a stock ROM. where you got the idea to flash a cwm file instead of a .tar ROM file is beyond me.
Now that i have given you some scolding. unless one of fascinates geniuses comes to your rescue. You're only option is to use unbrickable mod on you're phone. And you best follow directions on that mod a lot better than you have on this past endeavor. It does involve soldering your processor pins, so i wish you luck.
Sent from my SCH-I500 using xda premium
Have you tried making/buying a jig to trick the phone into Download Mode.
I found these 2 threads:
Jig 1
&
Jig 2
I found these on the captivate forums when I needed it and it works pretty well, but buying one is much easier.
If you arent familiar with what I'm talking about, putting 301k of resistance on the 4 & 5 pins on our phones will put the phone in Download mode, which is what a jig will do for you.
They are also sold on Ebay, and on MobileTech Videos.
Hope this helps!
hesh.monster said:
Edit: you should also pull the battery while flashing with Odin.
Click to expand...
Click to collapse
Flashing with the battery in is no different than flashing with it out really. The reason all Fascinate tutorials say to flash with the battery out is to prevent recovery from getting over-written should the phone reset and boot normally after flashing.
Also, I would say try a download mode jig. Since you flashed the i9000 kernel, it could be doing something odd that a Fascinate wouldn't normally do. If it was a MTD i9000 kernel, hopefully it didn't re-partition and wipe out or corrupt the bootloader/secondary bootloader.
imnuts said:
Flashing with the battery in is no different than flashing with it out really. The reason all Fascinate tutorials say to flash with the battery out is to prevent recovery from getting over-written
Click to expand...
Click to collapse
I am aware of that, just saying it doesn't hurt to follow directions.
Sent from my SCH-I500 using xda premium