Related
Hey guys, looking for some assistance here as I am at a complete loss.
Decided tonight to root my 4.2.2 Nexus 10 using the Nexus Rootkit v1.6.3 and the aid of a YouTube video. All went swimmingly up until the TWRP wipe. The video I followed failed the wipe attempt and the guy showed how to get the N10 out of the bootloop and do a 'wipe data/factory reset' via Recovery Mode in the Bootloader and then restart.
Problem is, my wipe never failed like his did in the video (great I thought!) and so I restarted after that and now I find my N10 booting up to the Google Logo (with the padlock at the bottom) and it just sits there. Doesn't even get to the 'X' logo which should come after.
I've tried a few things including the manual wipe data/factory reset from the bootloader and restart but everytime it gets stuck at the Google Logo. I am also now at the point where my N10 doesn't show in Device Manager as it did before. It now shows under 'Portable Devices' as a 'MTP USB Device'.
I am really at a loss here and searching various solutions is just confusing me even more and would appreciate it if someone could help me out, even just getting back to stock for now. That's if it isn't goosed?
Thanks in advance
Have you tried using a different usb port on the PC, and rebooting the PC?
bigmatty said:
Have you tried using a different usb port on the PC, and rebooting the PC?
Click to expand...
Click to collapse
I have yeah. Left my PC off overnight and went back to it again this morning and same issue.
Plug it into the PC (this time using a USB port on the back) and it initially comes up 'installing device driver software' quickly followed by 'device driver software was not installed successfully', quickly followed by 'installing device driver software' again and that's when it shows up in Device Manager as 'MTP USB Device' under Portable Devices, whereas before during the root attempt it was show as 'Nexus 10'.
When I first read the subject line I thought it was "another one of these" where OP hadn't searched on the existing boards. But when I read OP I see you did try "the usual suggestions". Hoping a more seasoned pro jumps in here to help...
I can say that on the handful of "really bad" posts like this that I've seen they usually end with the person saying something like "well I don't know what happened I just kept trying all the power button / charge recommendations and finally it worked" - so don't underestimate the effectiveness of repeatedly trying it like a mad man!
Some random suggestions I have that may help:
-Can you leave it on, on the Google screen, to where the battery 100% drains, maybe this could act as a "battery pull"
-Try a different USB cord
-Try rebooting it via the power buttons while the device is plugged into the wall charger
-Download the Android SDK, then use its "update manager" to update its USB drivers to today's definitions
-Try another PC
Good luck!
Thanks for the suggestions bigmatty, I'll certainly give them a go when I get in later.
I think my biggest concern is that there doesn't seem to be any OS on it, possibly to do with the wipe during TWRP and then I rebooted - was I supposed to reboot at that stage? That's where I got into this loop. And now it doesn't detect it as 'Nexus 10' in my Device Manager on my main PC. Only this MTP USB Device - sometimes showing a conflict warning triangle, sometimes not and no longer showing as a storage device in My Computer.
I did connect it to my Netbook (Running XP) earlier and it detected it as an 'Android Device' under Other Devices in Device Manager. Tried installing it with the naked drivers on the Android SDK and it now lists it under 'Android Device' in my Netbook's Device Manager as a 'ADB Device' (I think, would need to double check as I'm not on it at the moment.)
I just want to find some way of getting it back to factory settings and stock OS if possible and then take it from there again. Don't fancy at £319 paperweight! I'm usually alright with these things too.
Thanks again (And if anybody else has any other input in the meantime I would be grateful - I'll try anything at this stage!)
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
bigmatty said:
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
Can't really get into much on the Tablet itself. It boots up, gets to the Google logo (with the padlock symbol at the bottom suggest it has been partially rooted (?)). I can get into the Bootloader by holding down the Power + 2 vol buttons. Once in the Bootloader I have the options of Start/Power Off/Recovery Mode/Restart Bootloader.
When I go into Recovery Mode I can get access to the blue menu where I get the options to restart/something about adb/wipe data/factory reset/delete cache partition (paraphrasing here).
Don't know how many times I've tried the wipe data/factory reset option and reboot but always get sent back to the same loop.
I'll give you're other idea a shot as well later. Thanks again.
bigmatty said:
I'd say its a good thing that the PC exhibits varying behavior - because that means there is still hope!
It really boils down to if you can open an adb.exe shell to the device. Can you? It would not be when its showing as MTP but it would be when its showing as adb in Device Manager. If you can then here is a thread where I explain (pretty good, I think) how to get back to stock:
http://forum.xda-developers.com/showthread.php?t=2185123
Now I realize Im not clear on a second avenue - can you still get into TWRP?
~bm
Click to expand...
Click to collapse
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Scotman57 said:
bigmatty, you the man!
Managed to get back to factory stock following yours and styckx's guidelines. Couple of little teething problems along the way but nothing I couldn't get around.
I now have a fully functioning Tablet again and I thank you for it.
Might give the Rooting a miss for now but if I come back around to the idea I'll be sure to follow the guides on here this time instead.
Thanks a bunch again for taking your time out to reply to my thread and get me back up and running again. :good:
Click to expand...
Click to collapse
Awesome! Glad it worked out
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
Any help is appreciated! First some background:
Flashed device to stock using KK 4.4 version d80020c following steps found here http://forum.xda-developers.com/showthread.php?t=2432476. Successfully rooted using directions (and ioroot25) found here https://www.youtube.com/watch?v=HKuedInhdjU&noredirect=1.
Here's where I got into trouble...Downloaded TWRP 2.7 recovery img and flashed via Flashify. Since this step, my D800 has the exact same symptoms found on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
- No download mode (tried many times)
- No recovery (tried many times also)
- Secure booting error
- LG detected as qhsusb_bulk in device manager
- Device is recognized as 15 different drives, one of which contains a folder named image with 79 different files being .B0X files and Microsoft Access Add-in Data files
- Upon restarting, LG logo with secure booting error, then the screen goes black while your phone is still on
I've followed the steps in the thread that matches my G2's symptoms, run ubuntu 13.1 in VM, apply usb filters for my device which is then recognized as either LG Electonics Inc. QHUSB_BULK or Unknown Device 05C6:9006 when running in VM.
Upon running command ls /dev/sd* in VM Ubuntu Terminal, all that is returned is /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 which are the partitions for Ubuntu, no LG.
I've tried to download and update the Qualcomm drivers, device manager tells me that the drivers were recognized, but cannot be installed and do not pass the hash check (Note: PC is running Windows 8.1).
I've spent over 12 hours on this trying to fix this problem, researched and searched everywhere. If I could get ubuntu to recognize the device, I would be able to continue on with the instructions on this thread http://forum.xda-developers.com/showthread.php?t=2582142.
Links for windows 8 qualcomm drivers, suggestions on how to get the device recognized in ubuntu vm, experiences from others in similar situation, or any with experience working with LG to get a repair done if I'm SOL (as in eMMC is fried) would be so helpful right now.
Thank you all!
After flashing recovery did you flash a patched kernel to boot stock kk?
Sent from my LG-D800 using Tapatalk
I had the same, also with a lot of drives etc.
Screen is black but low backlighted?
Then try with pluged USB Cabel in Phone, hold Power button until screen is realy off, then hold the Power Up Button and plug Cabel into PC.
So I got download mode after I tryed many times
I had problems a few weeks ago getting mine to go into Download mode... turned out that the cable I was using was great for charging, but sucked for everything else. Once I switched to a different cable things worked fine and I was able to load D80010c on the device.
I was running D80020c this morning (with the D80010c boot.img to have a custom recovery) and decided to do an update. Since you can't load D80020k if you have the older bootloader I went all the way back to D80010c, updated to D80010o, D80010q, D80020c and finally D80020k. I was able to root that using IOroot and have restored everything back onto my phone.
-Daryel
Thanks so much for the responses! I've tried endlessly to get the device into download mode, and tried a new cable to no avail. Any other suggestions?
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
d800 partitions are here
Still no luck
bender_007 said:
The URL you've linked to will help you solve your problem.
So once you power off your device, hold volume down and power till the lg logo shows, then release shortly and hold them again together till the white window with "factory reset appears", you should notice a text behind the white screen it's fine. So right now when you think it's gonna enter recovery mode the screen is gray(not black), now you connect your device to your ubuntu or whichever linux. You will notice the screen repeatelly blinking when linux is trying to automount the partitions. Figure out which device it is according to the messages it throws. (sdc, sdb, sdX)
This way you should proceed according to the instructions on the thread you linked.
Click to expand...
Click to collapse
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Sneaky Elephant said:
Thanks for your advice.
I got the white screen asking whether or not I want to perform a factory reset. If I choose No, the phone sends me right to the LG Logo with the error screen. If I choose Yes, it does the same thing. If I plug my phone into my computer while on the white screen asking if I want to perform a factory reset, the device isn't recognized and the PC doesn't see it as plugged in or mounted. I'm not sure what you mean by the timing of when I should try to plug in my device. Thanks again for all your help.
Click to expand...
Click to collapse
As soon as in the background of the white menu (factory reset) the secure boot appear plug it in. I'm not sure how much usb filter helps you(maybe it does) but try installing ubuntu over WUBI installer so your win remains. Or at least try ubuntu from usb stick. So you can know for sure if it's working.
Hi Sneaky E. I have the same issue you have. I'll be following your thread. If I figure anything out I'll let you know. I am also having an issue getting mine to charge now. Have you tried downgrading your TWRP?
VirtualBox Error
VirtualBox recognizes the device is plugged in, but won't allow me to push the device for use in linux. I keep getting this error message:
Failed to attach the USB device LG Electronics Inc. QHSUSB__BULK to the virtual machine Ubuntu.
USB device 'LG Electronics Inc. QHSUSB__BULK' with UUID {d8db3712-b86c-4257-a87b-275cef04e5a3} is busy with a previous request. Please try again later.
Result Code: E_INVALIDARG (0x80070057)
Component: HostUSBDevice
Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}
Click to expand...
Click to collapse
I've tried all USB ports, 2.0 and 3.0. I feel like if I can get past this there should be no reason linux can't see the partitions in the phone. Please Help!!!
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
ambetdelarosa said:
you are not alone dude. i had the same issue since sunday and i have spent almost 46 hours already trying to restore my LG G2 F320S korean model.
i followed that instruction in linux, everything went well but then I ended up with a phone not going past the LG logo. the screen no longer dims like how it used to with the secure boot fail error. again, it stucked at the LG logo and thats it.
pressing the 3 buttons though for 5 seconds shows a white screen with 3 options and a bar code under.
but all of these options will just take me back to the LG logo.
I went to a phone technician today, and they said the doing a JTAG fix is the only way to resolve the problem because after trying to fix it with linux, it is no longer identified by my PC.
what are your solutions so far?
anyways before this issue came up, i tried to flash TWRP using flashify, it failed. then went back up. tried to update the OS via OTA then thats it.
i home someone could help us out.
Click to expand...
Click to collapse
What are the negatives to doing a JTAG fix?
Sneaky Elephant said:
What are the negatives to doing a JTAG fix?
Click to expand...
Click to collapse
Here is your fix.
follow exactly. LINK
ingoljosh said:
Here is your fix.
follow exactly. LINK
Click to expand...
Click to collapse
Followed steps already, still can't boot into recovery.
Sneaky Elephant said:
Followed steps already, still can't boot into recovery.
Click to expand...
Click to collapse
if your device is insured maybe report it lost and pay deductible and get a new one AND NEVER ROOT AGAIN
linux cant recognizy my lg g2 f320L
Sneaky Elephant said:
Ok so thank you for your help so far. I was able to install Linux on a USB drive and ran the commands and pushed appropriate files from there. I pushed all files including recover.img but the phone will not boot into recovery. Please help!
Thank you!
Click to expand...
Click to collapse
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
dr jam said:
HI Sneaky elephant........bro I am having the same problem with my lg g2(hard bricked) that its not recognised by Ubuntu...it just shows hssusb-hulk.....no partitions to mount.............
in ur next reply u said that issue solve.....
kindly tell me too that how ur issue resolved...........thanks......
Click to expand...
Click to collapse
The same with me - UP
install ur Ubuntu sing VMware....then partitions will appear.........
---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------
install ur Ubuntu using VMware......then ur mobile will be recognised and partitions will appear.....
Alright so here's what happened. Last night I decided to update to the latest Cyanogenmod nightly. Turns out that was a bad idea, because it blackscreened on me. Ok, so I flashed the stock firmware, it was working. I decide to reinstall TWRP back on it. It didn't seem to take so I just said "**** it" and went to sleep. I wake up the next morning and what do I see? "Secure booting error Error: Boot Certification Verify!" No download mode, no recovery. So alright, I've followed the guide here: http://forum.xda-developers.com/showthread.php?t=2582142 but I hit a roadblock. Now this is where things become weirder. When I plug my phone in to USB in its current state, it's kind of hard to explain, but here's what it does: The backlight flashes on and off constantly. In Windows (currently in Linux right now as per the guide) it acted as if it kept trying to mount itself. Windows didn't like this at all because apparently it was doing it constantly, and bringing up a lot of dialog windows with multiple drive letters telling me to format it. Now I suspect the problem has carried over to Linux as well, meaning I can't push the images I need to to my phone in order to fix it, since it won't mount itself properly. Yes, I even tried disabling automount like the guide suggested and that didn't help. I'm guessing it's a bootloop issue? I dunno. I'm completely stuck, frustrated, and I really hope I don't have to buy a new phone. Any suggestions? I really need help with this. Thanks.
The long list of tons of drives (and no Download mode) is fairly easy to fix thanks to the solution at:
http://forum.xda-developers.com/lg-g...6#post56739916
To simplify, just download his premade package for the D800 (he lists other versions in the description of his YouTube video) at https://mega.nz/#!mN0SkDpb!1R36L-F05...88X5OuIqwNdezM
and also download and install the Qualcomm drivers from here:
http://www.mediafire.com/download/pb...SB+Drivers.rar
In the instructions he shows Computer Management, a Windows tool. If you are unfamiliar, you can find it under Control Panel -> System and Security -> Administrative tools (click on it)
bought this phone used and I don't think it was rooted but never checked, confirmed. Last night it turned off and will not turn on anymore..
Tried the pwr button for several minutes and no change. Plugged it in with several different cables and no change.
Any other suggestions or options? USB to computer detects something but says it can't install the driver.
Any ideas?
oNe
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
martinfarrell11 said:
Can you enter to the bootloader menu? Maybe you can enter recovery and wipe the cache and dalvik
Click to expand...
Click to collapse
negative, either the phone is totally dead or the screen is dead but NOTHING happens when pwr is pressed
here is what I have tried:
1. Press and hold PWR button for over 3minutes
- Plugged in and unplugged into ac - no change
2. Press and hold volume DOWN + Pwr for over 3minutes
- Plugged in and unplugged into ac - no change
3. Plugged into different a/c power outlets with 2 different chargers - no change
NOT sure what else to try or do?
Funny thing is if ya plug into a computer it does indeed detect "something'
However it says it can't load the USB drivers something about QU_***
Open to any ideas and suggestions.. WHILE I would love to get the phone working whats more high priority for me now is the 20gb's of pics that apparently did NOT back up.
oNe
Sean Price said:
Funny thing is if ya plug into a computer it does indeed detect "something' However it says it can't load the USB drivers something about QU_***
Click to expand...
Click to collapse
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
Several threads with no solution. I went through the same "something" . Can't be fixed
v12xke said:
Funny thing is- that "something" is the solution to your problem. Capture the error message completely and search the 6P forums for that. Several threads on the "something" issue.
Click to expand...
Click to collapse
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either.
Any other ideas?
please advise..
oNe
Sean Price said:
fixed that issue, aka QHSUSB_BULK is now working properly according to Device Manager.. but Nexus 6P is not detected, and doesn't even show up in Disk Management either. Any other ideas? please advise.. oNe
Click to expand...
Click to collapse
If you found the right EDL_9008 thread, there is Qualcomm software to download for your PC. If your phone is in the right downloader mode you can use the PC software with a special recovery.img. I don't know anything about it, just read through the threads long ago. It's a mixed bag with some success stories, some not. Keep looking though, I think you are on the right track. The original poster was "Tenfar" if I recall correctly. Good luck.
Try cleaning out the charging port.
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Maybe disable big cores?
apples1678 said:
Hi there,
I think we are in the same/similar boat. My phone shut off while using it (screen froze, then went black) and seems to have bricked itself. I *am* able to get mine to turn on, but only about once per day after it has been left plugged in for a few hours (although there is no indication it is charging while plugged in - never gets warm, no lights, etc.) I can get into recovery if I am lucky (usually get to the android bot laying on its back, then PWR+VOLUP just causes the phone to shut off instead of actually getting into recovery menu.) I've been able to clear cache/factory wipe from recovery menu with no luck. I never did unlock the bootloader so I am unable to use fastboot to do anything. I tried to flash a few OTA (full and incremental) images using adb when I am able to get into recovery, but they always failed in one way or another.
I've been trying the methods described in the 'tenfar' threads - using the xiaomi flasher and QPST tools. The xiaomi tool always fails for me. I have been able to get the QFIL tool to successfully 'download' about 3 times now, with tenfar's recovery images. However, after the success message, the phone doesn't do anything (I read in other threads it should reboot itself) - and after unplugging, the behavior of the device seems to be the same - just stuck and won't turn on at all.
Right now I think I am stuck in 'EDL' mode where the only evidence that the device isn't completely dead is that it shows up in device manager as 'Qualcomm HS-USB QDLoader 9008 (COM3)', and the factory imager tools do recognize it.
It *seems* like the only way forward is to somehow get one of these factory tools to flash the right set of files onto the device - I've tried a few now with no luck. I even tried extracting the relevant *.img files out of the google factory image download and replacing tenfar's image files with them. I was able to load those onto the device with QFIL. This morning my attempt at turning on the device has me stuck on the white google logo, which is new behavior for me - usually it shows the logo for ~5-10 seconds then the device powers off. I've left it on for a while stuck on the white google image, but I'm not sure if I'm doing anything useful here.
Here are my reference threads:
tenfar's 'debrick' thread
QFIL thread
If anyone has any crazy ideas, I am open to try them. Thank you.
Click to expand...
Click to collapse
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
ncc8uetou5et said:
I have the 100% same issue. Screen froze,then went black and now its stuck in EDL mode. I need my data. Recovery access or anything else would be fine/enough for me. I have had LineageOS and TWRP on the device. With TWRP i can access my data.
How have you got your device on? Mine dont start once a day or so. Its always in EDL mode ( 9008 ).
Click to expand...
Click to collapse
Sorry bud - I never was able to get any further than when I posted this. I eventually gave up, got a full out of warranty refund through my CC after the manufacturer wouldn't help me at all, and upgraded to a Pixel XL. I still do have the device, I should try to boot it up again . I didn't have any data concerns on my device so I was able to give up... good luck!