hi, i rooted my nexus s and now it is just stuck on boot logo so i can access recovery and download mode but my computer for some reason, when ever i mount my sdcard in recovery mode, my computer doesnt detect it. whenever i put my phone in download mode, it is not detected. what is the problem? please help this is my friend's friend phone and i dont want any trouble. thanks
You're either lacking the fastboot driver or the USB port is faulty.
Try uninstalling all drivers then gey everything setup with pdanet or sdk driver package downloader help.
Sent from my Nexus S using XDA App
alright im going to uninstall and reinstall all the drivers. should i reinstall the android sdk? and the computer use to detect download mode but now it doesn't and in recovery it says failed to find cache partition to mount at /cache
thanks for the help
i tried to install pdanet drivers but it asks me to put my nexus in debugging mode when my phone cant turn on.
anybody there?
That's ok, that part just installs PDA net on your phone. The only part that matters is getting the Samsung driver on your windows machine.
Sent from my Nexus S using XDA App
well i installed the samsung drivers but the computer still doesnt detect the phone?
please help
http://forum.xda-developers.com/showthread.php?t=1246964
Donate it for the greater good.
If you for some reason feel it isn't a good idea to donate your friends phone:
redo everything that has been said in this thread and start from scratch. You'll most likely realize that you forgot something important.
Good luck with whatever option you pick
Sent from my Nexus S using Tapatalk
Have you tried changing the USB cable / port?
yes i have tried changing usb port and cable
i tried going to recovery then to mounts and storages and mount usb storage but the computer still doesnt detect the phone
so this is kind of a computer problem
so if i can use usb mass storage from recovery i would have flashed it back to stock but computer doesnt detect it, same with download mode. in the bottom of download mode it says usb control init usb control init end. what does that suppose to mean?
try to look, control panel - system - device manager - android phone
Mine is written Android ADB Composite Interface
U can right click there , and update software driver - choose browse for software driver in computer - click on let me pick from a list of device driver on my computer - ( Uncheck ) show compatible hardware.
You should go with Android Bootloader Interface Version: 4.0.0.0 if u want to work with recovery or download mode. ( or u can choose which driver work with you )
Hope this help
thank you everybody for trying but still no solution i appreciate your guys time but i still need help
Did you try reinstalling the all sdk drivers?
Sent from my Nexus S 4G using XDA App
maybe this is whats causing it?
yea i tried, still no nothing. when it use to work before i flashed something to the phone and after that, my computer wouldn't connect to my phone. i think thats the problem and do you guys think there is a way to reverse that? and when i go to recovery its says:
ClockworkMod Recovery v3.0.0.5
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
so why is it saying that and how can i fix it?
Use clockwork 3.0.2.4 or later and I think you will have success
Edit: but now I realize you cannot flash the recovery image without USB. Sorry
Sent from my Nexus S using XDA App
Use Samsung exe to restore recovery or adb to flash new one.
Sent from my Nexus S 4G
Related
I probably have a defective phone.
I've installed the 32bit drivers for my WinPc, and selected Mass Storage and enabled USB debugging on my mac.
On the pc, I can see two drives but when clicked, I get the "please insert a disk into drive" error. eh?
On OSX, the mac obviously recognizes my phone, I can use ADB without issue and OSX attempts to use the phone as a modem, but the drives never mount at all or even show up in disk utility.
Anyone else having this issue?
Double Twist (OSX) also recognizes the device, but if I can't mount the drives, it's useless to me.
#Frustation
To get a Mac to recognize the phone, you have to turn on USB debugging under Settings > Applications > Development. I had the same problem but this solution fixed it.
Not sure what to do about a PC though. Maybe the same fix works for both?
There's another thread going on with same issues.
Seems to be a re-occuring issue. I am going to replace mine today.
Keslynn said:
To get a Mac to recognize the phone, you have to turn on USB debugging under Settings > Applications > Development. I had the same problem but this solution fixed it.
Not sure what to do about a PC though. Maybe the same fix works for both?
Click to expand...
Click to collapse
You didn't read where I said that I did that? Gimme a little credit...
This might have something to do with why I can't mount my drives on an computer:
When I tried to mount via adb, this was my output:
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
Plug in phone USB to computer,
Choose Mass Storage
Swip down from the top bar and choose mount USB.
Now you will be able to see MicroSD as well as phone storage.
Wish I know this before I returned the first phone. 8' )
wease said:
Plug in phone USB to computer,
Choose Mass Storage
Swip down from the top bar and choose mount USB.
Now you will be able to see MicroSD as well as phone storage.
Wish I know this before I returned the first phone. 8' )
Click to expand...
Click to collapse
There's no "mount usb" option in the notification bar... Well, at least on mine.
cashless said:
There's no "mount usb" option in the notification bar... Well, at least on mine.
Click to expand...
Click to collapse
Click where it says usb connected. Then it will give you the option to mount it.
thedon809 said:
Click where it says usb connected. Then it will give you the option to mount it.
Click to expand...
Click to collapse
I shoulda explained better. The "USB connected" option doesn't appear at all when I connect to my Mac. It does in Win though.
cashless said:
I shoulda explained better. The "USB connected" option doesn't appear at all when I connect to my Mac. It does in Win though.
Click to expand...
Click to collapse
Does it show up in System Profiler? You said the Mac tries to use it as a modem, so I would think it would.
When mine is plugged in, with USB debugging enabled, I get 2 USB options in the status dropdown. USB Debugging Connected, and USB connected. Clicking the "USB connected" gives me the option to mount the drives to the computer. Once I hit that, the Mac sees them in Finder just fine.
I would expect it would work about the same in Windows.
ttabbal said:
Does it show up in System Profiler? You said the Mac tries to use it as a modem, so I would think it would.
Click to expand...
Click to collapse
I'm sure it does, really haven't looked yet because I'm sure of the usefulness since I know it recognizes the phone. The only thing I haven't tried so far is a full wipe, which I'm reluctant to do, but will try tonight.
I am having the same issue with my HTC desire. When I plug it into my Mac, it charges but the mac doesn't recognize it as an external storage device and the phone doesn't recognize that it's plugged into a computer, it simply charges (no USB notification).
Any ideas how to fix this? I have USB debugging enabled ...
plzz help ... when i enter to recovery mode i cannot do anything
it just come like this
E:unknown volume for path [/data]
E:unknown volume for path [/data]
E:unable preocess volume! Skipping...
Checking /cache
E:unknown volume for path [/cache]
E:unknown volume for path [/cache]
E:unable preocess volume! Skipping...
Done!
E:unknown volume for path [/cache/recovery/command]
E:can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:can't mount /cache/recovery/log
E:can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:can't mount /cache/recovery/last_log
E:can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]
when i go into download mode by plugging usb cable on my phone after pressing vol up + vol down button . my com port does not show on ODIN and windows says - "USB DEVICE NOT RECOGNIZED"
what i have to dooo plzz help ???
i am waiting u
have you tryed reinstalling the usb drivers
got-petrol said:
have you tryed reinstalling the usb drivers
Click to expand...
Click to collapse
yes i have
Try installing the USB drivers on another PC if you have one available, preferably one that hasn't had the samsung connected to it before, then try putting the phone into download mode and re-flashing using Odin
bigdyl69 said:
Try installing the USB drivers on another PC if you have one available, preferably one that hasn't had the samsung connected to it before, then try putting the phone into download mode and re-flashing using Odin
Click to expand...
Click to collapse
i tried many pc and laptop
still same problem
Any help ??? I lost my phone ??? This is the end ????
When you used a diff PC or laptop, which USB drivers did you install? Where did you get them from?
Install the USB drivers from the Android SDK. Install the SDK, then from the SDK manager, choose Google USB drivers under extras/third party.
After this is downloaded, choose update driver to your unrecognized device in device manager and point to the SDK directory. You may get a new unrecognized device and will have to repeat this step.
After this Odin should work.
Sent from my GT-I9000 using Tapatalk
Pierreken said:
When you used a diff PC or laptop, which USB drivers did you install? Where did you get them from?
Click to expand...
Click to collapse
no diff
the one ehich come with kies and i inatall Android SDK as josteink said
still not work
plzz help sam problem
josteink said:
Install the USB drivers from the Android SDK. Install the SDK, then from the SDK manager, choose Google USB drivers under extras/third party.
After this is downloaded, choose update driver to your unrecognized device in device manager and point to the SDK directory. You may get a new unrecognized device and will have to repeat this step.
After this Odin should work.
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
still not work with this way ,, plzz help
Why do you post this in "Galaxy S I9000 Q&A" and here?
elhennig said:
why do you post this in "galaxy s i9000 q&a" and here?
Click to expand...
Click to collapse
coz i need fast help ... I don't know what i have to do
i am getting crazy but for i will post here only
fhkal said:
still not work with this way ,, plzz help
Click to expand...
Click to collapse
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
tried to replace USB cale ??
tried to replace USB cale ??
I had a similar problem - resolved cable replacement
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
Not bad, but those drivers are old. It could be "better" to download latest and use those instead
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
Perfect guide, will work 100%
josteink said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=803492
Download the pack found there, unpack it somewhere safe and remember the location for the drivers-folder. You will need this later.
With that done, open Device manager. Connect your phone in download mode.
Find all devices in device-manager which represents your phone. Double click them, go to the drivers tab, and click "Uninstall". In the uninstall confirmation-window (at least in Windows 7) you have the option to "delete the driver software for this device". Do this.
Do this for all devices representing your Galaxy S.
Now. Disconnect the USB cable from your phone (still in download mode) and connect it back to your PC.
Verify in device-manager that it is an unrecognized device. If it gets recognized, repeat the driver removal process above and try again.
If Windows tries to download drivers from the internet when you hook it (if it says "Installing drivers" in the system tray), be quick and double click that thing up and abort the installation.
Now. You should have your PC clean of drivers.
Double click your unrecognized device and click "Update driver". Point it to the location where you unpacked the drivers you downloaded earlier.
This should work and you should get some new devices. Repeat this process and you should see Windows install a million devices "Samsung USB Composite device", "CSC device", "Gadget serial", "Samsung Modem device" etc etc.
Unplug your phone and reconnect it (still in download mode). Verify there are no unrecognized devices. If there are, repeat the process above until there are none.
Now. Unplug your phone (still in download mode)
Now you can start Odin, as administrator. Now plug your phone back in (still in download mode).
Now it should work. I know. I just went through this right now after some ICS firmware updates
Click to expand...
Click to collapse
still not work mate ... after remove all thing belong to galaxy at the first i get like in the picture .... then done ur way still get USB DEVICE NOT RECOGINZE
THANKS FOR UR HELP
for ur info my bro have same phone and work normal in download mode in the pc and lap top which i worked with it
STILL NEED UR HELP
fhkal said:
still not work mate
...
for ur info my bro have same phone and work normal in download mode in the pc and lap top which i worked with it
Click to expand...
Click to collapse
Then I honestly have no idea. Really. best of luck.
Hi guys
any idea
i am sooo sad coz that ?? Mean lost my phone ?
connect pc to phone, go to devices and printers, delete all the unknown devices from there. Open device manager and remove all the unknown devices. Remove each and every samsung usb drivers and remove phone connection with pc then reboot. Then install fresh drivers from http://forum.xda-developers.com/showthread.php?t=961956 . "Dont connect your phone to pc during all this process!" Now get the phone to download mode and then connect the phone to pc and it will recognize the device. Remember that during all this process only connect phone to pc when in download mode!
Hi, I'm editing this thread.
I was browsing, and the kindle freeze, so I reboot it, and it never came back.
What I can do :
# go in TWRP
E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open /cache/recovery/log
# see the bootanimation in loop.
What I can't do
# accessing th SD with TWRP ( freeze)
#accessing SD with pc (freeze)
# adb devices
adb shell
error : device not found
I have :
#normal cable : device manager/Android composite ADB Interface
#factory cable : device manager/Android ADB Interface
I can go in fastboot, but it doesnt help... kfu says ''offline'' but I can reboot in different mode.
#drivers are installed
I'm lost, I tried almost everything
edittt
Try uninstalling any drives that are named kindle, kindle fire, android device etc. Then reinstall them with Kfu. Dot you have fff1.4 already?
sent from my Nokia 5110
pbailey212 said:
Try uninstalling any drives that are named kindle, kindle fire, android device etc. Then reinstall them with Kfu. Dot you have fff1.4 already?
sent from my Nokia 5110
Click to expand...
Click to collapse
yes fff 1.4a.
Drivers are tested with kfu and the one came with sdk package (add kindle device manually)
I tried it on win7 with a recent pc usb2, and tried on winXP on a p3 USB1.
thanks
oVeRdOsE. said:
yes fff 1.4a.
Drivers are tested with kfu and the one came with sdk package (add kindle device manually)
I tried it on win7 with a recent pc usb2, and tried on winXP on a p3 USB1.
thanks
Click to expand...
Click to collapse
The 2 drivers might be conflicting each other. I had to uninstall all drivers related to kf and android and install them again.
sent from my Nokia 5110
pbailey212 said:
The 2 drivers might be conflicting each other. I had to uninstall all drivers related to kf and android and install them again.
sent from my Nokia 5110
Click to expand...
Click to collapse
understand.
What was your problem?
I've tested it also on ubuntu. I can barely do some stuff...
++ On xp, when I'm mounting the SD with TWRP, I can see all my folders and files in it for about 5 seconds. After the computer can't see the mass storage anymore...:crying:
oVeRdOsE. said:
understand.
What was your problem?
I've tested it also on ubuntu. I can barely do some stuff...
++ On xp, when I'm mounting the SD with TWRP, I can see all my folders and files in it for about 5 seconds. After the computer can't see the mass storage anymore...:crying:
Click to expand...
Click to collapse
I wonder if your battery is dead. Have you tried plugging it in to the wall charger that came with it for a couple hours?
sent from my Nokia 5110
pbailey212 said:
I wonder if your battery is dead. Have you tried plugging it in to the wall charger that came with it for a couple hours?
sent from my Nokia 5110
Click to expand...
Click to collapse
The battery is ok, the kindle can bootloop for ever, twrp nerver shut down, it just freeze. On twrp it has battery meter, so i'm always around 80% when I'm playing (well repairing) with it.
oVeRdOsE. said:
The battery is ok, the kindle can bootloop for ever, twrp nerver shut down, it just freeze. On twrp it has battery meter, so i'm always around 80% when I'm playing (well repairing) with it.
Click to expand...
Click to collapse
You tried going to boot normal on the fff1.4a screen right? Sorry I'm trying to narrow down your issue
sent from my Nokia 5110
pbailey212 said:
You tried going to boot normal on the fff1.4a screen right? Sorry I'm trying to narrow down your issue
sent from my Nokia 5110
Click to expand...
Click to collapse
thanks for your help, it make me think about something new.
So far, twrp IS the problem.
#1 reinstall sdk (I started from a fresh pc with winXP)
#2 open a cmd windows from sdk tools folder, not the platform-tools, just tools and run this:
android uptade adb
#3 then go to user folder c:\users\username there should be a folder named .android in there, open adb_usb.ini and add this line at the bottom
0x1949
save close
#4 update driver kindle manually from ''Kindle Fire Utility'' while its in twrp. (the one a lot of people seem to be missing after you select the android_winusb.inf file you have to (in win 7) UNCHECK the "show compatible hardware"
tickbox and select the Android Composite ADB Interface driver. if you don't uncheck that box it will install the wrong one for you automatically. )
#5 reboot kindle in recovery in FASTBOOT(with a factory cable) and INSTALL CWM with KFU!!!! it wont freeze anymore !!!
#6 -boot to CWM
- test adb with "adb devices"
- open shell -> "adb shell"
- issue "echo /dev/block/mmcblk0p12 > /sys/devices/platform/usb_mass_storage/lun0/file"
- now the sdcard should mount to the computer
- windows will probably respond that the volume/device needs formatted before using it
#7- choose quick format and let it format it as fat32 block size 4096
#8 drop a rom in sd card
#9 reinstal twrp?
#10 intall fresh rom
Lol and I was talking to you like you didn't know what you were doing. Now that you have adb working, put kfu in the same directory and use that to try and boot normal
sent from my Nokia 5110
pbailey212 said:
Lol and I was talking to you like you didn't know what you were doing. Now that you have adb working, put kfu in the same directory and use that to try and boot normal
sent from my Nokia 5110
Click to expand...
Click to collapse
well, I have a desire Z , so the only way to root is with adb.
I started with that and I took all the information from a site to and other. I came with that.
with CWM I can finally format cache, and data ( twrp freeze).
I can now put ROM.zip to the sdm but can't install it (error status 7).
I'll try to install with TWRP, and see.
If its not working, I'll try the hardware method with kindle kit and ubuntu.
next step>> garbage! (or selling it for parts)
I probably miss something :
- I reinstalled TWRP
- Tried to install : jandycane_otter-v1.7.2.zip
Got this message :
symlink : some symlinks failed
E:error in /tmp/sideload/package.zip
(status7)
FAILED
maybe I need the stock rom?
oVeRdOsE. said:
I probably miss something :
- I reinstalled TWRP
- Tried to install : jandycane_otter-v1.7.2.zip
Got this message :
symlink : some symlinks failed
E:error in /tmp/sideload/package.zip
(status7)
FAILED
maybe I need the stock rom?
Click to expand...
Click to collapse
Try downloading and transferring it again. Make sure signiture verification is not checked. Status 7 is usually caused by a bad download or transfer
sent from my Nokia 5110
---------- Post added at 09:01 PM ---------- Previous post was at 08:51 PM ----------
And you are far from a hard brick, as long as you don't screw up your partitions, or use the old version cwm that locked up the mmc chip, these things are virtually unbrickable
sent from my Nokia 5110
Well, I'm using the CWM from the kfu, I believe is the last one.
I understand that I cant flash 3.0 kernel roms.
I tried to install CM7.2 hella fire
no luck: black screen.
and I had to format again because it crashes AGAIN under twrp.
well I'm tired. I'll try again in few days.
thanks
So , I push update.zip (from kfu) to the SD, I installed it with CWM, and same problem. BLACK SCREEN on rom loading.
Then I dont have fff and recovery anymore, so go back in fastboot mode ( factory cable) and reinstall fff and CWM.
Now, trying to reinstall a rom, after a full wipe ( dalvik, factory reset, system wipe, data wipe).
black screen
I want to save my backup to my computer but when I go to mount and the MOTO Shows up but no available files. I have no Idea what going on. I don't know if its a bug or a simple fix.
&
Same with trying to mount MTP in DOTOS (DROID ON TIME) other roms are doing the samething. But someone said go under developers settings and run in USB DEBUGGING I did... It work for a little while but it stops working???
Hello, today after failing to install LineageOS on my Samsung S7 Edge I wanted to wipe the phone to try again. In doing this though, i fricked something up which causes the following error: Failed to mount '/data' (Device or resource busy). When I plug my phone into my pc, it recognizes it but doesn't see a partition. Does anybody know how to fix this?
(Sorry if this is not the right thread for this questions, it's my first time posting something on here.)