Related
Hi everybody,
I've been searching on forums, tried multiple solutions but nothing helps. Though I'm familiar with all this, I'm just stuck on one point which makes all this unlocking process very frustrating. My phone is a Xperia P (JB) and I went to Sony's dev page in order to unlock the bootloader. Unfortunately, even if my phone is eligible for unlocking, I just cannot pass one of the point: fastboot mode.
Basically, when I power on, vol up, fastboot mode is enabled for a few seconds only (led) then disconnects from my device manager and stays with an amber (orange) led on. I just can't have my phone stay in fastboot mode. Same if I go with the command line adb reboot bootloader...
After looking for this problem on various forums, I've tried to update the drivers to (S1 fastboot) found on multiple posts, didn't help. I thought it was a problem with my PC (Win 7_64) so I tried with a fresh install in 32bits on another disk, didn't help. Tried even with Win 8 64 and 32, no chance... USB debbuging is on.
Is anyone experiencing the same problem or has anyone a solution for this? I'm just getting mad by not being able to unlock it.
Hi! I think that the driver is not properly installed! Another site I found this description to see if it helps!
Install Sony Xperia (P / U / Sola / Go) Driver and fastboot in Windows 7
Sony Xperia Driver Installation
Go to Setting > Development
Check USB Debugging
connect Xperia (P / U / Sola / Go) to PC / laptop
Open device manager
Right Click on SEMC HUSB (it should have a yellow triangle warning)
Then select “Update driver software”
Choose “Browse My computer for driver software”
Choose “let me pick from list of device driver on my computer”
Click “have disk” button
Browse to Xperia_P_Xperia_U_Xperia_sola_drivers extract folder
Select sa0104adb.inf
Approve all confirmation
Click OK
Sony Xperia Fastboot Installation
Turn off Xperia
Open Windows 7 device manager
Press and hold Volume[+] Sony Xperia button
Connect to Pc / Laptop
Right click on yellow triangle warning (device warning)
Choose “Update driver software”
Choose “Browse my computer for driver software”
Choose “Let me pick from a list of device driver on my computer”
click “Have a disk” button
Browse to fastboot driver extract folder
Select android_winusb.inf
Approve all confirmation
Done
Note:
A sign that fastboot connection is success is LED will stay in purple
In fastboot installation, open device manager before connect the device is a trick. A yellow triangle (device warning) only appears around 5 sec
It`s better to restart the windows after driver and fastboot installation
Download Support Files
Download Sony Xperia (P / U / Sola / Go) Driver
Download Sony Xperia Fastboot driver
Hi Rajen,
Thanks for your help... I've done all this before, repeated it now step by step but no luck... Cannot have my P to stay with purple light on (fastboot). It still stays purple for 3-4 seconds then amber.
Any other idea?
@swissman you should open device manager on Windows 7 first then connect your phone......when its connected youll see anerror or something sign there and click it then choose install driver from pc......navigate to those drivers and Finish....hope this helped....
Sent from Space!
Hi! Thank you... I really did that... I think almost 20 times but nothing helps. I think I've done almost everything possible (Imagine, thinking that it might be a 64bits issue and Win 7, I've even tried to downgrade to Win 7 32 and Win 8 32! ..
But nothing helps. It installs correctly the drivers, computer reboot (or even not), replug the phone with Vol up and still getting a 3-4 seconds purple LED and then disconnection. I'm getting mad as I tried almost everything I found on XDA or others but nothing helps.
The only thing I haven't tried yet is to downgrade to ICS, try to unlock the bootloader and upgrade back to JB
Ok, I finally have been able to unlock it. What I did, VM with Windows 7 64, booted in fastboot and updated drivers with "Android ADB Interface" drivers from Google directly (not the one provided with SE modifications)... My phone stays now in fastboot and has been successfully unlocked.
Don't ask me how it did happen, I'm just being happy to have it fully under my control
Anyway thanks guys for your help!
When the purple led doesn't last it means you haven't installed it correctly......the thing we are teaching you is I think, a shortcut method,just in order not to install to many files.......so I recommend installing the whole android SDK if you have time......
Sent from Space!
Thats right good work
Sent from my ST27i using xda app-developers app
After browsing forums this what I found http://forum.xda-developers.com/showthread.php?p=23794050.........that is the exact way that you should do....
Sent from Space!
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
JNiels1980 said:
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
Click to expand...
Click to collapse
When you press up on the USB icon and it freezes that it normal.. This is fastboot mode.
You now must access it over a PC after installing the naked drivers.. If it is not showing on your PC then either try a different PC or your cable is faulty.
Thanks for the quick reply.
I tried once more to enter fastboot. Same result.
But when I disconnected my usb cable to connect it to an other computer, suddenly I got this message on my tablet:
"Starting Fastboot USB download protocol"
This message didn't show up before.
I plugged the tablet back to my pc, but still no device detection in device manager, even when refreshing (So I can't install naked drivers, as it is not recognized).
My computer is a Windows 8.1 system.
I restarted my tablet again, (after disconnecting it from my pc) and followed the procedure to enter Fastboot again.
I waited for the message "Starting Fastboot ..." and then I connected the cable to my other pc (Windows 7 system)
Same result as on the Windows 8.1 machine, not recognized
You say it could be that my cable is broken. Maybe, but it's a strange coincidence that this happened when switching from ICS to JB.
I know JB for the tf201 is been out a long time, and I updated since I could. So over time, maybe my cable could be broken now. But I'm sure I had this problem (not recognizing) since then, because right after updating I wanted to do some things with ADB and so I found out I had this problem.
Hi there,
yesterday I tried to root my new Tablet Z (16GB, LTE, Model: SGP321, Firmware: 10.4.B.0.569) and it doesn't start since then.
I used an ubuntu live CD for all these tasks because fastboot doesn't work on my win 8.1 and my debian wheezy didn't have the libc-dev needed in its repositories (didn't want to mess with packets that weren't yet integrated into my OS).
What I did:
unlock the bootloader according to http://unlockbootloader.sonymobile.com/instructions
I followed the instructions here: http://forum.xda-developers.com/xperia-z/general/how-to-root-10-4-b-0-569-t2590781
a few annotations to this:
the firmware rar didn't include a "Recover.zip", so I used the boot.img directly inside the firmware rar
although sony and this CM tutorial use the "-i" parameter of fastboot, I didn't use it because it wasn't used by the tutorial
after I did the "fastboot reboot" step, the device wasn't listed anymore when typing "fastboot devices", which, I think, is okay since the device should restart then.
I think it didn't really restart, because the LED on the side glew red.
I tried to turn on the tablet but it didn't do anything (the LED kept glowing red).
I tried holding vol up and power for a few seconds (until the LED blinked first once and then three times) but the tablet wouldn't do anything except for the LED glowing red. at somepoint, the LED would turn off (I think that happened when I hold vol up and power for more than 10 sec).
I was able to let it glow red again by pressing vol up and power again and release the vol up button before the power button.
I also tried to use the PC companion on my windows machine to repair the tablet but the tablet wasn't even recognized (either using the fastboot-procedure by holding vol up while connecting the tablet nor normal plugging in...)
any ideas what I could do next?
Same Problem!
Hey wullxz!
I have the same problem. Red LED most of the time, and I cannot make ANY USB connection to the PC. The tablet won't show up in the device manager. So obviously cant use flashtool, nor PC companion. Ive tried all this volume up and down button stuff, but simply cannot get it to show up on the computer.. Tried a different USB cable as well.. Same issue. The USB port is definitely not broken. Its brand new..
Have you found any solution ? Or anyone else? Mine just got back from Sony Repair.. they wont fix it cuz they detected that Ive tampered with the original software.... meaning Warranty Lost!
Great!
hi,
i also sent mine to sony for a repair. i wrote that i did a firmware update and the tablet wouldn't boot afterwards.
i didn't try the bootloader-unlock again afterwards.
Help Needed!
Tablet Z with unlocked bootloader and rooted 10.1.C.0.370
My issues occured after a downgrade to 4.1.2.
I CAN:
1) Start my tablet, everything normal...
2) Charge my tablet
3) Go into safe mode
4) Go into fastboot mode (solid BLUE LED)
5) Use the memory card and use root apps (maybe this could help restore?)
I CAN NOT:
1) Get my PC to recognize that a USB device is connected. Neither in Mass Storage mode, Media mode, nor fastboot mode.
- Tried with several cables and computers (this is not a driver issue, since it won't show up at all in device manager)
- Flashtool obvious;y says, no device connected
2) Get in to flashmode: device blinks red for about half a second, then green for half a second, and then LED is off. Nothing recognized via USB on PC
3) Get into recovery mode
4) Update over WIFI (fails because unlocled bootloader I suppose)
Any help would be greatly appreciated!
i think you should open a new thread for your problem because it seems like it's not really similar to my issue.
you should get more/better replies in an own thread.
Oki
wullxz said:
i think you should open a new thread for your problem because it seems like it's not really similar to my issue.
you should get more/better replies in an own thread.
Click to expand...
Click to collapse
Oki thnx, will try that!
centinel_x said:
Tablet Z with unlocked bootloader and rooted 10.1.C.0.370
My issues occured after a downgrade to 4.1.2.
I CAN:
1) Start my tablet, everything normal...
2) Charge my tablet
3) Go into safe mode
4) Go into fastboot mode (solid BLUE LED)
5) Use the memory card and use root apps (maybe this could help restore?)
I CAN NOT:
1) Get my PC to recognize that a USB device is connected. Neither in Mass Storage mode, Media mode, nor fastboot mode.
- Tried with several cables and computers (this is not a driver issue, since it won't show up at all in device manager)
- Flashtool obvious;y says, no device connected
2) Get in to flashmode: device blinks red for about half a second, then green for half a second, and then LED is off. Nothing recognized via USB on PC
3) Get into recovery mode
4) Update over WIFI (fails because unlocled bootloader I suppose)
Any help would be greatly appreciated!
Click to expand...
Click to collapse
let it charge to 100%, check for flashmode drivers installed and then try attaching it to pc only when flashtool asks you to do it.
Rootk1t said:
let it charge to 100%, check for flashmode drivers installed and then try attaching it to pc only when flashtool asks you to do it.
Click to expand...
Click to collapse
Hey thanks for your reply... It wont go into flashmode... Theres something fundamentally wrong.. I cant figure out what... I leave it plugged in for 48 hours..but it doesnt really get full.. the most Ill get the orange LED.. like 50%... now its on since about 12 hours.. no LED on at all... strange..
But yea.. no flashmode... Nothing showing up when connecting the USB cable... nothing in device manager..and therefore flashtool sees nothing!
SOLVED
Problem solved! I can't believe it. Two bad(?) USB cables. Bought a new one, charges fine, flashmode fine. Flashed stock ROM.
However the Camera still doesn't work. Maybe the problem of the cable inside which may have come loose!
Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
There is no solution for this atm. The best way to fix it is to send it to the service center.
kimocoder said:
Hi there peeps!
My Xperia Z2 has gone into a bootloop, with no recovery, no boot logo, not registering ADB / fastboot drivers anymore.. BUT.. the buttons seems to work, so i may reboot it some different ways. The only indication of life it got, is the red light when booting.
Someone want to tag team with me to find the solution?
Donation will be gived to a working solution
Best regards!
Click to expand...
Click to collapse
I may have a solution. Red light usually means it cannot boot the kernel.
I have a simple fix. Follow this guide and make sure to download the firmware of your exact model and current software version number.
When you get to this step, on the right side don't check anything under 'WIPE', leave them blank. And under 'EXCLUDE', check everything except 'KERNEL'. Leave Kernel blank and the rest under exclude check them.
Proceed and press 'volume down' and connect the usb cable at the same time. Let the flash finish and boot the phone back up. Let me know how it goes.
Thanks! I'm trying your solution now, but i dont think it works... none of the drivers are either so. Give me some hours, i will walkthrough here
I can say, it is NEARLY dead i would think, but there must be a way somehow..
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
kimocoder said:
Yeah, this will not work.. It gets stuck on "HOLD THE VOLUME DOWN + PLUG THE CABLE" and both ADB and Fastboot are missing so.. It won't do anything there. Holding the Volume UP + Power reboots (that works for some reason). And the orange reboot button in the charging is working but nothing that will help me i think.
Click to expand...
Click to collapse
When the device is connected in flash mode (USB + Vol down), go to device manager and see if the device is there (may be called 'Xperia Z2" or "Unknown Device", right click and go to properties and update drivers to this. Update me how it goes. I had the EXACT same issue and it took me some time to resolve, by solving the drivers issue you can flash the kernel again without losing data.
If that doesn't work, install these drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Hi!
When my went to Bootloop the only thing that woked was using sony's Pc recovery tool.
sony's Pc recovery tool
Hope this helps you out
Try Software repair on the new Xperria Companion
http://support.sonymobile.com/global-en/xperiaz2/tools/xperia-companion/
Both Sony Companion and Sony Emma are not registering the devices, but after fiddling around with VOLUME UP, VOLUME DOWN and lots of trying, at some point the device manager finds a unknown device. "hiredantispammer" may got the solution, but i will try all posted solutions right away! Post update soon
1. On "VOLUME DOWN + PLUG" the Device Manager refreshes, and the Z2 got the "red light" -- but Device Manager does not show any connected devices nor drivers needed.
2. The Sony Companion does not find the device either.
But.. i was reading about some Windows 10 driver problems, so i will try switch to Windows 7 x32 to ensure the drivers are working correctly.
Another thought.. Is it some way to put a "update.zip" on a sdcard for force installation of new kernel or anything?
Yeah, the solution is right. Hopefully Win 7 solves your driver issues. I had to reformat my laptop and install Win10 again because of driver issues when I have the exact same issue as you. Hope you get your phone working again!
Sent from my D6503 using XDA-Developers mobile app
And no, there's no other safe way to reflash the kernel. Even with an unlocked bootloader, you need fastboot drivers.
This worked for me.
Grab your original cable and make sure the phone is charged to st least 80%.
Start the pc companion and the repair program.
Hold the down key and connect to the computer.
In around 20 minutes the phone is repaired
Hope this helps.
It is important to use proper cable and not any old thing laying around. Mine would not connect until i got the original one.
Ah, charge your device fully. Reboot Windows 10 in safe mode and disable driver signature. Install device drivers. Use Sony PC companion or flashtool to fully reflash the right firmware for you device. You are still able to turn it off and on, so it should work if you do it right.
Best to first flash just the kernel and see if it boots, if it doesn't since you have the firmware files, flash everything and don't wipe data.
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.