Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
Hi all my phone has some how only boots in Safe Mode for some reason. I'm running CM7 and whenever I boot my phone it doesn't go past the LG logo unless I press a button. However, whenever I press a button it takes me straight to safe mode. I've used Xiaona custom recovery to fix the boot load but that doesn't work either. I'm quite confused and discouraged because I've tried everything I can think of to fix this. None of my buttons are stuck IMO. I've search endlessly for solutions but have forum none, for most people, rebooting their phone takes them out of safe mode, that unfortunately isn't the case for me.
I've spent probably 8+ hours fooling around, I only got this phone yesterday so you can just imagine going from a beginner who knows nothing to having to use ADB commands and stuff to try and fix their phone. I'm finally ready to ask or beg for help. Please help me
Just wanted to say I've fixed this issue by holding down ALL 4 of the face keys on the phone while it was booting up. You have to hold them down until the phone is completely booted up. However, this is the only way I know how to fix it, unfortunately I have to do this everytime I boot my phone but I don't turn my phone off much so I'm happy as long as it's working.
Hi guys, stupid question (hopefully)...
I accidentally went into Download mode instead of Recovery (forgot what USB jig actually did ) and now don't know how to exit out of Download mode....
Anyone help?
Yes, "stupid" is the right word...
Had to hold power button longer than usual - almost twice as long.
Sorry all, will crawl back into corner now.
Hi
Sometimes it happens with me too , but remove the battery to get away with the download mode . This has happened alot with me and I usually do this.
my s2 is still working and there are no issues .
There's no need to take off your battery. Long pressing more than 10 sec the power button, does the job everytime.
Actually the power off tick leads my SGS2 out of download mode. But it hangs on charge screen... Weird, no?
Take a look at "it"
we were all once the same
"Had to hold power button longer than usual - almost twice as long."
Worked for me ty, went into to download mode after using s2root though i didnt had cwm to put in odin.;-)
doing this just bricked my phone...
Hey folks,
I have some serios sh!t over here.... I have installed a new rom and accidentally deleted the launcher3.apk (because usually I use nova) but in that moment I didnt have nova launcher installed!!!! And the phone rebooted itself since that moment I just see the boot animation for example but nothing else.
It wouldnt be a problem at all if I could just enter recovery wipe and install it again, or restore a twrp nandroid backup BUUUUUUTT my home button doesnt work! And thats why I cant boot into recovery since I cant touch the 3 buttons. Last time I went through adb commands into recovery but now adb says liste of device and there is one BUT it is offline... So when I type a command it says Error: Device Offline!
Is there a way to fix it without putting money into it?? Or do i need another LCD so I can boot into recovery with a working home button?? That would be a real real bad thing
Thanks a lot for help
Sanj3k
Okay, someone told me a hint! You can enter the download mode also, when you are holding volume down and then connecting the device to a charger. It worked well flashed with Odin FW etc. so no problem at all LOL! Maybe this information will help someone other. Please close the thread.
Sanj3k said:
Okay, someone told me a hint! You can enter the download mode also, when you are holding volume down and then connecting the device to a charger. It worked well flashed with Odin FW etc. so no problem at all LOL! Maybe this information will help someone other. Please close the thread.
Click to expand...
Click to collapse
Thanks for Information
I have problem with getting back to stock fullmics 5.5 on h850. I have installed it reboot and now Im stuck in secure start-up lock pattern from previous rom I believe. Pattern wont work and also meanwhile "FC system UI has stopped" warning is showing all the time.
I can get into download mode but port is not recgonized in vista so ADB cant be used (WHQL usb drivers 4.4.2 are installed ok)
problem is also that I cant get into recovery mode or
factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect.
Im really getting out of ideas to solve this...tech brain of the world please gather for help
fonejay said:
I have problem with getting back to stock fullmics 5.5 on h850. I have installed it reboot and now Im stuck in secure start-up lock pattern from previous rom I believe. Pattern wont work and also meanwhile "FC system UI has stopped" warning is showing all the time.
I can get into download mode but port is not recgonized in vista so ADB cant be used (WHQL usb drivers 4.4.2 are installed ok)
problem is also that I cant get into recovery mode or
factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect.
Im really getting out of ideas to solve this...tech brain of the world please gather for help
Click to expand...
Click to collapse
Go into twrp format data type yes how I fixed it on mine
TheMadScientist said:
Go into twrp format data type yes how I fixed it on mine
Click to expand...
Click to collapse
Why dont you fully read what I wrote
"...problem is also that I cant get into recovery mode or factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect."
ps: please excuse my writing my first language is clearly not english :fingers-crossed:
edit: just right now I opened phone up for check if buttons are OK...well turns out I wrecked button pins on motherboard.f*ck...now I know why I cant get into powerup menus...more specific I wrecked power button down pin on MB while opening back case with plastic card fkmylajf. Can be closed. SORRX
edit2: luckly I solved problem with straighteing pins so now twrp works as it should. What a noobish mistake huh...Be careful w with opening case!!??!
fonejay said:
Why dont you fully read what I wrote
"...problem is also that I cant get into recovery mode or factory reset menu from startup, seems power button down procedure wont work like previously did...for some reason bootloader warning appears almost immediately after power on so power button off and on for a sec like I believe it should, has no effect."
ps: please excuse my writing my first language is clearly not english :fingers-crossed:
edit: just right now I opened phone up for check if buttons are OK...well turns out I wrecked button pins on motherboard.f*ck...now I know why I cant get into powerup menus...more specific I wrecked power button down pin on MB while opening back case with plastic card fkmylajf. Can be closed. SORRX
edit2: luckly I solved problem with straighteing pins so now twrp works as it should. What a noobish mistake huh...Be careful w with opening case!!!
Click to expand...
Click to collapse
Sorry bout that mate I speed read a lot of stuff and sometimes miss Key details:silly::silly:
I ran into the problem with the corrupt startup and couldn't get out of it.So thats what I saw...
I run across a lot of devices so i spend a lot of time reading many many pages hard to catch it all