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
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 was wondering how it was possible to brick your phone (which somehow happened to me..) just by trying to get into CWM Recovery by doing the 3 button press.. As it is possible because it happened to me earlier today I was just wondering if it was a step that I did wrong.. Also I had nothing installed except flashing the Froyo EB01 modem which flashed successfully and than reflashed cwm recovery all which worked though I forgot I had to reboot fast or else samsung would replace cwm. So when I flashed a second time and than tried rebooting into cwm that's when it got stuck and bricked..
I got it solved earlier thanks to Adranalyne.
If anybody needs his thread for the all in one odin:
http://forum.xda-developers.com/showthread.php?p=9711053
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Shadowchasr said:
Ensure it's not simply blank screen...hit search soft key when it ' should' go into cwm
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Naw, it was stuck on the samsung logo screen for an hour-got bricked. But i fixed it .
Can someone explain how exactly you fix it? I am having that problem as we speak...
sengokubattosai said:
Can someone explain how exactly you fix it? I am having that problem as we speak...
Click to expand...
Click to collapse
Odin it back to stock. Either Dl01 or Eb01. Both files include everything for you to recover your phone ans be able to boot back up past the samsung logo.
Taking it back to EB01 every time can be a bit extreme. There are CWM tar files that you can use to just flash CWM with Odin. I've used them when my phone would not boot into recovery. Remember the best way to get to "Download" mode is to pull the battery and while holding the down vol button plug it into your PC. I know thats common knowledge but it's always good to put it out there. Other techniques can prevent Odin from establishing a connection.
I've even seen complete Super Clean tars up to 2.6. I don't remember where but when 2.7.1 bricked my phone I just used Odin to flash a 2.6 tar and my phone was back to normal. Now I use that ROM image instead of EB01 when an update fails.
I would stress that any ROM compiled by someone else is not going to be endorsed by the Dev that created the update. I just took a chance because I was already down and it worked great.
I just bricked my device I guess.
First off flashed:
http://forum.xda-developers.com/showthread.php?t=1162302
TouchWiz UX for 10.1
- Cleared all (factory reset)
Which was working nicely, but then I needed some extra kernel modules, so I installed:
http://forum.xda-developers.com/showthread.php?t=1175299
3.1 Galaxy Tab Wifi OC1.6
- Cleared all (factory reset)
It booted at first, but then rebooted and eventually went to black screen. Now powering up won't work.
So yes it really won't come to life out of it's own.
-------------
My first step: Hang it to a PC
Well it recognized the tab, and was asking for the APX driver, which I found over here: http://forum.xda-developers.com/showpost.php?p=11901016&postcount=75
Which installed correctly, and is recognizing my device (for now).
Who can help me further (it is possible to backup and restore using nvflash)
-- Update 0x4 error...
NVFlash seems to be a dead end. You can't use it without sbk, which we don't have. Any more suggestions?
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
sassafras_ said:
Use Odin to flash CWM recovery (if you haven't already), then reinstall a ROM using Clockwork Mod.
sassafras
Click to expand...
Click to collapse
Been there, done that... I've flashed all through CWM recovery, always made a backup, but it doesn't go through the bootloader anymore, so I can't access the recovery, nor the download mode (for Odin flashing).
The only thing I can access at the moment is that stupid NVFlash, and since my device is I/O locked, I can't flash anything.
tmbk said:
Could be "sleep of death" there are other threads on here about it. There are various ideas about waking it up, but just letting the battery discharge and then charging it worked for my (unmodded) tab. Admittedly that is a little tricky when you can't power it on in the first place!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I will check on this. It's the only way to fully reset my device. Since it is I/O locked, it can't have harmed my bootloader or CWM recovery.
I made sure before flashing that the MD5 checksum was right (which it was). The only thing it flashed was a kernel. Well I will drain my battery and check if it is possible to boot it up after that. Else I buy a new one
Exact same thing happened to me.. ran poitee kernel over OTA update.. killed everything but nvflash + all black screen.
Cannot get it to flash w/ bootloader.. Have 2 days to RMA and I really don't want my data out there in the event this thing comes back up after the battery dies.
PS- My unit was bootloader unlocked and rooted.
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?
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