[Q] HELP! My Vibrant won't turn on! - Vibrant Q&A, Help & Troubleshooting

I did all that rooting crap. Now when I press the power putton, it flashes the "Samsung Vibrant" Image, then plays the tmobile tone, but no "S" image appears. And it stays black. How do I fix this?

define "all the rooting crap"? Did you flash a Voodoo Rom and try to flash something else on top of it?
There is NO way to tell you what you need to do unless you tell us what you did.
But based on what you have described.. Gonna say u are SOL.

Use odin to flash stock rom then start over. I have been stuck on that screen a couple times. Lol
Sent from my SGH-T959 using XDA App

Truth be told
Anthony is right. i had this issue earlier this week when trying to flash a mod to my phone. Odin is the only choice at this point.

This has happened to me twice, most recently after "fixing permissions" in the oclf market program. Both times I've rectified by booting into recovery and "reinstall packages". Both times I also removed sim and sd and after a couple repetitions of package reinstall it comes back to life. Maybe dumb luck, maybe not, worked twice...
Sent from my SGH-T959 using XDA App

Correction, fixing permissions in Rom Manager...
Sent from my SGH-T959 using XDA App

Also...My Vibrant Wont Turn On
Dear All
I am new to this forum and need some assistance. I recently bought a T-Mobile Vibrant from a friend who had brought it with him for the US. I am using it in the Middle East where I live at the moment.
I have been reading a lot in the past few weeks about the Vibrant and almost everything there is to know. It seems there is always more to discover.
Back to the issue at hand. I had been having problems with getting my phone to reboot into recovery mode but I finally managed to do so last night. I wanted to flash my phone with Axura 2.1E, Nero V2 or the Macnut v14, so I can use the the Black Froyo theme on it.
First, I flashed the original firmware (T959...JDF) which I got off your site, using Odin v1.3. That worked as it should. Then I proceeded to follow instructions to download the ClockworkMod from this thread: [RECOVERY] ClockworkMod Recovery for Vibrant (FINAL! SAFE!)
After I copied the CWM file to the Internal sd card, I downloaded Rom Manager, rooted the phone with Z4root, chose the Samsung Vibrant in Rom manager and clicked install ROM from sd card. it rebooted into recover mode (blue writting), I clicked 'reinstall packages', which it did and it rebooted into the ROM recovery mode (green writting). I chose the option to install zip file from sd card, then chose Axura 2.1E and it installed until it said complete.
So far everything was working as it should, or at least that was the impression I got. I am not sure of this next step. It said installation complete, so i chose 'go back', then 'reboot device'. When it went into reboot, nothing happened...just a black screen. It wont start, neither normally, not into any other mode (recovery or download). i plugged it into the charger and not even the battery icon would come up. i assume that it is...'dead' and I just did the impossible. I tried several ways and combinations to get it back to life somehow, but I have a feeling that's it.
Any suggestions, advice, remedies, whatever help...even condolences would be much appreciated..
Much appreciated and all the best to all.
Cheers

What the heck is up with all these HARD BRICKs?
Past few days, I keep reading people who have appeared to truely HARD BRICK their phone.
Meaning they can not get into download mode, they can not use odin, they are truely hard bricked.
What is up with the sudden surge of hard bricks.
This guy sounds like he did everything correct.
Scary.

Ya I've seen a lot of those also... could it be a newer version of the Vibrant? Yes he did everything correctly... he could try a jig.. its only maybe 10 bucks? worth a try at least...

My Vibrant wont turn on
Thanks guys for the reply to my post. I was thinking today that even though I did follow instructions correctly, that I might have missed a step at the end.
My thoughts went to the fact that after the installation of my chosen ROM (Axura 2.1E) was complete, I was given the choice of installing update.zip again, along with some other ones which I forgot what they were and the option to 'go back'. I went 'back' and pressed reboot device.
If the installation was fully complete, would not the phone go into automatic reboot?
Anyways seem like the boot is screwed and I am getting help from a friend to get it back to life again.
Anyone can confirm what to do after I install a 'ROM' successfully. Is there another step afterwards which I must be aware of to fully complete the flash?
Cheers again

Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..

hellobitchdog said:
Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..
Click to expand...
Click to collapse
Get into download mode try again,
if not try getting the files from a different source
Sent from my SGH-T959 using XDA App
Sent from my SGH-T959 using XDA App

Hey everyone...
I need help.. And its not my phone nor do i have it in my possession... Kinda troubleshooting over the phone... My nephew got a samsung vibrant... Got his phone rooted and had Darky's v7.7 Gingerbread Edition rom running... It booted up ran for a bit had a LOGSPROVIDER error stopped unexeptedly message....
He shut the phone off then rebooted and it wont boot past the first boot screen... HE also cant get into recovery but download mode works fine..
Possible solutions..?

