Fascinate won't turn on - Fascinate Q&A, Help & Troubleshooting

Hey guys, I have this Verizon Fascinate that I used to use when I was wayyy younger. Back then I was using it, deleted a wrong folder when I was browsing through the My Files app, and it hasn't turned on since. If I try to power it on, all I get is a white screen that continues to flash. I've looked at all of the other threads about resetting the Fascinate to stock with Odin and Heimdall, and I've tried the steps given there, but it hasn't helped. I can still set it to download mode, and I can still charge it with the charging battery screen, but no recovery/boot up what so ever. I tried flashing multiple stock firmwares in Odin with the stock pit file or the atlas pit file, but this is all I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The phone wasn't rooted before and didn't have any sort of custom rom on it. Any help would be greatly appreciated by those still browsing these forums.

MexicanBRUHH said:
Hey guys, I have this Verizon Fascinate that I used to use when I was wayyy younger. Back then I was using it, deleted a wrong folder when I was browsing through the My Files app, and it hasn't turned on since. If I try to power it on, all I get is a white screen that continues to flash. I've looked at all of the other threads about resetting the Fascinate to stock with Odin and Heimdall, and I've tried the steps given there, but it hasn't helped. I can still set it to download mode, and I can still charge it with the charging battery screen, but no recovery/boot up what so ever. I tried flashing multiple stock firmwares in Odin with the stock pit file or the atlas pit file, but this is all I get:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
The phone wasn't rooted before and didn't have any sort of custom rom on it. Any help would be greatly appreciated by those still browsing these forums.
Click to expand...
Click to collapse
To do it, get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.

Related

[HELP]Stuck in Download Mode

I've searched everywhere, I am not a noob when it comes to root/flashing/odin, but I am at a dead end here.
I picked up my phone today to see it at the Samsung i-9300 boot screen, just sitting there. I popped the battery and tried to reboot, no go. Tried to boot to recovery, won't go past that Samsung screen. I can boot to download mode, and odin recognizes the phone, but when I try to flash anything to the phone, odin freezes at SetupConnection.
Does anyone have any ideas?
Output from odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXDLJ4_I9300OXADLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
This is a stock firmware downloaded from SamMobile. I have tried just a twrp recovery to try to boot to recovery and that does not work either. I found a few .pit files and tried to re partition with those, hoping that would help, but no luck. Running windows 8, also tried windows 7 with no luck. Has anyone ever run into this?

[Q] [SC-02C] Japan NTT DoCoMo Galaxy S II refuses to flash

Here's the rundown of what I did:
Using Odin 3.0.7 on Windows, I flashed a kernel from Sakuramilk, don't quite remember which one. The flashing succeeded according to ODIN but the phone wouldn't boot and I would get the Docomo Logo with the yellow triangle.
Following that I downloaded the stock kernel from Sammobile and tried to flash that (SC02COMMP4/SC02CDCMMP4), but since it didn't work I tried to flash + re-partition using a stock PIT file I found at some thread. The re-partitioning went through but the flashing failed half-way. The result of that was that now, when I try to power on the phone there's no logo, only a message on the top of the screen in green text:
'nps_fail_ntt.jpg' draw failed
Click to expand...
Click to collapse
my guess is that my re-partitioning with the PIT file broke the partitions and now it can't find the logo (or any other file).
So this is an almost bricked phone that can go into download mode and is seen by odin but now odin can't upload anything (I've tried a few stock kernels from sammobile). I always get:
<ID:0/003> Added!! <---- phone is .. recognized I guess...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SC02C-JB-KBC-20121031#36-SAM-odin.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Any advice on how get this phone flashed back to it's original state or any other working state for that matter would be very much appreciated.
Turns out that Odin 3.07 I had wasn't working well with sc-02c. I used Odin3 v1.85 and the flashing worked!

[Q] Samsung Galaxy SIII Soft Brick Desperate Situation

