Related
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Martyn.h said:
Firstly I apologise if this has been covered anywhere - I read a load of posts and did a load of searches but came up empty handed about this specific issue.
I bought a Galaxy Ace (GT-S5830 Baseband:S5830NEKA3 OS:2.2.1) as a dev device and it's been working fine up until today, and at some point it decided it doesn't want to be able to connect to my computers. I've tried three different computers, two different operating systems, and ever tried installing Kies (urk) with no luck.
The phone can charge over USB, saying that it's charging over AC, but that's all that happens.
I can't boot in to recovery mode as holding the power+middle button+vol up just gives me a ramdump message.
Can anyone help me out?
Click to expand...
Click to collapse
When phone is turned off. Press and hold home+power/lock button untill it reaches recovery menu.
Check - that works. Thanks.
I'm now unsure as to how to proceed - neither adb devices nor fastboot devices are reporting anything back.
Connect device to pc. Open device manager (windows). Remove all drivers related to the ace and Samsung.
Remove the device and reboot the pc. Then connect the device. Windows update will detect the device and install the necessary drivers. If it doesn't automatically do that then open up device manager and install them manually by right clicking on the device and selecting update drivers from internet.
From the Galaxies to your Ace...!!
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Martyn.h said:
Thanks for your reply.
In windows there's no sign of any Samsung or Galaxy Ace drivers. Plugging it in to my Kubuntu machine gives me identical lsusb results as when not plugged in.
Have done a data wipe, checked that USB debugging is on and tried different cables
think it's screwed.
Think I could stick a ROM on the SD card and flash it? Would that work?
Click to expand...
Click to collapse
hmm.. kies didnt work right? So i guess only option IMO would be card reader or CWM
Yep , the phone's USB port is frayed
This was sent from a Galaxy Ace. Problem?
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
JJ2197 said:
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
Click to expand...
Click to collapse
It is not bricked. I'm still not convinced you are on jellybean bootloader as there is not a version of Cwm that works with it and you still have cwm.
First thing you need to do is confirm what bootloader you are on before you really brick it.
Switch the machine on and look where the tegra logo is. If it is bottom center you are still on ICS bootloader and if it is bottom right it is jellybean bootloader.
We need to know this to point you to the correct version of twrp to flash to start.
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
JJ2197 said:
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
Click to expand...
Click to collapse
Really you are going to need to get into fastboot and get the drivers installed.
I'm guessing you know how to get into fastboot but if you don't then hold down volume down and power button for 10 seconds when off. When the icons appear press volume down to go over to the USB icon and then press volume up. It will freeze on the prime screen at this point and that is fastboot mode.
Now go into device manager and try to install naked drivers. If this does not work then try in on another pc. If this still does not work then you have a faulty cable. A faulty cable can still charge the tablet but will not work in pc.
At this moment my money is on your cable being faulty over something you said earlier about having to play with it. You can buy a replacement cheaply on eBay.
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
JJ2197 said:
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
Click to expand...
Click to collapse
Without getting any drivers installed at all there is not much we can do.
Cwm doesn't support external cards and even tho I could make you a flashable zip to install twrp you couldn't get it on there.
If you can get back into the machine at all then we could use wireless adb and send the files over that way or use es file explorer to access network shares and take them over.
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
JJ2197 said:
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
Click to expand...
Click to collapse
This normally happens with a faulty cable and as you said you think the pins are faulty so it could be that instead.
You could try going to the wipe icon where the fastboot icon is and try running that. If there is a rom still on there it will try to factory reset but I can't guarantee that will work but at this point you have nothing to lose.
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
JJ2197 said:
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
Click to expand...
Click to collapse
I'm not talking about in CWM. I'm talking about the wipe icon where the fastboot icon is also.
Isn't the factory reset the same in both CWM and bootloader?
JJ2197 said:
Isn't the factory reset the same in both CWM and bootloader?
Click to expand...
Click to collapse
No
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
JJ2197 said:
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
Click to expand...
Click to collapse
It reformats the partitions back to stock except the system partition.
I'm not saying this is going to work for you. Just as you are your only other option if the pins are broke is to get it sent back to asus and they will swap out the whole mobo so you might as well have a go.
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.
I have a mtk6580 the phone only stays in fastboot for 10 seconds and doesnt respond to any fastboot comands.I don't think its a driver problem because it works fine on another phone which is also a 65xx. I also tried a linux vm. With the same results. Mostly i just want to root the phone. Even set my bios so the usb are recognized as usb 2. As well i tried a lot of one click solutions to get root. Also miracle box and mtk-tools. The phone has no reset button and the battery cant be removed. Please help.
smackpotato said:
I have a mtk6580 the phone only stays in fastboot for 10 seconds and doesnt respond to any fastboot comands.I don't think its a driver problem because it works fine on another phone which is also a 65xx. I also tried a linux vm. With the same results. Mostly i just want to root the phone. Even set my bios so the usb are recognized as usb 2. As well i tried a lot of one click solutions to get root. Also miracle box and mtk-tools. The phone has no reset button and the battery cant be removed. Please help.
Click to expand...
Click to collapse
I take it you're on Windows?
Ya i tried a linux usb stick but my bios won't let me boot from usb. Im getting shut down at every step
Ok i tried a linux usb stick still no results
Get fastboot and adb package?? Maybe that's the problem
Hi all,
I tried to flash the latest TWRP but for some reasons it's messed up. Now I can't enter recovery mode and just wondering if there is a way to re-install it.
I tried to do it via Fastboot mode but my PC(windows 10) can't recognize the phone when in Fastboot mode. I tried several ways(e.g. reinstall USB driver, remove / install driver via device manager, etc.) but no luck.
Any help/suggestion is appreciated.
Try with the original cable. It will work for sure. I had almost the same issue, tried various drivers, etc. Once I've connected the phone with its original cable, it was recognized instantly.
Strange, other people say, the original cable is bad quality??
I would use a different cable but an usb port on the mainboard no a front usb port.
Also i do all the adb und fastboot stuff on a linux machine, it's less struggeling with drivers then.
The original cable still works though, I'm not so sure what bad quality can that be... And yes, I haven't used it in these 3 years more than half of the time. In the past year I was using a 3m Ugreen cable which didn't do the trick for drivers, still working well.
However, with some changes in the kernel or whatsoever, the original cable doesn't charge the phone anymore while connected to the computer, but it ensures a good data transfer.
PS: USB type-C is more complex and not standardized for all manufacturers, which is a bit surprising, but that's it.
eqt2010 said:
Hi all,
I tried to flash the latest TWRP but for some reasons it's messed up. Now I can't enter recovery mode and just wondering if there is a way to re-install it.
I tried to do it via Fastboot mode but my PC(windows 10) can't recognize the phone when in Fastboot mode. I tried several ways(e.g. reinstall USB driver, remove / install driver via device manager, etc.) but no luck.
Any help/suggestion is appreciated.
Click to expand...
Click to collapse
you need to format whole phone in oder to be recognized by pc.try first deleting all drivers for x2.go to windows in device manager,reboot pc and reconnect phone to pc by using usb type c cable
thank you for all the recommendations. I will try original cable and other PC using Linux and see if that works.
Update: My windows 10 PC installed the wrong driver when phone is in fastboot mode. Working fine now after deleting it from Device Manager and reinstalling.