Hello, I have a Samsung Galaxy S2 Skyrocket and the other day I tried installing the CF3D Drivers for my phone. But apparently, Chainfire doesn't really work for JB and I'm running CM10. I installed it and the phone rebooted but now I can't get passed the Samsung logo. I downloaded a fresh CM10 and booted into CWM recovery and hooked my USB to my computer. Problem is, the computer won't show my phone. it downloaded the drivers but won't connect. Please help. Thanks in advance.
DoctorXdownz said:
Hello, I have a Samsung Galaxy S2 Skyrocket and the other day I tried installing the CF3D Drivers for my phone. But apparently, Chainfire doesn't really work for JB and I'm running CM10. I installed it and the phone rebooted but now I can't get passed the Samsung logo. I downloaded a fresh CM10 and booted into CWM recovery and hooked my USB to my computer. Problem is, the computer won't show my phone. it downloaded the drivers but won't connect. Please help. Thanks in advance.
Click to expand...
Click to collapse
Boot into fastboot then recovery to wipe data and flash the original CM10 to get it booting then go from there.
Related
Hi guys,
First of all sorry for bad english.
I turned my dives of because it was stuck when deinstalling an app.
Now, when i boot it, the boot animation comes, then the samsung logo,then the boot animation and so on.
My device is rooted. I had a backup with cwm but when i restore it it says:
Checking MD5 sums...
Restoring system...
Restoring data...
Error mounting /data!
Skipping format...
Can't mount /data!
But this backup worked before...
I tried to flash a new firmware with odin but odin won't recognize my device in download/odin mode.
What can i do? I searched for 5 hours now...
Thx for answers
Odin must recognize your device if you are in download mode.Just wait a moment and he will.If not try to change the usb port.
When you see the com in yellow tick repartition select you pda and flash
Even i had the same problem there r 3 things u can change
1:change your connecting cable
2:reinstall samsung drivers and then try again
3:change ports
Even after u flash stock firmware it does bootloop then do a factory reset from stock recovery
This should work
dylan.james1947 said:
Even i had the same problem there r 3 things u can change
1:change your connecting cable
2:reinstall samsung drivers and then try again
3:change ports
Even after u flash stock firmware it does bootloop then do a factory reset from stock recovery
This should work
Click to expand...
Click to collapse
Thanks, I will try it
Hmm...
I installed samsung kies, changed usb ports and reinstalled the drivers but odin
still won't recognize my phone...
flashonium said:
Thanks, I will try it
Hmm...
I installed samsung kies, changed usb ports and reinstalled the drivers but odin
still won't recognize my phone...
Click to expand...
Click to collapse
Odin recognize devices in download mode. Ur devive was in? If not.
Remove battery, sd, plug in pc.
Hold power+volumeUp+volumeDown for 6sec.
Inserts batery.
Run odin as adm.
Sent from my GT-S5830i using xda app-developers app
did you try to do a factory to do a factory reset from stock recovery
How it worked
Thank for your help guys, i figured that maybe doing this in a virtual machine was not a good idea...
But thats the recipe:
1. Try to AWAYS use the drivers that automatically install when you plug in your phone, because the samsung drivers I downloaded didn't work
for me.
2. NEVER install new drivers on top of the old ones; always deinstall the old ones first.
3. Try again and again and again! Don't stop after the first five times trying.
hai,i have a serious problem and i need your help.....
the problem is I installed galaxy y (gts5360)'s stock rom on galaxy ace (gts5830i).now i couldnt enter into recovery mode nor download mode it stands in small screen showing galaxy y's logo
krishna prasad said:
hai,i have a serious problem and i need your help.....
the problem is I installed galaxy y (gts5360)'s stock rom on galaxy ace (gts5830i).now i couldnt enter into recovery mode nor download mode it stands in small screen showing galaxy y's logo
Click to expand...
Click to collapse
you guy deserve an oscar for waking up a dead thread (the thread is from november last year...) and we have THIS SECTION FOR QUESTIONS LIKE YOURS ... use it... and stop waking up such corpse..
sorry bro...
I'm new to this kind of stuff.thanks for the link brother.
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
A.R.Cante said:
Hello,
my device (i9300) as mentioned above got stuck in a boot loop.
First I did was I installed the latest pac-man ROM from here. After successful testing I decided to flash the latest OmniRom 4.4 from here.
Now here comes the dilemma with: My Failure was that I had a old Recovery (CWM-based Recovery v5.5.0.4) and I didn't see the point where it says that I have to update it first.
My USB Connection to my PC was already broken before I started to flash any of the ROMs. So I can't connect to the PC to flash via Odin. It fails on the driver installtion. (I copied everything in my cloud and downloaded it to the internal sd)
The Device Manager shows alwas a ! in a yellow triangle near the "Samsung Mobile USB CDC Composite Device" (Download Mode) with a errer code 10: Device cannot start. I did millions of solutions but nothing worked against this issue ...
Currently my device starts where the Samsung galaxy s3 logo pops up, get stuck by that with a red 1 on the upper left corner and boots into the "old" recovery.
This is my Problem. Please help me to fix this (and the USB bug).
Thank you very much
Kind regards,
A.R.Cante
Click to expand...
Click to collapse
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
abidifethi said:
To fix the USB bug, you must uninstall that driver and download the driver ( try to install kies for example )
To fix the bootloop try to do a full wipe in recovery mode
Click to expand...
Click to collapse
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
A.R.Cante said:
None of your advices worked. I did unistall all drivers and also Kies. Reinstalled and it doesn't worked. So I uninstalled it again and installed only the drivers but this didn't worked too.
Everytime I uninstall the drivers and connect the device to the PC it is trying to Install the Drivers over Windows Update and Kies isn't reacting at all.
Now since I wiped data/factory reset, cache partition, dalvik cache and formated /system and /preload my device won't start automatically in the recovery anymore. It get stuck on the Samsung Galaxy SIII Logo with the red 1 in the upper left corner. To Access to the Recovery I have to take the battery out and and insert it again and press volume up + home + power.
What can I do now?
Thanks in advance
Click to expand...
Click to collapse
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
abidifethi said:
Try to download any custom ROM if you don't done yet and put it in your external sd card ( use an other phone or card reader ) and now try to enter in recovery mode and install it and let us know the result
Click to expand...
Click to collapse
I tried this now on my Desktop Computer and it worked fine. I didn't need to install drivers manually. It installed it by itself and therefore i was able to use odin!
I flashed the new recovery and put the omnirom and pa-gapps on my sd card (I also tried this on my notebook but my card reader is maybe broken)
so i installed teamwin recvovery over pc, put rom and gapps on my sd card and flashed them over recovery.
Now all works fine.
Thank you for your help.
But what I don't understand is my Win 7 OS (32 bit) is recently set up on my VM everything was fresh but it didnt recognized my device... Google says a lot of people are having this issues. I've tried everything whenever I found allegedly a solution for this problem. None of them worked. I simply switched the computer and everything is fine. This is ridiculous. One year ago, when I had running windows as main OS, there were no problems at all. If the problem was caused by a virtual machine I think that not many people would complain about this issue.
Kind regards
Why would old Win 7 recognize your device unless you install drivers .
JJEgan said:
Why would old Win 7 recognize your device unless you install drivers .
Click to expand...
Click to collapse
I don't really understand your comment. The Problem of this USB error has no root. When your Windows System says error code 10: device cannot start then you have a big problem because you don't know why and how to fix this. Try and Google this. You will find thousands of people complaining the same error. Everyone has other solutions for that. Some edit their registry, others simply do a soft-reset and try another USB-Port.
Samsung support can't help you at all because they don't know why this is happening. And the solving of this problem is really random. i tried for hours to solve this with no success (except switching to another computer).
Windows says on my laptop the device cannot start but it is perfectly connecting to my other computer. How can this happen? I don't know. Maybe the error code 10 is not that specific and there is something other wrong than my device.
Ugh, totally my fault for not thinking this through.
Had downloaded the Paranoid Android ROM, a newer version from what I had, as I had installed it incorrectly.
So I thought, no worries, I'll just reinstall the ROM.
Booted into recovery mode, did a full wipe and then tried to install the new rom, only I couldn't find it anywhere...
Thinking I'll restart the phone and figure it out from there, but of course it doesn't go past the loading screen.
I can boot into download mode, but on my PC if I boot Odin, it doesn't recognize the phone and I get no yellow colour.
Pretty sure my internal SD card still has one or two custom roms on it, but without booting into recovery mode, I can't do much.
Odin doesn't recognize my phone. I installed the drivers from the samsung website, but it is not reading the phone in download mode.
Now I am unsure if there's another driver I need to install, i.e. a USB driver, seeing as this is a brand new pc, but other than that, I'm stuck.
Any ideas are greatly appreciated!
Download galaxy s3 toolkit from original android development section,install it and agree when asked to install drivers , reboot Pc and cross fingers for your Pc to detect your phone in download mode then just flash stock ROM
Sent from the grey stuff inside my skull
If you have a custom recovery (CWM or TWRP), you can use an OTG cable to connect a USB stick to your phone (which will be discovered by CWM, haven't tried TWRP) and install a new ROM with gapps from it...
Of course if you want to install stock, you have to stick with Odin.
Hope it helps
hey guys...
My phone is in trouble and I tried to solve it but couldn't even after a day long struggle..So, I decided to post this thread!
I just installed the cwm recovery v6.0.4.5 through Odin..
And then I tried to install a custom ROM after wiping the system data,cache and dalvik cache...
But unfortunately when I did a system reboot it started booting into the cwm recovery...
And to my surprise Odin is no longer detecting the phone in the downloading mode...
When I checked the device manager I saw "Samsung Mobile USB CDC composite device" under the bus controllers and its drivers are not installed properly... So, I tried updating its drivers but I only get "This device cannot start .(Code 10)" error.
I installed kies to check if I have proper drivers installed but still Odin isn't detecting my phone.
So someone please step up and help me in recovering my phone..
Thanks,in advance!
My samsung galaxy grand quattro was bricked then i am upload the stock rom and it was successfully uploaded but one problem is there.. My phone is not start on battery life but it shows 100% if i connect the charger then my phone is started but after 10 to 15 seconds it is turning off.... How can i solve this problem...? Please help me.....
bbsankarreddy said:
hey guys...
My phone is in trouble and I tried to solve it but couldn't even after a day long struggle..So, I decided to post this thread!
I just installed the cwm recovery v6.0.4.5 through Odin..
And then I tried to install a custom ROM after wiping the system data,cache and dalvik cache...
But unfortunately when I did a system reboot it started booting into the cwm recovery...
And to my surprise Odin is no longer detecting the phone in the downloading mode...
When I checked the device manager I saw "Samsung Mobile USB CDC composite device" under the bus controllers and its drivers are not installed properly... So, I tried updating its drivers but I only get "This device cannot start .(Code 10)" error.
I installed kies to check if I have proper drivers installed but still Odin isn't detecting my phone.
So someone please step up and help me in recovering my phone..
Thanks,in advance!
Click to expand...
Click to collapse
Update drivers on your pc Odin will detect then after that, reflag stock os for battery either use battery cal liberator or most probably like my case Battery is dead
bbsankarreddy said:
hey guys...
My phone is in trouble and I tried to solve it but couldn't even after a day long struggle..So, I decided to post this thread!
I just installed the cwm recovery v6.0.4.5 through Odin..
And then I tried to install a custom ROM after wiping the system data,cache and dalvik cache...
But unfortunately when I did a system reboot it started booting into the cwm recovery...
And to my surprise Odin is no longer detecting the phone in the downloading mode...
When I checked the device manager I saw "Samsung Mobile USB CDC composite device" under the bus controllers and its drivers are not installed properly... So, I tried updating its drivers but I only get "This device cannot start .(Code 10)" error.
I installed kies to check if I have proper drivers installed but still Odin isn't detecting my phone.
So someone please step up and help me in recovering my phone..
Thanks,in advance!
Click to expand...
Click to collapse
your phone is not soft bricked....its just in a cwm loop.....
https://forum.xda-developers.com/showthread.php?t=2716953&page=4#post70376808
just check this thread.
it helped me
youre welcome:fingers-crossed:
Facing the same problem!
I had a J6, just rooted months ago. Everything was fine, I got it rooted successfully, and today I just updated Magisk this afternoon and restart it. And it got bootloop.
I don't know what to do so I wipe data and cache partition. It didn't help
My phone can't connect to my laptop, Odin didn't detect my phone, Installing Samsung USB Drivers didn't help
My phone could only go to recovery mode and go to Downloading mode
Can anyone help me plz?
Try to reflash the stock rom maybe
Hello,
is your phone a SM-J600FN/DS? And how do you root?
Thanks
Efcegames said:
Try to reflash the stock rom maybe
Click to expand...
Click to collapse
To reflash the stock ROM we need Odin to detect my phone to flash. It didn't detect anything (despite already have Samsung USB Driver). I was stupid not installing TWRP before rooting my phone. What should I do now?
[SOLVED]: IT WAS THE CABLE PROBLEM​
It turns out that the problem all along was the cable. I had 2 Micro USB cables and none of them connect the phone to computer, only in charge mode
So I borrowed my mom's Xiaomi cable and it worked perfectly. Just connect to computer, open Odin and flash the stock ROM back.
After this incident I don't feel like I want to root phone. It was good but it seems to me that Magisk has a lot of problems right now... Or probably just me