Related
I am trying to flash my vibrant to stock, but my laptop says usb unrecognized.This causes Odin not to detect my vibrant in download mode. I have downloaded all drivers including nexus drivers, but still same error usb unrecognized. I have then start on switching data cables including the stock data cables but the errors remain the same. I have tried on different computers and different windows, nothing working its the same errors on all computers. I have messed up by formatting everything in the Vibrant, now it boot loops to Vibrant logo. I can get into download mode normal but I cant get into CWM or any recovery mode, its probably because I have formatted the whole phone. When the phone is off, I plugged in the micro USB to the phone from the laptop, all it shows is the white lines that are in circler motions and then freezes. Weird my laptop still detects it as a USB unrecognized. As the phone is plugged in to the laptop I try taking the battery out and my phone is still on with the frozen screen of those white lines in circler Motions. Can anyone help me, or at least explain to me what the problem may be? My thoughts is that it may be a hardware problem. If so can anyone provide me some schematics on the USB portion? I hope we can bring some light on this problem. Giving it to T-Mobile is not an option. I have dealt with many problems and solved it, but this is one problem that keeps me stomp in my own tracks.
You can give a man a fish and he will eat for a day, but if you teach a man to fish, he will be able to eat for a lifetime!
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Woodrube said:
Ok, so I am in a similar situation as yourself. I bought another Vibrant that was stuck on the bootloader screen. I gets into DL mode just fine, however Odin doesn't recognize it. I have uninstalled, reinstalled the drivers, used Nexus S and GNex drivers, 4 cords and 3ports and still no joy. My daily driver Vibe is like a mid-town flasher and is seen all over the place. So this leads me to believe that it is not driver/SW related but rather HW realted for me.
I think that my next step is to clean the USB ports on the phone and see if that works. If not, then I'll have to probably crack her open and clean there. I have another laptop that is using WinXP, so I might give that a try since nothing Samsung has ever been installed on it.
Keep me up to date with your findings and I will do the same with mine. Clearly I am not a noob but now this is just making me mad. Why one phone works/is seen and not the other. Common denomitator has to be HW.
Click to expand...
Click to collapse
I agree with you, it may be a HW issue. I have tried connecting other phones to my laptop and it reads it just fine, but for my vibrant no success. Im gonna go ahead and actally open it up and check on some componets, i have a feeling that it may have burnt one of the componets due to over charge. Ill get back with you on my findings. Keep me updated on your progress.
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Woodrube said:
Before you open her up, have you tried cleaning the metal contacts inside the USB on the phone? I am at work not, so I can't try anything, but I would check that before opening. Might just need to be cleaned.
Click to expand...
Click to collapse
yes i've tried. I used a Q-tip and some alcohol, still same problems.
Update: Nothing!! How about you?
I have tried un/reinstalling the drivers, Odin v1.8, 1.3 and 1.0, about 4-5 cables and all 3 ports. I have cleaned the USB with alcohol and at this point am at a slight loss. The phone boots into DLmode and charges fine, so I don't think it is a faulty USB port. I cannot get into any recovery or ROM boot. All I have is DLmode and the GB bl screen. No kernel or ROM splash.
Gasp! I'm in a similar boat guys. My phone charges fine, and all my drivers are working and up to date...I can get into DL mode and all that jazz...phone even boots up and works! (fortunately)...but no dice on it being recognized by my or any computer. Glancing into the port, it looks like there may be some corrosion on the left hand side of the port, or some sort of damage...can't really tell without a proper magnifying glass. but it does look damaged or at least irregular. I've been reading around, and cleaning sounds like a potential solution...I've no idea how you guys are cleaning with giant q-tips lol but hopefully I can figure that one out also and give it a whirl xD But in the mean time, I sure hope somebody can come to the rescue
I don't know if this can help you guys, but this is how i hard bricked my vibrant few months ago. I get into download mode trying to get back to stock from ICS and my computer didn't recognize my phone....after a couple of hours my phone was completely dead and after a few days of research i brought it back to life using the unbrickable mod. What i'm thinking now is to use the Unbrickable Resurrector but you will need Linux...it always worked for me but i'm not sure if you need the unbrickable mod already applied. However i think if you have Linux installed you can have a try. Here is the link for the unbrickable resurrector http://forum.xda-developers.com/showthread.php?p=17135277#post17135277
I just got a galaxy note for my galaxy nexus last night (traded) and I took it home and install goomanager and downloaded a rom that was "compatible" it saved to the directory that goomanager puts it in so I rebooted into CWMR and cleared cache / data etc then proceeded to install zip from SD Card. it started by saying flashing kernel 4% or whatever and then came back with an error. me being as bright as I am recently...I fixed permissions and rebooted thinking that it would at least let me back into recovery.
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot. Is there a way I can at least get it into Download mode? Hell stick a magnet on it to erase everything even?
I don't need another paper weight..I have an iPhone for that.
Can you boot into download? If so, use Odin to flash the correct kernel.
Can you boot into recovery? If so, flash the correct kernel.
If you can't do either one, your phone is bricked and you will need to send it for a repair. $50 and one week later you will have your phone back with stock 4.0.4 ICS rom. Its called a JTAG service, from www.mobiletechvideos.com. Many note user have gone there, from just this thing.
The jig that works with other phones 99% of the time won't work with the note.
Don't trust CWR. Get your roms from our developers.
Jig 99% Of the time won't work... you made that statistic up. If button combos aren't working it's definitely worth a shot, resistors are super cheap, especially compared to jtag which doesn't sound needed here yet.
And what do you mean. "Don't trust cwr get your roms from the devs here"?
That is a recovery... he didn't download anything with it, he used goomanager.
And even if he downloaded it from here...he would've flashed it in cwm... xda isn't a custom recovery...
So you tried holding the down volume button+ power to get it into download? Flashing a kernel will not remove your recovery/download mode unless you flashed a Rom not made for your device that installed something on said partition(s).
As for the jig...don't know statistics, but I am a one percenter. Worth a shot imo.
https://www.youtube.com/watch?v=6K-lvaAop2w&feature=youtube_gdata_player
Sent from my SAMSUNG-SGH-I717 using Xparent Gray Tapatalk 2
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade. Josh from mobile tech gave me one of his he sells on the site.
As nun said, the combos should work, they are in the bootloaders, flashing a kernel won't effect those unless says kernel is for a different device, then you wouldn't get a single thing outta the device at all, no charging screen, no bootloop. Nothing. Whatsoever.
studacris said:
Volume down and power, then when prompted volume up, for download mode.
And I'm also a "1% er" and my jig isn't homemade.
Click to expand...
Click to collapse
Right amigo 99% + 1% = 100%. You and Nunhugger are the only ones who said a jig worked for them. So actually its way higher than 99%. . . But you guys are ninjas. Your phone would probably reboot if you just told it to. I just wanted to kill the eventual jig question early.
And my response about CWR was because it sounded like he used the old app Rom Manager to see what was available. Clearly it was wrong so I told him not to trust it, and put in a plug for our developers.
When an update is released the forum gets slammed with complaints about bad flashes of incorrect kernels, and I have seen several members heal their phone by flashing the correct kernel. I just figured he was not accustomed to the button combos of the note and would get to that eventually. But if it was for the wrong device I wanted him to get his mind around the $50 and week wait.
Sheesh. . . decaf.
Well seeing that I can't Get into either mode and no button combos will work, I am assuming I need the JTAG. I figured an app like GooManager would have at least gave me the right roms for my device. it did say i717 but that could just be my memory playing tricks on me.
Man, I'm real sorry. But the JTAG service has been used by many, and with lots of positive comments. Good luck.
hahah thats okay, I mean its a great phone, definately not worth keeping in a draw collecting dust so I will go with the JTAG service. Thanks Guys!
You still have signs of life, it shows the charging animation, therefore your phone isn't bricked.
Do some searching on making a jig, I personally think it's well worth a try.
You could very well fix your phone for under $10 and have the satisfaction of accomplishing this yourself And have the know how to do it again...
It doesn't have the charging animation. just a dead black screen.
Then why did you say this?:
leveliv said:
I now have a "Dead" note sitting on the floor infinitely "charging" so to speak its just plugged into the wall, Will not boot.
Click to expand...
Click to collapse
That's more than a little misleading...
Will not boot...could mean many things.
From a easily fixed bootloop down to a brick.
Saying it was infinitely charging made it sound less severe.
if it weren't for that line, I wouldn't have bothered to tell you to use a jig.
JTAG it is
cris, why do you need to experiment with finding the proper resistance? Why should there be any variability in that circuit? Perhaps that is why some users have used up as many as six usb port replacement parts.
By the way, my 99% statistic is, like my entire post, just my opinion, and strictly a figure of speech. If it were a fact I was quoting I would have included a footnote. Remember those painful things? Do we have to include disclaimers for any figure we use? Sorry to mislead anyone!
I said "dead" because its not necessarily dead because a JTAG thing can fix it..and I said "charging" because to the normal person who didn't know anything was wrong with said device it would look like it was charging. But anyhow. I'm sending the phone out this week. I just don't understand why all the phones can't be as open as the devices straight from google.
You're phone is dead.
JTAG is akin to zombie, the phone needs disassembled and a special rig is needed to hook to the motherboard and flash EVERYTHING back to the nand at the prebootloader level.
The I717 is pretty much just as open as a nexus as far as easily modified and rooted...
No locked bootloader even which nexus have though it's a single line in a terminal to unlock, that step isn't needed on this device.
Only thing that isn't as open is the hardware drivers.
You may have flashed an incompatible kernel for a DIFFERENT device... and that on any phone will brick you.
And ranger not sure if it's the circuits within the phones that vary from device to device, ands seem to require a more specific voltage across those pins to trigger download mode
Or, if It's the resistors that are the variable. They are only rated within a certain +/- tolerance the cheaper ones having a larger margin of error.
And lol yes I am a ninja, but I didn't do anything special to my jig at all, I got mine from mobiletechvideos, funny enough it's worked on 4 captivates, a vibrant, 2 note 1s, and an s3, but didn't work on an s2 I was fixing.
the one I got from Goomanager was probably for the i700 which shouldn't even be able to happen.
They have video proof of them fixing phones with dead black screens from exactly what happened to mine using the JTAG Method. As far as I am concerned this thread can be closed cause I got the answer to my question.
the JTAG rewrites basically everything anyways so it is being sent out later this week. Till then I'll use a blackberry or something...Take care guys hopefully next time you see me post it will be to help someone and not asking for help
You'll be up and running by next weekend. By then, lots of exciting development will be happening on the released rom.
I doubt it, I live in Canada and have to send it to the states. It probably be closer to the weekend. Unless I expedite everything.
Alright. let us get this straight. I have searched in countless number of forums for solving my issue but I'm NOT able to fix it.
I have a Samsung Galaxy S Vibrant T959. It currently seems to be "soft-bricked" (I always see a mobile connected to a computer and an exclamation icon in between). So to reset it, I have left almost not stone unturned. But no luck so far
As far as I remember, I happened to land it in trouble while I was trying to flash some secondary bootloader using ODIN.
I also tried the micro-USB JIG method by building a 300k-Ohm USB JIG on my own (using three 100k-Ohm resistors), but even that is not working for me. Whenever I connect my phone to my computer, it starts up and shows those three icons. The same happens when I remove the battery, insert it back and start the phone up again. The same happens for each of the numerous key sequences mentioned online for download/recovery mode. So literally NOTHING is working for me. I also tried OneClick.jar, Heimdall. None of them are making me lucky as the phone is not getting detected.
I believe there has to be a way to reset it somehow (although I seem to have screwed something seriously) but nothing seems to work for me. What can I possibly do now?
Attached images show the micro-USB jig that I made and the icon on my phone I see.
From my experience if you can get that far you don't need a jtag. But you did say that you flash bootloader. So you ether need to get the right combo to get to download mode or you are done with out working bootloader. The only other thing that I can think of would be to do the unbrickable mod.
Sent from my Nexus 4
Thanks jrongi1 for the reply.
>> So you ether need to get the right combo to get to download mode or you are done with out working bootloader.
I have tried many, many combos for getting the download mode but no luck so far Can you suggest some if you are aware of one?
The only other thing that I can think of would be to do the unbrickable mod.
>> I tried to know about this but I did not understand what this exactly means? I believe this involves some sort of hardware rework. Can you please point me to steps to do this? Are you referring to this procedure? If yes, I don't believe it's a solution since that procedure is just a preventive measure and not a solution (that's what I understand after reading that whole thing out).
Try that.
reboot computer, turn off phone, take out battery, put the battery back, hold volume up and down buttons and then plug in usb.
Sent from my SGH-T959 using xda app-developers app
This is from N00B_IN_N33D's MIUI guide stickied at the top.
"SOFT" BRICKED WHILE USING ODIN?
If you are getting a "Phone.. ! ..Computer" image (seen above) when booting phone, yes, you are bricked but it is reversible! Just follow these steps...
Make sure you have ODIN OPEN with admin privileges!
1.) Take off your back cover, remove your sim & mirco sd card.
2.) Remove your battery.
Make sure you have the USB plugged into your PC but NOT your phone!
3.) Hold the volume buttons.
4.) Put the battery in.
5.) Put the USB in.
You don't necessarily need the download mode image to be present. As long as you are getting the COM ID to light up yellow in ODIN, just flash back to stock like normal.
Click to expand...
Click to collapse
Sometimes the key combo can be a bit precarious and the timing needs to be precise. I know that when I have taken my Vibes back to stock, it takes me more than a few tries to get it right. You've said you have tried the key combos several time, I think you should keep trying them and get your timing right. I would hate for you to screw up your phone when doing the Unbrickable hardware mod, when it could be something as simple as a timing thing.
As the other guys said work with the buttons and only try the unbrickable mod as a last resort.
Sent from my Nexus 4
Thanks guys for responses.
testomat/Woody, I tried as per your steps almost 8-10 times, but that does not work either
jrongi1,
I do not wish to go for Unbrickable mod either. Anyway, I have contacted a local repairs guy for this issue. He said he can fix this issue using JTAG interface. That costs me 1500INR. That's the only solution I have I guess.
Good luck with the repair I hope that you can get going soon.
Sent from my Nexus 4
Thank you so much again!
Woody said:
This is from N00B_IN_N33D's MIUI guide stickied at the top.
Sometimes the key combo can be a bit precarious and the timing needs to be precise. I know that when I have taken my Vibes back to stock, it takes me more than a few tries to get it right. You've said you have tried the key combos several time, I think you should keep trying them and get your timing right. I would hate for you to screw up your phone when doing the Unbrickable hardware mod, when it could be something as simple as a timing thing.
Click to expand...
Click to collapse
This worked for me.....Many thanks
Hey, guys, before sending it to the LG services, I'd like to tell you what's this thing about, while editing aboot.img to unlock the bootloader, I think I made a mistake there, anyway, finished the bootloader unlocking process, and then I gave it a reboot. Now I'm left with a black screen. :/
Can't enter download mode, neither recovery. can't even see anything in device manager, but, if I put it to charge and I take the battery out, I can see the charging screen, an empty battery and yellow exclamation sign on it.
What's your opinion? Should I just send it to service, telling them that old story about updating the phone and the screen suddenly became black, or should I try to do some magic?
Anyway, not seeing anyting in Device manager tells me that the motherboard is DEAD.
Fulga666 said:
Hey, guys, before sending it to the LG services, I'd like to tell you what's this thing about, while editing aboot.img to unlock the bootloader, I think I made a mistake there, anyway, finished the bootloader unlocking process, and then I gave it a reboot. Now I'm left with a black screen. :/
Can't enter download mode, neither recovery. can't even see anything in device manager, but, if I put it to charge and I take the battery out, I can see the charging screen, an empty battery and yellow exclamation sign on it.
What's your opinion? Should I just send it to service, telling them that old story about updating the phone and the screen suddenly became black, or should I try to do some magic?
Anyway, not seeing anyting in Device manager tells me that the motherboard is DEAD.
Click to expand...
Click to collapse
First of all sorry for your trouble. It seems like a hard "brick". The only way to solve this issue is to send the phone to service. Say that there was a electric shortage or cutout while updating.
Before doing that you may try to update the drivers on your PC (even id they are new install it again), then try to put the phone in a different USB slot and wait for 10+ minutes to see if it enters download mode. This is quite a hail Mary, chances of this working is %0.001- But doesnt hurt trying. your device is looking forward for a service guy touch..
Pondera said:
First of all sorry for your trouble. It seems like a hard "brick". The only way to solve this issue is to send the phone to service. Say that there was a electric shortage or cutout while updating.
Before doing that you may try to update the drivers on your PC (even id they are new install it again), then try to put the phone in a different USB slot and wait for 10+ minutes to see if it enters download mode. This is quite a hail Mary, chances of this working is %0.001- But doesnt hurt trying. your device is looking forward for a service guy touch..
Click to expand...
Click to collapse
I know it needs a service guy touch, but I was wondering if there's something worth a try. Even if it has such a low chance to work, I'll still try that, thanks for the reply!
Last week I learned a very important lesson. When the OP says wait, the initial boot may take a while, they mean wait. I flashed Super6 using Flash Fire. I used to use Super6 and loved it and wanted to relive the old days. During the boot process I saw the blue light flashing (pulsing) for a while, so I left it alone. After about 15 minutes I got impatient and pulled the battery. Big mistake, HUGE MISTAKE. I was thinking it would reboot and go back to the rom I was running. Boy was I wrong. I know most of you are thinking, "you idiot, why would you do that?" Like I said I got inpatient and truly lost track of time. That hard bricked my phone. The phone no longer boots, to any point. I think when I pulled the battery it wiped the boot.img and that bricked the phone. I am usually pretty patient when flashing custom rom, because they are re-writing the OS. I don't know why I pulled the battery. I can't blame anyone but myself for such a bone head move. I have learned from hours of on-line research that the phone is repairable, with a new mother board. Thankfully I have a friend with a Galaxy S4 that he is not using and is willing to help me out. I would upgrade to the S6, but I have so many accessories for the S4 that I don't want to give up. I know at some point I will have to since support for the S4 will eventually end.
Thanks for listening (reading). I wanted to share my woe's so other people don't make the same mistake I made.
Once I get my phone back up I will confirm that the mother board fix worked.
Did you try to get to QDL mode? Pull the battery and press volume up when connected to a computer, I think. I turned off my n9 during the first boot after flash. Thought I was hard bricked but turned out my charger was bad. Hope I helped
whowatchlist said:
Did you try to get to QDL mode? Pull the battery and press volume up when connected to a computer, I think. I turned off my n9 during the first boot after flash. Thought I was hard bricked but turned out my charger was bad. Hope I helped
Click to expand...
Click to collapse
I did, and no luck. I tried multiple cables and two different computers. Download mode is a no go.
ErisDroid? said:
I did, and no luck. I tried multiple cables and two different computers. Download mode is a no go.
Click to expand...
Click to collapse
QDL mode is not download mode
whowatchlist said:
QDL mode is not download mode
Click to expand...
Click to collapse
What is QDL mode? I Googled it and found posts for the Note 3 and the S4 mini, but nothing for the S4. Any help is always appreciated.