So, I made the ludicrously stupid mistake of somehow accidentally basically wiping the OS from my tablet with TWRP because I was having problems with it and was trying to figure stuff out. Anyways, I didn't have a backup on the device so I found a stock rom online for it. I tried plugging it into my computer and directly transferring the zip to the device, but it just flat-out refuses to do so. It tells me the device is either not responding or disconnected. I found out that if I try dragging it into a folder it should work, but all it does is give me a different error, telling me that it exceeds the size limit or something. Anyways, next I tried using ADB sideload but the device isn't recognized at all. As a last resort, I finally got a USB-OTG cable and tried that. However, TWRP refuses to mount the thing. It isn't recognized at all. I'm using TWRP v2.8.0.1. Tell me, am I completely screwed?
My device model is SM-T230NU, if that helps at all.
Jorvalt said:
My device model is SM-T230NU, if that helps at all.
Click to expand...
Click to collapse
Download one of the following files to PC, extract with either 7zip or WinRAR, and flash with Odin (boot your tablet into download mode: home, vol-, and power; and connect with USB):
--SM-T230NU UEU0AOD1 XAR Region (USA)
--SM-T230NU UEU0AOD1 XAC Region (Canada)
--Nook Edition SM-T230NU OVU0AOG1 BNN Region (Nook Edition)
thisisapoorusernamechoice said:
Download one of the following files to PC, extract with either 7zip or WinRAR, and flash with Odin (boot your tablet into download mode: home, vol-, and power; and connect with USB)
Click to expand...
Click to collapse
Forgot to mention, Odin doesn't recognise it either.
Jorvalt said:
Forgot to mention, Odin doesn't recognise it either.
Click to expand...
Click to collapse
install drivers and stop kies if running, also reinstalling drivers will help if you already have drivers
thelous said:
install drivers and stop kies if running, also reinstalling drivers will help if you already have drivers
Click to expand...
Click to collapse
The problem is that my computer doesn't actually recognize the device type, and therefore doesn't have any drivers for it and can't find any drivers for it.
Jorvalt said:
The problem is that my computer doesn't actually recognize the device type, and therefore doesn't have any drivers for it and can't find any drivers for it.
Click to expand...
Click to collapse
I'm pretty sure you can get the drivers from here:
http://www.samsung.com/us/support/downloads
Jorvalt said:
So, I made the ludicrously stupid mistake of somehow accidentally basically wiping the OS from my tablet with TWRP because I was having problems with it and was trying to figure stuff out. Anyways, I didn't have a backup on the device so I found a stock rom online for it. I tried plugging it into my computer and directly transferring the zip to the device, but it just flat-out refuses to do so. It tells me the device is either not responding or disconnected. I found out that if I try dragging it into a folder it should work, but all it does is give me a different error, telling me that it exceeds the size limit or something. Anyways, next I tried using ADB sideload but the device isn't recognized at all. As a last resort, I finally got a USB-OTG cable and tried that. However, TWRP refuses to mount the thing. It isn't recognized at all. I'm using TWRP v2.8.0.1. Tell me, am I completely screwed?
My device model is SM-T230NU, if that helps at all.
Click to expand...
Click to collapse
you don't have an sd slot? just copy a FLASHABLE zip onto the card and flash in TWRP from there.
thisisapoorusernamechoice said:
I'm pretty sure you can get the drivers from here:
Click to expand...
Click to collapse
I meant that I have drivers for it, but neither my computer nor Odin actually recognizes it, so having the drivers is pointless anyways.
Droidphilev said:
you don't have an sd slot? just copy a FLASHABLE zip onto the card and flash in TWRP from there.
Click to expand...
Click to collapse
I don't have an SD slot in my computer, no. I also don't happen to have a spare micro SD card laying around either. As soon as I'm able, I'll try and get one and let you guys know if it works.
Side note: The ROM doesn't necessarily have to be flashable considering TWRP can install zips directly. Obviously it has to be in connected storage that the device recognizes, though.
Jorvalt said:
I meant that I have drivers for it, but neither my computer nor Odin actually recognizes it, so having the drivers is pointless anyways.
I don't have an SD slot in my computer, no. I also don't happen to have a spare micro SD card laying around either. As soon as I'm able, I'll try and get one and let you guys know if it works.
Side note: The ROM doesn't necessarily have to be flashable considering TWRP can install zips directly. Obviously it has to be in connected storage that the device recognizes, though.
Click to expand...
Click to collapse
TWRP can only flash *TWRP flashable* zips or .img for kernels/radios but nothing more. i meant sd slot in the tablet of course.
im having the same issue, because odin will say it worked , but simce it doesnt show the device , in win 10 device manager it only shows samsung usb composite drivers, in idin it doesnt show anything , if im not mistaken , odin need to recognize the device, so how do i get win 10 to recognise the tab 4?
Vintage144 said:
im having the same issue, because odin will say it worked , but simce it doesnt show the device , in win 10 device manager it only shows samsung usb composite drivers, in idin it doesnt show anything , if im not mistaken , odin need to recognize the device, so how do i get win 10 to recognise the tab 4?
Click to expand...
Click to collapse
Only odin will detect your tab if there is no rom booted up. Try flashing deodexed stock rom from twrp
Related
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I was having a similar issue with my MBpro, nothing would recognize my phone. Tried it on another comp and bingo. I think stuff is just finicky with USB ports. Lame-o.
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure so when u see its charging for 30 sec. Then put the cellphone into download mode... and that should work
maldito.boss said:
when did u plugg ur phone in dowload mode?
try this ... load odin ... turn ur phone off!!! plugg it to the computure let it charge for 30 sec and the put it into load mode... that should work
Click to expand...
Click to collapse
Yea...this post made my brain hurt...and of course didn't change anything...but..thanks?
Here's another piece of info that may help nail down the problem...
Odin is able to see the phone if I boot into Clockwork recovery mode but because clockwork is up the phone can't receive a flash but Odin does see the phone with no problem. It just still won't see the phone when booted into download mode.
ghsthntr said:
I'm trying to revert back to stock on my Epic. I previously flashed using Clockwork and wanted to try Odin this time around but when I put the phone into Download mode my computer doesn't recognize the device. I've tried multiple cables and USB ports including one on the board itself. I am using Windows 7x64 and have the 64 bit samsung drivers installed properly. If I do a battery pull and boot the phone normally the computer recognizes the phone no problem.
Any ideas?
Click to expand...
Click to collapse
I use windows7 64 too. I encountered tons of problems when trying to flash my epic. first my computer doesn't recognize my phone in download mode. after i wipe out all the drivers and reinstall them. finally i get my computer recognize it under download mode, but Odin froze every time during the flash.
Finally, i tried on another desktop computer with windows XP. Everything went perfectly. So maybe you should try that too.
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Pirate-M.Lifnen said:
I cannot connect to my Epic in download mode on mac os x either.
I was trying to install a lag fix, and now all my phone will do when powering on is show switch between the normal Samsung screen, and another reading "Samgung GT I9000".
I can still boot into Clockwork Recovery. But OS X will not recognize my phone.
Either that, or Heimdall isn't recognizing it and won't let me flash.
Help! Any ideas?
Click to expand...
Click to collapse
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
I had the same problem, I couldn't connect it to 3 of my pc's. 2 xp's and one windows 7. Turned out the port on the phone it self was broken, had to take it sprint and get it replaced.
Pirate-M.Lifnen said:
Really!?! No one has any idea? Please guys, I'm just sitting here with a broken phone, there must be a way for me to fix this.
Click to expand...
Click to collapse
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
i had an extremely similar issue as to what you are having. I have 3 win 7 machines and 1 xp, none worked. I went to a friends house he has 2 win 7s and an xp also didnt work. I did a general search and found all kinds of crap. One dude something about using his chicks blackberry usb cord and suddenly it worked on any and all of the machines it had previously not worked. so at the time im reading this on my chicks laptop which has a damn blackberry cord attached to it chargin her evo(go figure) ... anyway u didnt need the whole story but i have nothing to do right now.
Point is everyone says try different cords, i say try the damn blackberry cord if you happen to have one or a friend that has one.
Benjamin Dobell said:
If OS X isn't recognising your phone it's likely your phone has the buggy secondary bootloader. Samsung corrected the bootloader for at least the GT-I9000 JPA firmware but I'm unsure if they have done so for other devices or firmware releases.
Unfortunately the only solution then is to use Windows or Linux. If you don't have access to a system running either of these OS then I recommend downloading a 64-bit release (assuming your PC has a 64-bit CPU) of Ubuntu, then you can download the Heimdall binaries from my website and use it to recover your phone.
Click to expand...
Click to collapse
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
ldartez said:
Is it the hardware on the Macbook pro itself? or just the OS? in other words, If I were to partition my macbook with ubuntu would that work with heimdall? would it be able to recognize my phone while it's in download mode as opposed to OSX, which couldn't...?
Click to expand...
Click to collapse
In this particular instance Apple haven't done anything wrong at all, both their hardware and software is fine. The issue is that Samsung are distributing secondary bootloaders that aren't complaint with the USB specifications.
Whilst that is annoying, the good news for you is that you can simply install Linux (Ubuntu etc.) or Windows on your Macbook and you'll be able to flash just fine.
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
BraydenJW said:
Hey everyone!
So I made a critical mistake. When installing a new ROM on my LG G2 D803 (Rogers) is mistakenly (without thinking about it) reformatted the phone. Thus, I can now boot into recovery (TWRP 2.6.3), but I have no ROM to install and my backups are gone. It's bricked.
I read that you should be able to do an ADB push from TWRP, or use ADB sideload to do this, but ADB doesn't recognize any devices (adb devices returns an empty list) and the adb sideload feature of TWRP gets stuck after I swipe to initiate it.
I assume the reason I cannot connect through ADB has something to do with this (taken from Windows device manager). I installed the [email protected] driver from LG's official site (LG United Mobile Driver 3.10.1) and let Windows do it's thing when I connect the phone from TWRP (Using Windows 8) but it still shows up like this every time.
i.imgur.com/EXp2qbZ.png
Any advice/help? I've been working on this for hours.
Click to expand...
Click to collapse
try these as drivers
Trying now
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
Thank you. Trying this now. I'll let you know how it goes.
datechnerd said:
try these as drivers
Click to expand...
Click to collapse
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
BraydenJW said:
At the risk of sounding like an idiot. What exactly do I do with these?
Note for others: contained in the attachment is wdfcoinstaller.dll and lgandnetadb.sys.
Click to expand...
Click to collapse
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
datechnerd said:
go to device manager, right click g2, update drives, browse specific location, and pick where you extracted those
Click to expand...
Click to collapse
I'm afraid that did not work. I get an error message saying there wasn't any drivers found in that folder.
i.imgur.com/mkLZzBe.png
The two files are directly within the extract folder on my desktop. I'm running Windows 8. I right-clicked g2 in device manager, and selected update driver software and navigated to the extract folder on my desktop.
Thank you for your help so far, do you know where I could go from here?
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
BraydenJW said:
It may also be worth mentioning that my phone is on the main menu screen of TWRP 2.6.3.2 when I plug it in.
Click to expand...
Click to collapse
go to sideload and install drivers
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
datechnerd said:
go to sideload and install drivers
Click to expand...
Click to collapse
I'm sorry. I'm not entirely sure what you mean. When I go to sideload on TWRP, it gets stuck on the loading feature part indefinitely.
cityneversleepz said:
you aren't bricked. some computers are better than others at recognizing your device in adb. I found that my hp laptop with windows 7 will not recognize my device when I am in twrp. but my wife's acer with windows 7 does. you have two ways to get a stock rom back onto your device. one is twrp sideload and the other is adb push.
Click to expand...
Click to collapse
Thank you. I've tried it from my own laptop and my work computer and both have similar results. I'll try it from one of my older computers. I'll post back with my findings.
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
BraydenJW said:
Still no luck. All three computers I've tried it on (two Windows 7 and one Windows 8) all complain that no g2 driver was found when I plug in my phone when it is booted into TWRP. This happens both before and after I install the LG United Mobile Driver. No matter what I do I can't get this phone to talk to my PC. I am also using the usb cable that came with my phone and I've tried others as well. Any other ideas? Will LG fix it even though warrant is void for money?
Click to expand...
Click to collapse
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
datechnerd said:
http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
install these drivers (different lg device but allows support for g2) when installed, plug phone in and go to sideload, on pc go to device manager find the phone, right click, update drivers, browse computer, let me pick from a list, you may have to unclick show compatible, find google in the list then the most recent dated adb interface driver
Click to expand...
Click to collapse
Thank you! Trying this now. I'll report back soon.
It's looking good! It showed up in my adb devices now. Just have to re-download the rom
I pushed the ROM and am installing it now. If this goes through successfully, I'll send you some money over paypal if you wish. Nothing huge, but at least a little as a token of my appreciation.
The ROM installed successfully. I'm just waiting for the first boot now. It's taking a while (about 5 minutes now) and I'm VERY nervous.
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
BraydenJW said:
The first boot got stuck. It just stayed at the animated ROM boot screen. I used the ROM here. http://forum.xda-developers.com/showthread.php?t=2502789
Is there a file that might've been erased in the reformat that the ROM wouldn't replace?
Click to expand...
Click to collapse
that rom says let the first boot take as much time as needed.
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Alright! I'll leave it for a few hours. PM me your paypal email if you'd like me to make a donation to you! You've been an extreme help!
datechnerd said:
that rom says let the first boot take as much time as needed.
Click to expand...
Click to collapse
Left it for over an hour. No luck. Something is wrong.
I have a S4 I got in a trade, and It has this error when it boots up. I plug a usb cable in, and it does not recognize it in windows in either the yellow triangle or downloading mode. I have enclosed two pictures to show the errors. Is there any hope for my phone or am I out of luck ? I do appreciate your alls help and directing me to the correct place to fix this.
Thanks!
VaRMiT
VaRMiT said:
I have a S4 I got in a trade, and It has this error when it boots up. I plug a usb cable in, and it does not recognize it in windows in either the yellow triangle or downloading mode. I have enclosed two pictures to show the errors. Is there any hope for my phone or am I out of luck ? I do appreciate your alls help and directing me to the correct place to fix this.
Thanks!
VaRMiT
Click to expand...
Click to collapse
Looks like whoever had it tried to flash a ROM or something and failed. You'll have to flash the stock firmware in ODIN. I recommend downloading MDL and MK2, because if by chance MDL works then you can get a full custom recovery and not be restricted as to what you can flash. This phone has a locked bootloader so flashing is not as straightforward as other phones.
Sent from my GT-I9505 using xda app-developers app
DeadlySin9 said:
Looks like whoever had it tried to flash a ROM or something and failed. You'll have to flash the stock firmware in ODIN. I recommend downloading MDL and MK2, because if by chance MDL works then you can get a full custom recovery and not be restricted as to what you can flash. This phone has a locked bootloader so flashing is not as straightforward as other phones.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What links can you provide that gets me the stock ROM, MDL, and MK2.
And thank you so much for the help.
Definitely try the AMDL image first like DeadlySin9 stated. If it is still on that version, you found a diamond in the rough. You'll want to keep it from updating afterwards if it is on AMDL.
AMDL is available from sammobile.com
MK2 is available from http://forum.xda-developers.com/showthread.php?t=2621279
I believe you will have to register on that site to download them.
Red_81 said:
Definitely try the AMDL image first like DeadlySin9 stated. If it is still on that version, you found a diamond in the rough. You'll want to keep it from updating afterwards if it is on AMDL.
AMDL is available from sammobile.com
MK2 is available from http://forum.xda-developers.com/showthread.php?t=2621279
I believe you will have to register on that site to download them.
Click to expand...
Click to collapse
My biggest problem is this, It will not reconize the usb when I plug it in the computer. I am a computer tech, I know about usb drivers for samsung. etc...Ive done the volume down, power etc where its in download mode, it doesnt reconize the usb. Is there a way to put this on a micro sd card and install it from there? Or do I have to do it from usb?
I would try downloading the Android SDK. It may give you the drivers you need.
Otherwise, try different cables (OEM is best) and different USB ports. Make sure you download the drivers off of the Samsung website. If there is a bad driver on your machine, ensure you are checking the box to delete the driver file when uninstalling.
Otherwise, there is another program called Heimdall that ignores the windows drivers, but I'm not well versed in that one.
VaRMiT said:
My biggest problem is this, It will not reconize the usb when I plug it in the computer. I am a computer tech, I know about usb drivers for samsung. etc...Ive done the volume down, power etc where its in download mode, it doesnt reconize the usb. Is there a way to put this on a micro sd card and install it from there? Or do I have to do it from usb?
Click to expand...
Click to collapse
Have youtried installing Samsung Kies into your computer to get the driver?
gorgy76 said:
Have youtried installing Samsung Kies into your computer to get the driver?
Click to expand...
Click to collapse
What the biggest problem is, I can go to Device Manager and when I plug it in, It doesnt do anything at all. No indication that a USB device in the USB section. But I havent tried kies, I figured, if a unreconized usb device wasnt in the device manager, theres no sense in going any further. EX: I plug my mouse in, it shows up in device manager somewhere. The S4 doesnt at all.
VaRMiT said:
What the biggest problem is, I can go to Device Manager and when I plug it in, It doesnt do anything at all. No indication that a USB device in the USB section. But I havent tried kies, I figured, if a unreconized usb device wasnt in the device manager, theres no sense in going any further. EX: I plug my mouse in, it shows up in device manager somewhere. The S4 doesnt at all.
Click to expand...
Click to collapse
If changing cable and different USB ports hasn't helped, then the USB port on the phone is probably defective and that's an entirely different issue.
EDIT: Also try a different computer if possible.
I know this thread is an old thread but I still wanted to share. I was recently working/ playing with a couple of Samsung Galaxy s4's ( sgh-i337 & sgh-m919). I managed to get the "secure fail: kernal, unauthorized software has been detected by the system" message. These days you hook the device to smartswitch and do an emergency recovery. What I did was hooked the phones up to z3x Samsung Tool Pro in download mode. After selecting the proper device, I clicked the option to read the pit file. After reading the pit file, the device restarted normally with no message. The first time I thought may have been a weird bug but I have replicated it 3 times and the same result each time. This happened after installing or having issues with custom recovery.
Hmm it looks like whoever was trying to install a ROM or custom recovery, forgot to use the Loki exploit.
You can download the MDL firmware from my Google drive here:
https://drive.google.com/file/d/1ZXv9FAcDbfkbFZzh078SSMZ85jbMVPSx/view?usp=drivesdk
I've flashed my i9505 many times. I can't remember exactly what I've done, but now the situation is very weird.
1. I can go into Download mode. But Odin doesn't recognise it. Kies doesn't recognise it either. The error message on the bottom right corner of the screen says "USB device not recognized. Your usb device has malfunctioned." I've tried re-install the USB driver, use the original USB cable, even tried it on another PC with no luck. I suspect the very low level USB driver in the phone has corrupted because possibly I flash something wrong in the past.
2. I can go into Recovery mode and flash new ROMs in zip format from there.
3. I can use my phone normally, e.g. make phone call, SMS, WiFi......My computer can recognize my phone as usual when I am in Android.
Any thoughts? Helps are appreciated.
Hello,
Uninstall any previous installed of Samsung USB drivers, clean your Windows registry through CCleaner (not needed but highly suggested) then download and install latest Samsung USB drivers
Now download mode will be recognized on PC
Inviato dal mio GT-I9505
There is an easier way. If you are using windows, go into control panel-> Devices-> Right Click on your phone-> there should be a Driver Details-> Go details I think it is-> Uninstall driver-> Have the box ticked-> Uninstall-> Unplug then replug the cable in and it should work.
Sent from my Nexus 4 using XDA Free mobile app
AntaresOne said:
Hello,
Uninstall any previous installed of Samsung USB drivers, clean your Windows registry through CCleaner (not needed but highly suggested) then download and install latest Samsung USB drivers
Now download mode will be recognized on PC
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
I've tried to re-install the driver. I even tried to connect the phone to another PC where the driver had never been installed before. Nope.... it doesn't work. Actually, I've searched around in Google for long time. The most likely reason is the usb piece of Android code is corrupted. Well, maybe not android, it should be the lower layer of Linux. I previously installed dual boot system follow this link and I screw it up when I tried to upgrade the primary OS:
http://forum.xda-developers.com/showthread.php?t=2447534
procket said:
I've tried to re-install the driver. I even tried to connect the phone to another PC where the driver had never been installed before. Nope.... it doesn't work. Actually, I've searched around in Google for long time. The most likely reason is the usb piece of Android code is corrupted. Well, maybe not android, it should be the lower layer of Linux. I previously installed dual boot system follow this link and I screw it up when I tried to upgrade the primary OS:
http://forum.xda-developers.com/showthread.php?t=2447534
Click to expand...
Click to collapse
You said that in Android USB connection works.
The download mode depends on bootloader, that can't be touched in any way by Android, even you can't touch the bootloader.
It's also write-protected, you can only upgrade it through Odin or through an official OTA update, when flashed you can't downgrade and can't write on its partition if not through JTAG
Inviato dal mio GT-I9505
procket said:
I've flashed my i9505 many times. I can't remember exactly what I've done, but now the situation is very weird.
1. I can go into Download mode. But Odin doesn't recognise it. Kies doesn't recognise it either. The error message on the bottom right corner of the screen says "USB device not recognized. Your usb device has malfunctioned." I've tried re-install the USB driver, use the original USB cable, even tried it on another PC with no luck. I suspect the very low level USB driver in the phone has corrupted because possibly I flash something wrong in the past.
2. I can go into Recovery mode and flash new ROMs in zip format from there.
3. I can use my phone normally, e.g. make phone call, SMS, WiFi......My computer can recognize my phone as usual when I am in Android.
Any thoughts? Helps are appreciated.
Click to expand...
Click to collapse
Hi friend, did you found out how to fix this issue i have the same problem with a I9500 please help
banziitox24 said:
Hi friend, did you found out how to fix this issue i have the same problem with a I9500 please help
Click to expand...
Click to collapse
Sorry mate, I am still stuck in Odin. Since I can flash new ROM via recovery mode and everything else still works, I give up.
procket said:
Sorry mate, I am still stuck in Odin. Since I can flash new ROM via recovery mode and everything else still works, I give up.
Click to expand...
Click to collapse
Dang I have this phone here I can connect it in Odin but in normal mode it doesn't connect and I need it to connect so I can finish the IMEI Repair
change the modes of usb
try *#0808# mtp + adb or others
try *#9090# try all of them
best of luck
Ok so. I bricked my gt-i9505, and i have tried everything to try and fix it. The problems are as follows:
Phone wont turn on
Wont boot to recovery mode
Odin, Kies and pc wont recognize phone
The things i did that got me to a bricked phone are i flashed paranoid android onto the phone and tried to flash gapps full modular, it wasnt working, clockworkmod gave me a status 6 error and so i decided to use mobile odin to flash it as soon as it began the phone crashed and it wont turn on anymore. i am able to go into download mode
I need some help if anyone can help. I dont know what to do.
Sir,
Please wait until mods will move this thread to the device specific forum.
Stand by
Until then read/ask in this thread: How to Unbrick Samsung Galaxy S4?
Good luck
mujtabay said:
Ok so. I bricked my gt-i9505, and i have tried everything to try and fix it. The problems are as follows:
Phone wont turn on
Wont boot to recovery mode
Odin, Kies and pc wont recognize phone
The things i did that got me to a bricked phone are i flashed paranoid android onto the phone and tried to flash gapps full modular, it wasnt working, clockworkmod gave me a status 6 error and so i decided to use mobile odin to flash it as soon as it began the phone crashed and it wont turn on anymore. i am able to go into download mode
I need some help if anyone can help. I dont know what to do.
Click to expand...
Click to collapse
If the phone won't turn on at all you might be boned.
Odin and all that obviously require you to be able to boot to download mode.
Are you positive the battery is good? Could you find another battery to try?
Does the charging light come on when its plugged in? Are there any signs of life at all?
Skipjacks said:
If the phone won't turn on at all you might be boned.
Odin and all that obviously require you to be able to boot to download mode.
Are you positive the battery is good? Could you find another battery to try?
Does the charging light come on when its plugged in? Are there any signs of life at all?
Click to expand...
Click to collapse
I think it does turn on because the phone does continue to heat up but its just a black screen also i can put it into download mode and it stays there without being plugged into charge. I'm not sure about the battery ill have to check that out. ill get back to you.
It sounds like you dont have recovery or a rom installed at all.
To fix that you need odin. If the PC wont recognize the phone that is a problem. Did you try a different USB cord to connect to the PC? They are not all created equal.
Skipjacks said:
It sounds like you dont have recovery or a rom installed at all.
To fix that you need odin. If the PC wont recognize the phone that is a problem. Did you try a different USB cord to connect to the PC? They are not all created equal.
Click to expand...
Click to collapse
yes i have used both the original one that came with the phone and the s5 one that my brother has, i have had no luck.
my phone shows up as "msm8960" or mtp usb device also it it device driver software was not successfully installed.
[UPDATE] i have found something similar to odin called JOdin3 that connects to my phone, through this i will try to flash a stock firmware, downloaded from sammobile, and see what happens.
Odin doesn't work without the drivers, and since you had an issue with the drivers that would explain why Odin doesn't work yet JOdin3 does.
Strephon Alkhalikoi said:
Odin doesn't work without the drivers, and since you had an issue with the drivers that would explain why Odin doesn't work yet JOdin3 does.
Click to expand...
Click to collapse
I installed the samsung drivers several times and it still wouldn't connect to the pc, i also installed kies and it still wouldn't work, but it was working before i bricked my phone. i have fixed my phone through JOdin3.But thank you everyone for your help.
Will it connect now through Odin or Kies?
Strephon Alkhalikoi said:
Will it connect now through Odin or Kies?
Click to expand...
Click to collapse
No it still wont connect to either but the computer does recognize the phone.
MTP is built into Windows, so the fact the PC detects the phone is a good sign. The entire problem you're having seems to hinge on your PC rejecting the Samsung drivers, which are absolutely required for Odin to function. Those drivers should have no problems installing, and I have successfully installed them on both Windows 7 (x64) and Windows 8.1 machines so I know the installer does work.
There could be many reasons as to the source of your problem, such as a corrupt file or registry entry from when the phone soft-bricked. You want to take a closer look and do some detective work here. Uninstall the drivers if you haven't already done so. Clean out the PC with CCleaner. Even attempt a reinstall of the drivers in the PC's safe mode. Regardless of what you choose to do, if you ever wish to use Odin, you'll need to get this resolved.
Strephon Alkhalikoi said:
MTP is built into Windows, so the fact the PC detects the phone is a good sign. The entire problem you're having seems to hinge on your PC rejecting the Samsung drivers, which are absolutely required for Odin to function. Those drivers should have no problems installing, and I have successfully installed them on both Windows 7 (x64) and Windows 8.1 machines so I know the installer does work.
There could be many reasons as to the source of your problem, such as a corrupt file or registry entry from when the phone soft-bricked. You want to take a closer look and do some detective work here. Uninstall the drivers if you haven't already done so. Clean out the PC with CCleaner. Even attempt a reinstall of the drivers in the PC's safe mode. Regardless of what you choose to do, if you ever wish to use Odin, you'll need to get this resolved.
Click to expand...
Click to collapse
yeah ill definitely try to fix the problem because odin is such a great tool. i have uninstalled and installed the samsung drivers but i'll go search the net and what not to try and find a fix. odin was working before when i flashed the stock rom and changed something to mtp and adb (i think i put in an ussd code or something (*#0808#) and through that i was able to use odin) but because the wifi wasn't working on the stock rom, i flashed a custom rom to fix the wifi problem but was once again greeted with the odin problem.