Ok, to start off, im new here. i have read a TON of threads about rooting and flashing roms to my vibrant. i have watched a dozen youtube videos on many different ways to do this but nothing seems to work for me. i am trying to get the team whiskey bionix v rom. i previously rooted my phone when i was on 2.1 but ended up unrooting because i didn't really know what to do yet. after upgrading to android 2.2 i tried to root again so i could get this new rom. i eventually got rooted after some difficulty. i used superoneclick root to do this. however i was stopped when i could not boot into clockwork recovery mode. i searched for hours on how to make it boot into this recovery mode but nothing worked. so i tried using odin but ran into a massive problem with it not recognizing my phone in download mode(YES I HAVE ALL THE DRIVERS). so i tried to unroot my phone and re-root it. however it wouldn't let my unroot it through superoneclick. it would not recognize my device. i got very frustrated and uninstalled the superuser app on my phone which actually got rid of my root access but now i cant re-root my phone.
I am very frustrated having spent a good 8 hours on this by now and getting stuck at every turn. should i go back to factory default? or is there something i should do to try and salvage this? also if i do restore to factory default will i end up on 2.1 or 2.2?
And yes i have read the entire noob guide and vibrant bible thread.
(BTW i have tried making this work on a windows 7 machine, windows xp, and a mac)
When you connect to pc in download mode, do you already have odin up on the pc?
Does it show a com #?
i have Odin. when i connect normally with my vibrant it picks up a com port. however it doesn't during download mode. i have tried with it up. with it down and then opining it up. plugging in my phone and reconnecting it over and over again and pretty much every combination i could think of because i read that it is a really finicky program.
btw i have done a complete factory reset and cleared all my sd card data(i backed it up on my computer beforehand) it is on froyo and still refuses to be rooted and Odin still wont find it while in download mode. I have followed every step of every walk through to a tee and yet i still have had no luck. maybe ill switch back to my windows 7 computer and try that again.
Related
So after searching the vast horizons of XDA I haven't found an answer that really helped me. Nor have I found someone with this distinct issue. I have an unlocked Samsung Vibrant. I have not rooted it. I updated to J16 with that P.O.S. Kies Mini a few months ago. I hadn't noticed this problem until the last month or so but I haven't had time to sit down and curse at my computer long enough or offer supplications to Google until now. I've just been using Awesome Drop to get what few files I wanted onto my phone. I've had enough of that now. And...I also want to update it to Froyo but I can't do that if I can't get my computer to see my phone. I'm running a Toshiba Satellite A205 with Windows Vista 32bit.
I have checked the drivers and as far as I can tell, I'm using the right ones. I downloaded Kies Mini again today (I deleted it after I was finished with J16 because I wanted it as far away from me as possible) and it seemed to say something about downloading drivers as well. I tried plugging in my phone. Nothing new. So, I went in search of drivers again. I have searched and tried a few different ones but nothing has solved my problem.
The phone charges fine from my laptop. It hooks up immediately and charges without a problem. Unfortunately, my phone seems to regard the PC as a complex wall-wart. Debugging on/off, USB Settings on Mass Storage, Kies, or Ask on connection, it doesn't matter. It doesn't give me the option to "mount" as it has in the past. It doesn't do anything except charge. I've seen some people say it's a problem with their cables (I've only got one at the moment) but since my phone charges fine, how can it be a problem with the cable?
Only thing I hadn't tried was a factory reset. So, I sucked it up and tried that. Nope. No change. At this point I'm wondering if it's a hardware problem, not a software problem.
I'm out of ideas. Anybody else?
Well you can always root it, install ROM manager from the market, install clockwork recovery, download the ROM you want to install in flashable .zip format from your phone and flash away. A new ROM might fix your USB issue.
If you don't want to root it, see if you can get into download mode, and flash a new ROM using Odin. I would check with a different cable first, just to be sure that's not the problem though. It might save you some headaches.
If it was me, I would just root it and load a custom 2.2 ROM. I would also get Titanium Backup from the market and backup my apps and would do a nandroid backup from recovery before flashing anything new just to be on the safe side.
There's some good info on how to do most of that in this sticky post.
http://forum.xda-developers.com/showthread.php?t=849028
ive researched for hours on the forums trying to fix my vibrant and I cant seem to find a situation similar to mine.
So i tried to install a rom from the romkitchen website. before that I did not have any rom I was just rooted via OCLF and i had just updated to the newest clockwork recovery. i did a nandroid backup and proceeded to install the rom. after it installed it just hangs at the first screen that says vibrant samsung. only it doesnt say that. it say galaxy s gt i9000. i tried to restore my nandroid file but it says it cant mount the sdcard. anything regarding the internal or external sdcard wont work. the recovery also looks different from the one i had before. it says clockworkmod recovery v2.5.1.0 speedmod ULFK at the top. and thats the only recovery i am able to access. i tried to odin back to stock and i tried so many different methods but no matter what i do it wont register in any odin version nor in that alternate odin program. i keep disconnecting/ reconnecting but nothing. i just get a a popup in the bottom corner that says one of the usb devices attached to the computer has malfunctioned. i dont know what else to do. any help would be greatly appreciated. im getting off the computer now so please email me at [email protected] if you can help. ive gone back to using my g1 for the time being
Use a usb port on the back of the computer .
hook up yer phone to computer , reinstall drivers , if u are not bricked because i dont know i didnt read everything u posted lol enable usb denbug and reinstall drivers than .
Im pretty sure I did the same thing a long time ago. I thought my phone was screwed.
Definitely try plugging it into another usb port if you have one first. Supposedly the ones in the back of the computer are better. If you have to, try every usb port you have.
Also, make sure youre downloading the drivers that are right for your opertaing system. For example, if you have windows xp 32bit, dont download the drivers for windows 7 64bit.
Even just reinstalling the drivers didnt work. I dont remember step by step, but I got into recovery, and wiped my cache and user data and was then able to have odin recognize my phone. Be careful in recovery mode though, because if I remember right it remapped my volume buttons, (up was down and down was up)
Lastly, make sure if/when you get odin to recognize it, you put the .tar file in the right spot (PDA) and make sure its checked. you need to have the .pit file there too, the 512 pit is the one Im pretty sure you want to have, not the 513, one is just newer. You probably want to make sure the re-partition box isnt checked in odin too.
Its been a while since Ive had to use odin, so I may be wrong on a few things, like which pit file is newer and so forth.
Hello all, I have a GS3 international GT-I9300
I'll try to go through the story as fast as I can and give as much detail so you guys can understand how I got here.
Bought the phone unlocked, I was stock, I rooted and then I decided to install a new ROM. I went with Resurrection Remix, it was working great. I did this on a desktop back home. They released a new update to RR so I did a OTA update with "Update Me" apparently the thing flashed but it didn't, the phone still worked but NFC wasn't working as well as having lost root access and some other stuff wasn't working correctly, but I lived with it.
I moved to Florida (home is in NY) and I have a laptop with me, for some reason my laptop used to be able to transfer files to my S3, but it wasn't doing it any more after a while. So it would just charge it. I was in a hotel room last week trying to tether via USB but the PC wasnt having it, it could not locate the phone. This week I moved to a different hotel with internet and decided I would flash stock on my S3 to get rid of all these bugs and get root again, I tried flashing stock through recovery and it wasn't going, so I tried flashing RR again (this time downloaded from the site RR site) and it worked. Still no USB connection but I had root back. I looked around my PC and apparently the Samsung drives are not installing or something on my PC. I installed Kies, but nothing, I tried a stand alone driver install and nothing, so I just gave up and bought Mobile Odin pro from Gplay to try to flash again.
Mobile Odin for some reason (I blame it on myself) wasn't finding/flashing stock so again I decided to try and flash RR and see what would happen. It flashed RR and turned on fine. Then I just decided to look for an NFC fix on XDA. Once I found my NFC fix (http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367) I decided to just copy the files to the system folder, NFC still not working, rebooted and NFC still no working, so I figured I would try to flash the fix through mobile odin seeing as how I can't get my PC to pick up on the USB. I tried flashing but MO just kept bouncing it back and re-booting into RR. Tried again and no flash. So I decided to again try and flash stock. I tried going into Recovery, the phone shut off like it always does, came back on but stayed in the Galaxy S3 GT-I9300 logo and would not move. I shut it off again, tried turning it on again and still stuck on the galaxy logo. Now, if I leave the phone off and plug in the USB, it won't show the battery charging image, it will actually turn straight onto the galaxy logo again and stay there. I can get the phone into download mode, but like I said my pc won't recognize the drivers.
Now, here are my questions:
What happened?
Can this be fixed?
Am I an idiot?
If I can get the drivers installed on another PC as well as Odin (1.85), will the new PC "see" the S3 or are the drivers on the phone deleted as well? (if that sort of thing can happen, idk.)
I'm going to see if I can borrow a buddy's PC and download the drivers as well as odin to try and bring my S3 back to life, I just want to know, what happens if I can't get the other PC to pick it up ether because the drivers on the phone are deleted (if that's a thing) or what I can expect if it is connected.
What are the steps or guides to follow here? I just got it into Download mode and it says on the top of the screen:
ODIN MODE
Product name: GT-I9300
Custom Binary Download: Yes (2 counts)
Current Binary: Custom
System Status: Custom
sorry , i am sometime getting headache reading long english text so i just briefly look over.
your PC doesn't recognize your S3 ? is that correct ? hmmm , is it possible that your PC (Microsoft Windows I assume?) system is damaged due to something like virus or some reasons ? i have encountered that kinda problem before and be OK after i reinstalled the system.
If it's a soft brick, then it can defiantly be fixed. You might, however, lose your data along the process.
Be glad it's not hard bricked
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
djembey said:
It happened to me many times, USB error "unknown device" connected. Only fix for it was reinstalling Windows so better if you can use different PC or laptop. Install Kies and other USB drivers. Restart computer, download and run Odin v 3.0x. Flash your phone.
If this doesn't work then maybe your phone have a problem with USB port?
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Don't forget to delete kies as you only need the drivers
Sent from my GT-I9300 using Tapatalk 2
Thanks for the replies guys. I'll try to fix tit today, I didn't get a chance to do it last night. If anything I'll update you guys with what's going on.
Like I was saying, I'll try using a different PC to fix it. Now, if I can't get Odin to recognize the phone, what would be the next step?
Hello All, I've been trying to find a solution for about 9 hours straight now. I've been on multiple forums and multiple threads. Some help would be AMAZING.. I am really agitated and want to throw my phone on the floor and stomp on it.
Here's my story:
I tried to root my phone watching a youtube video and something went wrong. So I reverted back to the factory reset.
Then after factory resetting, I tried to upgrade from 4.11 to 4.12 to follow the CASUAL root (( http://forum.xda-developers.com/showthread.php?t=2272066 )), but it would not allow me to do so. So I tried doing it manually using .tar.md5 files and Odin3. I was able to connect to Odin3 but it would not allow me to update, it gave me the green android man lying dead with a red triangle over his body.
This is where the problem gets worse:
I am trying to follow this thread (( http://forum.xda-developers.com/showthread.php?t=2043636 )) to get it to reinstall the baseline.
Odin does not read my phone anymore. I've tried installing, unstalling, reinstalling the USB Driver, while restarting computer after each uninstall, I did this about 7 times with 3 different samsung USB drivers. one from their main website version, 1.514, found another updated one 1.523, and even an older one 1.385. None of them work for me. I've used a registry cleaner after each uninstall and nothing. I've used 3 different wires 2which are from samsung one from note2 and another from s3.
Not only can I not connect my device in Odin Download Mode ( I was able to before when I first tried to root), I can't even connect my phone while its on ( I was able to transfer music/pictures before).
PLEASE HELP ME! I am desperate
I've researched many forums and some people had the same problem but I can't seem to fix mine
Some threads that I went through.
http://forum.xda-developers.com/showthread.php?t=1044840
http://forum.xda-developers.com/showthread.php?t=961956
http://forum.xda-developers.com/showthread.php?t=1229593
Hey everyone.
I'm running into a really annoying issue. I picked up the T-Mobile GS5 a couple weeks ago and rooted it shortly thereafter. That is the only mod I've done, but it obviously blocks OTA updates.
With the new (NE6) update stable, I want to upgrade, so am trying to use Kies. Unfortunately, I can't get it to work. Everytime I try, I get the "new firmware available" alert, but when I attempt to proceed, Kies just freezes. I've tried not using the auto-update and selecting "Firmware Upgrade" manually, but no difference.
I was originally trying on an XP virtual machine (VMWare Workstation under Linux), and thought maybe that was the issue so tried under a Windows 7 VM. Same issue. So I tried the Mac version of Kies on my MBP. This time, I got to the screen where you need to check off that you agree to the update terms, but when it begins to download, Kies loses connection to the phone and it eventually errors out. So I tried a Win7 bootcamp attempt, but same general Windows failure. So I tried a baremetal (on PC hardware) Windows 7 attempt, and I'm sitting here at a slightly grayed out Kies screen that is unresponsive. In each method above, I tried numerous times with reboots of the computer and phone.
I searched, but couldn't find any similar issues. Based on the number of attempts on different computer scenarios, I have to believe it's an issue with my phone, but outside of this it works great. I've tried disabling developer mode, rebooting numerous times (phone and computer), etc. etc.
Does anyone have any idea what could be wrong? I consider myself fairly adept at Android and have a lot of custom experience with Nexus devices, but am not super familiar with the intricacies of Samsung products.
I used the Odin root method, and see there are firmware packages to upgrade that way, but believe it would factory reset my device - correct?
Any help would be greatly appreciated.
Thanks.
I read that sometimes having an external SD card can cause issues. Just tried removing that since I did have one installed. No difference.
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
koolboyztn said:
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
Click to expand...
Click to collapse
Thanks, I did try that too but no difference. For some reason, my phone seems to be incompatible with Kies.
After a lot of frustration, last night I did manually upgrade using Odin and the firmware files in the stock zip thread over in the dev section here. Initially, I only did the 'firmware' upgrade, since it seemed that the 'full' package would wipe the device (based on the comments in that thread), but that actually caused a lot of issues (fingerprint reader stopped working, etc.). So I was forced to use the full one, and it worked without wiping my device, which I'm quite happy about.
I did lose root, but for now I'm good. I mainly wanted it to restore from TiBu, but haven't needed root since, so I'll leave it stock and try the next OTA update.
I'm just more concerned about why Kies failed on 5 different machines (virtual or physical).