Hey I'll spare the story but basically I've softbricked/bootlooped my S4 in a way I have many times and fixed easily, however now I can't. Basically I tried to launch a bad ROM; same one thats failed me multiple times, stupid to try again but I've fixed this exact problem with this ROM before many times by flashing back to stock with Odin. The problem is my family computer was recently reformatted so I lost Odin, Kies, Drivers, anything I was using before. I redownloaded all those things only now none of them are working properly... When I load up Odin like I always have with my phone in download mode of course, select the tar and run. Only now it recognized a device is connected and I get a COM:03 or whatever but when I hit run it basically goes nowhere and just says "all threads complete completed 0 failed 0" or sometimes "completed 0 failed 1" can someone tell me what these messages are trying to tell me? I though maybe it was cuz I hadn't installed Kies but Kies says my device isn't responding, which I was told could be cuz I have a custom bootloader and my phone needs be 100% for Kies to recognize it but I feel like it used to recognize it with the custom loader. Maybe not. I also tried updating the windows USB drivers but everything was up to date. My computer makes a noise when I plug my phone in and charges it but can't be viewed in windows file explorer. Maybe that's cuz I'm in download mode.
I don't understand why it isn't working but I think its my computer. It's software is the only variable thats changed, I'm doing everything exactly as I used to. I think one of the many components to make this work isn't lined up properly and I don't know what it could be at this point. And PLEASE no answers like "did you check the USB port?". . . yes of course I checked the USB port, yes I'm in download mode, yes my cable works, redownloaded every program in multiple firmware versions. those are the only answers I've been able to find on this topic and none of them get me anywhere.
Can someone tell me what is different on my computers end now? As I've said, I've done this successfully 100 times on my computer before doing exactly what I'm now it just isn't working after the harddrive reset so I assume something has to be wrong on the computers end.
I have a VZWJFLTE SCH-I5454 galaxy s4 and I'm trying to boot back to stock (4.4.2 NC5 found on galxys4root.com).
Related
ive researched for hours on the forums trying to fix my vibrant and I cant seem to find a situation similar to mine.
So i tried to install a rom from the romkitchen website. before that I did not have any rom I was just rooted via OCLF and i had just updated to the newest clockwork recovery. i did a nandroid backup and proceeded to install the rom. after it installed it just hangs at the first screen that says vibrant samsung. only it doesnt say that. it say galaxy s gt i9000. i tried to restore my nandroid file but it says it cant mount the sdcard. anything regarding the internal or external sdcard wont work. the recovery also looks different from the one i had before. it says clockworkmod recovery v2.5.1.0 speedmod ULFK at the top. and thats the only recovery i am able to access. i tried to odin back to stock and i tried so many different methods but no matter what i do it wont register in any odin version nor in that alternate odin program. i keep disconnecting/ reconnecting but nothing. i just get a a popup in the bottom corner that says one of the usb devices attached to the computer has malfunctioned. i dont know what else to do. any help would be greatly appreciated. im getting off the computer now so please email me at [email protected] if you can help. ive gone back to using my g1 for the time being
Use a usb port on the back of the computer .
hook up yer phone to computer , reinstall drivers , if u are not bricked because i dont know i didnt read everything u posted lol enable usb denbug and reinstall drivers than .
Im pretty sure I did the same thing a long time ago. I thought my phone was screwed.
Definitely try plugging it into another usb port if you have one first. Supposedly the ones in the back of the computer are better. If you have to, try every usb port you have.
Also, make sure youre downloading the drivers that are right for your opertaing system. For example, if you have windows xp 32bit, dont download the drivers for windows 7 64bit.
Even just reinstalling the drivers didnt work. I dont remember step by step, but I got into recovery, and wiped my cache and user data and was then able to have odin recognize my phone. Be careful in recovery mode though, because if I remember right it remapped my volume buttons, (up was down and down was up)
Lastly, make sure if/when you get odin to recognize it, you put the .tar file in the right spot (PDA) and make sure its checked. you need to have the .pit file there too, the 512 pit is the one Im pretty sure you want to have, not the 513, one is just newer. You probably want to make sure the re-partition box isnt checked in odin too.
Its been a while since Ive had to use odin, so I may be wrong on a few things, like which pit file is newer and so forth.
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
My phone has the AT&T installed ICS, using odin and the ics .tar files my friend found for me the phone went through most of the process, and failed right at the end. It is now stuck at the recovery mode screen and I can't get Kies to recognize it at all, but it is recognized by both computers I have tried it on. I am really not sure what exactly I can do to get it back running again. I have tried to read all I can, but honestly I just don't know what I am doing enough to be sure of what to do next to recover it and if that relates to other problems people have had that have been solved.
I found this post about odin tips for better success - http://forum.xda-developers.com/showthread.php?t=1863995, but nothing I have seen has helped me from it. I found a few other occurrences of the same thing, but no solution within those threads, so I have no idea how even to proceed.
Any help is appreciated!
Make sure you reboot your pc, start odin, put phone in recovery, then connect usb cable. Make sure Kies isn't running in the background.
Agreed....
Run the process again........but you must ensure a clean working environment, and "NO" kies running while Odin is running....g
I did those steps multiple times on two separate computers. The first initially didn't even have kies installed, just the samsung drivers, but Odin failed repeatedly without even really starting. I restarted computers no USB hubs, tried different cables, different USB ports, nothing changes. Even the kies recovery doesn't recognize the phone at all, but it does still appear to the computers. I appreciate the responses, but what other steps can I take to ensure I am doing this properly? Could it potentially have been the tar file I have, and if so, can I just do the process from this screen, and where can I find the correct files if it wasn't include in one of the tons of threads on here about it?
722ish said:
I did those steps multiple times on two separate computers. The first initially didn't even have kies installed, just the samsung drivers, but Odin failed repeatedly without even really starting. I restarted computers no USB hubs, tried different cables, different USB ports, nothing changes. Even the kies recovery doesn't recognize the phone at all, but it does still appear to the computers. I appreciate the responses, but what other steps can I take to ensure I am doing this properly? Could it potentially have been the tar file I have, and if so, can I just do the process from this screen, and where can I find the correct files if it wasn't include in one of the tons of threads on here about it?
Click to expand...
Click to collapse
Go to samfirmware.com, and restore the device from the website direct...
It appears that you may have the download mode drivers, or a portion of them damaged or unreadable...( due in large part, to the fact that Odin "must" complete the flash process, then disconnect and reboot the device, in order for the flash to stick, and this didnt happen)
Be very careful here my friend, you are one step away from needing a JTAG repair....(BAD)
The website will push a recovery rom image to your device without the need for Odin drivers....and should give you a factory rom that functions correctly....
I dont have a direct link...(sorry) but this is the last attempt before the device is needing much deeper attention....g
Again..its samfirmware.com, or very near that....g
Edit: I'm very sorry you are having this issue, but we are here to help you through it.....So take a few deep breaths, and relax a bit, then hit the website I gave you..
then look in the tools section at the top, and go from there.....you got this....g
Ok, I will take a look at that when I get home! typical of me to push it to the limits. Thanks for the help, much appreciated!
722ish said:
Ok, I will take a look at that when I get home! typical of me to push it to the limits. Thanks for the help, much appreciated!
Click to expand...
Click to collapse
Always welcome my friend.......g
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.
Hi everyone, i hope to find a solution writing there, since i'm kinda desperate about my situation.
So, i got this telephone, a s2 I9100g, but only the day after i noticed the browser was in chinese. Looked up a bit better inside and i found it is a chinese version of the telephone (original one, but made for chinese market).
So i tryed to pull in an original rom, but it failed; i found a guide to how to fix this problem, and become able to flash the italian rom on it.
Basically, i followed this guide http://forum.xda-developers.com/showthread.php?t=1702479%22 I did all the steps using the CHN version of the bootloader and.. i know, i was so stupid there, but since it got stuck at NAND writing (i did not see the progress bar after 15 minutes), i simply unplugged the cable.
Well, after that the phone didn't enter reset/download mode, but it started showing the yellow phone---!---pc screen, with wrote above "software update fail", and something else in chinese.
There is what i tryed to do:
-Flash another rom (tryed 2) with different versions of odin, 1.3,1.6 and 3.07.
odin does recognize the telephone with the drivers installed, but if i start it, it gets stuck at setup connecting phase and failing after. Same with all versions.
-use OneClickUnbrick, i tryed to start it normally and from CMD.
with the drivers which odin and windows use to recognize the telephone (last ones available on samsung website), it says "usb drivers are not properly installed attempting to install drivers". So, it starts Zadig. I follow the steps there, and the installation completes succesfully. But at this point, when i plug in the telephone windows recognizes it but fails installing the device with drivers, and odin doesn't recognize it at all, while oneclick keeps showing the "usb drivers are not properly installed" window, time after time even if i keep reinstalling with success the drivers using Zadig.
-delete everything and install Kies.
none of the programs above does see the telephone now, neither windows.
Tryed to follow the steps i did before after having it installed, nothing changed.
Every of this tryes, i did the following "changes":
-removing and inserting the battery
-changing usb port
-changing cable
-changing computer
-trying to enter reset/download mode by holding vol up/down+mid button+power
Would be enough to make odin go over the setup connecting phase, or kies to recognize it, or OneClick to stop showing the window about drivers.
I read that seems i'm in a hard brick case, but since the phone is seen by odin and windows and the battery does recharge, i got still a bit of hope.
Thanks
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Hopper8 said:
Click the link in my signature, there's more troubleshooting steps to try. You've done a few but not all of them.
I would usually say that pulling out the cable leaves you with no hope, but you seem to have gotten a little lucky. Don't hold your breath though.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Tryed all the steps.
Nothing changed.
You can either keep trying or take to a service centre & pay to have it fixed *shrugs*