Related
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.
In anticipation of flashing Eugene's MacNut with GPS working, I managed to somehow got to the point where the phone will now not even boot up. I did a factory reset, "Linda" said "complete", then when I rebooted it did so but then shut off. I was able to get to Odin via reboot download, I flashed back to stock, but when it rebooted it shut off again. Now I cannot get the phone to boot up, either normally or in to recovery. Anyone ever have this experience, and is there any way out? TIA.
New issue...
Good to see that nobody else had this problem. Fortunately I found out how to get into download mode. I may have successfully (maybe?) reflashed stock through Odin. However, when I reboot the screen goes black and the phone turns off. I've spent hours trying to find the exact type of potential issue I have, and none of them get me past where I'm at now. The most promising I found was this one
http://forum.xda-developers.com/showthread.php?t=811820
but I am not exactly sure of the sequence: constant "adb push update.zip /sdcard" that I should be doing. Like, how many times do I do this? When I push the power button while in recovery it (obviously) just reboots, which is what it is supposed to do. Am I trying the wrong thing/ in th wrong thread? TIA.
This worked for me, but it re-partitions, so you'll lose your data.
http://forum.xda-developers.com/showthread.php?t=803492
I was also trying to find the instructions where you odin "froyo that doesn't brick" and then odin the original, but I don't see it now.
if you need to get into download mode, use Eugene's method:
pull battery and leave it out
plug in the usb to the phone and the computer
hold volume +/- key
insert battery while holding the volume key
burgon said:
This worked for me, but it re-partitions, so you'll lose your data.
http://forum.xda-developers.com/showthread.php?t=803492
I was also trying to find the instructions where you odin "froyo that doesn't brick" and then odin the original, but I don't see it now.
if you need to get into download mode, use Eugene's method:
pull battery and leave it out
plug in the usb to the phone and the computer
hold volume +/- key
insert battery while holding the volume key
Click to expand...
Click to collapse
Hey, thanks for the reply. I am able to get in to download. I'm uploading the file now, it's a big one. We'll see when it's done. Thanks again.
wbexpress said:
Hey, thanks for the reply. I am able to get in to download. I'm uploading the file now, it's a big one. We'll see when it's done. Thanks again.
Click to expand...
Click to collapse
Oh well, so much for the theoretical impossibility of bricking a Vibrant. I did the whole YouNeek fix, no go. It still does the same thing as it has since I screwed it up, it turns on, reboots and then goes black. Oh well, I think I've about had it with Samsung. The screen is awesome, but the OS is just not user friendly. The irony is that when I bricked this thing I took the SIM out and threw it back into my G1, which I have NEVER had an issue with. HTC...
I had the same issue you had, boots, screen goes black but buttons still light up. I posted the fix in a few different threads, one of which I started myself. If you search for threads I've started your fix will be there. You have to flash eugene's "froyo that will not brick" through odin and then flash the stock rom again through odin. Check my thread for a link to the exact instructions. I fix my phone in about 5 minutes once the roms were downloaded and happily shipped my replacement back so I won't have to pay the $20 in shipping
Hello everyone, I know what you're going to say but I did a very wrong move.
I tried flashing recovery image through Rom Manager. It gave me four options and I chose Vega Advent. Now after a reboot, it doesn't even boot. I tried to connect to my PC but the USB doesn't detect a thing. I tried pressing the power button for about half a minute and then I tried pressing the power button together with the volume + and - and all together, but still nothing. I fully charged the battery until the light was green but this didn't make any difference.
The NVFlash always gives me "USB device not detected".
I don't know what to do. I'm in a hurry as I'm leaving the country in a couple of days and I don't have the time to argue with woot.com
I learned a lot from this forum in my HTC Hero, LG Optimus, Samsung Tab and the Asus Transformer. You are my last hope. Is there anyway I can unbrick this? Can I hard reset the device? Can I remove the battery and put it back again? Is there anyway out of this?
Please direct me to the right direction. thanks in advance...
Did you download the adb drivers and boot your gtab holding ppower and vol-
Check out http://viewsonic-gtablet-for-dummies.webs.com/
Mantara said:
Did you download the adb drivers and boot your gtab holding ppower and vol-
Check out http://viewsonic-gtablet-for-dummies.webs.com/
Click to expand...
Click to collapse
Well, I downloaded the usb drivers for the NVFlash. And yes I tried booting the device this way but the PC didn't detect it. The notification of new devices never came up.
What do you think I should do?
What os is your PC running?
You're effed.
You probably got the worst case of rom manager bombshelled. Permanent loop in apx mode + usb recognition borked.
I'm guessing you know how to get into apx mode by power button and volume -. If you haven't tried it, then I strongly you go to the website linked in my signature and go to nvflash page. I just included nvflash stock files with CWM pre-installed.
If you have been using apx mode all this time and nvflash still can't recognize your usb, then you have a nice life.
Windows XP 32 bit
goodintentions said:
You're effed.
You probably got the worst case of rom manager bombshelled. Permanent loop in apx mode + usb recognition borked.
I'm guessing you know how to get into apx mode by power button and volume -. If you haven't tried it, then I strongly you go to the website linked in my signature and go to nvflash page. I just included nvflash stock files with CWM pre-installed.
If you have been using apx mode all this time and nvflash still can't recognize your usb, then you have a nice life.
Click to expand...
Click to collapse
I tried to use your guide, well not from the start unfortunately. I downloaded all the files but I can't get the PC to recognize the gTab or even detect anything when I plug it in.
If I send it back to viewsonic, do you think they can refund back my money or at least send me a replacement (though I'll be leaving)??
Then like goodintentions said check out the link and do it start to finish. The links there are the right files.
I have beard of people recovering from this. Just make sure you have the right drivers installed. They are on the link above.
Check it out, try it start to finish and report back. We are here to help
Mantara said:
Then like goodintentions said check out the link and do it start to finish. The links there are the right files.
I have beard of people recovering from this. Just make sure you have the right drivers installed. They are on the link above.
Check it out, try it start to finish and report back. We are here to help
Click to expand...
Click to collapse
Thanks a lot. I'll try this first thing in the morning as I don't have access to a PC now. I'll definitely report back if the PC recognized the device. Because when it says "USB device not found press any enter to continue" it stop after I press enter. There is no way to make it start to finish...
ahmadshawki said:
Windows XP 32 bit
Click to expand...
Click to collapse
Here's the problem. I didn't think to post the driver for xp 32 because... well, I didn't think anyone was using it nowadays. Going to bed now. You should, too. Check back tomorrow. I'll work modify the website after I get back from my lab.
goodintentions said:
Here's the problem. I didn't think to post the driver for xp 32 because... well, I didn't think anyone was using it nowadays. Going to bed now. You should, too. Check back tomorrow. I'll work modify the website after I get back from my lab.
Click to expand...
Click to collapse
Don't know what to say. This is the best place where someone can get some real help. Just a small question, do you think if I had access to a Windows 7 32 or 64 bit or even Linux, it will help detecting the device? 'coz I can do that...
http://www.slatedroid.com/topic/171...ther-11-or-12-babased on.sed-images-g-tablet/
Link to files and nvflash I used on XP 32. Hope it healps
Xp64 is standard so you can find those files easy but this is what I used and I'm on 32
Mantara said:
http://www.slatedroid.com/topic/171...ther-11-or-12-babased on.sed-images-g-tablet/
Link to files and nvflash I used on XP 32. Hope it healps
Xp64 is standard so you can find those files easy but this is what I used and I'm on 32
Click to expand...
Click to collapse
I'm checking this out now and I'll report back if it worked. Thanks a lot...
http://www.myadventvega.co.uk/SystemUSB.zip
This is the adb driver I used
I wanted to add something. The device feels hot or warm to be precise from the back. Now after unplugging it for about five hours. Do you think it is running and this is only a software problem?
it might be in apx mode now. It is a blank screen. Hold power for 30 seconds and release. That will make sure its off. Then connect it to your PC and hold power volume -
I just helped vvvccc a little over a month ago... see link; my post starts as post #8. Before that, did you try pluggin into a different USB port and/or use a shorter USB cable on the PC?
http://forum.xda-developers.com/showthread.php?t=1056860
While you are at it, you may want to flash just the CWM once your computer recognizes the gtablet in apx.
http://forum.xda-developers.com/showthread.php?t=1058649
If this doesn't work... there are two more options floating around but one involves opening the gtabled up.
--- BTW, stay away from Rom Manager, it's the reason I wrote up the instruction to just flash CWM ---
Any news/progress?
Unfortunately none. I guess I'll go to bed now and tomorrow I'll have access to a linux pc. May be that will be a better idea. Thanks a lot for your support. I'll update you once I do it...
It was indeed working. It stayed like this for more couple of hours. I went to sleep and when I got up it was cold. I pressed the power button and it WORKED. Just like that. Now I shut it down once again and left to charge.
Thanks a lot everyone, I'm so proud I belong to this community.
One last question, what should I do now? Do I still have to NVFlash? Should I flash the right recovery now? Also, which Rom is recommended? At least to start with, knowing that I'm on 1.2.
I tried to not start a new thread but ... I'm at a loss so here's the sitch..
I rooted, unlocked, and installed CWM using ViperMOD tool here
I got successful on upon running the program. Confirmed root, proceeded to unlock and install CWM. Like I said, the messages informed me of no errors and got successful. HOWEVER, when I power off the prime and attempt to button combo into recovery, the phone just boots up. I don't see text to even press the volume up button.. the only text I see is the asus kernel splash and boot ani..
I then went to RM and tried to flash CWM that way.. again i got successful but button combo's aren't working or I'm just not getting it right.. (thought, you should know I tried bout every damn combo I could think of, AFTER reading an trying what is suggested.) So then I tried rebooting into recovery via RM.. phone just reboots. I then tried installing touch recovery via RM.. got successful but again, no way to boot into recovery.
According to RM my current recovery is 5.8.x.x
I read another way to install CWM via BLOB, but I've also read installing anything BLOB after installing CWM will lead to a brick. Obviously I'm trying to avoid that. For the love Android, if anyone can point me in the right direction I'd be really happy. Thank you!
*EDIT****UPDATE**
This is a little confusing as i just watched yet another how-to vid.. and this one showed booting into recovery from power on .. and I don't believe it but it worked. Finally saw the 3 text lines at the top when Asus spash showed up. I powered off the Prime and tried again.. no problems whatsoever.
I'm sorry for starting a new thread.. believe me, I started searching yesterday and gave up at 11:30 last night.. started my quest again this morning and no dice so I started a new thread. Again.. Jerdog, I'm sorry man. Ugh.. feeling pretty bad about this thread now. If it can be deleted, please do. Otherwise close.. :-\
[/YOUTUBE]
Coreym said:
I tried to not start a new thread but ... I'm at a loss so here's the sitch..
I rooted, unlocked, and installed CWM using ViperMOD tool here
I got successful on upon running the program. Confirmed root, proceeded to unlock and install CWM. Like I said, the messages informed me of no errors and got successful. HOWEVER, when I power off the prime and attempt to button combo into recovery, the phone just boots up. I don't see text to even press the volume up button.. the only text I see is the asus kernel splash and boot ani..
I then went to RM and tried to flash CWM that way.. again i got successful but button combo's aren't working or I'm just not getting it right.. (thought, you should know I tried bout every damn combo I could think of, AFTER reading an trying what is suggested.) So then I tried rebooting into recovery via RM.. phone just reboots. I then tried installing touch recovery via RM.. got successful but again, no way to boot into recovery.
According to RM my current recovery is 5.8.x.x
I read another way to install CWM via BLOB, but I've also read installing anything BLOB after installing CWM will lead to a brick. Obviously I'm trying to avoid that. For the love Android, if anyone can point me in the right direction I'd be really happy. Thank you!
Click to expand...
Click to collapse
I had the same issue with the TF101, TF201 is the same...POWER OFF completly, now POWER ON HOLDING POWER AND VOLUME DOWN until white writting comes up on TOP LEFT OF SCREEN, then let go of power and volume down and press VOLUME UP you should see "ENTERING RECOVERY IMG"
i did a quick vid and put on YOUTUBE for you check it out,
hope it helps
LNKNPRKFN said:
I had the same issue with the TF101, TF201 is the same...POWER OFF completly, now POWER ON HOLDING POWER AND VOLUME DOWN until white writting comes up on TOP LEFT OF SCREEN, then let go of power and volume down and press VOLUME UP you should see "ENTERING RECOVERY IMG"
i did a quick vid and put on YOUTUBE for you check it out,
http://www.youtube.com/watch?v=1VOiCogOQJ0&list=UUdwXLQixIUNxzkX0zHVsYpQ&index=1&feature=plcp
hope it helps
Click to expand...
Click to collapse
Thanks dude.. Yeah, this was a stumper for me. As I did the button combo right, and maybe just maybe I let go too soon when seeing the asus screen, but I can tell you I tried endlessly last night and never saw the little text in the top left corner. Just watched zedo's vid and he started from power on.. so I tried, and it worked. Now i see the little text everytime I button combo..
Oh well.. really glad I got it figured out.. and thank you so much for the reply and help. Really!
Coreym said:
Thanks dude.. Yeah, this was a stumper for me. As I did the button combo right, and maybe just maybe I let go too soon when seeing the asus screen, but I can tell you I tried endlessly last night and never saw the little text in the top left corner. Just watched zedo's vid and he started from power on.. so I tried, and it worked. Now i see the little text everytime I button combo..
Oh well.. really glad I got it figured out.. and thank you so much for the reply and help. Really!
Click to expand...
Click to collapse
I must have NVFlashed my TF101 100x cause i thought CWM didnt do on because i use quickboot and it didnt go to recovery and i didnt know how to get it there but then i figured it out, so since my prime is the same its GRAVY, at least you got it now!!!
food for thought: i have flashed my sgs and my maguro countless times both combined, and i never ever encountered such an error. Either adb reboot recovery, native rom option or if neither are available, button combo.
/offtopic: i'm eager to see what nvflash can do. definately more powerful than fastboot
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.