Related
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 there! First of all I don't speak english very well.
My Galaxy Nexus hard bricked yesterday.
tl;dr no boot animation, no recovery mode, no download mode, no response from computer.
I thought it had just a low battery level, I found it turned off. So I tried to recharge it but it gave no signals, no battery icon, nothing.
After an all night long recharge I tried to turn it on, to enter in download mode or in recovery mode but nothing works. I also tried to connect it with my computer with and without battery, no response, no "OMAP" device found, no sound from Windows for plugging it in, nothing.
I found this thread here in xda, many people has been redirected to it and found their solution to the brick problem.
I tried to follow all the steps but when I plug in the phone and start the .bat file nothing happens, just stuck on "Waiting for device".
The phone is unlocked and rooted. I'm running AOKP JB-MR1 Build 2 and Franco Kernel for a month, never had problems with them, never installed other ROMs after that.
What should I do now? Should I try to do something or just bring it to a support center? The phone is still in warranty, there would be any problem because it has a non-stock ROM?
I've red about a jig to force the Odin mode, should I buy it? (I found this one)
Thanks for the help.
Have you tried booting into Odin mode
ntb81 said:
Have you tried booting into Odin mode
Click to expand...
Click to collapse
Yes, it doesn't work.
have you your warranty on it?
return it and get a new one
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Beauenheim said:
It's hard bricked and a JTAG unit may force it into download mode, if you send it in for warranty, chances are it won't be accepted as it was obviously tampered with and they would find out that your bootloader is unlocked and charge you more money than the device is actually worth to fix it.
Click to expand...
Click to collapse
Yeah, that's why I'm not sure to send it in for warranty. So have I to try with a JTAG first?
[bman123] said:
I don't understand how it could of bricked if nothing has changed on the phone for a month or longer. Nothing was flashed recently so how can you hard brick the phone?
Click to expand...
Click to collapse
I'm not understanding that too, I don't know what happened. Suddendly it stopped working. Maybe is just a battery problem, I'll try to use another one before bringing it to the shop where I bought it.
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
galiganu said:
same happened to me, but I have an untouched phone with stock android. it worked well for over an year until today.
I see a lot of people having same issue, but they say that when connected to PC over USB the phone is recognized as OMAP.
for me the PC doesn't do anything...
any help? thanks
Click to expand...
Click to collapse
so right after I wrote that I plugged my phone into USB of my PC without battery. when I inserted the battery it started showing me the battery sign and I could started the phone. 3 minutes later it went black again, but the trick didnt work again.
any ideas? thanks
Try This !!
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Tech.Nik said:
Arrange a 4 ohm resistor and try to attach it in ur usb plug port of phone ..it 'll force the phon eto go in download mode or say Fastboot mode.
then follow a tutorial to flash any rom..
its quite easy else ping me !!
Click to expand...
Click to collapse
Please could you explain a bit more how to go about this? I have a Verizon Galaxy Nexus in a somewhat similar condition. This one is recognised as an OMAP 4430 device. I downloaded OMAP Flasher, installed drivers and tried to bring it back to life but after running the batch file I get this error: Operation FAILED (Remote: : Driver init error 0x00FF8080 - MMC CONFIG FAILURE). Can the resistor trick work on this and if yes, how can I go about it? I am not faint-hearted; I think I can handle it if given the right instructions.
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
galiganu said:
After I tried everything i could from the internet, I went to a shop and tested to see if the USB is broken - and indeed it was. I replaced the USB component of the phone and after that it started.
Thanks guys
Click to expand...
Click to collapse
Yeah, the faulty USB port is a very common issue.
My wife has a T-Mobile GSII. I successfully rooted it via ODIN to CWM-SuperSU-v0.87. My wife wanted me to put it back to stock so I unrooted it to T989UVLE1. It was killing the battery (and some other weird things began happening) so I want to re-root it but now the USB port is not working so I can't ODIN it back to the rooted MOD.
When I plug in the USB cable connected to my PC it charges but it doesn't connect for data. My computer doesn't see it, and it doesn't show the USB icon in my notifications on the phone either. When I try to boot to recovery, it goes into download mode (even if it's not connected to a USB cable). ODIN doesn't see that it's connected so I can't change the ROM.
Now, I also have the SGH-T989 and used this same process successfully. When I connect it to the same PC with the same cable I can do anything I want, ODIN works, I can get to recovery mode when it's not plugged into a USB. It's as if my wife's phone thinks it's connected to a USB even though it's not and when it is connected it doesn't recognize it. I'm thinking I could send it in for warranty figuring the USB port is dead but the ROM that's on there isn't stock and I'm afraid I'll get into hot water with TMO. For grins, I uninstalled all of my Samsung drivers and reinstalled them, and did the same thing with Kies. My phone connects fine, my wife's doesn't at all.
Anyone have a good idea? I've looked around on here all day and can't find anything that will work for me.
Once you Odin back to stock on your wife's phone you lost the recovery. Use [URL="https://www.dropbox.com/s/jdfj55rcj6p5c7c/odin3%20v1.85.exe]this version of Odin[/URL].
Remove battery
Open Odin (the one I provided)
Put battery back in after about 20 seconds
Hold volume up and volume down
Connect phone to computer via USB
Download mode should pop up on the phone and Odin should recognize your phone
After that just Odin a recover onto her phone and flash supersu to root
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Problem with your link...
The ODIN in your post doesn't lauch an ODIN session. Instead I get a dialog box that says, "Odin3.ini" and then seven boxes with an OK button. Now I'm really baffled.
stecina said:
The ODIN in your post doesn't lauch an ODIN session. Instead I get a dialog box that says, "Odin3.ini" and then seven boxes with an OK button. Now I'm really baffled.
Click to expand...
Click to collapse
Sorry about that man. That was my faul, the dialogue means you need the ini file for Odin. I've reuploaded everything in a zip file here. Just unzip to your desktop and follow the same steps I provided earlier.
*note* the zip file includes the two Odin files you need...just open Odin.exe. A recovery tar file and a superuser zip file...the superuser zip I provided outdated so just use your root zip file.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Didn't Work
Okay, so that returned the same result as before. Your method also didn't make my computer (or ODIN) think it was connected to anything, so I'm unable to get the root onto the phone.
What can I try next?
stecina said:
Okay, so that returned the same result as before. Your method also didn't make my computer (or ODIN) think it was connected to anything, so I'm unable to get the root onto the phone.
What can I try next?
Click to expand...
Click to collapse
You can try reinstalling the drivers. If you don't have them you can download it here. Just run the exe file. Also if you have Samsung kies on your computer that could be causing the interference so remove it
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I have uninstalled and reinstalled drivers as well as Kies. Remember, I have another phone of the same model that is easily recognized by my computer AND ODIN. I'm pretty sure there is something wrong with my wife's USB port. That's why I want to restore it to stock, so I can get a warranty replacement.
Sent from my SGH-T989 using xda app-developers app
stecina said:
I have uninstalled and reinstalled drivers as well as Kies. Remember, I have another phone of the same model that is easily recognized by my computer AND ODIN. I'm pretty sure there is something wrong with my wife's USB port. That's why I want to restore it to stock, so I can get a warranty replacement.
Click to expand...
Click to collapse
There is a flashable stock zip on the first post here:
http://forum.xda-developers.com/showthread.php?t=1858435
Scroll down to T-Mobile t989 UVLH1 and click show content. It's at the bottom.
---------- Post added at 11:59 PM ---------- Previous post was at 11:45 PM ----------
meekrawb said:
There is a flashable stock zip on the first post here:
http://forum.xda-developers.com/showthread.php?t=1858435
Scroll down to T-Mobile t989 UVLH1 and click show content. It's at the bottom.
Click to expand...
Click to collapse
After re-reading your OP I see you can't even get into recovery. I don't think there is anything you can do but take it to T-Mobile and hope for the best. Or send it to Samsung...
Have you tried using a PC which you have not used for flashing your own?
I realize its unlikely to make a difference, but trying to flash your wifes using a "virgin" PC is at least worth a shot...
Chris
Another thing you could try is disconnect the phone from the PC (leave it powered up and everything), load up device manager in windows then plug the phone in and watch for device manager to flicker or do anything. I'm thinking maybe your phones are the same (T989's) but possibly a different revision that requires a different driver. Device manager will tell you if the phone was able to start or not. One thing that SOMETIMES works with windows computers (although it sounds silly) is to use a different USB port. I always use the one on the back of my computer as it is directly connected to the motherboard and thus offers a shorter path for the data to travel. I have had issues using front USB ports with devices before (my MP3 player will time out during large data transfers if I use the front USB port sometimes).
Also, is "debug mode" turned on on your phone? It is under development tools. If it is off, try turning it on. And with it on, do you get any results from running "adb devices" (presuming you have the android SDK installed or a copy of adb floating around on your computer from some other tools)?
And lastly, does the phone charge when the USB cable is plugged in? It is unlikely that 2 of the pins on the USB connection are bad without them all being bad.
Good Ideas!
Well, I've tried a couple of those ideas. The Device Manager idea revealed nothing. Nothing changes in the Device Manager when I plug in the phone. The phone DOES charge, so like you said, it's likely a software issue not hardware since two of the pins seem to work fine. BTW- the phone acknowledges it has been plugged in, too, by beeping. The computer does not.
I had tried using different computer USB ports because I have found the same to be true as you: the ports on the back go directly to the motherboard but the ones on the front are actually going through a hub, though it's inside the case, the computer sees it as a hub.
I don't have ADB Devices. I don't have any experience with that program...can you advise me? Next up, trying on a virgin computer...
Thanks for the ideas. I've got to get this worked out or my wife's going to DIE. Currently, the home button doesn't take her home, it takes her to this weird Clock App based lock screen/screen saver. Anyone have an idea how to correct that problem itself?
UPDATE: I tried to install and run ADB Devices and it didn't result in recognition by my computer.
Sending in For Warranty
It appears that this is my problem.
I took it to TMO and they approved a warranty replacement for a faulty USB port. Just in case anyone wondered.
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my second Samsung device and have been rooting/flashing for almost two years, so not a noob.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware that way, but I get to the last step where it says "Upgrade Firmware" or something like that on the button but the button remains greyed out and I can't click it... I have tried everything. I downloaded the toolkit and installed drivers but each time I do that, the driver install freezes my PC at the end of the install. Same thing happens if I try to get the drivers from the Samsung site directly, the computer freezes. I have rebooted a million times and tried every USB port there is. I have had the computer try to "set up" the deivce while it's in download mode a few times but usually hangs at the end (probably bc drivers not properly installing). Once or twice it setup fine, but still Odin won't recognize. I think the driver thing is moot because it was recognizing the device before this mess just fine and it recognizes and accesses my wife's S2 just fine.
I am at my wit's end. Did I destroy my phone???? Is there nothing I can do to salvage it?
I just aged about five years in the last 2 hours. Please someone help!!!
Longshot, but try installing the toolkit on a different system and try again. I've had drivers from different systems mixed up and it worked fine when installed on a fresh system. Probably not your problem, but worth a try before trying to warranty your phone. Good Luck.
Also try a different usb cable.
Sent from my SPH-L900 using xda app-developers app
RTC88 said:
Also try a different usb cable.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
TMPOOLE said:
Longshot, but try installing the toolkit on a different system and try again. I've had drivers from different systems mixed up and it worked fine when installed on a fresh system. Probably not your problem, but worth a try before trying to warranty your phone. Good Luck.
Click to expand...
Click to collapse
Different cable didn't work.
I'll try a different system but I'm not holding out hope.
Will warranty work if in Odin mode the phone says that I have a custom ROM and custom recovery installed???
Am I out of luck here? I always thought that if it boots up, it's not completely bricked. Shouldn't a PC see it if I get the drivers installed???
If no computer sees it and the Download/Odin screen shows Root and custom ROM/Recovery so no warranty replacement, what are my options?
mikelav456 said:
Am I out of luck here? I always thought that if it boots up, it's not completely bricked. Shouldn't a PC see it if I get the drivers installed???
If no computer sees it and the Download/Odin screen shows Root and custom ROM/Recovery so no warranty replacement, what are my options?
Click to expand...
Click to collapse
You say it finds your wife's phone just fine and she has the same model? Have you tried installing the drivers manually through the driver update in device manager?
As to other options, if you're paying for the additional insurance Sprint offers, and are willing to pay the $200 deductable (as opposed to the $500 replacement cost) you could always turn it on and drop it in a bucket of water. They won't be able to pull root/rom info from the unit at that point. Otherwise I think it's a matter of luck as to what kind of techs work in the store you go to. I've heard stories about those who were sticklers and those who didn't care (the latter tend to those who root their own phones). All you can do is ask, hypothetically of course.
Wish I could be more help. Good luck.
Please help!!! Does anyone have any other advice?
DreamingWolf said:
You say it finds your wife's phone just fine and she has the same model? Have you tried installing the drivers manually through the driver update in device manager?
As to other options, if you're paying for the additional insurance Sprint offers, and are willing to pay the $200 deductable (as opposed to the $500 replacement cost) you could always turn it on and drop it in a bucket of water. They won't be able to pull root/rom info from the unit at that point. Otherwise I think it's a matter of luck as to what kind of techs work in the store you go to. I've heard stories about those who were sticklers and those who didn't care (the latter tend to those who root their own phones). All you can do is ask, hypothetically of course.
Wish I could be more help. Good luck.
Click to expand...
Click to collapse
Appreciate your help. Wife's phone is a different model, but also Samsung.
I do not have the Sprint insurance unfortunately. I will probably try to go through the Samsung warranty, but not holding my breath....
mikelav456 said:
Appreciate your help. Wife's phone is a different model, but also Samsung.
I do not have the Sprint insurance unfortunately. I will probably try to go through the Samsung warranty, but not holding my breath....
Click to expand...
Click to collapse
If you can get the drivers to extract (I know it crashes when you try to install) you could still try the manual update method for your phone's drivers. (can't count how many times I've had to do that for peripherals and my win7 laptop that isn't certified for win7)
Did you try completely uninstalling the drivers before you tried to reinstall them?
DreamingWolf said:
If you can get the drivers to extract (I know it crashes when you try to install) you could still try the manual update method for your phone's drivers. (can't count how many times I've had to do that for peripherals and my win7 laptop that isn't certified for win7)
Click to expand...
Click to collapse
Not sure how to do this. I'll look into it.
Avatar said:
Did you try completely uninstalling the drivers before you tried to reinstall them?
Click to expand...
Click to collapse
Yes. I'm going to try a different computer tonight.
I had the same problem.forgot what I did though. It was something like a oneclick selfextracting installer to install factory rom.older than ljc. let me look and ill try to find it for u..
---------- Post added at 07:48 PM ---------- Previous post was at 07:43 PM ----------
try this.http://www.sxtpdevelopers.com/showthread.php?t=228 same idea just different modem. read through and make sure you understand what garwin is saying. If you dont have anything special on your internal sd card I would use the wipe all as the no data restore didnt work for me some reason. also download this http://forum.xda-developers.com/showthread.php?t=1957155 as it will hook you up with the right drivers.
johntheman_692003 said:
I had the same problem.forgot what I did though. It was something like a oneclick selfextracting installer to install factory rom.older than ljc. let me look and ill try to find it for u..
---------- Post added at 07:48 PM ---------- Previous post was at 07:43 PM ----------
try this.http://www.sxtpdevelopers.com/showthread.php?t=228 same idea just different modem. read through and make sure you understand what garwin is saying. If you dont have anything special on your internal sd card I would use the wipe all as the no data restore didnt work for me some reason. also download this http://forum.xda-developers.com/showthread.php?t=1957155 as it will hook you up with the right drivers.
Click to expand...
Click to collapse
Thanks but this is exactly what I tried first and continue to try... The problem is I unplugged the phone while the one-click was doing its thing because it wasn't progressing. The phone still goes into to Download mode but the one-click no longer 'sees' the phone when I plug it in, so I can't try again...
mikelav456 said:
Thanks but this is exactly what I tried first and continue to try... The problem is I unplugged the phone while the one-click was doing its thing because it wasn't progressing. The phone still goes into to Download mode but the one-click no longer 'sees' the phone when I plug it in, so I can't try again...
Click to expand...
Click to collapse
You said the computer doesnt recognize it right? If it did I would recommend flashing a custom recovery then going from there.
Sent from my SPH-L900 using Tapatalk 2
Avatar said:
You said the computer doesnt recognize it right? If it did I would recommend flashing a custom recovery then going from there.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
If I get my computer to somehow recognize the device via the drivers, I should not use the odin one-click to just go back to stock? How do I install a custom recovery if I can't boot into Android?
mikelav456 said:
If I get my computer to somehow recognize the device via the drivers, I should not use the odin one-click to just go back to stock? How do I install a custom recovery if I can't boot into Android?
Click to expand...
Click to collapse
I would download the tool kit and reinstall the drivers from their. I had the exact same problem months ago. took hours of trying to flash different stuff to get it to work. make sure that you try to unplug then replug in the cord and I think you must use a cord that is made for your phone. Mine wont work unless I use the one supplied with it which is weird but I read somewhere that the prongs are longer or something.open the oneclick oden then plug the phone in and let it sit for a min or 2
johntheman_692003 said:
I would download the tool kit and reinstall the drivers from their. I had the exact same problem months ago. took hours of trying to flash different stuff to get it to work. make sure that you try to unplug then replug in the cord and I think you must use a cord that is made for your phone. Mine wont work unless I use the one supplied with it which is weird but I read somewhere that the prongs are longer or something.open the oneclick oden then plug the phone in and let it sit for a min or 2
Click to expand...
Click to collapse
I'm going to try tonight on a different computer.
So you think I should do the following:
1. install drivers
2. open odin one-click
3. put phone in download mode
4. plug phone in
5. even though yellow COM thing should pop up right away let it sit for a while
6. flash one-click back to stock
I'll give it a shot after work.
mikelav456 said:
If I get my computer to somehow recognize the device via the drivers, I should not use the odin one-click to just go back to stock? How do I install a custom recovery if I can't boot into Android?
Click to expand...
Click to collapse
I have actually had this happen before. I couldnt get anything to work even the one click. So what I did was use the toolkit to flash a custom recovery with the stock kernel. Then when it rebooted I held the volume up home, and power buttons. Go into recovery and nandriod back to my previous rom and it worked. But my pc did recognize my device.
Sent from my SPH-L900 using Tapatalk 2
Avatar said:
I have actually had this happen before. I couldnt get anything to work even the one click. So what I did was use the toolkit to flash a custom recovery with the stock kernel. Then when it rebooted I held the volume up home, and power buttons. Go into recovery and nandriod back to my previous rom and it worked. But my pc did recognize my device.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I didn't know you could flash a recovery to the phone without booting to Android. The toolkit says boot to android as pre-req for installing recovery. If I could get to recovery I could fix this. I'll give it all a shot again tonight.
mikelav456 said:
I didn't know you could flash a recovery to the phone without booting to Android. The toolkit says boot to android as pre-req for installing recovery. If I could get to recovery I could fix this. I'll give it all a shot again tonight.
Click to expand...
Click to collapse
Never mind I miss understood. Good luck with the pc switching
Sent from my SPH-L900 using Tapatalk 2
I was factory resetting phone because it was having some problems with the camera, and that's when I accidentally dropped it, causing it to soft brick (I can turn it on, but it stays on the LG logo, and as I said, I can't enter download mode. However, I can access recovery mode). The problem is that I can't make the computer to recognize it (when I connect it, it doesn't appear any port option, only the universal serial bus controllers followed by an "unknown device". This happened before I bricked my phone.), which makes the situation even harder. Besides opening it and retrieving the mainboard, is there any other option? because I'm not 100% positive that I'm not going to be able to do that. PLEASE help!
*I'm not an expert with phones, so if there's an answer, try to say it on the most detailed and basic way, if possible
Dropping it wont cause a softbrick in your case theres two possiblitys either A u droped it and damaged internally or B when u dropped it the battery fell out while resetting and uve corupted a file but probly the first. Either way this guide is for the g2 but it may give u some insight. http://forum.xda-developers.com/showthread.php?t=2582142
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
I didnt read very well in this case download ure rom on ure pc put ure sd card in ure pc put the rom on the sd card thr put it back in ure phonenand flash rom from there unless u got a backup on ure sd card just retore from recovery
---------- Post added at 06:42 PM ---------- Previous post was at 06:38 PM ----------
http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/
I would rather go for
-USB OTG cable
+
-USB FLASH driver with some rom on it
Didnt think of otg in most of my travels most people never even heard of it ill get u the site if u want it i vet em 75 cents apiece ive never tore one up always end up losing them
I forgot to mention, but when I dropped my phone, the battery DID came off, so the factory reset did get interrupted
If thats the case at worst lg flash tool back to stock using ure kzd or tot file but u should be able to do steps above
TheMadScientist420 said:
If thats the case at worst lg flash tool back to stock using ure kzd or tot file but u should be able to do steps above
Click to expand...
Click to collapse
I downloaded a stock firmware for lg g3 d855, stored it in my sd, and when I launched it in recovery mode it said "Failed to sysmapfile '/external_sd/download/<name of the rom>.zip".
Mono chromatic said:
I downloaded a stock firmware for lg g3 d855, stored it in my sd, and when I launched it in recovery mode it said "Failed to sysmapfile '/external_sd/download/<name of the rom>.zip".
Click to expand...
Click to collapse
You can't flash a KDZ file by recovery you need to do this with the LG tool
_SDroid said:
You can't flash a KDZ file by recovery you need to do this with the LG tool
Click to expand...
Click to collapse
But in order to use LG tool I need to have my phone connected to the PC, right? Here's my question: is there any way of fixing my phone without having to enter download mode, or in this case, connect it to the PC?
Mono chromatic said:
But in order to use LG tool I need to have my phone connected to the PC, right? Here's my question: is there any way of fixing my phone without having to enter download mode, or in this case, connect it to the PC?
Click to expand...
Click to collapse
You can try flashing a rom like cm12 by recovery
Yea just download any rom for ure device as soon as ure done make sure u make a backup just incase
_SDroid said:
You can try flashing a rom like cm12 by recovery
Click to expand...
Click to collapse
Now my phone won't even recognize the sd card... So I can't even try with recovery mode now
EDIT: It was a particular problem with my sd. I changed it, and managed to install the cm12 and IT WORKED! My phone is alive again!!!
Now u should try mking sure u got dl mode and recovery and all
And remeber if u find any post me or anyone else has posted here helpful remeber the thanks button
TheMadScientist420 said:
Now u should try mking sure u got dl mode and recovery and all
And remeber if u find any post me or anyone else has posted here helpful remeber the thanks button
Click to expand...
Click to collapse
I checked, and I only got recovery mode. Download mode is still an issue, and my pc won't recognize my phone
Just to be sure gou are tryin to enter dl mode corectly shutxown pull battery wait 5 or 10 sec put in bat hold only vol up then plug in usb on pc or phone side. If thats what ure doin just let me know ive seen a lot of peeps say no dl mode and theyre not doin it rite. Does your p. Aknowlege it in any form make the noise apon connection unknow decice
TheMadScientist420 said:
Just to be sure gou are tryin to enter dl mode corectly shutxown pull battery wait 5 or 10 sec put in bat hold only vol up then plug in usb on pc or phone side. If thats what ure doin just let me know ive seen a lot of peeps say no dl mode and theyre not doin it rite. Does your p. Aknowlege it in any form make the noise apon connection unknow decice
Click to expand...
Click to collapse
I did everything and nothing happened. I pulled the battery, put it back, hold the up button and then plug usb and again the lg logo came for a few seconds, followed by a charging battery animation. Once I plug in the usb, I hear the typical windows sound that you get when you connect a device, but it says that an unknown device has connected.
http://www.usoftsmartphone.com/t269796.html
TheMadScientist420 said:
http://www.usoftsmartphone.com/t269796.html
Click to expand...
Click to collapse
My problem is that my PC won't eecognize the phone, so when I execute a command in fastboot mode, the window stays in < waiting for device >, and I guess that stays until you connect your device.
Also, I'm having trouble understanding the concept of fastboot mode, is it the same as download mode, recovery mode, or it has nothing to do with that?
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
Problem with this method is its not exactly easy but not bad i hard bricked my g2 and used this method but u will probly lose everything. This works but u have to follow to the t
I'll send you a flashable fix when i get home