My phone was working fine after installing the DOW14 kernel yesterday. This morning it was even working fine. Even my alarm went off this morning on the phone and I set it an hour ahead (for more sleep) and it didn't go off. I looked at my phone and the screen would not come on. The "buttons" at the bottom lit up, but nothing I had to hold the power button down to get it to reboot.
It got past the "Vibrant" text and shows the green robot for TeamWhiskey, but just sits there. Tried taking the battery out and still it will boot to the same place. Can anyone help?
I did not overclock, I never ran SetCPU.
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
jmcghee1973 said:
If you can get it to download mode, try flashing another kernel through odin since you cant see anything. Just the kernel not a rom. Supercurio has some voodoo kernels for odin in the dev section. Just look for your base and odin the corresponding kernel. Goes in PDA. Dunno if there are any "stock" odin kernels or not.
Click to expand...
Click to collapse
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
raulcota said:
Hold vol up + down + power right? I can't seem to get into recovery/download mode. I am downloading Bay_wolf's AIO Vibrant Toolbox 2.5 right now.
Click to expand...
Click to collapse
Watch this video to get to download mode http://www.youtube.com/watch?v=D0aoabVtPJ8&feature=youtube_gdata_player
Sent from my SGH-T959 using XDA App
I had a similar issue and crazy enough, it worked. Then I just odined back to stock then rooted and flashing all over again
Sent from my SGH-T959 using XDA App
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
raulcota said:
I can get it to reboot using adb reboot recovery, but it never actually boots into recovery still sticks at the teamwhiskey robot chick screen, lame
Click to expand...
Click to collapse
not recovery...download mode w/the digging robot on the screen.. I'm not familiar with adb does it adb reboot download or anything of that nature?
Try this, it worked for me. Pop your battery, put it back in, hold vol up down and power. Wait for vibrant to pop up the second time and release. Should put you in recovery. Factory data reset, reflash you rom, wipe dalvik and fix permissions, then reboot. I had the same issue with the Bionix 1.2.1 update and the glasstopia theme w/ dragon 4. They didnt play well together. Hope this helps.
you may want to build a jig or buy one online in the future just in case you cannot get into the download mode.
http://cgi.ebay.com/ws/eBayISAPI.dl...25272&ssPageName=STRK:MESELX:IT#ht_595wt_1139
OK, I can get into download mode and I have been trying this method with no success:
http://forum.xda-developers.com/showpost.php?p=8698655&postcount=150
Odin flashes the phone and it just comes back and reboots again. Man this sucks
I am wondering if there is a full flash file somewhere I found one Fascinate, but I am afraid to flash my Vibrant with it.
http://forum.xda-developers.com/showthread.php?t=867648 that is the fascinate one
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
I agree man.
I've looked at every single thread with this same exact issue.
No avail. The file system, the ones that are reserved and locked for the bootloader and ROM are corrupted, is my guess.
I can load all the roms on there, but something isn't loading correctly, or is beyond corrupted, not allowing me to boot the phone at all.
My phone is toast too.
Damn, im not happy.
Nobody has a fix for this though. Nobody.
Anyway, sorry to hear about your phone. Mine is also bricked completely.
Keep in mind, this is from somebody who has bricked every possible way (apparently not this way), and ODIN at least once a week. I've also used Eugene's i9000 OC kernels, old DOW OC kernels, and TTBAL's OC kernel with NO PROBLEMS AT ALL!!! 1.4gHz stable.
Now this.
WTF Mate.
drewdude007 said:
Several people are having this problem including me... I worked on it all day yesterday. No matter what you odin, even eugenes no brick fix then JFD, nothing will work. I hate to tell you but your phone is toast.
Sent from my MB200 using Tapatalk
Click to expand...
Click to collapse
I see that in the DoW 14 thread now. I am not giving up yet, but that is discouraging.
Unbrick me!!!
ive bricked my phone before and ive used odin to get my phone running again but this time its diffrent it wont go into download mode it just keeps blinking at the VIBRANT samsung screen and when i connect it to my computer the battery loop turns on and if i let go of the buttons that take me to download mode it just goes back to flashing vibrant IM SCARED someone plz help!
posted by team whiskey
"Optional Kernels:
Optional kernels will be uploaded and posted when I get home.
They will include a Modded DOW and Modded Dragon to allow for mounting Internal SD. Do Not flash the current DOW/Dragon kernels or you will loose mounting functionality."
my girls phone is shot and i took the dow off mine real quick
no more oc for me thanks sold my bricked phone on ebay for 150$
maybe that will help for people to recover the loss a bit?
good luck i tried for days.
Still Broken...
Anyone ever get this fixed? I still have a broken phone
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
what rom are you running? did you check to see if it was even compatible with the kernel your flashing? I mean.... are you on gingerbread roms or froyo?
Related
This morning I wanted to install a new rom and for some stupid reason, I forgot my phone was a Vibrant and not a I9000.
The rom installed just fine using Clockwork but once booted into recovery mode, I am unable to use the power button as the select button. Also, the volume up and volume down buttons are reversed. I am guessing that the I9000 has a home button that my phone does not.
Question is this: Is there anyway to get OUT of recovery mode? I tried to connect using adb but my computer could not find the device.
Am I royally fcked?
Don't listen to the guys on top...everyone makes mistakes..try going into download mode and flashing "Eugene's froyo that does not brick". After that flash jacs nandroid backup. I would post links but I'm on my phone....you can find the links in the vibrant bible (its one of the stickys in this forum)
Instructions to get into download mode:
Turn phone off
Take out battery
Put battery in
Hold volume up and down and then insert USB cable.
This should take you to download mode.
Then flash the roms listed above in that order through odin (also found in the Bible). Hope this helps...
Sent from my SGH-T959 using XDA App
Do as he said above, but also make sure you have odin opened up before plugging in usb to the phone, and make sure you have all the drivers for the phone installed. I fought with odin for about two hours my first time before I finally realized I had to have odin opened first.
Sent from my SGH-T959 using XDA App
Thank you guys so much. Not only does it work but now Froyo is installed!
Like jtc442 stated, Odin must be started before anything will work.
As an aside: The up and down volume buttons are reversed and the splash screen is stuck with I9000. Not a big deal, something to remind me which roms not to use.
stefan.buddle said:
PS, Even if we were to give you directions to possible rectify this problem, you most likely couldnt follow it to save your life
Click to expand...
Click to collapse
Still Alive...
zednaught said:
Thank you guys so much. Not only does it work but now Froyo is installed!
Like jtc442 stated, Odin must be started before anything will work.
As an aside: The up and down volume buttons are reversed and the splash screen is stuck with I9000. Not a big deal, something to remind me which roms not to use.
Still Alive...
Click to expand...
Click to collapse
Well done dude! Mistakes happen, glad you sorted yours out. Those are pretty normal things in froyo as far as i know so its not a ROM issue. If you want a really good ROM I would recommend Bionix ROM, its currently the top dog of Vibrant ROMs
zednaught said:
Thank you guys so much. Not only does it work but now Froyo is installed!
Like jtc442 stated, Odin must be started before anything will work.
As an aside: The up and down volume buttons are reversed and the splash screen is stuck with I9000. Not a big deal, something to remind me which roms not to use.
Still Alive...
Click to expand...
Click to collapse
glad you got it back working. you should be able to get the buttons working right by flashing another rom, like bionix, or some of the other great roms in the forum.
You also could have used adb to reboot it.
Sent from my SGH-T959 using XDA App
Chalup said:
You also could have used adb to reboot it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I did give adb a try. The command prompt just sat there with a blinking cursor.
jtc442 said:
glad you got it back working. you should be able to get the buttons working right by flashing another rom, like bionix, or some of the other great roms in the forum.
Click to expand...
Click to collapse
Yeah i will give that a try. Im guessing roms only replace certain components?
zednaught said:
I did give adb a try. The command prompt just sat there with a blinking cursor.
Yeah i will give that a try. Im guessing roms only replace certain components?
Click to expand...
Click to collapse
can you not use odin and install everything to get it back to factory settings? using the correct pit and tar files? then start fresh? download the all in one zip, and start fresh.
There is a known issue with non-Vibrant froyo ROM's with the reversed buttons, and 3.5 mm jack. As far as the recovery is concerned, I think either home or back button should serve as a select button (on the original Galaxy it is the large home button).
Hey folks. Just had a similar case (all fixed now though ). In my case, I went from stock JI6 to the Vibrant Hybrid R3 ROM, and was stuck at the Vibrant screen for about half an hour. Decided to ODIN back to JI6, which made it stuck at recovery. Fixed that by using ODIN to go back to 2.1 July stock and then back to JI6. What is it that caused the two soft-bricks in the first case? (For the record, I followed instructions to the letter) Just wondering.
EDIT: I suspect I misinterpreted the term "stock." I assumed stock meant a T-Mobile ROM, not specifically the ROM that shipped with the phone. Was that the issue in the above incident?
jtc442 said:
can you not use odin and install everything to get it back to factory settings? using the correct pit and tar files? then start fresh? download the all in one zip, and start fresh.
Click to expand...
Click to collapse
In many cases no, but maybe in this exact one... If not you will get stuck after the "galaxy s" screen with a black screen and uplights on the four capacitive buttons...
Thread cleaned. Please either help the OP, or don't post. Simple as that folks. Don't flame
please help me ! i did the same thing. i accidentally flashed the i9000 rom instead of the vibrant one. im stuck in recover mode ! the up &down buttons are reversed and none of my keys work as the "OK" key so i cant press enter. i tried to go into download mode but every time i try it just goes to recovery again and nothing is working. please help !
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
so im trying to help my cousin out he wanted me to return his phone to stock because he was having issues with mms and gps. it was on one of the bionix roms i cant remember which version thou. so i was reading all this morning trying to figure out the best way to unroot and odin seemed to be the easiest. i followed this guide (http://forum.xda-developers.com/showthread.php?t=734475) and everything went perfect and when the phone began to boot it showed the 3 boot screens (samsung vibrant, pink stick together, then the blue one with the lil jingle that says galaxy s) and then the screen just goes black and nothing happens.. i have to take the battery out and i can still get into download mode and the android system recovery but idk what to do. ive tried redoing odin back to stock but always the same outcome. for the past 2 hours ive been non stop searching but cant find anything that will help if someone could shed some light on what i need to do that would be awesome. ty
I'll grab the link in a minute and post it for ya. You should try flashing eugene's froyo that doesnt brick via odin, let it reboot to recovery. Pull the battery, boot back to dl mode, then flash the stock jfd via odin selecting repartition the last flash. Be sure you can get to dl mode with the volume button- plug in usb method before flashing the froyo that doesnt brick, you'll need to boot back to dl mode that way after the battery pull.
Edit: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Hope it helps
Sent from my Loki powered Vibrant on the XDA App
When the phone is rebooting how long does the screen stay black, after the first boot of changing a kernel or any system files the dalvik cache needs to be rebuilt and can take some time (upto 5 minutes) on the first boot. My suggestion is to make sure and use jfd tar file and 512 pit file and then just let the phone sit for about 15 minutes after odin says pass. Once you get a pass from odin the phone is going to work unless something in the tar or pit files was damaged. Just let the phone sit and all should be well.
thanks for the quick replys im going to try both suggestions now and ill get back to u when i find out if they work
Br1cK'd said:
I'll grab the link in a minute and post it for ya. You should try flashing eugene's froyo that doesnt brick via odin, let it reboot to recovery. Pull the battery, boot back to dl mode, then flash the stock jfd via odin selecting repartition the last flash. Be sure you can get to dl mode with the volume button- plug in usb method before flashing the froyo that doesnt brick, you'll need to boot back to dl mode that way after the battery pull.
Edit: http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
Hope it helps
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
+1 this is the sure way to solve this problem
well thanks for both replys Br1ck'd ur method worked his phone is now back on stock! just one last thing how should i go about updating it to the latest stock rom. when i hit software update it says nothing is available. i know there is a newer eclair update but since i dont have a vibrant im not to sure what the latest is. i see there is a froyo update out there but has tmobile released an official that i can load on there for him? and how will i go about getting it?
dylan6879 said:
well thanks for both replys Br1ck'd ur method worked his phone is now back on stock! just one last thing how should i go about updating it to the latest stock rom. when i hit software update it says nothing is available. i know there is a newer eclair update but since i dont have a vibrant im not to sure what the latest is. i see there is a froyo update out there but has tmobile released an official that i can load on there for him? and how will i go about getting it?
Click to expand...
Click to collapse
The only official 2.2 we have for the vibrant wasnt released as an ota. You can snag it through Kies or KiesMini, but it was my understanding that it messed up some peoples sd cards. If youre looking for 2.2, and you want it as stock as possible, your best bet is to dl and flash one of Whitehawkx Ka6, KA7, or KB1 roms in the developement forum. My Loki build is 2.2, but far from stock, and we have a bunch of roms out here that are going to run better than any ota update.
Sent from my Loki powered Vibrant on the XDA App
Br1cK'd said:
The only official 2.2 we have for the vibrant wasnt released as an ota. You can snag it through Kies or KiesMini, but it was my understanding that it messed up some peoples sd cards. If youre looking for 2.2, and you want it as stock as possible, your best bet is to dl and flash one of Whitehawkx Ka6, KA7, or KB1 roms in the developement forum. My Loki build is 2.2, but far from stock, and we have a bunch of roms out here that are going to run better than any ota update.
Sent from my Loki powered Vibrant on the XDA App
Click to expand...
Click to collapse
+1 Loki Rules
I was trying to go from my current ROM Perception v1-RC1 back to UnNamed v2.21 and got stuck in a clockwork mod recovery loop.
None of the blue menu options work, they just go to the CWM icon. All I can do is power off my phone and it just boots back to the same place.
I did get to the ODEN option somehow at one point but haven’t been able to get back…(screen I came to when I first rooted.)
I have switched from ROM to Rom in the past but never had this issue. Yes I’m a noob and I have been searching for the answer and did find exitrecovery.zip recommended for other devices but not a SGS2 and don’t want to do any more harm. Also it sounds like those people have their CWM menu working in some fashion but just couldn’t reboot. Should I go back to ODEN and start from scratch like I am re-rooting? ANY help would be great. (Walk through, point me in the right direction, anything.)
Thanks
KC37
Here is my info (what I can get)
Phone: AT&T Galaxy S2
CWM: Recover Version 5.0.2.3
Kernel: (Whatever came with Perception v1-RC1)
(If you can tell me how to get more info that could help let me know)
**Update**
when "trying" to turn the phone off it goes to a battery icon and back to CWM. I can't get back to ODEN reader mode ( Vol Down+power)
Ancient kernels use home/back instead of power.
Yeah, I was dumb and back to the Odin mode...I thought I would start from scratch so I flashed the .tar file I started with a while back: SGH-I777-ATTGalaxyS2RootStockZedomaxKernel.tar
Passed in Oden, good right?
Reboot went right back to CWM loop...
Am I looking to redo everything? Phone DPA ect? 100% new firmware?
Entropy512 said:
Ancient kernels use home/back instead of power.
Click to expand...
Click to collapse
Like entropy said you use the home key to make your cwm selection. Also to get into download mode your phone needs to be unplugged , then you hold power + volume down and plug it in to usb.
Sent from my SGH-I777 using xda premium
Correction on my last post its just volume down and plug it in. No power button.
Sent from my SGH-I777 using xda premium
FIXED!!!!!
flashed SiyahKernel v2.6.14 in ODEN on a whim and I'm back!
Zedo's kernel is also ancient - definitely does not work with UCKK6, and probably doesn't have the fixed recovery keymap either.
I just use the pre rooted stock odin roms in Dev section and return the device to stock (No BL). Then flash CWM. Saves a lot of headache when jumping different roms.
I need help. Last night my phone was almost dead and I put it to charge overnight. I woke up checked the phone and strangely enough it was off. I turned it on and it was stuck on the Vibrant logo. I tried going on recovery mode since I'm using CM10.1 and it wouldn't go on it. I decided that I needed to ODIN the phone back to stock. I've done this before and I have the right files for it. Everything went flawlessly. When it was done and started to reboot It was stuck on the Vibrant logo. I need help (again). Is it actually bricked or what? This is my only phone and I've just recently changed it's cracked screen which costed me $100. :crying:
Nope.
Brick = Phone doesn't even turn on.
So basically what your problem is, is the phone just keeps rebooting?
I'm also guessing you can still get into download mode, which you ODIN'd from?
For recovery, try this method:
Hold Volume DOWN + power button, once phone says Vibrant, let go of power and only hold vol. down for ~3 more seconds.
If thats what you've been doing do this:
Hold Volume UP and DOWN + power button, the rest is same as above.
Have you made sure you are flashing the right files from ODIN?
Make sure to re-download all of the files, use a more recent version of ODIN (keep the old one, new ones don't work sometimes)
I'm pretty sure I'm using the right files because I've done this before and it worked. It's like if it doesn't want to work any more. My phone just displays the vibrant logo for about 3 seconds and it just turns off. Download mode does work but recovery mode doesn't work. I've downloaded the files like 3 times and I have ODIN v1.0 and v1.7. Thanks for the help tho...
-[X]- said:
I'm pretty sure I'm using the right files because I've done this before and it worked. It's like if it doesn't want to work any more. My phone just displays the vibrant logo for about 3 seconds and it just turns off. Download mode does work but recovery mode doesn't work. I've downloaded the files like 3 times and I have ODIN v1.0 and v1.7. Thanks for the help tho...
Click to expand...
Click to collapse
So the phone stays awake during download mode??
hmm.. I'm gonna do a bit of searching around here to see if I can find any solutions, pretty sure someone else a while ago had this issue.
edit:
Found EXACT same issue, guy managed to solve it and has left notes on how to do it
http://forum.xda-developers.com/showthread.php?t=2031809&highlight=phone+turns+off
oh wow.. so I guess that my Internal storage is messed up. I have a sandisk 8gb class 10 though. Thanks for the help mate.
If you're on stock , open Odin and place this overstock tar in PDA with everything else unchecked http://db.tt/ZUcGR23q . Before trying this overstock tar kernel, flash the GB boot loaders first and see if that gets recovery back. Anyway, after odining overstock try to boot and let the voice (Linda)complete the voodoo lagfix and pull the battery and try see if you're recovery is back
so while I put overstock tar I also put the pit file right?
-[X]- said:
so while I put overstock tar I also put the pit file right?
Click to expand...
Click to collapse
Just PDA no pit. You might have to extract it first before using it. It should just drop in there. No go on BLers?
Sent from a Slim Bean 4.2 Beta2..................
Dougfresh said:
Just PDA no pit. You might have to extract it first before using it. It should just drop in there. No go on BLers?
Sent from a Slim Bean 4.2 Beta2..................
Click to expand...
Click to collapse
no go on the bootloaders and on overstock. I think its time to save up some money for a new phone because everything is kinda complicated for me. Thanks tor the help tho.
Don't give up bro, Back in the day, I would spend like 6+ hours fixing my soft and hard bricks... My last advice would be to download the semaphore kernel tar and Odin it. http://forum.xda-developers.com/showthread.php?t=1847961 main purpose is to get recovery back. Devil's kernel also has a tar ball for Odin. Choose any version, good luck !!!
Sent from a 959 Slim Bean 4.2 Beta2..................
Dougfresh said:
Don't give up bro, Back in the day, I would spend like 6+ hours fixing my soft and hard bricks... My last advice would be to download the semaphore kernel tar and Odin it. http://forum.xda-developers.com/showthread.php?t=1847961 main purpose is to get recovery back. Devil's kernel also has a tar ball for Odin. Choose any version, good luck !!!
Sent from a 959 Slim Bean 4.2 Beta2..................
Click to expand...
Click to collapse
Thanks man, I'll try it out.
Just so you know there are plenty of Vibe users that have either fallen victim to the EU bug or other internal sd issues.
We can help. Just be patient and willing. I'll shoot up some links when I get back to my PC that might help.
Woodrube said:
Just so you know there are plenty of Vibe users that have either fallen victim to the EU bug or other internal sd issues.
We can help. Just be patient and willing. I'll shoot up some links when I get back to my PC that might help.
Click to expand...
Click to collapse
Hey thanks. I think My internal SD is shot. and thanks for your time to help me out.
Woodrube said:
Just so you know there are plenty of Vibe users that have either fallen victim to the EU bug or other internal sd issues.
We can help. Just be patient and willing. I'll shoot up some links when I get back to my PC that might help.
Click to expand...
Click to collapse
Indeed, I am one of them. I think I've been EU'd for well over a year now, but it's certainly workable.
You can still enjoy all of newer roms and whatnot, you just have to get the external sd card partitioning straightened out and get used to the vold.fstab swap.