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.
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 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.
Hi there,
I've read every kind of threads here and no one works for me. I rooted my Samsung GT-I9000 and all worked well, then the phone started acting crazy, my root was gone and when I boot the phone I come to the usual screen where you enter pincode but after that the popup screens start, multiple popups saying that twlauncher crashed, media, acore etc.. so I cant get to the screen where I can enable usb debugging. I can enter the stock recovery and my PC can contact the phone, but when I press vol down + home + power so I get the download mode the PC cant find the phone, not in win7 or in Linux. I have tried every kind of driver there is for Samsung but no one works that make it possible for the PC to find the phone when it is in download mode, win7 list it under "unknown device" and NO driver at ALL works so win7 can reqonize the phone. I've tried installing Kies how many times I dont know and uninstalling, updated SDK, uninstalled every USB driver and even the hubs and installed them again, updated win7.. what can I do to flash the phone!?!? Because Odin, no matter old from new; cant find the phone in DL mode, same with linux. And in stock recovery, I wiped cache and data but the problem is still there when I enter the OS after enter my pin...
How can I flash my phone without PC finding the phone in DL mode and no USB debugging enabled? Or how to flash CWM so I can flash a ROM from SD? Please help!!
At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.
DeMaCr said:
At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.
Click to expand...
Click to collapse
As I wrote, my desktop is under Linux and the laptop under Win7 and none can reach the phone, both computers can only detect the phone in Recovery mode, but the laptop under Win7 only detect the phone as offline, Linux on the other hand can reboot phone into recovery from recovery, to download mode and reboot normal. Already tried to use Ubuntu 13 Live and it cant detect the phone in DL mode either. And tried different cables also. And if I find a recovery or CWM, then what? Dont I need to get phone into DL mode to flash something?
But in Linux I've got a small breakthrough, Heimdall can detect the phone know, but fails to flsah anything. Maybe wrong files or something..? But anyhow, if Heimdall now can detect the phone and it couldnt before; know I just need the right files to flash.
Just find a friend who owns Windows desktop/ laptop, download stock from Sammobile, flash stock via Odin. If not, try Odin mobile...
Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone
simsale said:
Hello,
I followed Hasoon's all-in-one root toolkit and flashed the included TWRP 2.5.0.0 onto my AT&T HTC One X. Now I cannot do anything, whatever I do, it tells me "Unable to mount /cache". Could you please help me? I can't mount the sdcard to the computer either, so I am sort of stuck.
Thanks!
Simone
Click to expand...
Click to collapse
Can you format the SD card in TWRP?
exad said:
Can you format the SD card in TWRP?
Click to expand...
Click to collapse
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone
simsale said:
I was able to wipe it. However, it still gave all these same unable to mount /cache error messages. The data is gone though.
When I connect the mounted device to the computer it still doesn't recognize it.
Thanks!
Simone
Click to expand...
Click to collapse
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?
exad said:
Does the PC not recognize that anything is connected or does it detect that its plugged in but can't find the driver?
What rom is currently installed on the phone?
Click to expand...
Click to collapse
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone
simsale said:
Currently I think it recognizes the phone as a media device (or similar, I forgot the name), not as a disk drive. I am on a Mac, and I have Android File Transfer installed, which then tells me that the device cannot be opened. On Windows it couldn't be opened either although it talked about a driver issue. I currently only have a Mac, but from Monday I could work on a Windows machine again.
The ROM currently being installed is the original AT&T provided ROM.
Thanks so much!
Simone
Click to expand...
Click to collapse
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
exad said:
What version? IS it already installed on your phone? I'm trying to find out if you require MTP drivers or not. Latest version of sense/stock Roms require MTP driver to access the SD card.
In any case I wouldn't suggest using any version of TWRP above 2.3.3.1
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone
simsale said:
I see, this all sounds like I need to wait for a windows machine.
I am not sure what ROM version, unfortunately. I bought the phone in December from AT&T, and it all looks like it asks for MTP drivers. I will try this with a Windows machine and then get back to this post - thank you so very much for your help.
Simone
Click to expand...
Click to collapse
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.
exad said:
Yes, you would need mtp drivers for the latest software version. They are included with the latest HTC sync.
Click to expand...
Click to collapse
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.
simsale said:
Alright, I have tried this with the latest HTC Sync manager: the MTP Drivers however won't install. I have tried with the One X+ of my Dad (which is also brand new, so probably requires the newest version also), and it installs fine and appears as a media device in the explorer. Mine however does not do anything, and driver installation says it fails to install the driver. I have tried manually installing the drivers, however, it seems to have to do with the phone because when I disconnect it suddenly Windows 7 is able to install those drivers, and as mentioned before it also works with a functional phone.
Next week I will be back at work and I have a Windows 8 machine there. I don't have high hopes that it works there, but since there seems to be an MTP driver issue with Win7, maybe there's a chance.
Is there anything else I could do?
Thanks!
PS: don't use your vacation time to root your phone...haha.
Click to expand...
Click to collapse
OK, so on Windows 8 I am able to install the driver, and it does not fail like in Win7, but I still can't access the mounted storage. The message of the device is:
This device cannot start. (Code 10)
The process hosting the driver for this device has terminated.
Is there anything else I can do, or should I rather get a new phone?
simsale said:
Is there anything else I can do, or should I rather get a new phone?
Click to expand...
Click to collapse
Did you do all of what exad said in his earlier post (quoted below) already?
exad said:
So, I would download twrp 2.3.3.1 and check the md5
then fastboot flash recovery recoveryfilename.img
fastboot erase cache
fastboot reboot-bootloader
select recovery from bootloader then try to mount sdcard with twrp.
Click to expand...
Click to collapse
lauterm said:
Did you do all of what exad said in his earlier post (quoted below) already?
Click to expand...
Click to collapse
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.
simsale said:
Yes, in fact, I cannot connect to the phone with this strange driver issue, which means none of the commands actually do anything.
Click to expand...
Click to collapse
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.
lauterm said:
Are you rebooting to bootloader to do the fastboot commands? In bootloader it should say Fastboot in red. Then after a couple seconds that should change to Fastboot USB. I don't think fastboot needs the specific drivers to be on the PC like mounting the SD card requires.
Click to expand...
Click to collapse
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
You are definitely doing something wrong. fastboot commands only work within bootloader/fastboot and adb commands only work while the rom is loaded up or in sideload mode in TWRP. It's assumed you know this prior to rooting.
simsale said:
Well, when I turn on the phone, all I get is the TWRP interface. Mounting from there doesn't do anything. I am not in fact in bootloader. Maybe I am doing something wrong here!!
Click to expand...
Click to collapse
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app
lauterm said:
Turn off the phone. Then hold volume down and briefly press the power button. Don't let go of volume down until it gets to the boot loader screen. Wait for fast bot USB to display. Then you can try exad's fast boot commands.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!
use cwm
simsale said:
Oh, thanks so much. I actually did know this from rooting my old phone - I guess I forgot.
It doesn't go into Fastboot USB though, stays at Fastboot. Is there another trick? Thanks so much!
Click to expand...
Click to collapse
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.
lauterm said:
It should change to FASTBOOT USB if you are plugged into a computer. If you connected to the computer after you got to bootloader mode, you might have to press volume up or down to get it to switch to FASTBOOT USB Maybe this is the root of your problem. Have you tried multiple USB cables? Is there any crud in the micro-USB port on your phone? It's a little odd that the micro-USB port would break in a manner that charging would still work but not data connections, but I'm starting to wonder if that isn't the case.
Click to expand...
Click to collapse
OK, I managed to get into Fastboot USB and now have the SDcard mounted. I'll try flashing a new ROM now. Is this one you'd recommend?
http://forum.xda-developers.com/showthread.php?t=1868236&highlight=+rom+
Thanks so much!!
Simone
I installed some cyanogen rom on my tablet and now everytime I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile odi n(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically its useless and I do now know what do to... Please, someone just help me out here >.< :crying:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
ashkineeeeee said:
hi....dou have enabled android debugging? if yes go to downloading mode and flash cf auto root and recovery
Click to expand...
Click to collapse
Yes I tried to enable debugging still did not work... I can not flash it because it doesn't get recognized by any computer.
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
john99ap said:
If you manage to get root, then you can use FlashFire from play store to flash the stock rom.
Click to expand...
Click to collapse
I tried already the root app simply keeps trashing no matter what-
dionex2k said:
I installed some CyanogenMod on my tablet and now every time I try to plug it into my laptop or PC It says USB not recognized device descriptor request failed. I tried with 3 different cables and 3 different computers. I have Samsung drivers installed. I just need to get it to connect so I can restore my tablet to stock ROM. I was trying it on my own with mobile Odin(app) and tried to flash it but it went into a loop and deleted recovery. Now the tablet does power on and works - apps crash all the time and no root available. So basically it's useless and I do now know what do to... Please, someone just help me out here >.<: crying:
Click to expand...
Click to collapse
Basically, because what you get is a CyanogenMod, which does not relate to any piece of the Samsung Driver. All you need is Google USB Driver which supports almost all Android phones in the world. A thread in XDA talks about 15 seconds Google USB Driver Program for Windows which can be found somewhere in the XDA thread world.
And more here, for the problem about root access, have you tried installing a SuperSu flashable zip through your recovery yet? That should work a lot. Then, if you update your firmware using recovery without using an OTA update manually, apps may not be compatible and will crash. Reinstalling all your crashing apps from the Google Play Store should help.
Finally, if you want to update your phone through recovery, not an OTA-received ROM, please make sure not to install many apps on it, because when it crashes, you can do nothing but to reinstall it. although, all add-ons (Such as GApps, SuperSu, Xposed Framework, et cetera) need to be reinstalled so you don't lose them during a manual update, so don't delete your flashable add-on zips once you installed, you might need them forever.
Recovery is like a mobile version of Odin, use a Desktop version of Odin so you can get yourself out. A tutorial might be found somewhere on YouTube.
Hope you have a good day,
Shippo
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
dionex2k said:
I can't just install a new ROM or recovery - my tab does not get recognized by any PC or laptop
Click to expand...
Click to collapse
There is a tool called Forget Windows Use Linux in which all necessary drivers come preinstalled and your tab should be recognised from your pc with no problem if it's a driver issue. Try it
Try this slide down from upper left of the screen. If the window indicates charge only, click on it. It should then offer file transfer. In order to get adb to see the tablet turn on deveper options and enable USB debug mode. Hopefully that works for you.
hello
there is something very very very very very old which is called cf autoroot
every needed is in the zip use it
regards