I accidentally flashed a kernel for a vibrant onto my sgs4g. This isn't my first flash and I wouldn't consider myself a beginner. I just didn't realize that my phone wasn't the vibrant until after the fact. After I flashed this my phone would only boot into cwmr if the sdcard was in. I'm assuming this was because the update.zip was on the sdcard. However if i tried to flash from zip on sd card the device said that the sd card wasnt detected. I'm stuck on the samsung logo screen and I have been able to get the phone into download mode. I tried using heimdall to go back to stock gingerbread, but my computer wouldn't recognize the device. I have another sgs4g that works fine. I put it in download mode and the computer recognized it just fine. I'm pretty sure that if i could get my computer to recognize the device that the heimdall would fix it. If anyone has any idea how to get my computer to detect it, it would be greatly appreciated! Not sure where to go from here. Is it bricked for good if the computer wont recognize it? Thanks!
Even if it doesn't recognize your device using heimdall, just double click on the Jar file and you will notice that the status of heimdall says Connected. Flash once then flash again without leaving heimdall with the option flash boot loader checked. The package of one click contains the drivers within it, you don't have to do anything. It is really a one click solution, double click actually on some systems
Sent from my SGH-T959V using xda app-developers app
No, it doesn't say connected. The computer will not recognize the device. If I plug in one device it will connect and the soft bricked device will not. Is there anyway I can force it to connect? To be specific I flashed fluid kernel for the vibrant onto the sgs4g and it soft bricked it.
Related
Hello, I recently decided to root my phone and place Cyanogenmod on it. When I did that I realized my radio was no longer working. In an attempt to just get back to a working phone for the time being I flashed a rom that I believe was just for the Nexus S and not Nexus S 4G. Due to my stupidity I am unable to communicate from the device to my computer using USB. When I attach the device to the computer nothing happens. The device does not even appear in the device manager. I have tried on multiple computers as well. On top of that the rom seems to have put me back into the stock recovery. If anyone could help me figure out just how to get USB working again I would be very appreciative.
I should note that I can still transfer files to the phone using the sd card or via ftp.
Thank you for your time and help.
Change the USB cable?
Yes, forgot to mention that. I have tried 2 cables both of which work on other devices.
What if you hold in the middle of the volume buttons (i.e. both up and down at the same time) and keep holding, then plug in to your usb port? It should come up as download mode. If it will do that you might try using Odin.
Or try a different machine perhaps?
are the drivers the same for the S as the 4g?
do you have clockwork on the phone or have you tried to run recover by holding volume up and power?
just throwing things out.
Hello, I appreciate any and all suggestions and help.
I have Odin downloaded and installed, but the computer can not find the device so Odin can not do what it needs to do. This is even the case in download mode.
In terms of recovery I am on the stock recovery. I was on clockwork but made a small mistake and now am back to stock.
I know if I can just get the computer to see the phone exists I can fix it.
If you can find the full OTA package for NS4G, you can try putting it on the SD card and flash it via stock recovery.
Also another thing worth trying is connecting the phone to an Ubuntu machine and see if it's detected or not.
I have tried looking for the original full OS. I will continue looking, but the different OS thing is a good idea I did not think of. I will attempt that now. Thank you.
I installed Ubuntu and the Android SDK and Ubuntu was unable to see the phone as well. I am going to keep searching for the original firmware to see if that will fix it. Thank you for your help so far, it is greatly appreciated.
I have found the only rom my phone will accept now is
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Which is for the M200 variant. This apparently the Korean version.
I'm going to be honest. I flashed the wrong .zip file on my Infuse (just swapped SD cards over from my SGSi9000)...
... and well, it did not end well. I cannot boot up, go into recovery or download. ADB does not recognize the device, and I cannot use the Ultimate Unbrick.
I need help recovering it. :\
Thanks. I'm stupid.
Did you: Remove battery, replace battery, then while holding 'Both' volume buttons plug in the USB cable that is attached to you computer?
Did your computer recognize your phone before? If not install samsung usb drivers. If so, try a different usb cable.
Been there done that. But when it happened to me I had an image of a phone being connected to the pc instead of the samsung splash screen. But other than that there was no recovery download or boot. So I just did ultimate unbrick and it somehow saved me...
Sent from my SGH-I997 using xda premium
Ok! Changed USB cables to the one I'm guessing came with the phone (lol; I need to separate my SGS stuff). Both made by Samsung so I didn't think it would make a difference....
So I'm in download mode; however, the device is not recognized by Odin for Ultimate Unbrick.
Looked up that the best way to completely get all the drivers is to install Kies?
AH!!! Rejoice! My phone has been resurrected.
Thanks for the responses
alsken said:
Ok! Changed USB cables to the one I'm guessing came with the phone (lol; I need to separate my SGS stuff). Both made by Samsung so I didn't think it would make a difference....
So I'm in download mode; however, the device is not recognized by Odin for Ultimate Unbrick.
Looked up that the best way to completely get all the drivers is to install Kies?
AH!!! Rejoice! My phone has been resurrected.
Thanks for the responses
Click to expand...
Click to collapse
No problem also you can check out androidforums.com in the infuse root section thats a good place to get help...XDA is a bit cluttered
Hello, i am currently trying to root my sisters galaxy s 4g... Her Baseband is T949VUVKI1. Firmware is 2.3.5, Build Number is GINGERBREAD.VUVKI1. i remember flashing her phone to 2.3.5 and download mode working perfectly fine, and for some reason it wont go into download mode at all... the computer is not recognizing her phone either. YES, i do have usb drivers installed otherwise my galaxy s 4g wouldnt be recognized on my computer(odin specifically, not turning yellow). Please help, i have searched everywhere in the internet and tried almost everything... Volume up and down and plug charger, batter out volume up and down usb and battery in etc. PLEASE HELP!! Thank You in Advance.
Nvm
10c
1. Try reinstalling to drivers. Also make sure you're using the same USB port as Windows can be funny about it it sometimes.
2. if download mode is being difficult, go download the Android SDK from www.android.com. Install it, run it, and only download the platform tools. When that's done, open a command promt, CD to where the plaform tools installed (either c:\program files\Android\Android-sdk\platform-tools or c:\program files (x86)\Android\Android-sdk\platform-tools ), then issue the command: adb reboot download.
3. I suggest you check the dev section for bhundven's one-click collection. Uses Java and Heimdall vs. ODIN and works easily.
Sent from my SGH-T959V using XDA App
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Tytan0007 said:
i have this issue 2.3.5 messed me up. Odin sees my phone in debug mode but not in download mode...using odin 1.85 sinse it is the only version that responds to my phone at all. help please!
Click to expand...
Click to collapse
Get it back into download mode, go grab a bhundven's one-click. The one-clicks utilize Heimdall vs. ODIN, which means they use open-source USB drivers instead of the proprietary Samsung drivers. See if that enables the computer to see the phone. If so, flash the one-click
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Tytan0007 said:
Should I uninstall the samsung drivers prior to using Heimdall's One-Click?
Click to expand...
Click to collapse
That's a good idea. Some people have reported conflicts between the drivers.
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Tytan0007 said:
Why would only Odin 1.85 see my phone in USB Debugging and not in download mode? And all other Odin verisions never see my phone, no matter what state it is in... I am at work so I will give the one click another try when I get home. I never thought of uninstalling the Samsung drivers prior to install; however, I did use the one click method to no avail. However, Heimdall's one-click was able to see my device it just kept giving me a driver error. This is so crazy it might just work.
Click to expand...
Click to collapse
I wish I had a good answer. ODIN's a funny animal. I've been fortunate and not had any problems with it. I am hoping you are correct - maybe it was just a driver conflict. Let me know how it goes.
didn't work...
You could try downloading a terminal app from the market. Open the terminal and type:
reboot download
See if that does it.
***Update***
Okay, so Oneclick was not working at all no matter what I did with the drivers. However, in all my tinkering with it I installed the Samsung Driver, the Open Source one, and some gadget driver as well from oneclick.
Doing this put all these drivers in my computer. Then I went into my Device manager (Win 7) and looked at my USB driver and I uninstalled everything and went to the stock win 7 usb driver. Then I plugged my phone in and my computer began searching for drivers for this device when it decided that it would be a good idea to load all three drivers at once and voila my phone was then showing up on ODIN 1.85.
I then proceeded to flash my phone with a rom, probably the wrong one considering I was coming from 2.3.5 and my phone boot looped and then soft bricked(sorry if I used these term incorrectly, noobin it).
After, some nervous moment of scouring XDA I found the god-send of a post on getting in to download mode, using odin, and flashing stock 2.3.6 - thank you Raver(I believe). When I did this, my phone magically started obeying ODIN like a devout viking and is now running 2.3.6 superbly.
Keeping with my phones newly found viking heritage, I intend to figure out how to properly root it, update the kernal and modem(not sure which one is best), get CWM, and subsequesntly put in Valhalla Black.
Seeing as though this last rendevous with flashing caused me a little scare I may hold off and wait to see what the next big update is (maybe a port ICS variant) and then go with that.
Anyway, thank you Stephen for helping me out with this and to everyone in this post.
Here's some reading for you Tytan,
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4G#FAQ_.28with_answers.29
PS: Unless you wanna brick your phone, do not flash anything that isn't intended for the SGH-T959V Samsung Galaxy S 4G. You're saying you wanna flash a Vibrant ROM. You can, if you want an expensive paperweight. Happy flashing!
2.3.5 may have been for vibrant...yeah I think I got lucky. I did it prior to knowing about xda.
Sent from my SGH-T959V using XDA App
Tytan0007 said:
didn't work...
Click to expand...
Click to collapse
How are you getting into download mode?
There was a post in another thread where the person apparently was using the power menu to get into download mode or maybe the adb command.
Have you tried both the old fashion volume +/- and plug in usb cable? Or the adb command?
Do you have access to another computer? Believe it or not sometimes just changing computers will make the difference.
Weird when I replied there was no posts other than the ones on the first page...oh well glad its working now.
Im looking for help on fixing my SGS4G.
Here is the current list of problems:
1. Phone isnt recognized when i plug it into any computer (i download all the drivers, Kies and Odin both cant find it, and 1 out of every 10 tries my computer will recognize the microsd card and treat it like a normal sd card)
2. My Dialer and Messages will open for 3-4 seconds and close without a force close screen or anything. Obviously this is really annoying :|
3. Im rooted but trying to go back to stock to redo this whole process over is becoming a pain.
4. When trying to flash a custom rom from ROM manager i get the signature verification failed message.
Im about to try the heimdall one-click package to get back to stock and see if that works...idk if it will find my phone though.
My system info:
Firmware: 2.3.6
Baseband: T959VUVKJ6
Kernal: 2.6.35.7-T959VUVKJ6-CL694130
Build: GINGERBREAD.VUVKJ6
If i manage to get back to stock/unrooted where do you guys suggest i go from there? im kind of out of the loop as far as where we are with ICS or jellybean or any of that :|
Thanks a bunch in advance and sorry if this is nooby
Also:
adb devices shows nothing :\
USBDview shows nothing for my phone...i plug it in with debugging on and all it does is charge my phone
First problem. Do not use ROM manager. Download ROM zips and flash through CWM/TWRP.
Have you tried using a different cable when connecting to PC? Some cheaper cables do not work well, or at all. I have a blackberry cable that I only use for this.
Have you tried alternate USB ports. Sometimes that may be this issue as well. Also, some people have better luck with Odin, while others have better luck with heimdall. You may want to try the alternate and see if you have the same issue.
I would follow the guides on going back to stock. You may have old conflicting drivers so you may need to completely remove old ones first.
Sent from my SGH-T959V using xda app-developers app
I use the cable that came with it and the one that comes with my girlfriends phone which is a different phone with no problems. You might want to mess with the usb configuration on your computer
Sent from my SGH-T959V
As far as the dialer and messenger app backing out automatically that was an issue with all bml gingerbread roms. I think there was a fix but I'm not sure. Cm7 is mtd based gingerbread and it doesn't have that problem.
Sent from my SGH-T959V using xda app-developers app
Jiggly,
Ive tried every USB port on my desktop and my laptop. Both of them im reinstalled the drivers on. On my desktop the moment I plug it in it says the device malfunctioned.
Usbdview didn't show anything like the guides said it should. (HTC something...there was.nothing)
ROM manager is just on my phone ive never actually used it other than to boot to recovery
Sent from my SGH-T959V using xda app-developers app
The phone goes into download mode but heimdall still doesnt detect it, windows still tells me the device cant be recognized and im out of ideas.
i went into regedit and deleted all the samsung folders and reinstalled the drivers fresh but im still not getting anywhere...
flash the blastoff kernel, or some custom GB kernel.
Let it convert to ext4, it'll take 10 minutes,
flash a rom through CWM which you will now have.
Im missing something here...but i cant flash anything as everything is unsigned and i cant get out of 3e recovery. ODIN, heimdall etc still wont find my phone from my computer(s) and everything i attempt to flash is unsigned.
Can you boot into your ROM?
boot into my rom as in use my phone? yes the phone functions fine with the exception of not being able to plug it into my computer to tether it/use mass storage and these darn auto close problems with my dialer/messages
Well i was able to flash a new kernel with CWM then upgraded to cm9.
didnt realize contact sync didnt work so i lost all that info :\ computer still says the device malfunctioned but my messaging and dialer apps dont auto close now lol
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Daniel_NC said:
I did a really, really dumb thing a few months ago. I flashed a wrong something or another to fix an issue I had with my keyboard crashing after flashing another wrong thing..
Anywho, I couldn't get the damn keyboard to stop crashing for the life of me, so I set out to FORMAT/ CLEAR EVERYTHING ON MY PHONE. Yikes.
At this point, I can boot into recovery(CWM) and DL mode, but my PC will not recognize my phone at all. I installed your S3 toolkit v7.0, hoping it would help, but nay.
I cannot boot fully into Android to allow usb debugging, etc.
I can mount and unmount internal sd, cache, etc, but no drivers are being installed because it is not being recognized.
I've uninstalled Kies, etc.
HALP!HALP!
Click to expand...
Click to collapse
If you boot into DL mode and run odin on your PC does it fail to see the device?
apacseven said:
If you boot into DL mode and run odin on your PC does it fail to see the device?
Click to expand...
Click to collapse
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Daniel_NC said:
I'm waiting on my PC to free up again(currently on a Mac). I had not tried Odin because in the past I was unable to mount internal SD, which I understood was keeping it from being recognized. I instead thought the Toolkit would do the trick automatically, though I most likely had the wrong idea. Everything is mountable again (for some odd reason), so I will give it a go.
Could I accomplish downloading drivers and flashing rom to device using Odin alone? Or should I use the Toolkit?
Thanks!
Click to expand...
Click to collapse
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver http://d-h.st/vMk
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver ...
Thanks!! I'll give it a shot now.
Click to expand...
Click to collapse
apacseven said:
Installing the drivers is independent from using odin. Install the drivers on the PC, fire up odin, connect phone (that has been booted into DL mode) and see if it connects. If it does, just flash a stock image and you are back in business.
You can use this driver......
Click to expand...
Click to collapse
Odin is not recognizing the device. Should I unmount or mount anything on the device for this to work properly? I have drivers installed.