Hello everyone, I totally pulled a noob earlier, with all the excitement going around with the official ICS update going around, accidentally I pushed a 19100 ROM into my sgs2 by sprint; and now my device is semi brick, neither Kies, Odin nor SimpleDownloaderTool for SPH-D710 recognizes the device, after downloading the correct drivers into my computer.. now what do I do?
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
sgs4g SGH-T959V always reboot into download mode, even after successful oneclick
lumin30 said:
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
Click to expand...
Click to collapse
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Pro tip: Open a new thread if you need to ask a question or need help. Don't "hi-jack" other threads. (considering that the original thread is from 2012)
But it's done...
teevoo said:
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
Click to expand...
Click to collapse
Did you follow @lumin30's guide?
teevoo said:
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Click to expand...
Click to collapse
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
teevoo said:
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Click to expand...
Click to collapse
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
bhundven said:
Did you follow @lumin30's guide?
Click to expand...
Click to collapse
Yes. Oh and I made several posts (not hijack ) regarding this issue elsewhere in the forum but got no response. One thing I forgot to mention in this version is that originally, the download mode on phone was triggered physically somehow. My uncle accidentally dropped the phone in water. He then blew it dry with a strong fan and must have turned it back on too early. Since then the phone's been in download mode.
bhundven said:
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
Click to expand...
Click to collapse
I'm now wondering if there is a program that can do a reset like heimdall/odin without going through the whole reflashing process. Assuming the phone's memory components haven't been physically damage, at least this would mean I can restart the phone to normal mode quickly.
bhundven said:
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
Click to expand...
Click to collapse
Ok, I'll try to find a different computer to do this with, although right now I'm thinking USB is not the case as I have successfully performed the same flash on a different sgs4g and it works just fine (the difference was that phone was never stuck in download mode to begin with). For the problem phone, I have tried a couple of ports and 2 different cables on my Mac. From what you just told me, perhaps the phone's usb port is the culprit.
Thanks for your reply, and thanks for all the programming work you've contributed to this forum :good:
Related
Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(
Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.
Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions
Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.
I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.
If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.
Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.
After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.
Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.
Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
I pull out my battery and let it discharge for about 15 secs and hold volume buttons then connect USB cable and finally insert battery while still holding volume buttons of course, it'll get you into download mode. Never failed me. I've had my phone not even turn on the screen, it stays dark during a screwed up flash with odin. I then flash UCKI2 with bootloaders and then flash to gingerbread ROM I like. If you plan on installing custom ROMs your phone will semi-brick numerous times. If its showing a phone, exclamation mark and computer with a message saying firmware flashing failed. That is perfect! Just make sure you have Samsung USB drivers and simply flash using odin, it'll show COM and a number like 5 (COM5) then just flash. I'd advise you to remove any external SD card and restart before using odin it acts up. Hope this helps
hupo224 said:
So I been trying to fix my friends Captivate for a few days now.
I posted a video a few days ago. I did get it into download mode with my jig. However everything froze while I used the 1 click captivate heimdall to flash my phone. (It did flash but some things did not work)
Anyhow now My phone has "Phone - ! - PC"
No download mode, the jig sends it back to this screen too. I tried so many button combinations. I really don't want to send my phone in to some website. I was so freakin close...
Please help
My Evo 3D is laughing at me and the captivate.
Click to expand...
Click to collapse
The "Phone - ! - PC" will be your download mode screen. Just download from there.
However, if a flash goes foul somehow, you may be left with the infamous "phone--/!\--PC" screen.
If you see this, don't panic. Although it's not technically the download mode screen, many users (including myself) have been able to successfully flash from that screen. Give it a try.
Click to expand...
Click to collapse
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
asasione said:
Comes from this thread:
http://forum.xda-developers.com/showthread.php?t=1351224
Let me reiterate cause it will save you the same thing happening, reboot your computer, be connected to internet, remove SD card and then open odin and then connect your phone and flash otherwise high likelihood of something going wrong again. I'm used to it but its frustrating the first couple times.
Click to expand...
Click to collapse
100% - I had similar experience with my first flash but after a few goes at it and 3 or 4 "soft-bricks" all has been great!
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
It seems I got it in download mode this morning with the jig. Just trying to get my damn pc to read it. Sometimes the right drivers work sometimes they don't. ugh
Connection issue in my sig
Any chance you have another pc to try it with? Or possibly another cable?
Going to try one click on ubuntu...
Ive had issues in the past before with certain USB ports on my PC not reading the phone.
Try plunging in your phone to a different USB port and it can make a world of difference with the driver issue (even if you have to plug it in the back of your PC).
try one click unbrick in the android development page
hupo224 said:
Well when I plug it in Windows 7 doesn't even detect it anymore. But the phone will go back to that screen when the USB is connected.
Nothing in ODIN/Heimdall pops up...
Please help..
Click to expand...
Click to collapse
Are you running x64? If so are you running the 64 bit drivers?
I also had the same issue a couple of times, which is technically called a "soft brick" . You could resolve this issue using ODIN flasher and reverting back to stock. Now coming to USB problem in windows, this is a known issue with windows (especially Vista and Win7) and samsung!! The remedy which I found is as follows :-
1.Disconnect the phone from USB
2.Remove samsung USB driver software from your windows PC.
3.Reboot and then navigate to C:\Program Files\ (assuming that C:\ is your windows OS partition)
Delete "samsung" folder.
4.Download latest samsung USB Drivers for captivate and install.
5.Reboot the phone.
6.Open ODIN and connect your Phone to PC.
It should detect the COM Port by now. Try this and get back
"Thanks" , If I helped U
I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?
kmv_007 said:
I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?
Click to expand...
Click to collapse
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl
qkster said:
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl
Click to expand...
Click to collapse
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!
kmv_007 said:
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!
Click to expand...
Click to collapse
Try it on another computer. I recommended Odin back to stock first before you start flashing!
Sent from my SGH-I997 using Tapatalk
Thanks, I'll give a different computer a try.
kmv_007 said:
Thanks, I'll give a different computer a try.
Click to expand...
Click to collapse
make sure you are trying to get into DL mode correctly...
pull battery, hold ONLY the volume buttonS - not the power button -;
insert battery, plug in cable.
if that doesnt work, use a different usb cable.
try different port on the computer
try a different computer or winxp or win7
it's kinda finicky at times.
Finally got it working - needed to use a different computer. Used my brother's laptop and it worked first try. Thanks for your guys' help.
I am in desperate need of help .. I am not a noob to flashing roms and rooting, however I have a one-off situation w/ no precedents to my knowledge. I have read these and other forums for days to no avail.
I was flashing Infintium Rom 4.0.4 from MIUI 2.3.6. I followed the steps listed in the post (http://forum.xda-developers.com/showthread.php?t=1661690). After flashing I rebooted and waited however the phone was/is stuck on the Samsung logo and never progressed. I then pulled the battery and attempted to go back to recovery mode to reflash make sure I did flashed correctly. However, upon going back into recovery I was greeted by the below image.
Clockwork Mod is extremely distorted and flat out unusable !! As I read further down it advised to use Heimdall (http://forum.xda-developers.com/showthread.php?t=1331381). I downloaded and attempted to use, however my PC (Which by the way is Windows 7 64-Bit) recognized the phone but the Heimdall software did not. I already had the right drivers for the PC and phone. After a few tries I deleted the files and reapplied them. On the 2nd menu after selecting list devices, on the drop down the option for Samsung USB Composite Device neeever ever appears. I also tried on a different PC that ddnt have the drivers and started brand new. Still, Heimdall ddnt recognize.
I also tried to flash numerous files including but not limited to GTG Ultimate Unbrick via Odin. Again, PC recognized USB connection however program ddnt. At this point, I do not know if it is because the status of Clockwork Mod on my phone, but I know it is not because of the drivers or the USB ports on my PC.
In addition to that, I have just scrapped the idea of flashing or getting in CWM and just wanted to do a hard reset (While phone is off held Vol down and Power, once started released power and contimued to hold Vol down. This should take the phone from the Samsung logo to an alt menu that will give the option to do a factory reset. But again w/ my luck .. that screen neeever appears.
In short I have tried at least 3 different ways and many maaany variations to get the phone back into recovery or into a full boot and had NO success.. Please help and ask as many questions as needed to diagnose and resolve this issue .. Thanx in advance and apologize in advance if posted in the wrong thread.
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
andros11 said:
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
ohsirus said:
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
Click to expand...
Click to collapse
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
http://d-h.st/sKF
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
I will try again .. Downloaded, rebooting then will go thru the process again .. standby
Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
no change .. still shows disconnected
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
rkkaranrk said:
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just did that to post a pic as an example .. I did go to download mode and not recognizing it
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
drnecropolis said:
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
Click to expand...
Click to collapse
I know I need to get the bootloader and a kernel on it however I cant = ( .. yet .. I have 4 different ports on my PC and have tried them all. i have tried phone on then run programs and programs on 1st then phone on and no new results.
I found this short video and it describes my exact situation .. please watch to futher understand http://www.youtube.com/watch?v=OHLUYckTlug
So u have odin and heimdal both on the same PC and drivers for them if yes then try this.
On the PC/Laptop uninstall all the drivers for samsung or any other phone and follow this.
Go to accessories> system tool> system restore and check the restore point where the drivers for heimdall were installed restore to a previous restore point after restore finishes install the drivers for Infuse and see now Odin recognizes ur phone, It should.
I had the same exact problem, do you have another phone on which you can install the same CWM recovery on? ...Because the clockwork mod recovery still works, it's just that you can't see it. So just flash a new ROM, by going back n forth between phones, clock how many clicks it takes to get to 'choose zip to install' then 'download' on the not messed up phone, then do the same on the screwy one, just keep doing that till u flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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