Related
I had installed Voodoo and went to install one of the AOSP roms available. I didnt realize that it would overwrite the kernel and now upon booting the phone will go into FC loops. I cant get anywhere and cant get into CWM. I thought I would try using ODIN to get back to stock but now its doing the same thing at stock. I'm at a loss. What should I do? Is my phone Perma-bricked?
Was it my rom? I don't think it deletes the kernal?
Sent from my SPH-D700 using XDA App
blue breeze. I didnt think so either but now I get nothing but FC's from startup. So I tried to flash back to stock. Still nothing.
Oh my there are going to be a lot of these...
I don't know. I think that IF I had flashed the ROM first and then Voodoo I would've been fine. Unless I'm wrong and that's not what caused the issue. Any solution or am I out of a phone?
why can't you get into cwm? even by turning your phone off and holding the volume keys and the power button?
It goes to stock recovery, always has. I could only get into CW by going to ROM manager and booting into it that way.
do the update.zip and it should take you to cwm
the reason you're in FC HELLLLLLL is cuz you flashed over voodoo. that's why JT said don't flash over vooodooooo. you can fix it by going back to stock with odin. then i suggest loading bubby's kernal then voodoo over that.
Ive tried going back to stock with ODIN and it still does it. I'm going to try re-downloading the stock files and do it again. BTW the FC's are: android/process.media, and TwLauncher. I cant even get to any kind of homescreen or settings to turn on debugging.
i tried going back to stock with odin because i wanted to remove voodoo anyway before i flashed a rom and still am getting FC's like crazy
Have you tried this?
Have you checked this? http://forum.xda-developers.com/showthread.php?t=807088 ...would be a good idea....
I have someone that i am trying to fix a phone for, that bought their vibrant hacked. They thought it would be a good idea to wipe it completely, not loading another rom onto it. He says it does start up, and the wallpaper comes up..but that's it. It can receive phone calls, but it cannot send out calls. Anyone know what i could do to fix it? Minus load a new rom onto it, like how to go about doing that.
File a paypal claim?
Chalup said:
File a paypal claim?
Click to expand...
Click to collapse
I don't see how this would help either him, or myself.
Have you tried getting into recovery and wiping?
If its not loading up probably I'd suggest to look into getting Odin set up so you can flash the rom on it. Odin+true stock 2.1+then you can flash stock ji6 on top.
Sent from my SGH-T959 using XDA App
disturkis4u said:
Have you tried getting into recovery and wiping?
If its not loading up probably I'd suggest to look into getting Odin set up so you can flash the rom on it. Odin+true stock 2.1+then you can flash stock ji6 on top.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
How do you run it into recovery mode? Like i said, this isn't my phone and the guy lives 5 hours away..so im trying to help him the best i can.
He told me that he cannot get it into recovery mode, because he needs the application Rom Manager to run. This doesn't sound right to me. I have the htc Evo on sprint, and i can get into recovery mode via Volume Down and power button. What is the keys for the vibrant?
Can you point me on how to do the Odin thing you are talking about?
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
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.
Hello,
My phone was previously running an unofficial version of MIUI and AOSP voodoo kernal. My phone became very buggy and what I was running on was old so I wanted to update to newer things out there today. So I knew I had to disable the voodoo kernel before installing the new ROM but getting into CWM via "Volume up and down and power" didn't seem to be working so I got into CWM using MIUI's reboot option. Unfortunately, this took me to a normal blue CWM so I though huh i guess I don't have voodoo installed then. So I wiped data and cache and attempted to flash the new ROM. about 10% in it rebooted my phone and now it gets stuck at the SAMSUNG logo. I actually can now get into the red voodoo CWM for some reason, but I can't disable it because my phone won't boot. Even though I can set it to disable since it won't boot im guessing it wont actually disable.
How can I get my phone back to stock so I can start over?
Thanks.
You need to see droidstyle's guide on flashing rooms and going back to stock. You should not have three fingered into recovery. There us a section there for your particular situation.
Sent from my SCH-I500 using Tapatalk 2
You should have put it into download mode and re-flashed your radio choice with atlas pit 2.2
Sent from my SCH-I500 using xda premium
Sorry, I resolved this by flashing a DI01 Image over Odin.