I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!
I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.
Related
I was trying to install Cyanogen 7 and my first step was a one-click return to stock that seemed to complete fine.
When I rebooted I go into Android 3e recovery. Each time I boot the recovery message says:
Update media. please wait
update media. finished
#manual mode#
--Applying Multi-CSC...
Installing Multi-CSC
Install default apk-files. please wait
Install default apk-files. finished
The phone is no longer recognized by windows even though I've tried several different versions of the Samsung drivers. (also tried different USB ports, different cables and different computers per my search results in here)
I can get into Download mode but the device is not recognized so its not recognized by any of the ODIN utilities to repair or restore...
Any idea what is going on - or more importantly what can I do to recover this thing?
Help?
Thanks!
First of all, I would try Heimdall One-Click instead of Odin. It's more reliable, and uses better drivers. Will it not reboot into Froyo? And which one-click package did you use?
I used the Heimdall One-Click and it seemed to complete okay. Trouble started when I rebooted. I can't seem to redo it because the the One click utilities don't recognize the phone as connected.
I always get the Windows message "USB Device is not recognized" and when I go into my Device Manager the phone is listed as an "Unknown Device"
I would strongly advise against flashing back to froyo or eclair as the bootloaders are out dated.. As.for.your phone not being recognized it could be a number of issues from anywhere to ypur pc.needs a reboot to your usb cable is bad. I once had the same issue and i reinstalled the samsung drivers a few times with no reults. Believe it or not what fixed my problem was a fresh install of kies (a program i never use)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
I installed Keis, rebooted and it did in fact recognize and re-install the drivers. I then tried the heimdall 1-click and it failed on the attemped handshaking with Loke step. Now I am back to not being able to recognize the USB device again.!
ugh!
WinoOutWest said:
I installed Keis, rebooted and it did in fact recognize and re-install the drivers. I then tried the heimdall 1-click and it failed on the attemped handshaking with Loke step. Now I am back to not being able to recognize the USB device again.!
ugh!
Click to expand...
Click to collapse
Heimdall uses completely different drivers
Sent from my SAMSUNG-SGH-I777
Yes it installed the heimdall drivers successfully when I tried to run the on-click. Then it timed out. I now appear to be back to an unrecognized device again. Installing Keis, Samnsung drivers etc trying to get it to recognize the phone again. It easily goes into download mode.
Anyone got any ideas how I can get this thing breathing again?
Try rebooting the computer. Use a USB port in the back of the computer. Try a different cable. Open Odin before connecting phone to computer.
mrhaley30705 said:
Try rebooting the computer. Use a USB port in the back of the computer. Try a different cable. Open Odin before connecting phone to computer.
Click to expand...
Click to collapse
Tried all of this - still no love. Every once in a while it will search and install Samsung drivers but then it disconnects almost instantly.
I also fumbled through getting a Ubuntu up to try it in Linux but the download mode isn't found in linux either.
Running out of options here. Wondering if I've pooched this phone.
WinoOutWest said:
Tried all of this - still no love. Every once in a while it will search and install Samsung drivers but then it disconnects almost instantly.
I also fumbled through getting a Ubuntu up to try it in Linux but the download mode isn't found in linux either.
Running out of options here. Wondering if I've pooched this phone.
Click to expand...
Click to collapse
Its not broken permanently, I promise.
Well slap my a$$ and call me Judy!
After 1 million attempts (cords, ports. pcs, windows, linux) I finally managed to get back into my phone. I literally must have had this phone in and out of download mode several hundred times in the last 24 hours. One of my attempts finally worked in Ubuntu! Not sure why really - but I am okay with that at this point.
Thanks for all you help!
Darren
<smack> good job Judy.
I've tried a few other forums but haven't got any replies, I guess since the Galaxy 5 isn't such a popular device. I figured if there's anyone who can help me they will be here though.
I wanted to put CWM on it so I could get a CM7 port on. Unfortunately it's just about impossible for it to get detected on USB. I've installed Kies (and even the generic USB drivers found in the SDK). In 2 days I only got it to connect once, and then I went and bricked it.
The one time it finally connected I ran Odin and tried loading CWM onto it. It still hadn't finished after half an hour so I figured it ended with an error that was never displayed. So I unplugged it and as expected - brick! I can get into download (upgrade/firmware) mode so I think it can be fixed if I can get CWM on it (and just install the CM7 port I had originally intended to put on).
Problem is I cannot get the darn thing to connect! to my computer I've tried two separate PCs, one running Window 7 x64 and another running XP x32. Is there a a certain process of connecting things? I haven't ran across anyone making mention of one.
Has anyone else experienced USB problems like this with Samsung phones? Would it even be possible to flash CWM on after it's been bricked like this? When I boot (normally) all I get is an image showing a phone and a PC with and exclamation error connecting the two. Please help!
Try to look for stock firmware on the forum.xda-developers.com and flash via ODIN. You need to be able to put the phone into download mode, so maybe get an USB jig. That should do the trick. Odin has to recognize your phone. First of all right click on the ODIN executable and select "Run as administrator" on windows. Plug the phone in the DL mode and wait until it appears as active in Odin. Then flash the ROM and pit file. (Don't use ODIN one click). If ODIN does not recognize your phone try a different USB port or reinstall Kies. The Kies trick was which I used and it was able to recognize my phone.
Thanks, martin0176. I can still manage to get the phone into download mode - it's getting recognized by a PC that's the problem.
Could you tell me more about the pit file? I only have an ops file.
Try a different cable. I was having the same problem on the Samsung Continuum and it turned out that the cable was working for power, but not for data.
So, i have Android Debugging enabled on my device, and when i connect it to a pc over usb, it reports that android debugging is on. But my pc (tried on many machines at this point) wont see the device. If i issue an "adb devices" i get nothing in the list. I've tried restarting adb, no help.
The tablet is a TF101, running CM9 nightly 6/13, but it was having the same problem on a rooted stock .17.. i think it was, that i was runinng, and on two other cusom roms.
Is there some low-level change i may have made at some point that might have killed off adb?
Thanks.
Have you tried reflashing the kernel? That might magically fix it, otherwise try it on a linux box/something that doesn't need drivers.
I have the same problem and I have tried absolutely everything within my scope of knowledge including every rom available, all kernels, different computers with various os, different cables, even mounting as usb in cwm. The reason I tried so hard was to downgrade to Honeycomb is because the bluetooth in ics is horrible.(tons of disconnects and constantly oos). Finally I switched with my son and nvflashed Honeycomb on his.
If anyone can think of why my tab can't connect please let me know.
gangrif said:
So, i have Android Debugging enabled on my device, and when i connect it to a pc over usb, it reports that android debugging is on. But my pc (tried on many machines at this point) wont see the device. If i issue an "adb devices" i get nothing in the list. I've tried restarting adb, no help.
The tablet is a TF101, running CM9 nightly 6/13, but it was having the same problem on a rooted stock .17.. i think it was, that i was runinng, and on two other cusom roms.
Is there some low-level change i may have made at some point that might have killed off adb?
Thanks.
Click to expand...
Click to collapse
If you are using Windows, you need to install USB driver for adb to work:
http://support.asus.com/download.aspx?SLanguage=en&p=20&m=Eee+Pad+Transformer+TF101
tingtan said:
If you are using Windows, you need to install USB driver for adb to work:
http://support.asus.com/download.aspx?SLanguage=en&p=20&m=Eee+Pad+Transformer+TF101
Click to expand...
Click to collapse
Yes I have them installed, tried those and universal naked drivers beta, I don't think it is anything that simple as I have nvflashed my sons transformer back to HC but thanks anyways!
joefloater said:
I have the same problem and I have tried absolutely everything within my scope of knowledge including every rom available, all kernels, different computers with various os, different cables, even mounting as usb in cwm. The reason I tried so hard was to downgrade to Honeycomb is because the bluetooth in ics is horrible.(tons of disconnects and constantly oos). Finally I switched with my son and nvflashed Honeycomb on his.
If anyone can think of why my tab can't connect please let me know.
Click to expand...
Click to collapse
+1
I also have the same problem, it used to work once, but it stopped after I changed kernel (I think), I will try stock kernel tomarrow.
if it will not work then I've tried everyting like you....
anyone ?
I want to try the ubuntu dual boot so I need APX.
btw: it doesn't show in device manager in any shape or form, no beep no nothing...
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.
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
chaosrde said:
So Ive just bought a brand new U12+, and obviously the very first thing I did was attempt to root it.
Main hiccup Im running into here is that my PC wont recognize the phone while its in recovery or fastboot/download mode.
If I had to guess, I think it's a driver issue, problem is I've been searching for hours now and cannot find the proper drivers for it to be recognized. (I've also tried every USB port on my PC, both 2.0 and 3.0.)
Ive tried using HTC sync, uninstalling it and leaving that driver, Ive tried letting windows auto install the driver, and I tried a generic android USB driver, none of which have seemed to work.
PC will recognize the phone while it's fully booted to OS, and I can even command it to reboot into recovery from there, but once its in recovery I lose connection.
Not sure how much of a difference this makes, but I bought a factory unlocked phone, still sealed, with all the plastic and accessories inside the box. But when I boot into download I get the message "Security checking failed DENY", this is only supposed to show up after the bootloader has been unlocked isn't it?
Anyways, if someone could point me in the right direction for these drivers it'd be greatly appreciated.
Click to expand...
Click to collapse
Strange suggestion but try a different pc. My phone isnt recognised when I try to install magisk on my phone on my home pc but it works on my work pc.
I got about 9 different USB ports on my home PC and none work
Also download platform-tools_r29.0.2-windows for fastboot etc.
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Icculus760 said:
While you're in troubleshooting mode, try another USB cable. I had issues running fastboot commands and the like when using a generic USB cable, but it worked fine using an OEM one. Can't hurt to rule that out too.
Click to expand...
Click to collapse
I am using the OEM cable, straight out the box. I'm gonna try meddling with it again when I get home and see if I can get it working.
bigAL99 said:
Also download platform-tools_r29.0.2-windows for fastboot etc.
Click to expand...
Click to collapse
Ive done a fair bit of searching but I can't find anywhere to download older version of platform tools, I have the current build 29.0.5.