Bricked Vibrant even after Odin restore - Vibrant General

Hello all!
I was trying to replace a .9 file when everything force-closed on me, so I could not go into Clockworkmod Recovery to restore the NAND.
I restored with Odin, but during the messages tell me that the "data wipe" has "failed" in red text. The phone boots up through the stock animations and pink text, but I'm greeted with a blank screen no matter how long I wait. The bottom buttons light up.
What should I do?
EDIT: Yes, I've done it multiple times, each with the same outcome. I'm sort of frantic right now. Recovery mode works fine, but I don't think there's anything I can do there to unbrick my phone. I wiped all user data and the cache and rebooted, but no avail.
EDIT2: Never mind. Mods please close this thread. I restored the kernel image, and it is working like a charm now.
EDIT3: Never mind yet again. I followed instructions from androidforums. com/vibrant-support-troubleshooting/186959-samsung-vibrant-bricked.html#post1662645
but I end up with a bad kernel that asks me to force close every process over and over. I'm desperate as of now.

Have you tried Jacs/Kings kernel? WCS use the Froyo method in Sombionix ROM thread. Good luck...

Related

Tried to flash CM7rc2, failed, now phone won't boot

WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
it goes OK, BUT:
"Restoring boot image..."
"Restoring system..."
"Restoring data..."
dalvik-cache
^^^ wtf is that?
it's stuck on "dalvik-cache" forever.
Pulled battery, tried again, same result.
Pulled battery again, tried to reflash older backup. BOOT LOOP.
So now I have a phone that isn't exactly bricked, but is unusable. I suspect there's a way to recover this, but I have no idea how to go about it. Help?
I almost see why no one else is helping. I surely posted in the last thread you had about the same thing. Your list never once mentioned a full wipe before installing CM7 over stock.
Sent from my CM7 powered G2

SBF'd yesterday, now it boot loops

So like the title says, I SBF'd my phone yesterday to start from scratch, and now the damn thing is boot looping. I was running LB .5 on .595, and flashed the VRZ_MB810_2.3.34_1FF_01.sbf file using RDLite 4.8 (same thing I've done before, just not while on GB).
I've tried SBF'ing it a few more times, and I've let it sit, trying to boot, for 20+ minutes. The SBF seems to go through successfully. The result says PASS, so then I reboot the phone, and then boot loop.
Anyone have any suggestions?
Well, nevermind...instead of doing those multiple SBF's, I should have just looked around. Found this on droidxforums.com, and it's going through the activation now.
http://www.droidxforums.com/forum/droid-x-rescue-squad/14548-bootloop-after-flashing-sbf-file.html
You always need to wipe data and cache a few times before SBF'ing or installing any new ROM from scratch. Only with incremental upgrades to existing ROMs where the ROM chef says you don't have to wipe, can you avoid doing so.
Well, I didn't think I needed to specify, but yes, I wiped data/cache/dalvik when I flashed the ROM. So I don't really know why I then had to boot into stock recovery and do it again.
How many times did you wipe them? It doesn't work like deleting regular files on a computer, you need to clear them at least 3 times each. I don't know the details as to why, but never clear data/cache fewer than 3x. I do 5x.
weird.... mine usually works and on the pc just stops on 99% eventhough it's done and working. And once it bootlooped after installing a custom ropm and coudn't access both clockwork or original recovery so sometimes it may work, sometimes it may not work.

Tried to install CM7 - now I can't get anywhere.

Hi all,
I'm having a little problem. I have researched but everything I've found leads me back to square one...
So I followed this guide to installing CM7 on my M2. Please note that I have in the past successfully rooted my phone, installed the Argenstone ROM and one other basic Great Britain Rom. So I'm not a total nub. However at this stage I have a phone that's is useless to me...
My phone is rooted. I have Droid2Bootstapper installed and I managed to get the CWM 3.X installed. I downloaded the all-in-one.zip file from the CM7 ROM thread (the zip is actually called EndlessCM7-110901-nightly_build.zip - hope that's not an issue?)
I booted into CWM and applied the EndlessCM7-110901-nightly_build.zip and after (without a reboot) wiped everything (I had backed it up previously).
I rebooted the phone and...well I get the Google logo with the Motorola M and the Cyanogen bot as the 2 'O' characters. Then after a while a 3D rotating 'square' and the android writing and logo 'shimmering' in and out but that just goes on forever. I left it for an hour at one point and just gave up.
Now I can't even get past the Google logo. I've tried restoring my previous back up but that won't work either. I can't boot into the OS to actually use RSD lite to flash a known working ROM over the top.
When the LED turns blue and I hit the volume key it displays "Android BootMenu <v1.0.3>" which is different to the CWM 3.X that I was getting prior to applying the EndlessCM7-110901-nightly_build.zip file.
From here I can select to recover the last 'latest recovery' which when done loads into CWM-based Recovery v4.0.1.6-defy.
Basically I'm at this point where I seem to be able to load just about every boot menu under the sun and do everything but actually launch the damn OS.
How can I get out of this hole? Preferably I'd like to get everything back to the stock ROM the phone came with so that I can start from scratch again.
Any bodies help would be more than appreciated.
Cheers,
- Matt
EDIT: I have even used CWM 4.X+ to try and restore the Argenstone ROM. it goes through the whole process of checking the MD5 sums, restoring the system and boot images etc and seems to work without any issues. I then wipe all data and reboot. Nothing - still the same cyanogen Google logo and the only thing I can do is boot into all the CWM menus.
*sigh*
Argh feel like a true idiot now. It took me about an hour of searching earlier but I've only just found/remembered how to get RSD lite to see my phone (pwr+volume+camera) and I'm wiping the whole thing to the factory (vodafone) ROM. Might take the opportunity to take it to Vodafone and tell them it never gets a damn 3G connection lol...provided this flash works (touch wood).

Not soft or hard brick...half brick??? Help!

Hi all....not a noob here, but nowhere near a dev, and I'm perplexed beyond reason here......
My phone was being all glitchy so I did a complete hard reset, flashed stock MDL ROM, flashed upgrade to MF9 (didn't want to wait for OTA), flashed cf autoroot then philz touch recovery and everything and was running great.
Then I went to flash CM10.2 and afterwards and didn't get a reboot, but didn't want to deal with the unrooting issue so I flashed a different kernel first (which I think may have been the problem.) I pulled the battery and attempted to reboot from being off. All hell breaks loose. It won't load no matter how I attempt a boot, (recovery, from "off") so I decided it may be best just to start the process over.
Odin flash back to stock MF9 thinking no biggie, then when I go to boot things get weird. No bootloop, but it takes awhile then boots but no "main screen" I have the status bar on the top, then when I go to shut down I can see the shut down menu, but nothing else. Blank face.
So....I'm totally lost at this point. I've tried stock kernel, stock ROMs, reboots galore, and I have no idea what component of the ROM is missing. I have no clue how to fix it!!!! Can someone more informed than I PLEASE help???
UPDATE - tried flashing crawjr's stock rooted odex - no dice. Still reboots through yellow logo to "blank" homescreen; I can hear touch sounds when I mess with the screen...it's like the ROM is running I just can't see it?
crawjr's ROM fixed after booting into recovery and factory reset. This can be deleted.

[Q] At my wits end

tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk

Categories

Resources