Well if he can get into download mode the he should just odin back to stock and reinstall the rom!
Sent from my SGH-T959 using XDA App

Thats what I was thinking... Im not familiar with samsung phones.. Whats the purpose of download mode?
Safety feature? I presume..
I find it odd though that it booted fine and was ok until he rebooted and it wouldnt load... Any specific reason that could happen

Nah if you read the disclaimers devs put up it clearly says "i am not responsible for bricking, etc."
So no, there should be no specific reason why your nephews phone won't boot, more unless he was running a lag fix and flashed the wrong zip or whatever then yeah...
But download mode is I guess a fail-safe for samsung if the phone bricks or anything, afterall the vibrant is nearly impossible to fully brick
Sent from my SGH-T959 using XDA App

Thank You for the help...
He opted to call tmo and there sending a replacement.. Then asked him if he bricked the phone... He played dumb.. and said he rebooted the phone and it wouldnt load...
And yes i know about the devs disclosure... Got myself a mytouch slide which just finally got s-off courtesy of ALPHAREV woohoo.. Also have a G1 from back when it first came out.. SO i got plenty of rom downloading under my belt

hellobitchdog said:
Hey I got a old stock rom from off one of these forms off xda... for my samsung vibrant... After i flash the rom odin said reset and the vibrant never turned on.... its been like this for a day now... the battery sign dosent even turn on... what can i do..
Click to expand...
Click to collapse
This same thing happened to me. I read about making a jig, yeah right. So I continued for the better part of three hours plugged into my computer with data cable continuing the same motion that I would to get into download mode. And finally I got the download dude. I used the s1.odin somthing .pit file I think it was the first .pit to come out. Not the 512.pit Along with the first .jar. Anyway keep trying to get into download mode even with a black screen, can be done.
Sent from my SGH-T959 using XDA App

Related

[Q] Phone stuck at Vibrant Screen after Voodoo Lag Fix

Hello everyone. Forgive me if this is in the wrong section, but this is my first time posting. I tried to apply the Voodoo Lag Fix, and I got up to the point where the voice told me that the conversion was successful, but it was stuck at the Vibrant screen for a really long time, so I pulled the battery and tried to run it again. Now it's been stuck at the Vibrant Screen for a really long time now. Should I Odin back to stock or should I continue to wait to see if it resolves itself?
Thanks!
You're absolutely right. This should be in q and a.
What exactly is a really long time? Because like 5 minutes is normal after applying voodoo. But anyways you soft bricked it.
This happens to a lot of people by the way and you do need to use odin.
Download eugene373's froyo that doesnt brick. In odin click the repartition box and set it up and flash that.
Once done uncheck repartition in odin and set it up to flash the original jfd rom (not the ji6)
If you need instructions on how to set up and use odin search in the bible sticky thread. There are tutorials there.
And next time search is your friend. This has been answered hundreds of times.
Good luck.
Sent from my GT-I9000 using XDA App
Soft brick
Bob u might try wiping user data in samsung recovery. That seemed to do the trick for me when I had the same problem.
Good luck!
Aaron
AaronMFeld said:
Bob u might try wiping user data in samsung recovery. That seemed to do the trick for me when I had the same problem.
Good luck!
Aaron
Click to expand...
Click to collapse
I did what you suggested, and when I rebooted the phone, it told me that the conversion was successful, then proceeded to be stuck on the vibrant screen forever again. Looks like I'll be Odining this...
Odin to Eugenes froyo will fix you. Then reinstall your ROM. Voodoo will take a LONG time to install just wait it out.
Sent from my SGH-T959 using XDA App
stuck at vibrant screen
Hi guys,
I am having the same problem and im very desperate right now, my vibrant cant seem to get past the Vibrant screen, and it just loops back to vibrant screen.. after trying to install jk2 rom... please help me guys.,.. my email is [email protected]
Read post #5! If that isn't enough then go here...
http://forum.xda-developers.com/showthread.php?t=771111
I thought my phone bircked because it stock on Vibrant sign, for about 15 mins, I already went to this forum and was getting Odin , then suddenly it said "Succesful" in female voice. And it booted Guys you need more patience , and I used ROM Manager with Axura 2.0.6 rom

The impossible? I think I just did it...

