Related
My laptop shows LGE Android Platform USB Modem instead of LGE Virtual Modem after checking the debugging option.... Are both the options same?
ckand said:
My laptop shows LGE Android Platform USB Modem instead of LGE Virtual Modem after checking the debugging option.... Are both the options same?
Click to expand...
Click to collapse
It isn't same. It's two different thing but it tackles all LG drivers
Well, I've got the same. And I can't get adb to work. :/
droidaem said:
Well, I've got the same. And I can't get adb to work. :/
Click to expand...
Click to collapse
drivers are installed properly? debbuging is ON?
mastershefis said:
drivers are installed properly? debbuging is ON?
Click to expand...
Click to collapse
Yeah. Reinstalled drivers many times, but can't get it to work. I have already made a thread with this, but... no much help there.
droidaem said:
Yeah. Reinstalled drivers many times, but can't get it to work. I have already made a thread with this, but... no much help there.
Click to expand...
Click to collapse
So describe whole your problem. Maybe mistake will be elsewhere.
droidaem said:
Well, I've got the same. And I can't get adb to work. :/
Click to expand...
Click to collapse
it's the same for me but adb is working ok. there must be something you're missing i suppose
Guys without disabling the LGE virtual modem i cant update ma phone wth official GB update...... So pls help
ckand said:
Guys without disabling the LGE virtual modem i cant update ma phone wth official GB update...... So pls help
Click to expand...
Click to collapse
It's normal way to disable LGE VM .. don't worry & panic
I'll post the link.
http://forum.xda-developers.com/showthread.php?t=1155161
(maybe the OP has the same problem)
droidaem said:
I'll post the link.
http://forum.xda-developers.com/showthread.php?t=1155161
(maybe the OP has the same problem)
Click to expand...
Click to collapse
Did u tried on another PC?
mastershefis said:
Did u tried on another PC?
Click to expand...
Click to collapse
No.. But I'm pretty sure, it'll work.
I will try it another time.
droidaem said:
No.. But I'm pretty sure, it'll work.
I will try it another time.
Click to expand...
Click to collapse
Put this file http://www.megaupload.com/?d=RTEY0Q97 to the TOOLS folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back).
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
mastershefis said:
Put this file http://www.megaupload.com/?d=RTEY0Q97 to the TOOLS folder of the SDK (they were taken out by Google in the R08 version for some reason and need to be put back).
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
Click to expand...
Click to collapse
I already had these files
yea.. i too am having the same problem ..
the device manager shows android platform usb modem.. but not LGE virtual modem, as in this thread.. (this modem needs to be disabled)
http://forum.xda-developers.com/showthread.php?t=1060121
I'm a little paranoid about bricking the phone and I didnt wanna take the risk needlessly ..
Is it enough to disable the usb modem and continue?
ajphoenix said:
yea.. i too am having the same problem ..
the device manager shows android platform usb modem.. but not LGE virtual modem, as in this thread.. (this modem needs to be disabled)
http://forum.xda-developers.com/showthread.php?t=1060121
I'm a little paranoid about bricking the phone and I didnt wanna take the risk needlessly ..
Is it enough to disable the usb modem and continue?
Click to expand...
Click to collapse
well, I didn't disable anything when I was upgrading my phone with KDZ, and it worked - used this so many times (except the last time when I got an error - read my signature to see my phone's location )
don't wan't to scare you, but I also don't take responsibility about this.
maybe someone with smarter head can write here smth?
to risk .. or not to risk ..
guess i'll just go for it then ..
*hoping for the best*
cant connect to pc
dude. i have updated with 2.3.3 and now connecting to pc suite it doesnt connect it shows phone not responding..,
pls help me
Tried the one click root
My phone is stuck at the " Downloading.... Do not turn off target !! "
How long should this take ?
Am I screwed ?
Thanks,
John
jjmstang said:
Tried the one click root
My phone is stuck at the " Downloading.... Do not turn off target !! "
How long should this take ?
Am I screwed ?
Thanks,
John
Click to expand...
Click to collapse
Try reading through the thread. Several ppl have had your same issue and resolved it by reinstalling drivers, using the cable that came with the phone and/or changing usb ports. And make sure ti read instructions in tool window. As it states in the tool OP the root step is not a one click. You gotta do some work
BEAST......... that is all
jjmstang said:
Tried the one click root
My phone is stuck at the " Downloading.... Do not turn off target !! "
How long should this take ?
Am I screwed ?
Thanks,
John
Click to expand...
Click to collapse
You can also try the files in my signature. If you need to go back to root. Also download the updated USB drivers. You should be able to pull the battery and get in download mode again.
DarkMenace said:
You can also try the files in my signature. If you need to go back to root. Also download the updated USB drivers. You should be able to pull the battery and get in download mode again.
Click to expand...
Click to collapse
Thanks, I did get it too root earlier today. I missed a step ( user error ). The one click root process worked great after I got my head out of my butt.
Thanks to the developers here for all their work.
-John
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Edit:
No luck yet, but I remember a way I did before.It's not quite the same situation but...
I left the kindle on for a long time, and pressed the power button beyond the point from where it showed out of battery screen. It had like no batterypower at ALL. Yhen i plugged back up to PC and...
I'm trying it out now, if anyone is in the same position as me do the same!
Remember,charge only about 1-2%,if it doesn't work!
Thank you guys a LOT for support! I am in process of getting adb and stuff to work on linux...
let's see how it goes...
ferrouskid said:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Click to expand...
Click to collapse
Does adb work ?
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No, unfortunately!
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No,
well
ferrouskid said:
No,
Click to expand...
Click to collapse
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
jimyv said:
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
Click to expand...
Click to collapse
Man any ideas?
Thanks
Hashcode and I have talked about it. There IS a working fastboot, but you can't get to it with a fastboot cable, and it's very buggy and not too useful. So it sounds like you are SOL. Sorry. :/
Sent from my Amazon Tate using Tapatalk
?
ferrouskid said:
Man any ideas?
Thanks
Click to expand...
Click to collapse
Fastboot system files?
jimyv said:
Fastboot system files?
Click to expand...
Click to collapse
Wait I know android cowboy had the same problem some time ago. I'll ask him.
ferrouskid said:
Wait I know android cowboy had the same problem some time ago. I'll ask him.
Click to expand...
Click to collapse
If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.
http://forum.xda-developers.com/showthread.php?t=2588608 QUOTE=ferrouskid;53393803]If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.[/QUOTE]
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
HI, you did the factory reset, too?
ARUSTORI said:
HI, you did the factory reset, too?
Click to expand...
Click to collapse
I didn't, though you should try my solution (I'd got a black screen after the grey logo).
I'm sorry but I won't try the factory reset to see if it works
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Ause said:
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Click to expand...
Click to collapse
I'll be over the moon if this works, adb is installed, now waiting for flat kindle to charge...
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Please expand on that. Thank you so much.
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
ferrouskid said:
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
Click to expand...
Click to collapse
Connect your device to your computer.
By typing "adb devices", you should get this output :
Code:
List of devices attached
???????????? no permissions
Then type "lsusb" and note the ID of the Google Device (Should be 18d1:0001, but I'm not sure you will get the same).
Edit the file "/etc/udev/rules.d/51-android.rules" and add the following lines (If the file doesn't exists create it). Replace 18d1 and 0001 with the values you get in lsusb :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"
Run "sudo chmod a+r /etc/udev/rules.d/51-android.rules".
Restart your computer and you should be access your device using "adb shell".
Follow this post to restore your device : http://forum.xda-developers.com/showpost.php?p=53388919&postcount=23
Crap. I dont have access to a linux OS..ill have to call amazon i think.
Sent from my LG-D800 using XDA Premium 4 mobile app
i hard brick my phone yesterday. trying to flash bootloader with flashfire. (the lazy way) thats what i get. anyways could not turn on n6p, tried charging it for a couple of hours, try holding power button for 30 seconds, try power + volume . tried holding all buttons. nothing work.. read some threads saying its done. look for new phone or send to get repair. then i found tenfar thread. long story short. i used some of tenfar info and rwj5279955.. so big thanks to these two users
here is what i did to get my N6p to turn back on.. brick by bootloader.. this is my first how to .. bear with me. please.
you will need the following https://drive.google.com/file/d/0By19rrbnQfVUVFZEVUZqQzY1RWs/view?usp=sharing
Qualcomm drivers
QFIL software
3 files, patch0, prog_emmc_firehose, rawprogram0 .. for this to work
1. install qualcomm drivers, Connect phone to pc, open Device Manager. if you see under com port Qualcomm USB loader or something along those lines. your good, go to step 2. if not disconnect phone hold power button for 10 seconds, wait for 5 seconds connect phone to pc. check if in com ports you see Qualcomm drives. if you can not get qualcom drivers on com port. just stop. its not going to work..
2. extract the three files. in a folder somewhere easy to remember.
3. install the QFIL software, . once install run QFIL.
4. in QFIL software
if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008
Select Build Type: click Meta Build
Select Build :: patch0 ... if for some reason patch0 doesnt work try rawprogram0
Select Programmer:: pro_emmc_firehose
hit download ...if the blue bar get to half way mark your golden. its going to always fail. the trick is to get the blue bar at least half ways. then you disconnect phone, hold power button, it should turn on.. then you ADB what ever you need to do.
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
sorry for this horrible guide.. it work for me.. hope it works for you..
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
DEVILOPS 007 said:
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
Click to expand...
Click to collapse
Windows
Lw00d said:
Windows
Click to expand...
Click to collapse
Luckily there's already alternative for linux
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Clarkeofcurtis said:
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Click to expand...
Click to collapse
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
KLit75 said:
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
Click to expand...
Click to collapse
hard brick. phone does not turn on at all
Lw00d said:
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
Click to expand...
Click to collapse
I have done as stated, however when attempting to select build after clicking META BUILD, I have to change the browsing options to ALL FILES from META BUILD CONFIGURATIONS otherwise I can't find anything?
Once selected Patch0, I proceed to select programmer path, but then my download content isn't clickable please?
Select build type click flat build. See if u could click on download
Lw00d said:
Select build type click flat build. See if u could click on download
Click to expand...
Click to collapse
I can start it VIA flat build, however I get this error
Now try with meta build
Lw00d said:
Now try with meta build
Click to expand...
Click to collapse
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Clarkeofcurtis said:
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Click to expand...
Click to collapse
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Clarkeofcurtis said:
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Click to expand...
Click to collapse
It's on first post
Lw00d said:
It's on first post
Click to expand...
Click to collapse
Getting this
Clarkeofcurtis said:
Getting this
Click to expand...
Click to collapse
did you do this..
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
also try extracting all these files into the folder you made .. this includes the three files .. https://drive.google.com/open?id=0By19rrbnQfVUbFZSc3A3VXhGRzQ
Thank you so much! I messed up my 6P when I tried to flash a bootloader image via Flashfire. I hadn't been in a brick this bas since the good old days of Gingerbread and ROM Manager! For anyone else having similar issues, I got my dead 6P to be recognized as QHSUSB_bulk eventually in Windows 7. I then edited the rawprogram0.xml file (from OP's link) in a text editor. I removed the entries for all the other partitions I didn't want to overwrite (like system and vendor and userdata), leaving only the sbl1 (secondary bootloader, the part of the firmware that actually boots into the system/recovery/bootloader when the device is first powered on) partition entry - because that's what Flashfire said it had flashed the entire bootloader image to. Doing a bit of research, I found that our bootloader image is actually just many different small partitions all grouped together into a single image file. I couldn't figure out how to unpack the bootloader image, so I downloaded a full firmware OTA zip from Google, and lo and behold, there was a "bootloader.sbl1.img" (along with other small partitions) file in the OTA zip. I changed the sbl1.img entry in the rawprogram0.xml file so that it correlated with the filename "bootloader.sbl1.img", I moved the image file into the same folder as the rawprogram0.xml, and then I was able to restore my device to it's previous functionality using the "flat build" download configuration in QFil, though the whole process did take me like 3 hours. Lesson learned - screw using Flashfire for bootloader images.
ERROR: Could not access "C:\temp\vendor.img" with access mode 'rb'
When I'm finally lucky, rebooting, replugging the phone, it looks like it might flash...
...then I see this.
I've given all permissions to all users for full control, on the file, I've run time program as administrator, I don't know what else to do. If it can't open the file, I can't flash my phone. I'm not a Windows administrator so I don't really know what to do to get this to work and I can't find any hints on the forums.
Hi All,
Have been having a strange issue, not sure if this is a software related or hardware related issue. Unable to charge my phone unless i restart with charger connected added logcat for details, below is a sample snippet.
08-22 14:31:47.125 9232 9232 D UsbManager: setPortRoles Package:com.android.settings
08-22 14:31:47.126 1693 1712 I UsbPortManager: Setting USB port mode and role: portId=otg_default, currentMode=dfp, currentPowerRole=source, currentDataRole=host, newMode=dfp, newPowerRole=source, newDataRole=device
08-22 14:31:47.126 777 777 I [email protected]: filename write: /sys/class/dual_role_usb/otg_default/data_role role:2
08-22 14:31:47.127 777 777 I [email protected]: written: host
08-22 14:31:47.127 1693 1808 E UsbPortManager: otg_default role switch failed
Tried writing data to "/sys/class/dual_role_usb/otg_default" in adb root mode but was unable to do it. I guess this is related to Qualcomm drivers.
Please help me if any one has any idea.
If you are on a custom rom, it could be a kernel issue
TGDgr8est said:
If you are on a custom rom, it could be a kernel issue
Click to expand...
Click to collapse
Thanks @TGDgr8est i am on custom rom, i tried to fix the settings but unable to do so. Tried a couple of alternate Kernels, still no use.
saratsarat7 said:
Thanks @TGDgr8est i am on custom rom, i tried to fix the settings but unable to do so. Tried a couple of alternate Kernels, still no use.
Click to expand...
Click to collapse
No gravity kernel workers fine for me when I had this issue on derpfest
TGDgr8est said:
No gravity kernel workers fine for me when I had this issue on derpfest
Click to expand...
Click to collapse
Tried it again, unfortunately it dint work. Also i also started getting that error in DerpFest. Can you tell me what steps you followed when you had that issue.
If it isn't a usb issue then. I flashed ngk installed app and set things up. I use these settings . When flashing wipe davilic cache before rebooting
This aa well
TGDgr8est said:
If it isn't a usb issue then. I flashed ngk installed app and set things up. I use these settings . When flashing wipe davilic cache before rebooting
Click to expand...
Click to collapse
Yep, tried it still doesn't work. Infact the usb flex cable was changed from service center. So the usb issue can be ruled out.
Hi All,
Can anyone help me, seems to be a code in kernel not allowing me to reset phone to non charge mode when USB connected.
Thanks