Hi There,
After using temasek's stock android rom a while without any problem my galaxy s3 won't turn on anymore. About a month ago my S3 suddenly shutted down and now I get a bootloop where I only see the samsung logo reappearing every 5 seconds. I can't go into recovery mode, only into download mode. So my phone is soft bricked i supposed.
I tried almost everything, I searched for weeks for a sollution on XDA and I didn't found anything that could help me. So now i'm asking you guys because i'm a little bit desperate and i'm using my old nokia 3310 for a couple of weeks now.
I tried to reinstall my original firmware which I downloaded on sammobile with odin but there is always some kind of error.
I tried several versions of odin (new one's, olders one's) And still no progress.
Here's the log from odin v 1.85 :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_PHN_I9300XXALE8_I9300PHNALE4_I9300XXLE8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I just checked off the box "PDA" and "AUTO REBOOT" and "F. RESET TIME" . When I use a pit file this is the log of odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> GT-I9300_PHN_I9300XXALE8_I9300PHNALE4_I9300XXLE8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I'm sure that i used the right firmware, I've tried different pc's, i've also tried differend firmwares... Always a damn error in odin...
Can anyone help me?
ID:0/006> There is no PIT partition.
If you use a PIT file it has to be the right PIT file .
jje
JJEgan said:
ID:0/006> There is no PIT partition.
If you use a PIT file it has to be the right PIT file .
jje
Click to expand...
Click to collapse
I used the GT-I9300_mx_20120329.pit file which was suggested in this topic: http://forum.xda-developers.com/showthread.php?t=1894548&highlight=stock+firmwares
Weird. Sounds like SDS. What kernel were you using aling with Temasek s ROM?? And which version??
dhirend_6d said:
Weird. Sounds like SDS. What kernel were you using aling with Temasek s ROM?? And which version??
Click to expand...
Click to collapse
Version 77 and his kernel!

Please help i bricked my phone while installing another rom. Always failed

First of all,I did everything step by step to install a custom rom to my Samsung Fascinate but odin says "Setup connection....
"All threads complete (success 0/failed 1)
Then,after my phone got bricked,I tried installing a stock rom, but the same thing happened :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP NEEDED I AM REALLY TENSED :crying:
Did you ever find a solution to your issue? I am having the same issue but I paid OneClickRoot to Root my device for me and they screwed it up and are pretty much throwing their hands up about it. I am still giving them the chance to make it right but my patience are wearing real thin.
To save you as long as it is not hard bricked, follow these steps.
Get this file.
https://gofile.io/?c=tJd0Pd
Then get odin v1.85
https://gofile.io/?c=WHkZHO
Launch odin with admin powers (sudo/su for linux, or whatever).
Then click PDA and select the tar.md5 file and start.
And please make sure you got the drivers and that a COM port does show up in odin.

Having trouble restoring stock firmware to my Samsung Galaxy Tab S3

EDIT, SOLVED: I downloaded the most recent verson of Odin (3.14.1) and was able to get everything flashed. I was also using the normal CSC file and not the HOME_CSC file, which may have also contributed to the problem.
So I wanted to try out putting a custom firmware onto my Samsung Galaxy Tab S3 (SM-T820). I managed to install LineageOS 17 successfully via TWRP, but after trying it out for a bit decided I didn't like the tradeoffs and wanted to go back to stock.
Well now I'm having some trouble getting the stock ROM flashed back onto the system. Long story short:
TWRP recovery boot is still working
LineageOS has been wiped and the internal storage re-formatted
I have downloaded several different stock ROMs and now identified what I am relatively confident is the correct one (SM-T820_1_20200501145641_h0dxr2w1l3_fac, region code XAR for USA), although it only includes the BL, AP, and CSC files (not CP, none of the stock roms I found included a CP file though)
I have all the Samsung drivers installed onto my computer
I have Odin v3.10.7 on my computer (used it to install TWRP to get LineageOS installed)
When I select the BL, AP, and CSC files in Odin and try to run it while my tablet is in download mode, this is the output I get:
<ID:0/006> Added!!
<ID:0/006> Removed!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn.lz4
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
I have been on Google for quite some time and tried several things, but I haven't been able to make any progress. Most of the advice for the errors I found seem to relate to making sure I have the right ROM, but I've tried several different versions and finally downloaded the one I have through SamFirm so I don't think I have an incorrect ROM.

Categories

Resources