I've been rooted for several months and life was good. My charging suddenly stopped working. I'd restart the phone a couple time and it would work. Then it wouldn't work again. Went back and forth like this for a while, till finally I figured it wasn't the plug or connector (all would either work or not work, based on restarting phone, messing with battery while plugged in), but likely something more related to the software/system updates. Tried reflashing with odin to go back to stock, but can't connect. I can put my phone in download mode, but odin doesn't recognize it. I've tried every port on 2 different computers with probably 6 different cables. Tried different versions of odin. I can get the phone charging most of the time when plugged into the wall or computer, but can't be seen by odin. I've checked debugging and just did manual resets, losing all my data, but accomplishing nothing. Is there any way to go back to stock without odin? Some way to install from micro SD or something I'm not thinking of to get me connected to odin? I'm at a loss for what to do or understanding what in the world went wrong in the first place.
Additionally, I thought I'd mention the phone WILL NOT shut off either. When I power down, it restarts. I remove the battery, and as soon as I put it back in, the phone boots up again.
Based on your last paragraph, there is probably a hardware issue with the phone or micro-usb port. Load a stock rooted ROM through twrp, then unroot and bring it to a service store.
Try cleaning or blowing out the USB port. I've seen phone with lots of pocket lint packed in the USB port that exhibit the same symptoms.
Sent from my SM-N910P using Tapatalk
And the plot thickens...
Tried blowing out the port. The connection seems to still be there as I can maintain power without the battery when plugged in... just can't get any computers to recognize it as a device. Took the phone to the local sprint store to see if they could do some kind of hard reset with it. Their hardware couldn't connect either. The employee tried to do a soft reset and now my phone can't escape "recovery booting." The android logo blinks with "installing system update" under it but it doesn't boot and I can no longer get into recovery mode. I can still enter download mode, but odin still doesn't see my phone. The guys at sprint really kind of screwed me there. At least I had a functional phone before they messed with it. Is there any way to put a boot program on the sd card and boot from there? If so, any ideas where to find one? I've tried searching, but as the phone is so new, there isn't a lot of help I can find in the forums. Additionally I contacted Samsung, but they won't touch it due to knox being tripped. On my backup S3 for now.
Well I threw in the towel. Sprint is replacing it with remanufactured one. If they didn't offer to replace it, I'd have kept working on it, but case closed for now.
Related
Hi all, having a problem with my new Epic 4g Touch.
I rooted it, then after having some other problems, tried to flash back to stock via Odin. Not sure if I did something wrong, but in the middle of the flash, Odin had an error. Now the phone won't boot.. it goes straight to the [phone]....[!]....[computer] screen with the text "Firmware upgrade encountered." It goes to the same screen when I try to boot into recovery. It also goes to this screen when the phone is off and I plug it in (ie, there is no battery charging screen).
I can get into download mode, but I can't get my computer to recognize that the phone is plugged in. I have tried multiple computers, different USB ports, different cables, re-installing drivers on the computer, but no matter what I try, the computer never makes any indication that the phone is plugged in. Kies won't see it, Odin won't see it, nothing in device manager, no alert sound when plugging/unplugging, nothing.
I am afraid I have a soft brick on my hands and I might have to take it back to the Sprint store or send it to Samsung (used a USB jig to reset bin count to 0). Anyone have any idea how to get the computer to see it again so I can just try flashing it again?
SAME PROBLEM, PLEASE HELP, PLEASE. If you fixed yours tell me how.
Anyone come up with successful suggestions to this issue? I think I'm now in the same boat after going back to stock. I can't get any computer/cable combination so see the device, which keeps me from using Odin to fix it. Thanks!
I've gotten in that mode before. It does it whenever the phone has been opened in the special mode for updating (which is done by ODIN during the flash process and is a step beyond ODIN D/L mode), but that mode is not closed down properly. It'll do that even if you flash an unused partition like recovery.bin, so it has no bearing on whether your ROM is actually bricked or not. It is just the default behavior when the special flash mode wasn't close down properly.
USB jig restored functionality.
That is assuming you weren't flashing a GSM ROM by mistake.
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
I've owned my SGII since release, went through a few roms, never had any issues. I have been running liquidsmooth for a month or two, without much issue. Although, lately stablity has dropped off a little. Nothing bad, just a freeze every few days and other minor hiccups.
Then something bad happened.... Last night I was using the phone and it turned off. Then it wouldn't boot. Battery pull, and rebooted but no joy. Then I booted to recovery (TWRP, but I'm not sure which version) and found that it said something along the lines of "E: could not mount /system", along with lots of other similar failure to mount messages. Oh well, I guess I'll just wipe it and flash something new. Any attempt to wipe would hang and then the phone would turn off after a few minutes.
Then I went to flash the stock setup from odin (using the howto from the dev section) , but it too would fail every time. I even tried different builds from samsung's official roms, but they all would fail to install on the phone. I read every thread I could find, and the next thing to try seemed to be an emergency recovery through Kies. That also failed, except it left my phone hard bricked. I can't get into download or anything, nothing shows in the device manager, just completely dead... I made a USB jig, but no luck there either.
I'm completely frustrated... I don't know what to do now... Buy a MB from ebay? The phone was flawless before all this. Any suggestions? I'm using a blackberry pearl for now, I can't let that happen.
Have you tried the Jig on another Samsung phone so you know the one you made physically works?
Some people have managed to get into DL Mode by pulling the battery, SIM, SD, etc. For 5 - 10 minutes then connecting it to the pc with Odin running b4 inserting the battery to enter DL Mode.
Otherwise mobiletechvideos has a really good reputation and turn around time for JTag service.
There is a chance its a hardware problem, and hopefully another member on here can shed some light on the possibility of it being a HW issue or not..
Cheers,
Chris
Thanks for the suggestions. I don't have another samsung phone to try the jig with, but I'll see if I can get a friend to let me hook up this crazy looking thing. I got the resistors set up to 299K, hoped that would be close enough, but perhaps not.
I tried that plug-first-battery-second trick to get into DL mode, but that's not working either.
I looked at the jtag service too, but my fear is that I have corrupted memory. In that case, I wouldn't get a refund if I still couldn't get to a fully healthy boot. It seems odd though... not like it's a common trend for this particular model (that I've seen).
Just seems so strange that it happened for no apparent reason... before it was hard bricked I was able to USB mount the internal storage and access and transfer almost all the contents, except for one folder. I wonder if that one part of the memory caused all the problems?
Again, thanks for the suggestions. I'll keep plugging away at anything that might help, and in the mean time I guess I'll keep my eyes out for broken phones or some way to salvage a board.
If im not mistaken, a hard brick should show up in you device manager as the board itself when connected.
Does anything show in you device manager when its connected? And have you tried using a different PC which has never had Kies installed on it, where you just install the drivers for the T989?
Odin tends to fail at the modem or due to the presence of a .PIT
I got myself out of a brick which started over the a very similar issue, but due to a bad flash.
After 5 hrs of getting nowhere (I was using a Jig) I would get Odin to recognize the phone (My Screen was NOT displaying the DL Mode screen, It was going into DL Mode but other than Odin recognizing it, there were no signs of life!) after enought tries but flashing to stock would fail. I ended up taking a shot at flashing the stock kernel using 512.Pit from a T959, Reflashing the same Kernel, then flashing recovery. I don't advise anyone do this as that PIT file is NOT for a T989, and it may have been BS luck not the use of that PIT file that did the trick.
But I did get it back running %100
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
This happen to me before, I just cleared cache and Davik then rebooted recovery then flashed another Rom.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Unfortunately for me, since data, cache, and system couldn't be mounted, I couldn't successfully clear them.
KLR Rico said:
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
Click to expand...
Click to collapse
I would put the jig in with the battery and everything still removed, and alot of trial and error trying things like battery first then connecting the cable with Odin always being already running. Then doing the reverse, etc.
When I did get Odin to recognize the phone, one thing I learnt is when it would detect, it only ever happened after having killed and reopened Odin. I have no explanation on why using "End Task" after each attempt to connect and opening Odin again made a difference but it did.
Have you had a look at the QPST thread? I would ask one of the members contributing to it about why you would or would not see the board. And you could always try installing the boards drivers manually, or enable "Show hidden devices" in your device manager.....
Did you contact the guys at mobiletechvideos and explain the details?
You were able to boot to recovery, so it sounds partition related. But I would try just to flash the stock UVLH1 kernel and recovery with Odin vs full stock rom if you do get it to detect. And if it does detect with Odin eventually do not let it reboot or loose power. Just Kill Odin, unplug the cable if you need to, Start Odin again and reconnect the cable. Once in DL Mode it will stay in DL Mode as long as you have the reboot option in Odin unchecked, etc.
Also if you can get the battery charged fully somehow, your best shot is with a fully charged battery.
Chris
Hi i recently purchase a second hand LG-E971 (locked to rogers and not rooted).
The phone seem to be working at first but whenever
i connect the phone to the computer or charge it on the wall
it goes to "download mode" the only way to exit it is to hold pwr for 8sec.
i got all the driver installed properly in "download mode"
tried to factory reset it with E97110D_00.KDZ and E97110E_00.KDZ
with success but still having the same problem
whenever i plug a usb cable in
i installed the driver for PC
LGUnitedMobileDriver S4981MAN38AP22 ML WHQL Ver 3.8.1.exe
when i connect the phone the driver got installed automatically
but the phone doesnt connect to the PC (win7 i tried 2 different computer) in any mode it is only charging
Is there a KDZ that is already Root with CMW or TWRP that i can factory reset it?
Thank you.
I would contact rogers to get the device checker under waranty.
If you have flashed the original KDZ, you eliminate all software related issue that could've cause this. It must be an hardware issue.
i have same problem. since today whenever i plug the phone to charge it it goes to download mode.
any way to fix it? im on cm but didnt change anything recently
I would suggest to start with cleaning the USB pirt on the phone. Compressed air and a wooden toothpick will help. I had a similar problem with my old SGS2, when dirt in the socket was causing sime weird behaviour.
Worth trying before going to the service centre...
having the same issue as well..i hope there's a possible fix available.
dead thread i know but i have SOME valuable information if you have this phone lying around "dead"ish. i went through a lot of crap trying to revive my dead battery phone and i remembered, i just by chance stumbled upon a "solution" of sorts. it basically is taking out the sim card, turning on the phone WITHOUT the cable, and once it's on i can connect it again. the moment i put in a sim, the damn thing starts flaking out. i'm currently using solidkernel 1.95 gproj with cm 12.0 official nightly 10/16(2015). this had happened to me like a month and a half ago or so as well. ANYWAY, it's either a radio thing, a kernel thing, a rom thing, or a combination of the three. that would NOT explain why the phone assumes download mode has been invoked, especially given it should only happen through a special pre-boot procedure using buttons (two no less). still, it is possible that my sim slot is too dirty, or my sim itself is problematic? i don't know. what do you guys think?
I have an I747 that was running CM13. It was fully updated, NJ2. Had TWRP 3 on it. It was running great and one day the battery died. It charged for a little and will turn on, but not go past the CM guy logo. I tried booting into recovery and same thing, I get the TWRP logo but doesn't go beyond that. It goes into recovery but it's not recognized by the pc when connected. It's almost like the internal card went bad, and that's why it turns on but won't boot. Any ideas? Any help is appreciated
Did you try a factory wipe? Reinstall the same or different ROM?
I can't get into the ROM or recovery to do a wipe. I have a back up I'd like to try to restore first, but I'd gladly try any ROM I could get to work
Can you get into download mode to reflash twrp?
I tried. I can get into download mode, but when I connect to the pc, Odin never shows as connected. Usually it turns blue and says like COM1 or something
Are you using the original Samsung cable? Tried using different USB cables and USB ports?
It's not the original Samsung cable, but I've tried a few different ones. Tried every USB port on the computer.
One of the cables I retired I know works for data transfer because I use it for a different Samsung phone
It's possible the USB port is damaged. I have found with my s4 that even if a cable can transfer data, it can't flash a ROM in Odin.
I thought about that too. I found cracked screen phone on ebay so I can try a new internal board. It was cheap so figured it was worth a shot. Thanks for all your input.
I'll keep you posted with whatever happens.
So I got a new/old phone on eBay. Cracked screen but it turned on. I got that, opened it up, pulled the board out and swapped it in with my good screen. All is working new. Got my cm 13 working again. Thanks for your input.