Related
I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
npo123 said:
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
Click to expand...
Click to collapse
Mine did this the first time. This is where the phone is never commanded to boot into S/W update mode so at least this is not a step where it can be bricked, as no update has actually occurred yet.
This is how I fixed it and got mine to update. Use a different USB port on your computer. Yes there are different as some are on internal hubs. The update must have a direct USB port with no hubs in between. I also reinstalled the drivers through the LG Update program and not from the LG website. When I did this and plugged in my phone about eight new devices were detected and installed as opposed to about two the first time around. Also, make sure your phone is in debug mode in Android application settings.
Then make sure you disable any anti-virus programs and turn off the Windows firewall. Then use ctrl-alt-delete and close down any programs running. Also go to the taskbar and click on the up arror (if Windows 7) and right click on each icon and see if you can close it down. Also, unplug all other USB devices (even a mouse if you don't need it) as they can interfere with communications between the updater program and your phone. The only USB device I left connected to my computer was the keyboard.
The LG Updater must be run in Admin mode. If when you run it you get a Windows warning asking you if it is ok for this program to make changes to your computer then it is launching in Admin mode. If not right click the LG Updater icon by clicking Start>All Program>LGMobile Support Tool>LGMobile update. Right click the last item and run it in admin mode. Again this is assuming you are running Windows 7. Admin mode is not necessary for Windows XP.
If all the drivers get loaded properly and you are not on a flakey USB port then at 4% the updater instructs the phone to reboot into S/W Update mode and that is where the real magic happens if you are lucky.
coreycollins3066 said:
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
Click to expand...
Click to collapse
Use another USB port and try again. At various points in the update the updater resets the phones usb port and it has to reconnect. If it doesn't connect don't do a battery pull. Just try removing the USB cable and reinserting it. If you hear the computer beep wait a bit and then click restart on the updater. Hopefully it should see the device this time and continue the update.
My phone is dead after switching external sd with internal sd via CWM script .zip file and a little tinkering in the phones system files.
(“I have done this before with success but had just flashed new firmware, and in the rush I was in wile doing it I obviously did something majorly wrong and super bricked my phone”)
After rebooting to complete a step I was doing, the phone did not turn back on, the pc does not detect it properly anymore, no button combinations work, such as pressing vol up when connected without battery, power button and pressing up + vol. No RESPONSE:.
when plugged into the pc it just flashes "OMAP4430 device" but appears and disappears all the time in device manager, now I know all drivers are correct and how to go into download mode, recovery mode and every trick you can with the O3D but none work anymore, phone does not turn on and it only recognizes it for a second showing “OMAP4430 device”.
PS Sorry for the new thread but I have searched the forum and the internet with no real answers, it would be great if there’s a fix for this situation or is my O3D dead to the world never again to be reborn.
NOW IF ANY ONE HAS MANAGED TO FIX A TRULY BRICKE O3D LIKE MINE PLEASE HELP!!!!!!!
sounds like a harware brick i did that to my thrill had to take it in
That’s what I’ve been fearing, my other issue is that the phone is actually a LG thrill from at&t I just call it a O3D because in Australia were I live we only have O3D, and let’s face it they are basically identical, any way would that mean I would have to send it back to the USA for repair?
well is it under warenty? if so youll have to send it to who ever you bought it from. if it isent ull have to get a new logic board and relace it your self or have some one relace it. or send it to lg to fix it
I had a similar problem when installing rom. KDZ:
http://forum.xda-developers.com/showthread.php?t=1473781
http://forum.xda-developers.com/showthread.php?t=1244490
The problem with "OMAP4430" device I solved by connecting the phone to the computer via a cable from HTC Wildfire (such problems I had with the original cable, LG).
It can change the cable will solve the problem.
I wish you luck.
(google translate)
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
trust me i totaly bricked my phone i tryed every trick pulling the battery out and putting it in in download mode problem was omap didnt even show up just the other one and it would flash on and off way to fast to click on it in device manager then it would just stop.
So did you end up taking it in?, it should still be under manufacture warranty well hopefully I got it in october and I don’t even think the O3D has been out for a year yet.
defcomg said:
You have to remove the battery when omap flashes on device manager let go off the button and push and hold it agen it should stay. try this time omap like have your cursor ontop of omap4430 as soon as it appear quickly right click properties and find the driver unplug reconnect it will install the driver when it detects it agen i think with this phones its impossible to hardware brick the phones if only it was easy like samsung just plug in download mode let drivers install and push start button done. if flashing a phone was like a movie lg would be inception
Click to expand...
Click to collapse
The problem is that it only starts flashing with the battery removed so, and I can’t get into download mode at all, which is when it normally stays there and detects it properly, otherwise the drivers are all installed.
If it flashes omap its not a complete brick. If all fails try the resistor cable. You can find a post around in the forum
I have tried the resistor cable using 910k resistor, and I even checked it on the multimeter and it reads 908k resistance which should be ok since I think you can allow for a 1% difference.
I could figure out that ur device can be detected as OMAP, this means it isn't bricked totally, please be sure U remove UR battery, connect ur USB--phone side, then press volume up and insert the USB--pc side while pressing the button and continue pressing while ur pc is installing, first it will show OMAP, then after 10-20 sec it will show COM added, don't stop pressing until it finds the COM and installs it, then directly stop pressing and insert battery and don't try to turn it on and start flashing as usual
try to use other USB cable model like sony ericsson, it never failed me
hoping U will be lucky
See the problem is that no button combination work on the phone, pressing a button is like talking to a wall you get no response lol.
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
cephasara said:
I have the same issue and I bought my phone off of Craigslist.. is there anything I can do? I cannot send in via warranty because I do not know when the phone was bought.
Click to expand...
Click to collapse
its hardware bricked need a new logic board sorry to say
Hi, i had the same problem while upgrading to gingerbread. What windows version are you running? Ihad the same problem using win 7 x64. Got to a win xp computer with no lg software installed and used the tutorial of unbrick from this forum. had to try several times, but at least step by step my phone got back to life. Main thing is to get omap drivers installed on XP with no battery. Then taking the other steps mentionened under unbricking your phone in this forum.
Hope it helps
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
KurdX said:
I have the exact same problem and NOTHING works.
Just to clarify everything, you guys had the same problem where the OMAP4430 device appears and disappears over and over again in device manager and by doing what you all describe, the phone got brought back to life?
Because none of those things work for me, I even tore an old sonyericsson phone apart to get the phone pins connected to my O3D battery and see if the old phone turned on, which it did, so the battery does work.
I installed the OMAP4430 driver without any problems and I guess from here, everything seems to be working for you other guys, right? Because the OMAP4430 is still getting connected and disconnected 10000 times BUT as a "Known" device which has the driver installed.
No need to answer this with "you need to send the phone to LG". Just want to see if I'm on the same track as the guys who got their phone working.
Btw, mine got bricked when formatting the external SD card with CM. Seems as if CM formatted something else..
Click to expand...
Click to collapse
So let me get this straight. Like a few months ago, there was a way to completely destroy your phone:
install CWM and run an OTA update on stock rom.
That completely ruined my phone. It was explicitly said that no unbrick method is available.
Now I hear several people reporting yet another unfixable brick, caused by
- Erasing your SD card through cyanogenmod
- Formatting /data ?
All the available methods of unbricking are said not to work. And by those methods I mean
- Opening recovery and do a factory reset (recovery can't be opened I heard?)
- Connecting to a Windows 7 PC with battery out and volUp depressed (device disappearing reappearing)
- Connecting to a Windows XP computer With battery out, volup depressed (Same problem as Windows 7?)
So to put it simple:
Doing some things with CWM OR CyanogenMod can render your phone unfixably bricked. There is a genuine risk in hard bricking your phone when you have CWM and/or Cyanogenmod installed.
I'm not going to install either of those for that very reason.
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
thealgorithm said:
If the omap 4430 is detected when connecting the phone, then the phone should be recoverable. Try another pc system and then use the official lg recovery tool entering the imei number which should hopefully restore the stock rom.
Can i clarify whether or not any other devices appear in the device manager (Remember to hold the up button without battery until these appear and then insert battery after
The entries in device manager that should also appear would be something such as the following (This would probably vary based on whether in normal connection mode or flash mode)
PORTS
LGE android platrom usb serial Port (Com x) x may vary on system
UNIVERSAL SERIAL BUS CONTROLLERS
LGE Android Platform Composite Usb device
Click to expand...
Click to collapse
They said that the omap driver keeps appearing and disappearing. You can't do anything if a driver does that!
Sent from my LG-P920 using XDA
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
Interesting problem. I have bricked my phone a bunch of times and have always been able to get back to at least "download Mode". The method I use to go to "Download Mode" is With the usb cable plugged into the computer only, power off the phone. If phone wont power off, or stay powered off, pull battery, then put battery back in. Now hold vol down and vol up buttons only, keep holding these buttons as you plug the usb cable into the phone. In 3 seconds the download screen should appear. I hope this helps you get your phone back.
JaimeZX said:
Hey gang - I've been traveling for work and just have some crappy slow satellite wifi for access. The phone has been great because I can use wifi calling and all is good.
A few weeks ago my phone crashed. When I rebooted I was at the "touch android to begin" screen. Well... fix permissions and clear caches didn't work.
So next I restored a backup from CWM.
Unfortunately, after that the phone hangs at the initial Samsung splash screen.
Now, stupid me didn't go an a six-month trip with the Android software on my laptop - so I had to wait for my wife to mail me a thumbdrive that has SOC, HOC, drivers, & etc. on it in order to do anything.
In a previous thread from when this first happened, you all recommended I use HOC to flash the phone back to stock. Which now that (yesterday) I got the thumbdrive in the mail, I am happy to do.
My problem comes from the fact that the phone hangs at the Samsung splash screen seemingly no matter what I do... zadig.exe doesn't recognize the phone on the USB port (just "unknown device") and therefore HOC can't do anything (I think?) Furthermore, I can't even get back into recovery or download mode; at least not with the several techniques I've tried so far.
Recommendations? Or am I hosed?
Thanks in advance,
Click to expand...
Click to collapse
This sounds like a time where a jig would be helpful. Any chance you can have your wife order one, and send to you? http://www.youtube.com/watch?v=D7I4dFX_iJ4
This should put you straight into download mode, and you can then flash.
Thanks, guys. I continued fiddling and got the phone into DL mode.
I also noted that when plugging and unplugging the phone, it would show up in zadig as "unknown device."
I tried to load the drivers on that, but (a) it still shows up as "unknown device" and (b) when I run HOC it doesn't see the phone under the list of compatible devices.
So.... still kind of stuck.
Any more ideas?
Oop. duplicate post
It's been awhile since I've played with the one clicks, but, "serial gadget" is what I remember seeing when I used them.
Right. MORE messing around later and "Serial Gadget" is it.
That said, I still think I have a driver issue. I have tried uninstalling and reinstalling the zadig-recommended drivers for Serial Gadget several times. I also tried manually installing the drivers from Super One Click.
Anyway, now when I load up HOC I get the green <<connected>> at bottom; but then sometimes it wants me to install the drivers (again) and sometimes it gets past that part, but then goes to
Flashing Kernel: 0%
...hangs there for about 10 seconds and then
Failed!
So... driver thing you think?
Thanks again,
If you reboot the phone after the 0% hanging for 10 seconds, does it go to the yellow exclamation mark screen? If so, just reflash again and you should be back to working... both my and my wife's phone always did that when I had to flash a kernel.
That's just another download screen that theraze is describing.
Exacatly. But the alternate download screen always came up after restarting the phone after a 'failed' flash where it stayed at 0% where it was successfully communicating through the cable. That just meant to not break the drivers or unplug anything... just reboot fast and finish up quickly.
Okay - I can definitely try that! It had not occurred to me to try and reboot the phone right then.
Question, though - when I get the "Failed!" Then HOC essentially hangs, when it says something along the lines of "ending session..." and never progresses from there. So how do you "restart quickly?" Because I have to like, close and reopen HOC. I guess I will see if it succeeds at ending the session when I reboot.
I will try it again. Strange though, sometimes HOC accepts the existing driver (I managed to DL the Samsung driver installer) and sometimes it wants to reinstall "WinUSB." does that make sense? Is the WinUSB an acceptable one?
The winusb is the right driver for heimdall, it doesn't like the Samsung driver.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Samsung drivers and the one click drivers clash. Yes, uninstall Samsung completely if you want to use the one click.
Hm. Thanks for that - might be part of the problem.
Dunno what I did differently, if anything, but last night I tried flashing again and this time it went through! I was very glad to see the whole HOC process completed successfully!
So anyway - thanks so much for the help, guys.
I've had the phone for over 6 months, it'd belonged to my sister before and everything was fine. I got a new phone recently and stopped using J. Just turned it off and put aside. I turned it back on today, it was working fine, until I wanted to do a wipe, nothing happened afterwards. I've had 360 security installed, thought it may be causing problems, so I uninstalled it. Then the phone was supposed to reset and so it did, but it didn't start again. Until this moment it hasn't shown even one sign of life, no random vibrations, no diodes flashing. I read about taking out the battery, powering it for hours, turning on with power+vol, power-vol, whatever. Nothing worked. When I connect it to the PC, it recognizes that something is being connected, tries to install a driver but immediately I get a message that it's failed. Any idea how I may solve this?
pucykoks said:
I've had the phone for over 6 months, it'd belonged to my sister before and everything was fine. I got a new phone recently and stopped using J. Just turned it off and put aside. I turned it back on today, it was working fine, until I wanted to do a wipe, nothing happened afterwards. I've had 360 security installed, thought it may be causing problems, so I uninstalled it. Then the phone was supposed to reset and so it did, but it didn't start again. Until this moment it hasn't shown even one sign of life, no random vibrations, no diodes flashing. I read about taking out the battery, powering it for hours, turning on with power+vol, power-vol, whatever. Nothing worked. When I connect it to the PC, it recognizes that something is being connected, tries to install a driver but immediately I get a message that it's failed. Any idea how I may solve this?
Click to expand...
Click to collapse
have you try fastboot/flashmode...
what driver shown on your device manager?
pucykoks said:
I've had the phone for over 6 months, it'd belonged to my sister before and everything was fine. I got a new phone recently and stopped using J. Just turned it off and put aside. I turned it back on today, it was working fine, until I wanted to do a wipe, nothing happened afterwards. I've had 360 security installed, thought it may be causing problems, so I uninstalled it. Then the phone was supposed to reset and so it did, but it didn't start again. Until this moment it hasn't shown even one sign of life, no random vibrations, no diodes flashing. I read about taking out the battery, powering it for hours, turning on with power+vol, power-vol, whatever. Nothing worked. When I connect it to the PC, it recognizes that something is being connected, tries to install a driver but immediately I get a message that it's failed. Any idea how I may solve this?
Click to expand...
Click to collapse
if so, u may contact ur product manufacturer or where did u buy ur xperia j.,.