hi ive searched for a few hours and tried so many different sequences her eon the forums and for some reason i cant get odin3 1.78 to recognize my captivate... otherwise i would have an awesome Cyanogenmod 7 on it.
i rooted it and installed clockwork from the thread "how to install roms" under the dev threads (the big sticky) then attempted to install a custom rom through clockwork and it failed. now my original rom is messed up. i can load into it but android.phone continuously closes...i cant get odin to see my phone thus i cant reflash the original firmware....
yes i have drivers installed.
yes i have the AIO toolbox.
now for some reason i cannot get Odin to recognize my phone AT ALL (download/recovery/loaded). ive literally tried everything i can think of and to be honest i hope someone here can make me look stupid and help me fix it . ive flashed roms before back in the day with my tilt and cliq. but ive been out of the game for a very long time and lemme tell you im completely lost feeling.
im on windows 7 ultimate x86 fully updated.
ill be glad to donate a little bit for some success on just getting odin to recognize because i have everything. its just that stopping me..
in the meantime my phone is just useless
It might be problems with usb port. Try different ports and/or a totally different computer. Make sure you have drivers according to your computer (32-bit /64). I don't really know why it isn't working.
im sure if he got cwm copied to the phone the USB works...
i have never heard of odin3 1.78
only 1.0 1.3 1.5 1.7 1.81 and 1.82
and some odins only work with some phones..
did this odin ever work for you? or never?
try this one...
no i used my laptop MicroSD then transfered into my root folder of my phone.
ive tried it on 4 computers in my house so far all windows 7 32 bit.
installed the drivers from the AIO and even KIE after seeing no results. ive tried different ports as well and thats the exact odin im using ;(
i also attempted XP compatability mode seeing on another thread windows XP worked for another user in a somewhat situation so im debating whether or not to dual boot XP just to fix my phone lol
so your computer doesnt even see it when you mount usb to copy files? not just odin? did it ever work?
i run windows 7 64 bit no probs.
EDIT... i just re-read your first post....
ODIN ONLY sees the phone in download mode. ONLY
no it doesnt see it at all i think im goin to uninstall drivers and reboot.
now it makes the sound that windows found it but i cant access it or visually see it as a mass storage device even when i specify the settings (disabling debug/enabling mass storage) and under download mode it just doesnt see it at all.
i think im going to get organized and correclty reinstall anything i might think may be an issue
also installing xp on a virtual box on my linux machine to my right
virtual machines and odin dont mix well
with linux use heimdall instead of odin. but the machine still needs to see the device.
and try the drivers from samsung.
USE THE ORIGINAL SAMSUNG CABLE!!!!!!!
some cheap cables, like the one for my bluetooth headset are power only usb cables. the other 2 data pins dont connect end to end!!!!!!!!
ahh maybe thats the problem, i happened to pick up my captivate from someone on criraglist just yesterday and it was just phone and charger. how can i tell if i have an original or not? and yea i tried the drivers from samsung for the galaxy S as well. i was so irritated earlier lol i took a break and came back to it
if windows doesnt beep when pluggin in, then the cable is probably no good...
or try the cable with another phone/ usb hard drive / some data device that takes that input....? or go to radio hack and pick up a new cable. if that doesnt work return it to the hack for your$$ back.. if it does work its worth the 15-20$...
or maybe the phone has a dead usb port... that has happened to some people
okay i found a cord that gives me "usb device not recognized" when im loaded into my phone fully and select mass storage. this is after i installed the samsung driver exe 32 bit for my 32 bit windows 7.
looks like windows 7 attempts to install drivers for "mass storage device" and it fails.
my windows will fail on phone boot a few times because the phone cycles thru different modes.. adb and download mode work on different drivers...
remember to mount to see sd card on pc...
but at least you are getting something now... maybe now is the time to try other pcs..
just throwing out some ideas its getting late.... lol
lol yea thanks man ill reinstall android sdk and java se and see if i can get the adb to be seen and try different drivers for now. thanks for helping me ill donate to you in the end even if we cant get it but man my phone is wacked, all the services are force cosing on it. its so useless right now
ConnectionStatus: FailedEnumeration
Current Config Value: 0x00 -> Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!
===>Device Descriptor<===
*!*ERROR: bLength of 0 incorrect, should be 18
bLength: 0x00
bDescriptorType: 0x00
bcdUSB: 0x0000
bDeviceClass: 0x00
*!*ERROR: Device enumeration failure
thats what im getting in every port on my laptop.
okay man i got it.. i rebooted my pc after uninstalling EVERYTHING (java sdk,eclipse, android sdk, AIO Captivate toolbox, all drivers known to man that dealt with the phone) then logged back in, i downloaded and loaded up UVCView.x86 and tried my phone on every single usb port on my laptop while disconnecting ANY other device thats including my mouse and for some reason my captivate only worked on 1 usb port that was on the side of my laptop (left side) and would only make a (ding dong) sound if my external was detached from my laptop (weird) but wouldnt install drivers still. reinstalled the set of drivers needed and installed AIO captivate toolbox, nothing happened. so i put my phone in download mode and i went into the Compatibility options for the AIO toolbox and set to run as windows xp SP3 + checkboxed run in 256 color, Disable visual themes, Disable desktop composition, Disable scaling on high DPI settings and run as Administrator Then doubled clicked/loaded it up. sure looked like utter crap but my phone was seen by windows and sure enough it had 2 drivers it installed. i went into flash to stock and COM 3 came right up i cried with happiness and i flashed faster than my eyes blink while on a cup of sugar. then i went ahead and tested the com 3 detectability under Odin (i set odin with the EXACT same compatibility mode settings as the AIO - i used odin by itself just for testing) and COM 3 was instantly seen. after flashing to stock and making sure eveyrthing was okay, i went ahead and installed the speedmod kernel and yet again windows 7 x86 recgonized the device and it installed about 7 different drivers! i should be okay from here im not totally noobed feeling now.
Thanks for stickin by my side for the information and support TRusselo ill donate to you for that.
PS : i think im going to research for a week or two on getting what i ned for my linux box in the near future lol
congrats!!!!
yep yep, got cyanogenmod 7 running great, sure is a battery killer though, seriously im afraid of leaving the house with this lmao. my next paycheck be sure to see a donate from dahrat
Related
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
donk232 said:
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Make sure you are using the oem usb cable. I had the same problem, changed cables and it worked
some cheap cables are for charging ... bt headsets and other stuff the data cables dont connect, its just for power.
koreancanuck said:
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
donks232 said:
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
Click to expand...
Click to collapse
You gotta make sure that your usb port is directly connected to your motherboard (usually back of your computer).
same usb port that has always worked. ive tried them all by now anyway
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
donks232 said:
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
Click to expand...
Click to collapse
lolol
Duno what happened but I'm glad it worked out for you
I'm having the same problem with my captivate after flashing REDROM. It won't recognize it if I have USB debugging turned on...
i have a theory... were you on a GB or other i9000 based rom/kernel???
well, im still having a problem getting my computer to recognize the phone, i have to mess with it for a a while to get it to work. i really want to flash anew 2.3.3 rom but without being able to get everything working right im stuck in 2.1
is this a problem with my cord or the connection on my phone? or something weird with my phone after flashing it a lot. its currently back to odin stock, i have been trying to master clear it with no luck
TRusselo said:
i have a theory... were you on a GB or other i9000 based rom/kernel???
Click to expand...
Click to collapse
continiuum miui and cyanogen mod are the only things ive tried to flash
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Guys, this problem while connecting to the PC body is stupidly charging .... Even in the download mode Odin does not see a body that could be? Connect other Cappy-all OK.
donks232 said:
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Click to expand...
Click to collapse
it must be a powered usb hub, on my buddies laptop only 1 out of 4 usb ports saw his phone.
if you can get into download mode you arent bricked.
try installing i9000 drivers, or try another computer.
I came up with this a while back. Could very well be the same issue.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Well since you can't use your phone you should sell it to me
Sent from my GT-I9000 using XDA Premium App
I didn't even install drivers, ubuntu got them for me
Sent from my SGH-I897 using XDA Premium App
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!
I just wanted to relay my experience for anyone who might run across the same problem. There are so many solutions (some good, some bad) that I thought I'd try and help someone else out that was in one of these situations. Keep in mind, the solutions are all here at XDA, I just had to dig and try a few things.
This Captivate was on a Ginger Clone rom (2.2) from about a year ago and I wanted to go to Cyanogenmod. I personally run Cyanogenmod7 (181), and was trying to replicate that.
[Boot-Loop]
I Attempted to clear caches and go straight to Cyanogenmod. This may have been an inexperienced guess that I might be able to do this, but I know a few other folks that manage to do this. I ended up in a boot loop
[Getting to Download mode]
Can be frustrating, but seems to be if you have the usb unplugged, battery out, sim out, put the sim in, battery in, usb in (phone will turn on, so you have to move fairly quickly) and then hit the up and down volume buttons it will go into download mode.
[Go back to Factory]
I tried using the Odin 1 click solution. I believe there are more than 1 versions of this, but it would just get stuck at "Do not turn off target". I decided to try something else. The Java based Hemidal 1.3 aka "SamsungCaptivate-SGHi897-UCKB2-Rooted-One-Click.jar" seems like it is very well written and very easy. It has you update a driver in the mix and it works fantastically.
[Now I'm at Stock 2.2, rooted]
Need to turn on USB debugging, and I was expecting to be able to put
on the rom manager by copying over a file, naming it update.zip but it won't run due to some signing restriction.
[Unable to run any scripts or update.zip]
http://forum.xda-developers.com/showthread.php?t=833423
Basically, you need to turn off signing
[Went off the tracks, bricked the phone]
I decided I would try and apply the Cyanogenmod rom a different way. I went to their wiki and tried to use their Hemidal 1.1.1 update suite and script. I ended up with a brick. I didn't panic, I used the below url and it worked to get me back into download mode. I then used the previously successful Hemidal one click to fix it.
http://www.traemcneely.com/2011/05/...e-possibly-vibrant-kernel-error-black-screen/
I went back to the 3e recovery installer, ran that script, it worked and let me run unsigned code, I installed rom manager via update.zip, and from rom manager I was able to apply Cyanodenmod 7-v181 and then the Google apps and I was happy. Took about 2 1/2 hours to go through all that. Kind-of a pain... happy now.
Rich
Wish I had your kind of luck
I have a Captivate that isn't "bricked" per say but when I plug it into my computer when it's in download mode I only ever get "unknown device". Forcing a driver install causes a code 10 which makes it unusable as well. I have tried 4 different cables and 3 different computers now and tried all of the USB ports on each of the computers I tried at and always get unknown device even with the correct drivers installed. The 3 button trick doesn't work to put it in download mode but using a jig does. I have tried every operating system combo as well heimdall in OSX and Linux says no device connected, and in Windows 7 32 bit and 64 bit I get the unknown device error, also tried Windows XP and get the same error. I have tried 4 different usb cables now as well in each situation with the same unkown device/no device connected error (2 motorola cables, 1 samsung oem cable, and one no-name cable). I was going to gift this to my Dad because he's been missing Android since he gave his HD2 away and went back to a Blackberry.
Hi everybody,
I finally fixed my phone. It took 1 and a half month to fix my Galaxy S PLUS (I9001). I thought I should share my experience. May be it can help others who are facing same issue.
It all started in end of November. I wasn’t happy with Android 2.3.5. I decided to flash a CUSTOM ROM. First I flashed CM9. It was great. So I decided to flash newer than this one. It was CM10.1 and I was happy with it but there was a problem, Wi-Fi wasn’t working! I was new with Custom ROMS. So I didn’t know that flashing a new Kernel can fix it. So I tried CM12.1. and Yeheee! Everything was working and I was happy to run Android 5 on my S PLUS.
Two days later, my brother was playing CUT THE ROPE HD on my phone. He noticed that game is not running smoothly. So he reset the phone from “Backup and Restore” and it was it!
Phone restarted and it was in boot-loop of TWRP. I tried hundred times to make it work but no progress. I checked YouTube and other forums. The only solution mentioned was, put phone in Download Mode and flash CWMR using ODIN. I already installed Samsung Drivers in my Computer. So there was no need to do it again. I put my phone in Download Mode, Started Odin and when I plugged the cable in my phone. It showed “USB DEVICE IS NOT RECOGNIZED”
I changed THREE USB CABLES, TWO PHONE BATTERIES, THREE ODINs, FOUR SAMSUNG DRIVERS and TWO PCs to make it work but nothing!
I Googled the issue, tried many other things like cleaning window temp files, cleaning drivers, removing battery when connecting to ODIN and constantly pressing volume keys when connecting to ODIN in Download Mode. Nothing worked. Some said it is issue of cable, some said it is phone connector interface problem. clean it with something. I tried that too!
After spending ONE MONTH doing this and that, I give up and went to a phone repairing shop. He said, it is not connecting. I don’t know how to make it work again.
No more hope and phone was in my drawer. After fifteen days I tried all that again but no. but two days ago. I was given an assignment from my University. That was a C++ assignment. My DEVC++ software wasn’t working properly on my WIN 10 EDU (64BIT). I found that, it only works on Win 7 and earlier. So I installed a fresh WIN7 ULTIMATE 32BIT on my second Hard Drive. i installed DevC++ and it worked smoothly. I finished my assignment and my mind clicked that I can try my phone on this OS!
I installed:
MOBOGENIE 3.3.7_10002 (it was for my other phone, not for S PLUS of course!)
Ccleaner506 (Only Cleaned TEMP, registry Untouched)
Samsung Drivers v1.5.53.0
Pray To Allah
Opened ODIN_Multi_Downloader_v4.43
Put my phone in Download Mode and Connected the Cable and IT CONNECTED AND DETECTED BY ODIN SUCCESSFULLY!!!!
Everything was same as before: ODIN, Samsung Drivers, Mobogenie, Phone Battery and Ccleaner but two things were different.
OS: WIN 7 ULT 32BIT (NOW), WIN 10 EDU 64BIT (BEFORE)
USB CABLE:NOKIA ORIGINAL CABLE (NOW)SAMSUNG ORIGINAL CABLE (BEFORE)
The steps I did was, after connecting the phone, I selected “AriesVE.ops” in Select OPS option of ODIN then I checked on “ONE PACKEGE” in ODIN and selected “recovery-clockwork-6.0.1.0-ariesve.tar.md5” by clicking One Package button in ODIN. Then I clicked on START
After some second my phone was ALIVE AGAIN! All files were as they were and it was running CM12.1
Now it is working like before and I am happy to have it back. The reason of describing every single step is that I don’t know what exactly is the reason to make it work! The 32bit WIN7 OS or NOKIA USB CABLE! Or both. So, if you are facing the same problem. Try like I did. I hope it will help you!
Drivers: http://www.mediafire.com/download/wsb5kfqapdsv3w7/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
Unbrick tools: http://www.mediafire.com/download/6ymcjpl86fl82j7/Unbrick.rar
So...
So... you say that I need to go back to win7 for the problem to be solved ?
McAlexica said:
So... you say that I need to go back to win7 for the problem to be solved ?
Click to expand...
Click to collapse
That's what i said.. But i think if you have "UP TO DATE" Win 10. Will work too.
imDCStar said:
That's what i said.. But i think if you have "UP TO DATE" Win 10. Will work too.
Click to expand...
Click to collapse
i have win 10 bit will it worrk ?
Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Anyone??
$pooLz said:
Anyone??
Click to expand...
Click to collapse
1)First of all have you enabled usb debugging and oem unlocking options enabled from developers options?
2)Install latest usb drivers for your model no on pc, use original usb cable to connect your phone
3) Try different usb hub-ports on your pc, it is recommended to use main-usb port to connect device properly which is mostly located backside of cpu cabinet
4)Does odin recognises ur device? If yes then you can flash twrp and cf autoroot both ( Sometimes Kies or smartswtich like programmes enforces device not be reognised, so uninstall them before trying to connect and flashing thorugh odin)
5)Try to update device drivers manually from Pc's administration
6) Try to connect your phone on another pc running windows and see if it recognises your device or not
I've tried all of that, i have a 09 Macbook Pro hand me down running Yosemite with Windows 8.1 Pro n just put Ubuntu on her today through Parallels. None of which recognise the phone being there.
I've plugged it into 2 HP PC's and both just keep telling "device descriptor failed". They're both kinda old too.
Unless someone has a specific driver they've made or found or could make me?? Clearly I'm a noob.
Closest I've found is https://github.com/452/USBHIDTerminal/wiki/How-to-enable-USB-host-API-support but still need root or system mounted as rw.
Any other ideas? Any ADB codes anyone could help me with ?