Related
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
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?
First off, I want to apologize if I ramble on. I am trying to be as thorough as possible.
Also, I am relatively knowledgeable about rooting and whatnot, so hopefully I will understand whatever help you guys can give me.
Here's my problem:
I originally had Bionix-V 1.3.1 (which is a 2.2 rom), and I wanted to upgrade to a Gingerbread rom. So I downloaded "Trigger Redux" (addictivetips.com/mobile/install-android-2-3-5-based-custom-rom-on-t-mobile-samsung-vibrant/) and followed the instructions completely. The instructions told me to do a nandroid (which I did and it went perfect), then factory wipe the phone and wipe the dalvik cache (which I did), and then run the Trigger Redux zip from the sd card (which I did). Everything worked fine, but when I started messing around with the new rom, I didn't like it as much as my old rom, so I decided to reboot the phone into recovery to perform the nandroid restore. When my phone rebooted, I noticed the clockwork recovery looked different from what had before (it was orange, when the old one I had was red). Anyways, I tried to do the nandroid restore, it gave me an error about not being able to perform the nandroid for whatever reason (I honestly don't remember what it said now). So did a factory wipe again, thinking that may allow the nandroid restore to perform properly, and I still got the same error. So I restarted my phone, and now I'm stuck on the Vibrant logo screen. I can get into download mode (by plugging in usb/pressing vol up and down/inserting battery), but not sure how to get my phone into recovery mode again. I know I can probably use Odin, but I'm not real familiar with that program and I wouldn't know where to start.
What's the first thing I should do? I know my phone is fixable, I just don't know where to start Any help is very greatly appreciated. You guys are awesome!
Odin to stock is simple but risky...if it fails due to any reason u will have a completely bricked phone....there's a guide on how to do that process BC u will need to download two files...one is .pit and other is .Tar file......here's a video link..http://www.youtube.com/watch?v=VIBeLG4frjM...and here is a link to download required files....http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/....good luck
Sent from my MB860 using XDA App
deziguy420 said:
Odin to stock is simple but risky...if it fails due to any reason u will have a completely bricked phone....there's a guide on how to do that process BC u will need to download two files...one is .pit and other is .Tar file......here's a video link..http://www.youtube.com/watch?v=VIBeLG4frjM...and here is a link to download required files....http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/....good luck
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
bfranklin1986 said:
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
if it fails in the very beginning then it's ok but if it fails in the middle then definitely it will be bricked... if you record yourself pulling off usb in the middle of the process then send me that link...i would love to see the result...
Samsung Android T-Mobile SGH-T959 Vibrant Firmware
fallow guy and use from this roms
http://gsm-beyond.blogspot.com/2011/07/samsung-android-t-mobile-sgh-t959.html
bfranklin1986 said:
Yes you need odin but you won't be bricked if it fails for any reason. I have odin fail a few times and you start it back up and try again. The only way you can brick with odin is during a bootloader flash
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i hard bricked going to stock with odin, it froze at the very end so i unplugged to try again and it went off and wouldnt do anything after that
its froze afew times at the beginning aswell but just goes to the phone ! pc screen when unplugged
deziguy420 said:
if it fails in the very beginning then it's ok but if it fails in the middle then definitely it will be bricked... if you record yourself pulling off usb in the middle of the process then send me that link...i would love to see the result...
Click to expand...
Click to collapse
Why would you pull the cord? Never check auto reboot and if it fails just close odin and restart it. If you pull the cord and reboot with a half flashed phone then yes that would probably brick you
Sent from my GT-I9000 using XDA App
bfranklin1986 said:
Why would you pull the cord? Never check auto reboot and if it fails just close odin and restart it. If you pull the cord and reboot with a half flashed phone then yes that would probably brick you
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
that's exactly my point...according to other person he says odin to stock won't brick a phone...so i was just telling him to pull the plug out while it's running the procedure...and of course that will brick his phone and a prove that yes odin to stock can brick your phone... of course pulling a cable would be stupid...but what if your computer restarts all of the sudden or u lose electricity...stuff like that...can cause a dam hard brick....
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.
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
atcq28 said:
Yeah use the unbrickable reserector
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
I see thanks then.
avid_reader said:
I was reflashing back to stock firmware gingerbread 2.3.6 from eryigits due to its massive slowdown from its initial install. But then after flashing the stock firmware it boot looped so i thought maybe there was something wrong with the partitions and loaded what I got from another thread. But then the progress bar in Odin wasn't moving at all so I terminated odin and opened another instance similarly it didn't progressed. I plugged off my ygp and rebooted only meet a cellphone logo and a computer logo with an exclamation mark unpleasantly called black screen of death. Is this what they call a brick? Should I follow the guide on hardbrick recovery ie http://forum.xda-developers.com/showthread.php?t=1496360?
Click to expand...
Click to collapse
No, this screen is the forced download mode also called lucky brick. So while you are on this screen the player should be detected as it is in download mode. So you should be able to flash your rom.
Just flash the rom in odin again see post above me
if it bootloops again format the device in recovery mode
There is a way to fix this.
I was flashing STOCK GB 2.3.6, because i didn't like Erygit's rom, and i got the bootloop too.
The bootloop was caused by the fact i didnt do a Factory data reset, and when i did it, i rebooted from Recovery and the Stock ROM booted.
Just do a factory reset from recovery, it should work.
Thanks for the swift replies and sorry for my late reply as well! Thanks alot for your recommendations. I haven't been able to touch my ygp for awhile due to school. But I'll surely try out everything suggested. Btw I kind of already reflashed the stock gb rom it bootlooped after so I pretty much didn't have a cwm recovery. But I'll try flashing it in a while! Thanks again! ^_^