I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Doesn't really sound like anything you did would brick the phone - even though the screen doesnt come on, does your computer recognize it when you plug it in?
Yeah I agree. Nothing in those course of events would point to bricking your phone.
I am so sorry for your loss.
btw did you try pulling the battery for a few minutes then trying to power it on?
The phone is bricked. Same thing haopened to me flashing the same rom. I wasnt the first and you wont be the last.
I really wish we could figure out why this is happening.
Sent from my SGH-T959 using XDA App
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
tooclose said:
I think I might have permanently bricked a vibrant lol...ok well maybe I shouldn't be laughing. I have a vibrant that does not turn on, I don't get any images, but when im charging the phone still gets warm.
So here's what happen, I been telling my friend to root his phone and out custom rims on there...he finally gave in after being frustrated by the lack of support Tmobile and Samsung was giving and tried to root and flash himself. During the flash in odin something went wrong and I had to flash it back to stock. I rooted the phone with oneclick root. Installed rom manager and flashed clcokwork recovery. I rebooted into clockwork, reinstalled packages, cleared/wipe cache/data, and flashed team whiskey's bionix-v (awesome rom by the way!!) It flashed and rebooted....bit never turned back on. I don't even get to the boot images....just blackness.
I did some research to no avail....if anyone has any suggestions or anything, it would be greatly appreciated!!
I already tried the 3 button to try to get it into recovery, battery pull with the 3button fix....with usb plugged and unplugged...but odin still fails to recognize it.
My last resort is the jig to try to get it to at least download/recovery mode. =(
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
so you bricked your friends phone, not your own?? thats messed up... why did you wipe data before you flashed the rom?? lol is that a regulation? i never wipe my stuff until after i let the rom run for more than 10 mins. unless im told different.. besides i thought all of tw roms wipe so you didnt need to. lol correct me if im wrong
@jellette no my computer doesn't recognize it....I have a windows 7 pc...and the latest odin
@hazard99 yes I've tried several battery pulls with different options with 3button....no luck =(
@alkaloid i've flashed, rooted alot of phones going back to my pearl, sidekick, bb pearl, htc hd2, my own vibrant....maybe cuz they were all my phones and I took the time to be careful...haha
@kooksta yeah I know I feel bad...im letting him hold my hd2 til I can get a fix or just have it replaced...I usually do a backup and wipe before every flash never had a problem and I thought that was standard but not sure...
@krylon I was thinking the same thing ...when he tried to update it on odin with the froyo update it corrupting something...the devs on here do a great job!! Never before have ever had any problems!
Thinking back to it, the only thing I can think of is after I installed rom manager and flashed clockwork recovery and I booted into clockwork...I think the lettering was still blue? I think its my understanding that if its still blue the phone is not rooted, green lettering means rooted, and red means rooted with voodoo activated...correct me if i'm wrong. But I THINK the lettering was blue, but the phone has to be rooted to run rom manager right?
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
If anyone else has similiar experiences and/or fix....would love to hear them!
Sent from my SGH-T959 using XDA App
Like you said, the Rom would've done it for him regardless. It wasn't his fault he bricked his friends phone. Hopefully he told his friend the possible repercussions of modding his device however. Like Krylon said, its just a corruption caused by odin. Nothing he could've done differently to prevent it besides not modding the phone itself. Oh well, happens. Like Kyrlon said, warrenty replace it. Simple and done.
tooclose said:
Lazy to make so bought the jig from ebay, should get it in a few days to test ...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
@tooclose
off topic, i need a new jig (another one), can you send me the link in ebay where you bought that?
or anyone?
krylon360 said:
the PBL on the phone crashed. Most likely the bad ODIN flash caused the PBL to become corrupt. When it received the new SBL for froyo, it crapped on itself.
This is where people begin to blame the roms for bricking. When in fact, it is not the roms at all. It's ODIN corrupting the Primary Bootloader when ODIN freezes or crashes.
But other than that, your hosed. Just contact TMO for a warranty replacement.
They will tell you that you need to perform a master reset using the hardware keys...dumb asses.
then have you check the water damage square under the battery.
Then will send you off a replacement.
Click to expand...
Click to collapse
Wait, so if I was running Bionix V and wanted to flash a new rom, what would be the proper procedure? All these crashes from Odin is starting to scare me
I forget who the seller was but just do a search for vibrant jigs ...there's several sellers...good luck!
Just got the jig...its a no go =(
Sent from my SGH-T959 using XDA App
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Speaking of the PBL, how can I verify that mine is not corrupt? I flashed bionix V twice and assume the SBL is intact, but I still would like to verify that both are working correctly.
bartek25 said:
yes , i fix my phone fron the point where you are now without no jib anyway since u got solutin comin in mail i wont explain since it took me and hour to figure how to get my phone to odin .yes from blank screen to phone warm when chargin i got it to work =}
Click to expand...
Click to collapse
I think you should explain it just in case it happens to others later on or make a seperate post on how to please
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
method of unbricking
bartek25: Would love to know your magic to bring the dead phone back to life. Mine is completely dead acting like the battery is dead even though it is fully charged and I've read and tried ever method I can find.
Any suggestions other than sending it in Samsung or the carrier in getting a hard bricked phone fixed? Anyone with a jtag interface who likes to make a few extra bucks on the side?
I'm a noob to all of this custom rom business but earlier today I installed Bionix, everything went great and was a lot easier to do than I had anticipated.
Anyways I'm just wondering, I did not have to use ODIN, really all I did was root, install rom manager, cwr, create nandroid and titanium backups, transfer bionix zip to internal dir and then bootup in cwr.
I guess my question is, why was ODIN necessary for the topic poster?

[Q] Soft bricked...PLEASE HELP!!!

Installed the DoW kernel over Bionix-v and wound up in a boot loop, unable to get into recovery, but I was able to get into download mode. Tried using ODIN to flash back to stock, but it won't boot past the 1st Vibrant splash screen.
The ONLY rom I've been able to boot is Eugene's JK2+2e Froyo ROM, but it's not recognizing both the internal and external storage (shows unavailable). I'm assuming this is due to ODINing with voodoo enabled, so I tried flashing one of SuperCurio's voodoo kernels on top, but that seemed to have no effect.
I've tried using Eugene's Froyo that doesnt brick and then downgrading to stock JFD, but it still refuses to boot, same as if I negated the Froyo step. I'm fairly lost as to what my next step should be besides randomly changing settings, but I dont want to get to a state where I can't enter download mode.
ANY help anyone can provide would be amazing and greatly appreciated, and I can of course provide any additional information that would be helpful.
Odin needs time. Odin is your solution.
Sent from my SGH-T959 using XDA App
Thanks for the response, but could you be more specific? I'm aware that ODIN is the solution, because I'm unable to flash anything in recovery.
torturedsoul802 said:
Thanks for the response, but could you be more specific? I'm aware that ODIN is the solution, because I'm unable to flash anything in recovery.
Click to expand...
Click to collapse
Sure. If it was me id download an older odin version. Just try it. Id also go back to stock.
Remember to back up a program to root.
I still use odin 1.3 myself. Works every single time.
Let me know.
Sent from my SGH-T959 using XDA App
Using Odin 1.7 now, I'll try 1.3 and report back on that. The problem is, every time I attempt to revert back to stock (JFD or JI6), the phone refuses to boot, shows Vibrant splashscreen for ~1.5 sec and then shuts off. No boot animations.
torturedsoul802 said:
Using Odin 1.7 now, I'll try 1.3 and report back on that. The problem is, every time I attempt to revert back to stock (JFD or JI6), the phone refuses to boot, shows Vibrant splashscreen for ~1.5 sec and then shuts off. No boot animations.
Click to expand...
Click to collapse
Keep trying. It will work eventually for no reason.
Sent from my SGH-T959 using XDA App
Leave it alone for at least 5 to 10 min on splash screen. Sometimes that takes a while.
Sent from my SGH-T959 using XDA App
mr.orange303 said:
Leave it alone for at least 5 to 10 min on splash screen. Sometimes that takes a while.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
15 max
Sent from my SGH-T959 using XDA App
Would you recommend flashing Eugene's Froyo that does not brick first and then flashing stock on top? Or straight to flash? And should "re-partition" be checked at any point, since the ext4 system needs to be rebuilt to RFS.
torturedsoul802 said:
Would you recommend flashing Eugene's Froyo that does not brick first and then flashing stock on top? Or straight to flash? And should "re-partition" be checked at any point, since the ext4 system needs to be rebuilt to RFS.
Click to expand...
Click to collapse
No to repartition on my end. But u may want to ask about the ext4 going back to rfs. Ive always done it in cwm honestly.
Someone else with more expirience will have to answer that.
But I have never and read it doesnt need to be done.
Sent from my SGH-T959 using XDA App
Tried, still wont turn on on stock, just vibrant screen.
torturedsoul802 said:
Tried, still wont turn on on stock, just vibrant screen.
Click to expand...
Click to collapse
Its not bricked. Keep trying.
Sent from my SGH-T959 using XDA App
mr.orange303 said:
Its not bricked. Keep trying.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
+1. If your phone boots at all it's in my experience 100% recoverable. I own a RIFF box as well so if you brick it dead then I can still fix it... . I'll be getting a video up on ODIN usage for Vibrant/i9000 owners tomorrow. Check out my Boot Logo video on my website for a little bit of ODIN usage to give you an idea. You just need to open ODIN. The put the phone in download mode and plug in via USB. Then select your PIT and PDA file and click start. Then you can reflash stock firmware. PM me as I offer this as a service as well.
Thanks for the reply. Usage of ODIN is not my problem, the problem is that flashing to JFD (whether I use Eugene's Froyo 1st or not) results in a failed boot. The phone shows the 1st Vibrant splash screen for ~2 sec and then shuts off. No process I have tried results in a successful stock boot.
Thinking about trying both of these:
http://forum.xda-developers.com/showthread.php?t=823300
http://forum.xda-developers.com/showthread.php?t=940671
HOPEFULLY, one of these will let me get into CWM or access the filesystem in order to disable Voodoo.
Once again, if anyone knows of a way to revert EXT4 -> RFS through ADB or download mode, please let me know!
Well I have been working on it for a day straight and no luck. I have talked to several people and the phone has readonly partition now so it is ****ed! Nand death! I called T-Mobile yesterday and told them I have know idea why but my phone won't turn on, blah, blah, blah. So they are going to replace it under warranty and it will be here in a few days.
torturedsoul802 said:
Thinking about trying both of these:
http://forum.xda-developers.com/showthread.php?t=823300
http://forum.xda-developers.com/showthread.php?t=940671
HOPEFULLY, one of these will let me get into CWM or access the filesystem in order to disable Voodoo.
Once again, if anyone knows of a way to revert EXT4 -> RFS through ADB or download mode, please let me know!
Click to expand...
Click to collapse
Hey, thank you so much for posting this up. These are great finds. I'd be more inclined though, to just call Tmobile and get another phone. I'm really tired of messing with the phone. I don't have time to be messing with this anymore.
The fact that I can get into download mode may be good news, but it does nothing for me right now. With what we know about bricking and unbricking phones, I've thrown every trick I know at it already. I hope you get it fixed, but I"m not messing with it anymore.
drewdude007 said:
Well I have been working on it for a day straight and no luck. I have talked to several people and the phone has readonly partition now so it is ****ed! Nand death! I called T-Mobile yesterday and told them I have know idea why but my phone won't turn on, blah, blah, blah. So they are going to replace it under warranty and it will be here in a few days.
Click to expand...
Click to collapse
Yeah man, me too. I'm getting this thing exchanged. It's a paperweight right now. My phone is doing exactly the same thing.
Can you recap one more time? You are only having problems flashing a custom ROM? You said ODIN is not the problem so I'm taking it you could flash back to stock if you wanted to?
Size matters.
Hey, I haven't posted in here before, I've been a member for a while, just never had anything to contribute. So I got the whole soft brick problem. I spent countless hours trying to get into download mode. The size of the usb cable matters, I was using an LG Optimus cord, and my buddy tried his blackberry cord which had much more gerth, and BAM download mode everytime no problem. Maybe this might help some of you out there.
Also I would like to say, thank you for everyones hard work. I had to roll back to stock roms, and just got the Froyo.UVKA7 to work. I love it, it's quick, it's got color in the settings menu. I wanted to cry... Everyone that has ever had anything to do with the developement to make Android better. THANK YOU!
Absolutely,
I am having problems with the phone starting up and loading what I flashed.
I flashed JI5 Ji6, and Eugene's non bricking Froyo Rom
These 3 are the only ones I was able to find that is ODIN flashable
Why you ask?
I cannot get into Recovery, but I can get into Download mode. I can't get into any recovery at all. NOTHING. This is why ODIN seems to be my only option.
But regardless of any ROM i flash, my phone shuts off right after the Vibrant screen. No splash screen, no loading, no booting. .Nothing. It just shuts off.
I can't charge it either.
i get a Charging bootloop. HOurglass - battery shows up for a bit, then restarts over and over.
So in other words. it's ****ed.
Hope that explains it sufficiently. if you have any more questions or suggestions, Im open man, Im open.
Help me
connexion2005 said:
Can you recap one more time? You are only having problems flashing a custom ROM? You said ODIN is not the problem so I'm taking it you could flash back to stock if you wanted to?
Click to expand...
Click to collapse

What steps are needed to get a HW locked vibrant to go to the 2E recovery menu

OK, Ive tried all day W/O any luck, using every method I came across here in the forums, I thought I had the solution with Eugenes stock Froyo with the 2E recovery mode ROM TAR file, but the link to get it is no longer working. And yes Im rooted with ROM MANAGER and have version CWM recovery flashed to: 2.5.1.2
This is a replacement phone I got last month, and all I can say is its a F--kin POS, compared to the earlier model, that wasn't HW locked and had the 2E recovery mode working with CMR. I tried updating the newer update.zip file, but it wont load because of signature verification! Does anyone know how to replace the update file with a script that will allow CMR to go into the 2e recovery [green] menu so I can once again start flashing a custom ROM again, this phones obviously HW locked and is preventing this, and all I keep getting is the Samsung 3E [Blue] menu which wont allow you to select a ROM from the SD card. I need the 2E menu!! Thanks!!
Have you tried flashing the fix for HW locked phones?
Ya got to be kidding
iynfynity said:
Have you tried flashing the fix for HW locked phones?
Click to expand...
Click to collapse
Ahhh, could we be any more vague in your suggestion.
Ahhh maybe a link, and procedure or something from you that sheds some light on what may be the only thing I did miss in scouring this forum for this problem!!!
dseldown said:
Ahhh, could we be any more vague in your suggestion.
Ahhh maybe a link, and procedure or something from you that sheds some light on what may be the only thing I did miss in scouring this forum for this problem!!!
Click to expand...
Click to collapse
I had a H/W locked Vibrant. What I did was go to the main page of XDA and search for Hardware locked Vibrant and there is one that is for Odin made by Untermensch. Edit: here's the link for it. Good luck.
http://forum.xda-developers.com/showthread.php?t=804305
Sorry you can't click in it. I did this from my phone
Sent from my SGH-T959 using xda premium
You can also use adb to reboot into recovery and flash an image that includes the bootloaders. As suggested, search the forums and it should turn up. On my phone, or I would link to a relevant thread.
Sent from my SGH-T959 using XDA App
Actually if you have CWM recovery installed, you can install ROM Manager, and use it to reboot into recovery.
Sent from my SGH-T959 using XDA App
Tried that one a couple of times Bro, did exactly like it said, problem is it wont go past the signature check, because its a zipped file, I also tried replacing the script with what was supposed to be the fix, using root explorer going into system/bin/recovery and overwriting that older script, and that didn't work either, and then I tried using the ADB program while in shell root, and it wouldn't co-operate either, I mean nothing outa all the things I found looking thru the forum is working, and the only one that would've worked for sure would have been Eugenes solid Froyo build with the 2E recovery and Busybox and the other goodies, if the link was somewhere that I could obtain that, I would've ODIN'd that and it would've taken care of the problem and Id be sleeping right now with my vibrant finally working like it used too. I just don't care for using stock Froyo. But, I should've never exchanged this phone after I bricked the first one, using KIE's- found out about that horror stories about 5 mins too late!! I should've just had it JTAG'd by Josh over a Mobile tech, Im so f--kin pissed that they sent me a HW locked phone. Older is better with these phones, the newer ones have all these issues you gotta deal with before you can even Mod the GD things now!!
Anyway, I'm still stuck with nothing but 3E menu and there seems to be no GD way i can flash another ROM until this is resolved. I already tried to flash a ROM using CWM with the install from SD card, but it wont allow the ROM to open because of the signature problem again plus it goes back to the 3e menu, and when ya only have one option saying re-install package, it wont follow thru, and hangs because of the signature issue. Its a vicious cycle, and unless 2E becomes doable, this phones stuck at Froyo, and thats un-acceptable!!
?????
shrapnelx said:
Actually if you have CWM recovery installed, you can install ROM Manager, and use it to reboot into recovery.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Well Ill just at least thank you for the effort of replying.
But you got it backwards pal, you gotta have root and ROM Manager installed first , then you get the flash clockwork recovery mandate, otherwise ya cant go into recovery W/O it!! thanks anyway. Oh and BTW, Im really not too keen on messing with the SBL by itself, as that one thing alone can brick these phones, if it gets corrupted during ODIN flashing and Ive already been down that route when KIES corrupted the primary and SBL and bricked my phone!! LOL
Nevermind...
Easiest is to Odin one of supercurio's voodoo kernels (Google "xda vibrant supercurio voodoo kernel"). This will bypass all the update.zip/2e/3e/signature verification error crap and give you cwm as the default recovery built in. No need to flash recovery with rom manager either.
Or, Odin back to jfd, flash recovery using rom manager (better yet, here it is; http://db.tt/Klybpxeo), then install the rom you want.
Sent from my HTC Sensation 4G using XDA App
Well, I managed to get a hold of Eugenes Froyo with the 2E recovery in it, and It still goes to the blue Samsung screen, but does say 2E, WTF!! I'm done I guess this phone will never be unlocked to get the green screen to flash a custom ROM, F--kin TMO screwed me hard. I cant believe that after 8 different attempts/methods I still cant get the green 2E screen. GDmt This just flat out sucks, I guess my Modding days are over with this phone!! F--kin Samsung Kies is what started this whole f--kin thing, and TMO then sends a HW locked phone you cant do **** with!! I wish someone works on this problem with a solution that actually works, cuz none of the ones I tried worked, and I tried them all, but were still stuck with the CMR blue screen even though it does say 2E, WTF, not understanding this, I thought flashing this ROM would've done it!!
dseldown said:
Well, I managed to get a hold of Eugenes Froyo with the 2E recovery in it, and It still goes to the blue Samsung screen, but does say 2E, WTF!! I'm done I guess this phone will never be unlocked to get the green screen to flash a custom ROM, F--kin TMO screwed me hard. I cant believe that after 8 different attempts/methods I still cant get the green 2E screen. GDmt This just flat out sucks, I guess my Modding days are over with this phone!! F--kin Samsung Kies is what started this whole f--kin thing, and TMO then sends a HW locked phone you cant do **** with!! I wish someone works on this problem with a solution that actually works, cuz none of the ones I tried worked, and I tried them all, but were still stuck with the CMR blue screen even though it does say 2E, WTF, not understanding this, I thought flashing this ROM would've done it!!
Click to expand...
Click to collapse
Go back to my post right above this. I posted the cwm update.zip. since you have 2e recovery, select "reinstall packages" (or whatever it is), and you'll have your green cwm screen...
Sent from my HTC Sensation 4G using XDA App
Halleluyaa Brother, Your the Man
geoffcorey said:
Easiest is to Odin one of supercurio's voodoo kernels (Google "xda vibrant supercurio voodoo kernel"). This will bypass all the update.zip/2e/3e/signature verification error crap and give you cwm as the default recovery built in. No need to flash recovery with rom manager either.
Or, Odin back to jfd, flash recovery using rom manager (better yet, here it is; http://db.tt/Klybpxeo), then install the rom you want.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Flashed it with SCio's 5.5 lag Fix, using ODIN and wholla, Got my 2e GREEN SCREEN AGAIN, WERE BACK IN BUSINESS!!! As Gomer Pyle would say" Thank ya, Thank ya, Thank Ya" !!! I wish I knew exactly how or why it worked, but writing a kernel seems to have alot of merit to it, when sidestepping a problem like this with a HW locked phone. Anyway Appreciate ya, oh and BTW, In the beginning when I did start with JFD, and rooted it, and installed Rom Manger, I never got it to cooperate either, in spite of about 2 to 3 suggestions to do just that!! IDK- Go figure right!! Seems alot of problems with these phones in flashing is to do it multiple times until it decides to give it up or you hit the sweet spot!!

Where to send Bricked i777 to get fixed? The bad decisions that got me Bricked.

I finally bricked my first phone.Its been a long ride but it caught up to me. I have had three different android phones within about 4 years and have successfully rooted all three myself and have successfully flashed them over and over close to 1000 times between all three phones including modems, kernals, gapps, themes etc. So what gives? Why today? To be honest I don't know. But here is what happened...
The past few days I have been going back and forth between different kernals for this device to try to get something that won't freeze up. ( I liked browsing on this phone but I would get freeze ups and therefore would flash something new to try and resolve it.) Today my phone froze so I tried a simple reboot. The boot then did a freeze on the kernal's "intro" picture. It wasn't a bootloop it just frooze. (I was on XWLPT with Skyfire Kernal). I decided to reboot into recovery and flash a different kernel. I flashed NEAK The flash went halfway then stuck and froze. I rebooted to try to get back to the phone's main screen. This time it would not boot. I couldn't tell if it was in bootloop or was froze. I went back into recovery. Here I should of wiped everything but in the back of my mind I thought I could just do it in odin if I lost recovery. So I tried flashing Siyah for sammy roms. This is when I lost everything. It froze in cmw on the flash again but this time when I tried going back into recovery it stayed on the Galaxy SII screen. So I put the phone in download mode and started Odin up. When trying to flash anything in Odin I got stuck on nand write start! I never heard of this. I thought Odin would work as this is how I rooted the phone when I first got it. Last thing I did was install kies which couldn't even connect to the phone. So all I am left with is download mode and taking way more caution when flashing. I think it may have been a case of the brickbug. Even though I was on a I9100 rom and using "safe" kernels I believe something happened to lock me out from writing anything to the phone.
U already posted this in another thread. I posted a response there for ya
Sent from my SGH-I777 using Tapatalk 2
Sad.
I got my galaxy s2 bricked twice
Double posting is no bueno.:thumbdown:
Sent from my SGH-i777 using XDA
anup123456 said:
I got my galaxy s2 bricked twice
Click to expand...
Click to collapse
Not really related.. (Yes I know my post isn't related either)
I bricked my sgs2 not to long ago At&t could not fix so in one last attempt I tried to flash back to Pics stock it took some time but finally recoverd using odin
Sent from my SGH-I777 using xda premium
VICIOUSVIC1 said:
I bricked my sgs2 not to long ago At&t could not fix so in one last attempt I tried to flash back to Pics stock it took some time but finally recoverd using odin
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
what's pics stock?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
what's pics stock?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Pics stock is when you're typing and not paying attention then the auto complete changes pics stocks to pics stock. Got it?
Revert to stock using Odin and download mode probably or the guys and (sorry if I hurt anyone's feelings) but the guys at mobile tech videos offer a service to unbrick your phone.
Sent from my GT-I9100 using xda app-developers app
bocephus007 said:
Revert to stock using Odin and download mode probably or the guys and (sorry if I hurt anyone's feelings) but the guys at mobile tech videos offer a service to unbrick your phone.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Yeah I know . But its just a front man! They receive the bricked device, then send it to some Chinaman named Finchenzo. And he fixes em all and sends em back to mobile tech! Then you get your device back! Poor Finchenzo
Sent from my SGH-I777 using Tapatalk 2
paulfrankie said:
I finally bricked my first phone.Its been a long ride but it caught up to me. I have had three different android phones within about 4 years and have successfully rooted all three myself and have successfully flashed them over and over close to 1000 times between all three phones including modems, kernals, gapps, themes etc. So what gives? Why today? To be honest I don't know. But here is what happened...
The past few days I have been going back and forth between different kernals for this device to try to get something that won't freeze up. ( I liked browsing on this phone but I would get freeze ups and therefore would flash something new to try and resolve it.) Today my phone froze so I tried a simple reboot. The boot then did a freeze on the kernal's "intro" picture. It wasn't a bootloop it just frooze. (I was on XWLPT with Skyfire Kernal). I decided to reboot into recovery and flash a different kernel. I flashed NEAK The flash went halfway then stuck and froze. I rebooted to try to get back to the phone's main screen. This time it would not boot. I couldn't tell if it was in bootloop or was froze. I went back into recovery. Here I should of wiped everything but in the back of my mind I thought I could just do it in odin if I lost recovery. So I tried flashing Siyah for sammy roms. This is when I lost everything. It froze in cmw on the flash again but this time when I tried going back into recovery it stayed on the Galaxy SII screen. So I put the phone in download mode and started Odin up. When trying to flash anything in Odin I got stuck on nand write start! I never heard of this. I thought Odin would work as this is how I rooted the phone when I first got it. Last thing I did was install kies which couldn't even connect to the phone. So all I am left with is download mode and taking way more caution when flashing. I think it may have been a case of the brickbug. Even though I was on a I9100 rom and using "safe" kernels I believe something happened to lock me out from writing anything to the phone.
Click to expand...
Click to collapse
Send it to MobileTechVideo.com. I sent my bricked SG2 in and a week later and at a cost of only $50, it was returned fully functional.
Sent it to MTV. Mobile Tech Video said this...The device's onboard EMMC controller was in a non-responsive state.
I never flashed anything that wasn't specifically made to be flashed for an i777.
Everything I had ever flashed was on the i777 development thread.
My advice ...beware of the brickbug. Also don't flash anything when the phone is hot. This happened when my phone was hot and maybe a reason why it froze while flashing in cwm.
And for a recap... What did you flash right before tie happened and what were you coming from?
Clay
Team Pirate
Sent from my PINK SGH-I777
Specifically the rom booted fine with Shostock-XWLPT. When using the rom sometimes it would freeze up so I flashed NEAK kernal over it. Froze in cmw during halfway through the flash.Rebooted after about 5 minutes wating for cmw to finish. (it never did) Phone bootlooped. Pressed hardbuttons to get to recovery. Recovery worked went into NEAK cwm. Instead of wiping and starting fresh here decided I would take a shortcut and flashed a Siyah for i777 over that. CWM froze again halfway through flashing the Siyah. After waiting 5 minutes again decided to reboot. Phone bootlooped. No more hardbutton recovery. Phone bricked. I Can still go into download mode but even MTV could not unbrick it. Said EMMC controller was in unresponsive state. Don't know what that means but know its now a paperweight.
Got it back today I still can get into download mode. Odin will recognize phone. When I try to flash a kernal it follows through until right before it actually writes and says NAND Write Start. I believe the internal memory either is filled with bad sectors or someting like brickbug locked anything from writing to EMMC.

Categories

Resources