Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Rareutu said:
Hey all,
Please forgive me if i've missed this somehow, but i searched and searched and no luck. Here's the dealio. What happened is that on my first ever flash attempt to flash our amazing phone, i somehow grabbed the captivate stock rom and flashed via odin.
Yeah. Imagine how that soft brick felt to a noob after mustering the courage...
Well in any case, after a little research and experimentation i moved on, and flashed again and again, but that AT&T WORLD PHONE splash screen (basically the first thing you see after reboot or power on) right before the correct T-MOBILE VIBRANT splash screen just won't go away!
I've flashed several times, after reverting to stock, or over the current rom, and the damn screen just won't go away
I can't say what files are left behind by residual after that first idiotic Captivate flash to cause this, or how they affect my phone. After multiple roms i think we all know there there are no 2 Vibrants alike! So i experience some reported issues and of course all sorts of others with any available here...
If anyone can give me a hand with this issue or point me in the right direction i would really appreciate it. This community is the best!
Thanks in advance,
K~
Click to expand...
Click to collapse
Have you tried using Odin to go back to JFD? with re partitioning checked?
Tried JK2?
The splash screen is usually controlled by the kernel, you could also just try re flashing a stock vibrant kernel to see if that works.
I'm having the same issue. Just got a used Vibrant yesterday and I'm not sure what version it was on. I downloaded a bunch of apps and all was well - it worked great. I went to bed and when I woke up this morning it was stuck on the Samsung Vibrant screen. I tried using Odin with the 512.pit and the JFD.tar but that did nothing. I then found a one-click fix, not realizing it was only for the Captivate and used it. So now my T-Mobile Vibrant is stuck on the AT&T World Phone screen.
I can get into Download mode just fine and I have re-loaded the JFD in Odin several times, including doing so with the re-partition box checked but to no avail. I'm downloading the JKT rom now, though I have little hope that that will do the trick after all I've already done.
Any suggestions?
PS - I also tried downloading the All_In_One.zip and flashing to the Original.tar, then the T959UVJI6.tar. No dice. Nothing seems to work.
Related
So I was using Odin to flash the stock JFD to fix a soft brick. Everything went through and flashed just fine, no issues. I've done this dozens of times before, on several different devices, so I'm pretty familiar with the process. After the phone flashed, the screen switches to some weird distorted screen for a couple seconds and then it boots. It boots up fine, and when I get to the home screen, it'll just shut off and go back to the distorted image, then another boot. This will repeat 20 times if I let it. Any ideas of what might be the issue? Let me know. Thanks.
-Harris
Did it have the gingerbread bootloaders?
I really couldn't tell you. I'm just helping out a friend who said he tried to flash a ROM using Odin but screwed up. I'm pretty sure he tried to flash a SGS4G ROM, thus the soft brick.
EDIT: Just flashed the stock bootloader and no more issue. Guess I overlooked that. Thanks for the tip!
Hey All,
I've been looking for an answer for over a day now, but can't seem to find anything about my specific problem. Here's what happened:
I had flashed to ICS 4.0.3 on my Samsung Vibrant about a month ago and everything was working great until yesterday when I woke up to find the "Encryption Unsuccessful" screen on my phone. I did a little research to find out that there is a fix to this and to NOT reset the phone. So, I took the steps to ODIN the phone back to Stock Eclair in hopes that starting from the beginning again would be easiest way to fix the problem. The ODIN process finished completely fine (PASSED), but now when it reboots, I only get to the first "Vibrant" screen, then it shows the battery and spinning circle icon. Apparently it won't fully reboot. I've tried to ODIN it back to stock several times, and I keep getting the same results. I can get it into download mode and plugged into my computer, but that's about it.
From the posts I've read, it sounds like my phone might still be okay to recover since it does power up, but I can't seem to find a solution to get it fully back up and running.
Any help/recommendations would be greatly appreciated!
Thanks in advance!
Maybe your JFD file is corruption. Check with your MD5 sum if there any error or mismatch.. Just give you an idea.BTW what Odin are u using. I recommend Odin 1.7 I stay away the older Odin or the newer Odin
You are screwed.
Sorry to tell you this but i had the exact same problem and found no solution whatsoever to fix the phone. I finally gave up and bought a Galaxy Nexus. You can try flashing Eugene's Unbrickable Froyo Rom which is flashable through odin as a .tar package along with the pit file. You might be able to fix it but i highly doubt it. I flashed Eugene's rom and got the same results as you described. By any chance did you click "Reset Phone" when the "Encryption Unsuccessful" showed up? If so well yeah your phone is pretty much paperweight as of now...until someone finds a solution. Like you i am also able to access download mode. So i guess there may be a way to fix your phone. Not saying it's impossible...hopefully someone finds a solution soon.
Here is the link to Euguene's rom: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Good luck.
OP, what ROM were you running (specifically. Not just ICS 4.0.3-what is the name of the ROM)? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
Check here out for a possible solution/workaround.
Replacement Vibrant Coming
Thanks for your recommendations/help guys.
I decided to go to T-Mobile and complain and they are sending me a replacement phone. Apparently it's still under warranty, so it won't cost me anything, and if my data is lost, then so be it...at least all my contacts will still be in tact through my Google account.
Merio - I did NOT hit the Reset Button when I saw the Encryption Unsuccessful screen. Before doing anything I did a little research and I found a forum here on xda that said to not hit that button, and tried to explain a way to fix it using the Heimdall One-Click. Basically it sounded like I'd be flashing back to a Gingerbread ROM. So, instead I just went ahead and tried to flash back to stock Eclair. The results of that were obviously not good.
Woodrube - I was running the Passion 13 ROM (ICS 4.0.3). Was really enjoying it until I got the Encryption "Screen of Death"
I don't know what Kernel it was, actually, I don't really know what a Kernel is...
Thanks again guys. Hopefully I'll be up and running on my replacement phone soon!
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.
So, SGH-177 had been rooted and installed CM7, then Unnamed, then AOKP. All were pretty buggy. We wanted to bring it back to factory (with root if possible). Not for a warranty claim, just so it would be somewhat stable.
Anyway, I found a one click ODIN solution for UCKH7 stock. I used that, it passed. then the phone just looped through the AT&T "Rethink Possible" splash screen. I tried to get into recovery mode, but it wouldn't load, so I flashed the Siyah kernel to get CWM on there. Still I can only get into download mode and the phone loops the splash screen.
I hoped that it was just taking some time to load up the first time, so I left it overnight. Still stuck on the splash screen this morning.
I spent hours on here last night and found lots of people saying that if you have access to download mode, or recovery mode, you should be able to fix it. I wasn't able to find any answers as to how.
Help?!
I've had this same problem before. what always fixes it for me is to get into the factory 3e recovery to do a reset. I know you said you couldnt get there but make sure (while the phone is off; remove battery if you have to before this) you are holding down both Volume buttons and the power button at the same time until you see the "Samsung Galaxy SII" screen, then release the buttons.
factory reset, then it should be fine.
If you can't get to recovery, read some more on here. I'm sure something is out there, but I don't know what it is.
Here are two posts that might help you out. I've been doing the same research since my "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII is due to arrive today or tomorrow.
http://forum.xda-developers.com/showthread.php?t=1451590
http://forum.xda-developers.com/showthread.php?t=1580885
Best of luck to you!
UnNamed buggy?
Out of curiosity how did you root and flash, cause that is probably one of the most stable builds we have with minor changes to stock.
Anyways good luck getting back to stock.
So, for some reason, the next time I tried booting into recovery, it worked. I got a couple errors, but then it booted up just fine. Don't know why it wouldn't get into recovery before.
Everything seems to be working as it should so far.
I'm guessing this may be why some of the threads I had seen didn't really offer a solution. Sometimes it finally works if you just hold your head right.
Thanks all!
Regarding UnNamed... I don't recall the method I used to root, it's been a long time and I've done various work on this (my wife's phone) and my Nexus One. Easy to get it confused. I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Major Wood said:
I flashed it through CWM recovery, factory wipe, flash from SD.
It worked fine for a while (a couple months), then it got really glitchy. Unable to answer phone calls, random reboots, etc.
Click to expand...
Click to collapse
Did you also wipe cache and dalvik? May have been the problem...
I don't recall, but would be surprised if I hadn't done that
A year ago. When I first started flashing roms. I spent an entire week just reading the atrix forums and learning. I planned. I schemed. I asked questions. Through pm. And googled a LOT. Then when I had learned enough I did it. Point is....if yer not willing to have patience and learn as much as u can before u jump into this. Then its maybe not for you.
Sent from my SGH-I777 using Tapatalk 2
First of all, I am not new to flashing, rooting and etc. I have helped many of my friends with custom roms and etc so flashing and Odin is not something I know nothing about.
However, I was asked by my friend that his S2 was running slow and wanted me to put a custom rom on there. So I did the usual thing of using the ZergRush method to give him root access and I tested Superuser with Root Checker and everything was fine. So I went to install a custom recovery (Phil's CWM) via Odin and using the latest tar file from Phil's website but this is where things didn't go according to plan.
When I hit the Start button in Odin, it did the normal thing of writing to the NAND but instead of taking the usual 8-10 seconds, it took a lot longer. I actually waited 20 minutes and nothing was happening. There was no indication on the S2 that anything was happening and Odin was still stuck on the NAND Writing with all the buttone grayed out. So I waited a bit longer and after 30 min I decided to close Odin and try again, but when I try to get into Download Mode, I got the message 'Software Update Fail'. I tried to flash the custom recovery again but when it gets to the NAND Write, it instantly goes to 'Fail'.
Out of the 8 Samsung phones I have rooted and put a custom rom on, this is the first time this has happened. I searched the forum but most of it point to a bricked phone. I know at this point is is pretty critical that I do not try any random thing and asking you guys for any advice. I have tried flashing with a different version of Odin and also on different computers but gave me the same result. So any help would be much appriciated.
Hopper8's 'Odin troubleshooting' guide; search for it. You need to try everything in that thread over & over & over, only way you're fixing it is if you get a successful Odin flash away. In particular flashing the 3 part firmware might fix it.
Given the alternative - motherboard replacement or new phone - keep trying stuff, these cases are sometimes fixed by persevering (for whatever reason the first 8 stock rom flashes you try don't work but the 9th does, etc)
Thanks for the information MistahBungle, I have tried most of what has been said but I have not tried the leaked rom for the i9100. I will definately give this a shot.
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
MistahBungle said:
No worries The rationale with flashing the 3 part is it will wipe the phone & hopefully remove any 'remnants' of what was previously on the phone which might be causing issues. If that doesn't work, download a bunch of stock roms from Samfirmware (carrier/country doesn't matter, just make sure you DL I9100 firmwares) & start flashing, this sometimes solves problems like this as I mentioned in my PP. Good luck.
Click to expand...
Click to collapse
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Z-Blade said:
Just giving you an update. The 3 part leaked rom did the trick! I been flashing for a few years now but never ever had Odin go wrong so this is a new experience for me. I really appricate your help with this, was so worried I stuffed up a friends phone.
Click to expand...
Click to collapse
Good to see you got it working, always like hearing of people getting their (or not their own in your case) phone back to life
MistahBungle said:
Good news then No worries, glad you got it sorted (& you've still got a friend ). Yeah, that's a handy trick the 3 part, it's bailed a few people out. Don't forget to thank Hopper's OP in his thread.
Click to expand...
Click to collapse
Thanks for keeping on referring my thread, the more people it can help the better I'm working 6 days a week for now so haven't much time to go on Q&A and help out. Also thanks for before, I think you know what I'm referring to. Much appreciated. :good: