So I have an interesting little problem.
A few days ago after flashing Infinity ROM i noticed that when I plug my phone into my computer by USB, instead of reading the device correctly and matching/installing drivers I get an error message that says "USB device has malfunctioned" and is not recognized. This is a problem because I can no longer use ODIN to flash anything, it simply does not recognize my phone.
I have attempted to troubleshoot the problem myself by replacing the usb cable, uninstalling / reinstalling the drivers, resetting data and caches on my phone, using different computers etc.. So far nothing as helped. I would go so far as to guess that the USB controller in my phone is malfunctioning, but I can still charge my phone.
So I called verizon because my phone is still under warranty and they are going to ship me a replacement, so now my problem becomes how do I get back to stock or anything resembling stock so I don't void my warranty when I send this one back in.. remember I cannot use ODIN, and I am currently on the ext4 file system. Someone even suggested purposely bricking my phone, although I'm not sure how i would even pull that off. Thoughts? I'm still open to troubleshooting if anybody has any ideas.
Any ideas or help would be GREATLY appreciated!! Thanks!
In Summary:
Summary for those who think the first post was tfltr..
--Computer won't recognize phone through USB; device not recognized
--Phone will still charge but only with certain cords??
--Have troubleshooted through XDA boardsn
--Waiting on a replacement from Verizon
--Need to get phone to stock or close to stock for when I send it back in so i do not void warranty
--Is there a way to zip flash stock, even though I am on ext4 ow??
--If not, should I just brick my phone and then send it in?
Thanks bros!
If you get into download mode, your phone should be fine. If you get into download mode, go ahead and make sure everything else works. Use USB ports on the back of the computer, and try different ports. Try different cables. Try reinstalling drivers.
Sent from my SCH-I510 using XDA App
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Bleh..
xdadevnube said:
Also, try cleaning out phone USB port and inspect for damage. Keep in mind that many cables don't work. I have several crummy cables that I can't get data through on the Charge
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
Thanks for the response, but I have tried several official verizon USB cables to no avail. I just received the replacement charge which works on the same computer port and with the same cable that was definitely not working with the old phone. I will try compressed air when I get home later.
Does anybody know what would happen if I attempted to flash a stock recovery image with RFS as a filesystem through CWM, on the phone which is currently running an EXT4 filesystem? Would I brick it?
I'm not sure, but that seems like a poor way to going back to stock.
Just use the stock ODIN images. They will take care of all your needs. I've used them on multiple occassions.
Format your SD card first so that Verizon doesn't know you were rooted, etc. I usually do this through USB mass storage when its connected to the computer, but since you probably can't get it through the computer, either pop in your SD card into your other phone and do it through mass storage or simply use a memory card reader. I format with FAT32 /w 32KB block size.
Then just ODIN the stock recovery image and there you go.
*EDIT* der, I just realized you can't get the USB to work. This is a question for somebody who knows more than I do!
I'm not sure if this is possible with that rom(doubtful) but try disabling lagfix by creating a file on your sdcard inside the Voodoo folder, named "disable-lagfix"(may not even be a folder for this). Reboot. If you hear the voice again maybe it worked.
Does Imo kernal support reverting? If the above doesn't work(or try this first) flash the Imo 4.0 Kernel and try reverting. NOT sure if that kernel is compatible. Try all this at your own risk.
then cwm flash this:
http://forum.xda-developers.com/showthread.php?t=1108115&highlight=cwm
Related
First off, I have 3 Charges in the house. One is stock , one is on GBE 1.8 still and mine is GBE1.9RC2.3 with EXT4 on /system, /data, /dbdata and /cache. So, I have some idea what I'm doing.
This issue is driving me crazy. My daughter's Charge (stock with voodoo) will not connect properly so she can sync with Doubletwist. If I plug my phone it, it is recognized as a USB device and Doubletwist see it without a problem so it shouldn't be the drivers on the computer. When I plug hers in, the phone asks if I want to turn on USB mode (like mine does), but the computer says device drivers failed and it shows up only as a CD drive. Doubletwist will not work with that.
I've gone through her phone several times looking for the magic switch that will make it work, but I can't find anything. I've tried 3 different computers - all of which recognize my phone fine, but not hers...
Any help would be greatly appreciated. I'm just about to the point of flashing her phone with GBE1.9RC2.3 and telling her to get over not having TW (she's just used to it) and hoping that the new rom will work.
Set the USB settings to "Ask on Connection", it's a known problem with Gummy. Also, if that doesn't work you will need to flash the SD card fix(if you haven't already)
blarrick said:
Set the USB settings to "Ask on Connection", it's a known problem with Gummy. Also, if that doesn't work you will need to flash the SD card fix(if you haven't already)
Click to expand...
Click to collapse
I have tried ask on connection. The phone does ask but doesn't end up working right. This phone is stock. Not Gummy. I think I voodoo'd it but need to verify. Regardless of the kernel and recovery its running Verizons latest rom software - EE4?
Could the SD Fix work even on stock?
Sent from my SCH-I510 using XDA Premium App
Try the trick that worked for the Fascinate. Plug her phone into the usb with usb debugging enabled then reboot the phone while it is still connected.
Also try re-installing the Samsung drivers on the computer.
tdenton1138 said:
Could the SD Fix work even on stock?
Click to expand...
Click to collapse
I may be wrong on this, but my understanding was the sd card showing up as a CD drive on EE4 roms stemmed from flashing a custom kernel, which seems applicable in this case if the phone is stock with voodoo. When this happened to me I already had the fix file on the sd card, and flashing the fix ... well, fixed it.
I too was having similar issues with this on my charge running rc2.3, lo and behold, all I needed to do was reboot my pc, then reconnect my charge to the usb cable... Its been so long since I have actually used my desktop properly. Lol
Sent from my Transformer TF101 using XDA Premium App
Hi.
I don't know much about details about root/room/recovery, but know some about
ODIN, CWM and other ROM to use.
I've been using Humble 5.0 for a while and my phone got unstable recently, so I ODIN the same Humble rom again, but that is how the problem started.
The main problem is, I can't wipe userdata or cache at all.
CWM says it wiped, but I always get Force close, so many that I can't even use the phone normally.
I tried to go back to stock ROM or any other, but all failed.
Stock ROM with stock recovery says, E:Can't mount /dev/block/mmcblk0p1 (Invalid argument). and most of the time, Bootloops.
Humble is the only option I can go into, and actually use the phone, but it has all the apps and data from the past, even though I wipe data/cache thousand times.
I even erased all SD data, formatted in FAT32, and nothing works.
Finalizing my status,
Can't mount...error with Stock ROM.
Bootloop with other ROM.
Constant Force Close with Humble 5.0 (Can't wipe data/cache).
Please help.
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
I am no pro myself.. But I am running GummyCharge Froyo 2.0 which comes with Imoseyon's Kernel and its rock stable even overclocked to 1,200 mhz for me.. You may want to try getting a copy of that as well as flashing with your SIM Card out and Battery in after booting into recovery.. Let me know if this helps at all!
jiehooni said:
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
Click to expand...
Click to collapse
I had a similar problem but dont remember what I did to fix lol like that helps you. Did you format your sd card on a computer or with your phone? If not try using an adapter and format on computer. Going back to stock has always solved my problems. There is a new cwm that came out. Just throwing stuff out there. Have you tried re downloading images of the stock ee4 and pit? It is loading so shouldnt be a problem , hmm. Maybe someone with more knowledge will pop in.
I tried GummyCharge 2.0.zip from SD but it didn't help.
I tried CWM 5.0, with many ROMs to wipe cache/data, no use.
I formatted my SD on PC, and from phone, same result.
What I don't understand is, even after I flashed Humble 5.0 ROM which I used right before, and only ROM it works now, it shows all apps I had even after many times of Wipe Data/cache/dalvic.
Even funnier, I delete some apps causing Force Close, and I reboot my phone, it always goes back to where I start. Same Home, the app is still there.
It is just weird.
Im getting FC now all of a sudden. It's you fault damn it lol. Said I was gonna reload anyhow. Just didnt want to do it twice in one night. Oh it is past 12pm so I guess it is another day.
It's been now 3 days, and I found this thread hopelessly.
Same problem I think.
http://forum.xda-developers.com/showthread.php?t=1191650&page=2
I hope somebody can help me fix it.
Now I can't even flash Humble, can't even get through recovery(stock or CWM).
I can't do anything now.
I will Odin back to stock and take it to the verizon tomorrow.
Thank you all of you for the help.
Tried a different usb cable, how did you flash the new cwm? So everytime it says pass through ODIN? Are you checking the right selections through ODIN and using PDA? Man just trying to think of everything and thats about it. Get another phone lol. Superuser and busybox?
I tried different USB cable, PC, installed Samsung driver again.
I took the phone to Verizon today, and they can't hard reset it either at that place.
I dropped the phone 3 month ago and it has a little dent, so that they refuse to repair it under warranty. I am sending it to MobileTechVideo tomorrow.
Thank you.
I'm having the same issues. I was on Humble 5.0 and had been using it without a problem for about 2 weeks and yesterday I noticed my phone reboot on it's own. After the reboot it was stuck in the boot loop. I've also tried reflashing Humble 5.0, tried the instructions on the fix your phone thread, tried flashing to stock and also tried the all in one Gingerbread 2.3.6 W/Root/CWR/IMO Kernel 4.0 to see if CWM would help any.
All successfully pass according to Odin, but they all still boot loop and all give error messages in their recovery modes if I try to do anything involving /cache or /data stating that they fail to mount.
Any thoughts would be greatly appreciated.
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
JoeVsFox said:
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
Click to expand...
Click to collapse
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
ODIN Flash Stock
blueis300 said:
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Click to expand...
Click to collapse
If you have the charge pit file and EE4 you should be able to wipe everything on your phone. If I am correct, this bypasses all permissions and partitions and basically supercedes any roms or data you have. This should work. try another cable on a different usb port or another computer. I have hard brocked my phone numerous times and this was the only workable method. (if you want you can do a little solder job and have phone by fixed with the unbrickable mod here
I already sent my phone to the repair shop.
Btw, it is the normal case you described, but I tried different PCs, drivers, cables, USB slot, nothing works.
Thank you anyway.
blueis300 said:
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
Click to expand...
Click to collapse
Tried it with 2 different computers, different cables, different ports. Ask on connection is on. The SD card works fine when I put in in an adapter. The phone just doesn't data connect via usb. ODIN can't find it. Nothing. Pretty sure this is a hardware issue...
My phone just got back from the repair shop and they say they can't fix it. They think NAND got corrupted. Now I am really stuck...Man...
So my coworker hosed his Captivate this morning. Long story short, I can get into download mode, but none of the OneClick stock files will recognize that the phone is plugged in, but it is recognized by ODIN sees it and I can flash through it. I found an older samsung-firmware file with a .PIT and .TAR for the phone, which I flashed, and right after it will pop up AT&T boot screen then black. If i pull the battery it will pop up like the battery is charging (the little circle thing) and then go black.
Any ideas or things to try to get it back to usable state?
Thanks!
So I made some progress yesterday. I was able to get a Heimdall to recognize the phone (Link here: I897UCKK4_Stock_Wipe) and did everything that it needed to do without any issues. The phone will then reboot and load a "CWM-esque" screen (bootloader?) and say "can't mount dev block mmcblk0p1"
If I try to boot the phone normally, it will load the AT&T screen, Galaxy S logo will do its thing, go grey and then back to the AT&T splash. I even tried using a Heimdall back to Froyo then using a Gingerbread with BL and still a no go. I can flash kernels, but I cannot mount as USB or anything with the SD card.
Any and all help is greatly appreciated!
I believe you have a corrupt internal memory card. Odin one click should resolve it, but I know you're having issues getting it to connect. Have you tried a different computer, usb port, usb cable, etc?
So I've been able to get the one-clicks to do its thing and still a no go... brought it to an AT&T store and they referred me to the warranty replacement location (King of Prussia PA). After calling to make an appointment, they checked the info and I'm now 5 days out of warranty... What luck...
So here's a doozy. First, some background. During a routine update to a new version of my favorite rom, IMEI data got borked. My backup was apparently incomplete, so couldn't restore it that way. My phone has been unable to connect a computer via usb in more than a charging capacity for a few months, so any pc-based tools like ODIN or QPST were out of the question. Only hope was to go back to a rooted stock rom and try the dialer solution. So I try flashing root66 via Mobile ODIN. Note that this overwrites CWM to the stock recovery, in addition to overwriting pretty much everything else. For whatever reason, the OS is now borked. Can't get past the Samsung GSIII screen. I can still reach Download Mode and Recovery, though. However, as mentioned before, ODIN is not an option because no computer can see my device over USB. The recovery is now the stock recovery, so the only thing it will recognize is a signed update.zip from Verizon herself. Anything else I try to flash from external SD gets the whole signature verification error.
To sum:
The Problem
Need to get to a working OS. This likely needs to be stock.
Complications and Constraints
ODIN is not an option, nor is any other pc-based or usb-based tool.
I'm stuck with the stock recovery, which requires signature verification.
Theorized Solutions
I could either somehow flash CWM via signed zip file from stock recovery (don't know if this exists, if it does I haven't been able to find it), or,
I could flash a signed OTA zip, like what would arrive on the phone from Verizon. I've been having a lot of trouble finding one of these, since everyone and their grandmother seems to want to use ODIN to flash leaked OTAs. I'm thinking that of the OTAs, the initial upgrade to JB is probably my best bet, since it likely replaced more of the system than the other OTAs. I'm more than open to suggestions, though.
Thoughts?
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Boot into recovery and do a factory reset. That typically is recommended if you're stuck on the boot logo after an Odin flash.
How did you lose usb to pc access? When you install the Samsung drivers from their website, what does your computer do? Which usb cable have you been using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Factory reset was the first thing I tried. No go. I've tried every option available in the stock recovery, with no success. Gotta say, not really fond of this whole stock recovery thing. Fairly useless.
I haven't had usb to pc access ever since I played Ingress in a snowstorm a few months ago and some moisture got into the charging port, and I didn't properly dry it out. There's a little bit of corrosion in there now. It still charges fine most of the time (I'm sure not as well or as consistently as when it was new), but it can't connect to the computer in more than a charging capacity. I've tested a large variety of usb cables, most of which worked before the snowstorm, and none give me pc access. Some give me pc access for a few seconds, but none give a connection that's stable enough to run ODIN or QPST or the like.
I should note that I have a microSD to SD adapter, so I can still move files to and from my external SD card. Anything available on the internet can make its way onto my SD card so long as it's 7.96 Gb or smaller.
EDIT: I should clarify that I *did* have usb to pc access before the snowstorm. Samsung drivers worked fine, etc, the typical file transfers over usb worked fine, adb worked fine, etc.
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
I had the same problem a few months ago when I used mobile odin. I was lucky enough to be able to use the regular ODIN to start from the beginning flash stock everything. You need to get regular ODIN to work. Take the phone to a repair place have them clean the rust and re-soter the connections. That is what I would try. Sorry I wasn't of any more help.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
adiv.paradise said:
I took a closer look at the microUSB port on the phone. On closer inspection, with a bright light, I really don't see any corrosion, and I checked the water damage indicators, and none have been tripped. Which makes me question whether or not the port starting to fail really was related to the snowstorm, or if that was a coincidence. I've decided to just go ahead and get it replaced under warranty--even if I could rescue the system, that faulty port is actually a really huge problem, more so than I had realized. Not being able to use ODIN to un-brick is bad, I've decided. Now the big question is going to be, will they be able to tell the phone's been messed with, and if so, how can I cover my tracks with a bootlooped phone, stock recovery, and no possibility of Odin or Heimdall? I'm thinking it should mostly be okay--in Download mode, everything checks out as normal, except for system status, which says custom. I'm betting that if it came down to it, I could probably argue that it could fail to recognize a borked but otherwise stock system, and therefore call a normal system custom.
If not, though, then I better get started on cracking Samsung's update.zip encryption so I can sign my own injection package with their signature...
Click to expand...
Click to collapse
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
prdog1 said:
If using Windows the USB will act like there are no drivers at times. The fix I found was to connect to PC in charge mode. Then go to download mode while connected to PC. It will reactivate drivers from phone side. Have done this many times on Win8. Worth a shot.
Click to expand...
Click to collapse
Some phone is bricked that not recognize the phone on device manager and won't charge too.
tomy1986.nt said:
Some phone is bricked that not recognize the phone on device manager and won't charge too.
Click to expand...
Click to collapse
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
prdog1 said:
His charges.That is not a brick. A brick is black screen with no access to recovery, download mode. A bricked phone will be seen by USB but just as a device and not as an S3. If you have the screens that is a soft brick and need to find what the problem is. Could just be a bad USB port on phone or PC or an operator problem. If have any screen the device is not bricked. Ok I see now. You are looking for JTag work and are in Texas. I would still say send to Josh at Mobile Tech in College Station, Tx cause we know he knows what he is doing. You don't have video of unbricking S3? S2 is old and obsolete and no where near the same device. Also must have RIFF for the device. I can make it pass warranty for free over PM.
Click to expand...
Click to collapse
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
tomy1986.nt said:
You do not know how the bricked phone look like, some bricked like no power, some like download mode but can not flash firmware, some phone is bricked like wont recognize on device manager.
Please check my video for knowing what kind of device I have already done, and see my feed back on ebay.
Click to expand...
Click to collapse
If a device can boot to recovery or download or if it charges or is detected when connected to PC then it isn't truly bricked, it's only softbricked. A truly bricked device will not charge, has no LED when connected to PC, can't be detected by PC in any kind of way, will not boot to recovery or download mode and will not power on in any way. This is actually called a "hardbrick".
Sent from my SM-S903VL using Tapatalk
Have a Samsung Galaxy S4 i9095 updates to kitikat 4.4 but recently while playing games it keeps turning off completly even thou batt full. so tried a cache wipe format wipe and now it's locks in a reboot loop gets past the logo turns off and restarts. tried various roms on the Samsung page but keep getting 'E:/error verification not verified. or bootloader failed. tried phoenix arrow both do same. anybody got any suggestions, only thing i can think off is run Odin and re-install the stock ROM. was hoping to get it rooted so i can move my app to the secondary HDD. to save on space on the root drive. but non of the CW mods will open on my phone. so How do i resolve this.. thanks
MrNiceAngel said:
keep getting 'E:/error verification not verified.
Click to expand...
Click to collapse
Used to get a similar error with one particular SD card, worked flawlessly with a different one (both were FAT32 and the same size), so maybe try another card if you've got one.
sndsnd said:
Used to get a similar error with one particular SD card, worked flawlessly with a different one (both were FAT32 and the same size), so maybe try another card if you've got one.
Click to expand...
Click to collapse
will try i have a smaller HDD mini SD can use it, however the PC picks up the SD card no problem. any ideas on my second issue can't re flash stock ROM using ODIN cause usb port not seeing the phone (using cable came in box) but every time i plug it in it goes on a loop reconnect cycle.. could be something simple like a virus manged to get thru avast security and frak up phones OS so only resolve is flash it put stock back on. Is there any software out there that can fix the USB connection issue.
Could try just using a different cable. That is a known problem with odin. I have a one-foot-long micro usb cable that came with an old bluetooth headset. It is now the only one I use for Odin since my oem cable that came with my note 2 does nothing except make odin hang on "SetupConnection..."
tried that
kittie42 said:
Could try just using a different cable. That is a known problem with odin. I have a one-foot-long micro usb cable that came with an old bluetooth headset. It is now the only one I use for Odin since my oem cable that came with my note 2 does nothing except make odin hang on "SetupConnection..."
Click to expand...
Click to collapse
Ended up formatting PC and creating a whole new account on windows 8.1 64 bit which fixed the cable issue, strange i know. but now phone won't start up. tried the stock ROM non root pit file which manged to get phone to stay on for 22 hrs. now its just won't stay on at all. gets past logo and turns off. any last attempt u guys can come up with. Is there any zip files i can try that won't give me any E/: errors so the file can unpack successfully. Or is it back to shop for replacement handset.