Ok, so this was my first attempt at trying to root and flash a device, and somewhere along the way, I screwed up. I installed TWRP on my Galaxy Tab 10.1 WiFi only tablet (GT-P7510 32GB) via Odin, and rooted the device with the SuperUser and everything was gravy. Then, I tried to flash CM onto the device, and something went wrong. Bad install file or something along those lines.
OK, I'll just wipe it off and try again, went into TWRP "Wipe", and did all of the wipes. Which is where I went wrong. I did ALL of the wipes. So now the only thing still on the tablet is TWRP. Luckily I can still boot into that, but that's it.
So, this is where the real problem comes in. I need to be able to load the ZIP onto the device root so I can use TWRP to install it, but for the life of me I cannot get my Windows 7 Laptop to recognize the device. I have installed, uninstalled, and reinstalled the Samsung drivers at least 4 times, being extra patient to reset both the computer and tablet after each attempt, i've tried turning the computer on with it already plugged in, i've tried waiting to plug it in until after the computer is fully booted, everything.
The USB port on the computer recognizes other USB flash drives just fine, i'm using the OEM cable, and everything worked fine to connect the tablet with Odin before I did that wipe, so we can rule out the cable being bad.
I've been reading a lot of forum posts both on XDA and elsewhere and I've seen people talking about needing to uncheck the USB debugging in Settings, but obviously I can't get there, because there's no OS. This must have been unchecked before the wipe though, because it connected fine then.
Help
Interesting addendum.
I actually CAN access the device with Odin. It will allow me to reflash the TWRP .tar file onto the device. Not sure if that's helpful at all though.
Figured it out, questions answered
Related
After upgrading my phone (T-Mobile Galaxy S Vibrant SGH-T959) to vibrantmtd #30, my laptop (HP EliteBook 8540p - Running Windows 7 Enterprise 64-Bit) no longer recognizes my phone as a USB device. There is literally no indication of Windows trying to load the phone as a USB device. I have tried everything I can think of to get the device to load as a USB drive on my laptop.
1. Rebooted the Laptop, several times
2. Uninstalled and reinstalled Samsung and Nexus USB drivers
3. Made sure my laptop was up-to-date on all patched
4. Tried with USB Debugging was checked/uncheck
5. Tried with multiple cables
6. Tried multiple USB ports (1.1, 2.0, and 3.0)
7. Used USBdeview to uninstall all USB devices on my laptop (also tried this on my home PC) and then let window reload the devices after a reboot.
8. Tried with multiple systems (both Windows 7 and XP 32/64 Bit) – including friends who have Galaxy S and Nexus Phones.
a. The only system that will try to load a USB driver is my home PC [Windows 7 Ultimate 64 Bit] and no matter what drivers I install the phone always comes up as an Unknown Device.
9. Tried going into download mode to use Odin to revert back to a 2.2 mod. I can only get into download mode using a physical jig and even then Odin will not connect to the device.
10. I can’t even load a different build of Cyanogenmod. I tried loading build #31. It downloads, prompts me with the three questions about backup, clear data, and cache. I have selected every possible combination of those selections and it will download the build and reboot try opening rom manager (too quick to see what it says) and then loads back into build #30.
I am at a loss as to why I cannot get the phone to be recognized as a USB device or be capable of further MODing. Any help would be appreciated
Thanks,
Michael
MikeTheTechGeek said:
After upgrading my phone (T-Mobile Galaxy S Vibrant SGH-T959) to vibrantmtd #30, my laptop (HP EliteBook 8540p - Running Windows 7 Enterprise 64-Bit) no longer recognizes my phone as a USB device. There is literally no indication of Windows trying to load the phone as a USB device. I have tried everything I can think of to get the device to load as a USB drive on my laptop.
1. Rebooted the Laptop, several times
2. Uninstalled and reinstalled Samsung and Nexus USB drivers
3. Made sure my laptop was up-to-date on all patched
4. Tried with USB Debugging was checked/uncheck
5. Tried with multiple cables
6. Tried multiple USB ports (1.1, 2.0, and 3.0)
7. Used USBdeview to uninstall all USB devices on my laptop (also tried this on my home PC) and then let window reload the devices after a reboot.
8. Tried with multiple systems (both Windows 7 and XP 32/64 Bit) – including friends who have Galaxy S and Nexus Phones.
a. The only system that will try to load a USB driver is my home PC [Windows 7 Ultimate 64 Bit] and no matter what drivers I install the phone always comes up as an Unknown Device.
9. Tried going into download mode to use Odin to revert back to a 2.2 mod. I can only get into download mode using a physical jig and even then Odin will not connect to the device.
10. I can’t even load a different build of Cyanogenmod. I tried loading build #31. It downloads, prompts me with the three questions about backup, clear data, and cache. I have selected every possible combination of those selections and it will download the build and reboot try opening rom manager (too quick to see what it says) and then loads back into build #30.
I am at a loss as to why I cannot get the phone to be recognized as a USB device or be capable of further MODing. Any help would be appreciated
Thanks,
Michael
Click to expand...
Click to collapse
Do you have skype? It would make it easier for me to help you. If you're not comfortable with it, I'll just type everything
Try this, turn phone off completely, turn it on by holding these three.... vol up, vol down, power....let go of all three at the same time as soon as you see the Vibrant logo.
Edit.....do not have it plugged in at all while doing this.
Is this a bug with the nightly? Try an OLDER version.
Sorry, don't have skype.
I did your above steps and that puts me into ClockworkMod Recovery.. Was there something I need to do in here?
s15274n said:
Is this a bug with the nightly? Try an OLDER version.
Click to expand...
Click to collapse
Nope, it's a driver and human error. Rom manager cannot go into recovery mode, you have to use three button combo.
It's stated by the cm7 team.
No, I checked. I was just able to go to build #31 by rebooting into clockworkmod and installing the build #31 zip from there. I did have to wipe data, install, and clear cache to get it take though.
Removed.. Agh, been awhile since cm7, not what I remembered.
MikeTheTechGeek said:
Sorry, don't have skype.
I did your above steps and that puts me into ClockworkMod Recovery.. Was there something I need to do in here?
Click to expand...
Click to collapse
Yes, now if you have downloaded a cm7 nightly on your sd card, do this.
Wipe data, factory reset
Wipe cache
Go to advanced, format system, cache, and data.m.
Go to install zip, choose zip from sdcard, select the downloaded cm7 nightly, select yes.
Then reboot phone, not reboot recovery. Leave it for 15 minutes, reboot, now use it.
After it's up and running, please please go into recovery mode the same way I posted, do this after you finish all the steps above!
Go into backup and storage and make a backup!! This will save your phone if future problems occur.....this is a nand backup.
Ok, I did all those steps, I have a backup now.
MikeTheTechGeek said:
Ok, I did all those steps, I have a backup now.
Click to expand...
Click to collapse
Awesome, this will save you from bricks or anything unfortunate.
Is your computer still not recognizing it?
Correct, still not recognized.
Open device manager, find device installation settings and make sure it's on find drivers automatically.
Open Windows Update, settings, check give me recommended/additional updates.
Use the usb software to uninstall the drivers, uninstall kies, or any samsung software.
Reboot......install this driver, turn off your compute, don't restart.
On your phone, settings, applications, development, make sure debugging is on.
Plug the phone into the usb and plug it into a new usb slot. Now turn on your computer with it plugged in.
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
Well for whatever reason, those steps seem to bring to life my USB port.
I performed all the above steps and when I powered on my PC after perform the steps, the phone was not recognized as a USB device until I unplugged the USB cable and plugged it back in. Now it is recognized on every port on my laptop.
Interesting other issue was that after I used Odin to revert to stock, if I powered off my phone it would not load anything (not even the splash screen) when I tried to power it on and I know it was at 90-100% battery power. The only way to get it to boot was to go back into download mode and use odin to reflash the OS. I did this 4 times with the same results, with different copies of Odin and the stock rom and I got the same result.
I decided I was too tired to figure it out, left it on after a flash (not plugged into anything) and now it will reboot fine.
I don't know what strange voodoo possesses my phone, but thanks for your help.
That's good to hear and no problem. By the way, I highly recommend using Heimdall to flash roms....I've had no problems with it. I don't use odin anymore.
Thanks, I have heard of Heimdall but never tried it. I will give it a try next time.
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
JJ2197 said:
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
Click to expand...
Click to collapse
It is not bricked. I'm still not convinced you are on jellybean bootloader as there is not a version of Cwm that works with it and you still have cwm.
First thing you need to do is confirm what bootloader you are on before you really brick it.
Switch the machine on and look where the tegra logo is. If it is bottom center you are still on ICS bootloader and if it is bottom right it is jellybean bootloader.
We need to know this to point you to the correct version of twrp to flash to start.
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
JJ2197 said:
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
Click to expand...
Click to collapse
Really you are going to need to get into fastboot and get the drivers installed.
I'm guessing you know how to get into fastboot but if you don't then hold down volume down and power button for 10 seconds when off. When the icons appear press volume down to go over to the USB icon and then press volume up. It will freeze on the prime screen at this point and that is fastboot mode.
Now go into device manager and try to install naked drivers. If this does not work then try in on another pc. If this still does not work then you have a faulty cable. A faulty cable can still charge the tablet but will not work in pc.
At this moment my money is on your cable being faulty over something you said earlier about having to play with it. You can buy a replacement cheaply on eBay.
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
JJ2197 said:
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
Click to expand...
Click to collapse
Without getting any drivers installed at all there is not much we can do.
Cwm doesn't support external cards and even tho I could make you a flashable zip to install twrp you couldn't get it on there.
If you can get back into the machine at all then we could use wireless adb and send the files over that way or use es file explorer to access network shares and take them over.
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
JJ2197 said:
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
Click to expand...
Click to collapse
This normally happens with a faulty cable and as you said you think the pins are faulty so it could be that instead.
You could try going to the wipe icon where the fastboot icon is and try running that. If there is a rom still on there it will try to factory reset but I can't guarantee that will work but at this point you have nothing to lose.
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
JJ2197 said:
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
Click to expand...
Click to collapse
I'm not talking about in CWM. I'm talking about the wipe icon where the fastboot icon is also.
Isn't the factory reset the same in both CWM and bootloader?
JJ2197 said:
Isn't the factory reset the same in both CWM and bootloader?
Click to expand...
Click to collapse
No
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
JJ2197 said:
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
Click to expand...
Click to collapse
It reformats the partitions back to stock except the system partition.
I'm not saying this is going to work for you. Just as you are your only other option if the pins are broke is to get it sent back to asus and they will swap out the whole mobo so you might as well have a go.
Ok so i tried to install a new rom because my AOKP Rom wasnt connecting to my PC so i thought.
Ok so here is the problem. Half way through installing a rom, some how my phone crashes, after waiting 5 hours just incase i ripped out the battery and thought i will reinstall a rom that works the CWM. Nice and easy so i thought until i couldn't access CWM. So now i have a non bootable block of plastic and a screen.
Next i put the phone into download mode expecting to use Odin to just reinstall everything from scratch however my computer cannot recognise my Device. It says USB device not recognised and doesnt show up a drive letter on my computer. Any ideas of how to fix this?
No 1) let me make this clear it is not a driver issue, as all the correct drivers are installed and my girlfriends GS2 works fine.
No 2) it doesnt matter which computer i try to connect it to it wont work.
No 3) i have tried it with and with out Samsung Kies.
No 4) The batter is charging so the port cant be completly dead.
So how do i install anything on the phone if a computer cannot access it?
I even thought of trying to use killdisk to wipe any dodgy partitions but of course this wont recognise this device as a drive letter.
Please please can any body help or should i just assume the usb port is Dead.
Hi All,
I am having an issue with my S4 that when I plug them into my computer I get USB device not recognized. I have searched the forum for the past 2 days trying all kinds of different solutions the major one was changing my USB/charging port board on my phone.
I need to ODIN my device to an MJ7 image. At first I got the error and did a factory reset through safestrap recover. Still got the error so I did an advance wipe of every option. (Looking back shouldnt have done that) That took away my recovery, but I can get to download mode, but its not detected by my computer to use ODIN with. So I am stuck without a custom recovery without the ability to boot into anything.
Here is what I have tried so far:
1. Reinstall/uninstall drivers, reinstall/uninstall kies.
2. Changed USB ports on computer.
3. Changed USB cables
4. Changed computers from Win 8 x64 to Win 7 x64.
5. Changed computer to my MACbook using Heimdall.
6. Changed USB charging port board on my phone.
7. Tried everything again. *Still doesnt detect it*
Any ideas that I havent done already, or how to fix? I do have nandroid backup of my ROM, but dont have a custom recovery to flash it.
Cant ODIN back cause its not detected by my computer. Thanks in advance for your help.
Is USB debugging still checked on phone? You must use the USB cable provided with phone...
safestrap enabled, Hyperdrive driven
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
odlay75 said:
Thanks for the reply. I cant select USB debug on my phone because my phone does not boot into the main OS, it is stuck at the samsung custom padlock screen. The USB debug option was on when the OS was installed though. My phone will only boot into stock recovery and into download mode. I tried to use the original USB cable provided with the phone as I read this could be the problem, but I tried 4 other ones too and phone still gets detected as "Unknown Device" in device manager, so ODIN cant even see phone in download mode to restore. I have tried to install KIES and the Samsung Mobile phone drivers 1.5.x.x drivers. Just read somewhere where someone had this issue and installed Samsung mobile phone driver v1-4-6-0 so I am trying that now.
Click to expand...
Click to collapse
Tried Samsung Mobile phone drivers version 1.4.6.0 and still the same outcome "USB device not recognized". I went down to a local electronics store and bought two different brand microUSB data cables. Tried them both along with my original one from samsung, and still the same result. Any other ideas??
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
odlay75 said:
Anyone else have any ideas? Thinking of sending it in and having it JTAG'ed back to stock. Can anyone recommend any services? Heard mobiletechvideos is good.
Click to expand...
Click to collapse
Go to Saferoot thread in dev forum...your answer may be there
safestrap enabled, Hyperdrive driven
I tried flashing CWM recovery onto my AT&T Galaxy S4 and because my phone does not connect to my computer via USB for some reason (the phone charges and my computer recognizes that there's a device in, but I cannot actually do anything with it) I flashed it with Flashify. I rebooted into recovery mode, and I got slapped with the "Unauthorized software has been detected on your phone!" message. So I tried rebooting, and I got stuck in a recovery mode bootloop with the same message. Eventually, I realized if I just go into download mode and reboot by pressing the volume down key, it doesn't try to go into recovery mode. I have already endlessly researched my USB problem, and yes, I DO have USB debugging on. ODIN recognizes that I have an external device in as well, but I haven't tried flashing anything onto my phone with it because I don't want to brick my phone because the connection to my PC is faulty. I'm using the charger that came with the device as my USB drive, so that's not faulty either. I know rooting my phone did this, and I'm pretty sure it's because I missed a step. I used this tutorial to root my phone:
[droid views dot com] /root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/ (I'm not allowed to post links yet, so fix the URL if you're gonna have a look)
When I flashed the I337_NC1_Stock_Kernel, my phone refused to go into download mode and I couldn't flash the I337_NJ4_Stock_Kernel as a result. I'm pretty sure that's what caused it, but I have no idea how to fix it. I'm not an expert with my phone and, despite almost soft-bricking my phone via a corrupt CWM .zip, I'm not a newbie at this either. If I could figure out how to fix this problem, I wouldn't have to worry about throwing myself into a bootloop because I can just use ODIN. I was a sitting duck before download mode rescued me, so I'd like some help as to how I can accomplish this. Any and all help is appreciated. I am 100% certain my device is the right version for that tutorial, I wouldn't try to root my phone without checking all of the simple things first.