Hi my vibrant seems to be bricked and nothing I do seems to be able to fix it.
I was using different 2.2 ROMS and I tried to reboot recovery but then it got stuck on the bootup screen.
So I tried to ODIN back to stock, except when I ODIN and it restarts the phone it turns off after the "Galaxy S" boot animation. Trying ODIN back multiple times won't fix the problem either.
I can go into the stock recovery and Download mode just fine. Anyone know what's wrong?
BTW it happened after I did partition SD card in ROM manager.
I heard that you could flash Eugene's 2.2 froyo ROM and it'll work but I can't even get into the bootloader, stuck on the default on. Please help
EDIT: Figured it out!
Related
Hi,
I've been trying to root this phone and put clockworkmod, then an ics cyanogen rom on it.
I followed the noob guide.
http://forum.xda-developers.com/showthread.php?t=849028
I successfully used odin to put the phone back to a Verizon JFD.
The problem was that it would restart each time I plugged it into USB, I could still use download mode, not recovery.
To try to fix that problem I used:
http://www.mediafire.com/?98662oi9jcszov5
But now each time I connect USB the phone turns off.
I don't know what to do now that I can't get to download mode or recovery, or even connect it by usb..
I've looked at way too many guides today, and I think I've screwed up my phone big time.
Can anyone help me out?
Edit: I was able to get to CM7 and then ICZen 1.8.1 but it hangs during the boot animation. Because I can't get into the download or recovery menus, I cannot fix this issue.
The Skinny: updated to JB yesterday, worked great! phone died. wouldn't turn on after charging, kept booting to recovery.. so decided to go back to to stock with odin3 and then re-flash JB.
The Problem Now: stuck on "Over Stock" logo. can't get to recovery, or download.. though odin does still recognize the phone in bricked state, it can't effect any change to the device.
is there any hope??
ferther more..
every once in a while it will power on into download mode, but odin doesn't seem to be doing the trick.. but other times it boots into an "upload mode".
well out of my depth.. someone help!
Google ezbase recovery kit and try that. Even when it's for the i9000 you can use it. You can flash to stock after that.
failed
it failed miserably.. now it shows the GT-I9000 boot screen as it loops infinitely. though on the bright side, download mode is accessible again though even flashing stock wont wipe the GT-I9000 residual effects from it. more suggestions??
I'm just about at my wits end!
I have the T959. I was running Cyanogenmod 10 with no problems for a long time. Then overnight an application crashed and when I closed it in the morning my phone shutdown. After that it wouldn't boot (stuck at Vibrant logo) and won't enter recovery mode.
Following the Cyanogenmod Wiki I attempted to flash Clockworkmod to get back into recovery. It appeared to work but I still couldn't access recovery.
Failing all other solutions with the Cyanogenmod community I attempted to reset it to Stock setting using Odin. That appeared to work as well (I actually did it several times) but now it shows the vibrant logo and then goes black. Before it at least stayed at the Vibrant logo.
I've tried the "one click unbrick" application as well.
I can't find any other options. Is there any way to get my phone functional again, even at stock settings?
I recently tried flashing back to stock (JFD) from a CM 2.3.7 rom using Odin 1.7 and a 512 pit file. However, along the way I encountered many problems. For starters, the phone currently does not load past the vibrant boot screen; ergo, I can't call or text. During the process of flashing the stock rom, my phone had an error saying, "data wipe failed." Then my phone went to the Vibrant boot screen, which proceeded to the battery animation, instead of the usual T-Mobile boot screen/sounds. If I pulled the USB and pressed the power button, the phone would then proceed to continuously loop through the Vibrant boot screen.
The phone is most likely bricked right now, and I don't know how to fix it. I tried looking elsewhere and found people talking about flashing a "Eugene 2.2," but I have no idea what or where to find this; can anyone help?
I went on to use AIO Vibrant Toolbox to try to restore to stock, but that persistent error keeps coming up. Halfway through the ODIN process, I can see my phone's screen show a bunch of words, scrolling up. Among those words say, "Data wipe failed."Afterwards, the phone loads the Vibrant boot screen and battery animation; ODIN says SUCCESS, although I know the flash didn't work. I have reason to believe this is why my phone isn't flashing properly?
Hope this will get you straight.
Berzxrk said:
I went on to use AIO Vibrant Toolbox to try to restore to stock, but that persistent error keeps coming up. Halfway through the ODIN process, I can see my phone's screen show a bunch of words, scrolling up. Among those words say, "Data wipe failed."Afterwards, the phone loads the Vibrant boot screen and battery animation; ODIN says SUCCESS, although I know the flash didn't work. I have reason to believe this is why my phone isn't flashing properly?
Click to expand...
Click to collapse
Try using Heimdall One Click from this thread.
This probably won't help in your case, but try pulling the external sd card if you haven't already. Pulling the external sd card has solved a few boot loops for me in the past, but they were related to a new rom install.
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...