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! ^_^
Related
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....
Hi all
I'm not new to flashing but I'm new to flashing cm7.
I odin back to stock jfd eclair. Root and Install CWM 2.xxx. I downloaded the stable cm7 and I started flashing. (after I wipe data/cache of course)
IN recovery, it said finding package, opening package, then my phone processed a series of lines and reboot automatically. On the startup, it says VIBRANT SAMSUNG, then GALAXY S CYANOGEN(mod) then the same recovery screen with many lines. It moved too fast into another reboot I couldn't read what was on the screen. And it kept doing this for quite 10 mins now.
Is it normal? if not, what did I do wrong? I can get into download mode and odin back to stock but I did it last night and I couldn't think what i did wrong.
Please help!
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
stumpyz9 said:
Hmmmm..... seems a bit wierd, try going into recovery and wiping and reinstalling with a new download.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
wavestar92 said:
No i don't think its a bad dl. I checked md5. I'm odin back to stock again now.
Click to expand...
Click to collapse
Try reflashing cwm when your rooted, may have not flashed right
Sent from my Gewgle Phone via XDA App
This happened to me also, I went directly back to recovery, 3 button, and reflashed. Worked the second flash for some reason.
Thanks. I turn it off, get into recovery again, and re flash it successfully
Same exact thing happened. I have no idea how many time I odened back to stock trying to figure it out.
I did as you guys said, as soon as that loop began, pulled the battery and got back into recovery. flashed again and worked just fine!
same thing happened to me...i got back into recovery...i noticed cwm updated to 5.0.2.8 then i reflashed and all good...when i tried to flash at first. cwm was 2.5 ..maybe thats the issued it wont flash on that...has to be cwm 5.0
anyway getting ready enjoy some cm7 on my vibrant...
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.
Noob here, please bear with me:
Updated my I577 to ICS, then rooted it using this thread: http://forum.xda-developers.com/showthread.php?t=1806118
Worked like a charm, then I picked up ROM Toolbox Lite from PlayStore, which worked fine until I tried to change themes.
Somehow, it got to where boot was stuck at vendor logo. Unfortunately I did not Nandroid backup in time, but I was able to do a Kies backup before rooting, so not worry about the data loss at this time.
Used CWM5, did davlik & cache wipes, factory resets several times, no dice. No stock ROM available so I tried this:
http://forum.xda-developers.com/showpost.php?p=30444507&postcount=6
(flashed system tar through ODIN) Hanged at "system.img.ext4".
Here's where I'm at now:
-- Boot looping at second Samsung logo
-- ODIN 1.85 still reads device at port
-- Battery indicator visible when plugged in & power off.
-- Still able to get to cwm recovery 5.5.0.4
So, IS IT SOFT BRICKED OR HARD BRICKED?
Bonus Question: Is it unbrickable?
Any input or answers are GREATLY appreciated, and a fix will most likely be monetarily compensated through Paypal.
Black-wolf, j3r3goss, or shabbypenguin if you see this, your input is certainly appreciated as well!
Its soft bricked. Hard brick means there is no life at all and won't even power on (through software).
Any soft brick is unbrickable, the only nonunbrickable brick is a hard brick (which is rare)
Sent from my MB508 using xda premium
If you can get into Clockwork Mod Recovery still then select wipe data (Do this twice), then select whipe cache (Do this twice), next select factory reset (Do this twice), finally go back and select reboot system. This should unbrick your phone for you
Sent from my SCH-I535 using xda premium
shimp208 said:
If you can get into Clockwork Mod Recovery still then select wipe data (Do this twice), then select whipe cache (Do this twice), next select factory reset (Do this twice), finally go back and select reboot system. This should unbrick your phone for you
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
This.
If you can get into recovery you're only in shallow water
Sent from my MB508 using xda premium
Something's changed
THANKS so far for the input!
I was able to nandroid out of the loop, but now it's back to my original problem--it keeps booting to the "Rethink Possible" AT&T screen & freezing.
Any ideas? I'm thinking I'm gonna be outta luck until I get my hands on a legit Gingerbread Stock tar.
Did you whipe cache, whipe data and preform a factory reset like we suggested? Preforming a nandroid restore won't get you out of your phone hanging on the at&t logo.
Sent from my SCH-I535 using xda premium
Samsung Galaxy Ace GT-S5830i brick
hey there im a noob to all this but i registered to see if someone here could give me advice.
i tried to flash a new rom on my phone (see title) and it doesnt do a thing anymore...
i rooted it and tried to put Retribution beta_2 on it and itlooked to be working till it rebooted..
all i got was the startup screen with galaxy ace gt-s5830i.
i looked around and i found that i could use download mode and odin 1 click download to put in a new rom.
so i tried that and it looked to be working but it stalled at end of install and now it doesnt even turn on anymore...
HELP!!!
hope someone knows whats up and can give me some advice.
i hope i didnr hardbrick it like i saw in this thread...
Emil.warm said:
hey there im a noob to all this but i registered to see if someone here could give me advice.
i tried to flash a new rom on my phone (see title) and it doesnt do a thing anymore...
i rooted it and tried to put Retribution beta_2 on it and itlooked to be working till it rebooted..
all i got was the startup screen with galaxy ace gt-s5830i.
i looked around and i found that i could use download mode and odin 1 click download to put in a new rom.
so i tried that and it looked to be working but it stalled at end of install and now it doesnt even turn on anymore...
HELP!!!
hope someone knows whats up and can give me some advice.
i hope i didnr hardbrick it like i saw in this thread...
Click to expand...
Click to collapse
Are you able to get into recovery mode? Did you flash a custom recovery such as TWRP or Clockwork Mod Recovery?
Samsung Galaxy Ace GT-S5830i brick -
shimp208 said:
Are you able to get into recovery mode? Did you flash a custom recovery such as TWRP or Clockwork Mod Recovery?
Click to expand...
Click to collapse
Hi thanks for your response to my problem,
yes i flashed a custom recovery from clockwork and i rooted it. i cant get in to recovery mode.
after i did that i tried flashing custom rom like i said before but after reboot it didnt do anything.
i just got the startscreen and found that i could use download mode and odin to flash original rom.
i used 1 click downloader from Odin and it started to recover my rom,but at the end it stalled.
after that happened i couldnt do anything anymore.
i thought it was totally dead but i just saw that when i connect to my comp it says unknown device..
im an idiot for trying this stuff without the knowledge..it looked easy in descriptions
but i found different descriptions how to do it..
i cant put links in my posts yet cause i am new..
i used the 1st one.. but after that didnt work i found that other 1 and that is little different...
.android.gs/update-galaxy-ace-s5830i-retribution-gingerbread-2-3-6
.technostall.com/samsung-galaxy-ace-s5830i-installing-retribution-custom-rom-firmware
i hope i have given you enough info
greets Emil
Hmm today i found out smth new,i installed some samsung drivers and now my phone is recognized as a samsung android phone-android composite adb interface its says in device mananger on my laptop.
All Fixed!
shimp208 said:
Did you whipe cache, whipe data and preform a factory reset like we suggested? Preforming a nandroid restore won't get you out of your phone hanging on the at&t logo.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I did all that, but the one thing that finally nailed it was formatting my internal SD. I also formatted my external one, but I don't even think I put it back in the phone.
So, if anybody's reading this in the future, and you're still stuck after wiping the cache, wiping Davlik & performing factory reset,
FORMAT THE SD!
And flash this through Odin: http://forum.xda-developers.com/showpost.php?p=31765274&postcount=59
Huge thanks to j3r3goss!! :good::good::good:
Main Exhilarate thread here:
http://forum.xda-developers.com/showthread.php?t=1926253
Soft bricked my galaxy s4
gagdude said:
Its soft bricked. Hard brick means there is no life at all and won't even power on (through software).
Any soft brick is unbrickable, the only nonunbrickable brick is a hard brick (which is rare)
Sent from my MB508 using xda premium
Click to expand...
Click to collapse
Hey, total noob here but Im having problems with my Galaxy S4 so I was on this thread looking for a fix.I have an AT&T Galaxy s4 (SGH-I337) and I just rooted my phone and installed clockworkmod recovery. I went to backup and then when I rebooted it freezes at the AT&T logo. Ive wiped data/factory reset, wiped caches, etc ive done everything and it freezes at the same spot. I have no ROMS as I had just rooted, just stock 4.2.2. Then I saw a vid on how to unroot/unbrick and it was working perfectly until it went to reboot.(I downloaded 4.2.2 firmware for my model phone) I used ODIN and it said pass then when it was rebooting it froze in the exact same spot (also instead of the normal bootup it still had the "custom" and an unlocked lock that Ive had since I rooted) and now I cant enter recovery mode. It starts booting but then freezes when the blue letters come on! Now even when I try to turn it on normally it freezes at the samsung logo (with unlocked lock and "custom")Please help! I would greatly appreciate it!
Here goes, hopefully someone can help!
Ive installed a fair few roms on my phone and never had any issue, maybe this explains the complacency.
After updating to CWM recovery -6.0.4.7 I get stuck on my bootscreen, only seeing "Samsung galaxy I9100P" , ive been putting I9100 roms on it and losing NFC functionality for a while.
I went to update to the newest CM-11 nightly and read I needed to update CWM-recovery first. So did that, rebooted phone as instructed after installing new CWMr and nothing. Just stuck on I9100 screen.
No way to get into recovery mode, the only bright side I have found is I can boot into ODIN download mode. So what would be my next steps anyone?
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
andrewwright said:
Flash stock rom. or flash a kernel to get a working recovery bk with odin.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
From a dig through the forums it sounds like NAND rw corruption?
I wouldn't be calling it that just yet. Unless you'd like to pay for a motherboard replacement ? Most of these are recoverable.
Used ODIN and flashed a new kernel, still on the boot screen, except now I have the yellow exclamation mark. Now to, Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.. this day is not going well..
Fingers crossed, flashed 3 or 4 kernels before one worked and allowed me into recovery mode. Trying to restore back to my backup from this morning. Heres hoping! :good:
Worked perfectly, the first thing I did was retry the initial task which was what got me stuck, currently waiting on CM-11's initial boot up after a successful install Thanks for the calming responses!