So I have 5 days in research and trying to fix my LG G2 LS980 at first.
I wanted to install CM11 on my LG G2 tried and used the autrec for the recovery. After rebooting my phone it started up in fastboot mode. I attempted to get past the fastboot mode by using the method to flashing img files into it. After I had done so, I restarted my phone and it made the issue even worse. My phone now did not show anything on screen it was turned on, but it was black. I followed this guide:
http://forum.xda-developers.com/showthread.php?t=2582142
When I installed ubuntu on a fresh HDD I was getting them 15 drives but when I typed in lsusb it did not return the drive for my phone but I was able to follow through that guide all the way up when I pushed the file for sbl1.img from the stock files of ls980-ZV8 here: http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware/zv8_partitions Once I did that, I lost connection to it with ubuntu. At this moment the screen does not even turn on, but I have been able to get some communication between my windows 8.1 and it only shows as " Unknown Device: Device Descriptor Request Failed"
That is all I have been able to get and I'm at a loss as I just recently bought this phone. Please if anyone has any suggestions or advice please, I have looked all over this forum and have not found anything related to this similar issue.
Apologizies if this has been in the forum, but I've spent 5 days on this site. Thought that it was time to post my issue.
Related
So this morning i thought it would be a great idea to revert back to stock.
i was following the KDZ lg flash tool however while it was flashing (got to about 2%) i stupidly knocked the phone and the usb cable came out....
so now when i turn my phone on it goes to a black screen with
Fastboot mode started
---reset---
---port charge--
i have tried going into download mode again but it still goes into this fastboot mode.
i found a lot of threads on this such as
http://forum.xda-developers.com/lg-g3/help/tutorial-fixing-fastboot-mode-started-t2995854
this got me to install adb/fastboot which i did via
http://forum.xda-developers.com/showthread.php?t=2588979
however when i try and run through fastboot it just comes up as waiting for device
i have attempted to install lg drivers for this but still nothing.
inside device manager it comes up as
other devices - android?
so clearly the computer is recongnising it, i just need a better driver.
I have the ldf ready to go, if only i could get it to recognise the fastboot command...
anyone able to help, i realise there is a lot of information on the web for this, after extensive research everyone seems to suddenly get into download mode each time. which is something i cannot go. and no recovery doesnt work either.
other things to note, just to save questions..
i am running LG D855 16gb.
when i attempt to go into recovery it comes up with the option to wipe device, but when i follow through menu comes back to fastboot mode started.
i attempted to install lg pc suite in hope that it would suddenly pick up the device and go through the fix upgrade errors (to no luck)
so to clarify, i cannot get into recovery, or download mode. my screen is sat on fastboot mode started.
i am running windows 8.1 although i have attempted to plug into a laptop with ubuntu but same story.
any suggestions? i have also seen a through about jtag...but i dont have any screwdrivers at this point so trying to avoid that.
thank you for reading, kind regards
Anyone out there that has any idea on how to fix?
im convinced i just need to turn the "other device - android" into something that can be recognised by adb, but other then the stock lg drivers i dont have anything else.
help?
FIXED - figured it out, i plugged it into ubuntu again and noticed that when it was connected it came up under fastboot with "accepting commands"
i then put my laf.img file into my home folder and
opened terminal
sudo su <enter>
fastboot boot laf.img
phone then went into download mode
as i didnt have any tools installed on ubuntu i then unplugged and plugged into my windows laptop and ran LG Flash tool 2014 and flashed my kdz.
hope this helps anyone who has the problem in future
Hey guys, I managed to run myself into a little bit of a pickle..
I have flashed the Tipsy ROM v.4.9 on my G3 D550 a couple of weeks ago, and foolishly forgot to flash the extra file that was recommended to keep the phone rooted. During the process TWRP that was previously working perfectly has vanished and now when trying to enter recovery mode it gets into a weird flickering screen and a bootloop.
Now I have tried re-flashing TWRP from my Windows 10 laptop with a thousand different drivers that I found online (uninstalling, rebooting, reinstalling etc etc), but every single time the phone is reckognised with the adb devices command, but the fastboot devices command leaves me in the cold. I have tried everything I could think of. I tries a friends laptop, also windows 10, nada. Then I tried an Ubuntu live session from my own machine, same thing. ADB working, fastboot not.
Does any of you maybe have any idea of how I could get my root and ultimately my recovery back? I am kinda stuck with this rom now, which albeit being great, is obviously not fully fleshed out yet, plus of course it cuts the option of trying out more of the wonderful work that some of you guys here do!
I would appreciate any kind of help!
Thanks!
Hello,
I've bricked my phone and now it just turns on to bootloader, all options in bootloader except turn off just loops it back to bootloader where it says "continue the fastboot process".
I've download the xFSTK_ZE551ML but it won't install the moorefield driver it detect it for only a few seconds and then change to android-phone driver, i believe moorefield doesn't work on bootloader but i can get the phone to hang on something else.
I also can't acess via ADB, when i type adb devices, no device is found.
Also tried the Asus FlashTool, but the raw files i tried (WW_ZE551ML_2.15.40.13_20150506.RAW) didn't work, i believe because it's Android L and phone was on Android L.
I've searched alot but haven't found a solution, can someone point me in the right direction?
Thanks in advance.
What happens when you type "fastboot devices"?
Nothing happens with that command.
It's working now, after i tried several raw files, it worked with "WW_ZE551ML_2.20.40.194_20160713.raw".
I know it's sounds newbie since i've just oppened the thread, but it literaly spend all day yesterday following guides and installing stuff on my pc, anyway glad it's apparently solved.
Anyone stuck on bootloader like i was that can't use xFSTK_ZE551ML, install the "WW_ZE55t1ML_2.20.40.194_20160713.raw" with flash tools, this was the only one that worked for me.
Just a warning to anyone who visits this thread --- If you have bootloader-- DO NOT use xFSTK -- xFSTK is to install a temp bootloader to bricked devices and only used if you have NO bootloader .
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
carnagex420x said:
So I tried to migrate from CM to Lineage (which ive already done on my N5) and while formating my data due to encryption, my tablet is completely F'd in the A.
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank.
I ended up deleting all of the partitions but now i cant even see the device at all.
Since i cant get anyhting on the display and since i cant even get to fastboot, i have a feeling in screwed and need to go get a new board for it now... or just a new tablet i guess, but i rly liked my & and id hate to be w/o it over something stupid like this...
Can anybody else at least confirm or possibly have another idea?
I dont even get the charging animation with it off either...
Click to expand...
Click to collapse
Do you have ADB set up? if not, now may be a good time and through ADB try download a factory image.
carnagex420x said:
If I had it connected to my PC i could see it power on and would show 30 or so unknown partitions, but my screen would be blank. I ended up deleting all of the partitions but now i cant even see the device at all.
Click to expand...
Click to collapse
Connect it to a PC again and check the USB mode your N7 is in.
If it is, or if you can make it work in, USB mode 9006 then follow this post. The linked N7 image is from my 32GB Hynix but you can use it to restore boot on any eMMC and adjust it later. While you do not see the partitions anymore, you may be able to access the device to restore the image.
If it is USB mode 9008 then your only recovery option is JTAG or hardware programming of the eMMC chip.
Good luck, it is still fixable :good:
the device still appears completly lifeless however i am able to get the device to show up as
Code:
Bus 002 Device 064: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
but im not sure how to go about getting fastboot yet, i get that i can dd an image to it i guess but im pretty sure i only have the 16GB not the 32, wjich i cant seem to find.
After playing with it for a couple hours and reading the entire Unbricking thread, the spot im stuck at now is the 9008-9006 mode switch. I have the QPST software and drivers working right and i get the NAK error but i follow the directions and cant get it into 9006 mode...
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
ramon.hugo said:
LineageOS update of May 24 2017 bricked my Nexus 7 2013 also.
Can't even use the Nexus Root Toolkit to recover. Always get stuck in the Google symbol.
Can enter into recovery, but it takes 15 minutes. And the directory structure showed is all empty.
Rebooting it show some errors saying that the partition table is empty.
"OEM Device Info" of NRT shows that the equipment is now locked also.
Have no idea of what to do. Can't even install the SO again.
There is a thread on "general" that seems to deal with related problems:
https://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495
Click to expand...
Click to collapse
When you can boot into recovery you are good to go. Use a pendrive and an otg cable and flashthe rom from pendrive.
Already tried that ... Also impossible.
Try this way,
Connect to Computer
Use NRT then pess root, your Device will restart in TWRT then you can put the file in and reinstall.
You may be running into flash wear issues. This device is about 4 years old at this point, a similar thing started happening to the 2012 models. Don't blame the ROM, blame the NAND chip in your tablet.
I have a busted USB port so prefer to recharge via wireless. Sometimes wireless charging keeps disconnect and reconnecting if it's on so I need to shut it off.
I did that and now it just hangs at the Google screen as well.
If I hold Vol down I dont get twrp but the general bootloader. Any choice seems to just reboot it.
I think I'm screwed as well.
Prior to this my pc doesnt detect via USB at all, just charges it.
Hello everyone - appreciate in advance any help you can offer.
The Pixel C is stock. I use it mainly for reviewing/annotating documents. I'd like to recover that data if possible. My problem is very similar to one from May 2016 documented on Google's product forums titled "Pixel C boot mode after update". On August 7, I was using it in the morning. to review documents. No update notifications. I plugged it in to charge, and set it down for about an hour. I was not using it during this time. I picked it up and it was stuck in a boot mode (not Recovery or Fastboot) that has a scrolling list in the top left with 5 options: (which respond as follows):
Restart this device (Restarts to the same boot screen)
Switch to fastboot mode (Waiting for fastboot comamnd... needs to be restarted holding down power+vol dn.)
Reboot into Android Recovery (Restarts to the same boot screen)
Turn off this device (turns off)
Switch to USB recovery. (For more information on USB recovery, please visit: g.co/c-recovery)
In the middle of the boot screen, in yellow text, it reads:
PRODUCT NAME: GOOGLE Smaug
HW Version: 5
BOOTLOADER VERSION: Google_Smaug.7900.50.0
LOCK STATE: Locked​
Pixel C is not recognized by Windows 10 when plugged in via USB. Under Device Manager it shows up as "Unknown device". However, I can't seem to find any drivers that will work.
I've spent the better part of the week on the phone/email with Google. They are replacing the tablet out of warranty, but won't provide any explanation as to what the probable cause of the failure is (I'm almost certain the cause of the failure is a bad patch or update that was pushed when the Pixel C was charging). They are also not providing any assistance for recovering the data.
Any ideas/advice based on the above?
Thanks again, cj
I'm in the same boat as you. It happened last night. I was playing Last Day on Earth, set it down (off) for twenty minutes, then the bootloop with the "No Command" screen. I called google and they're replacing it. However, while all my photos and videos are backed up, I have some files in my Downloads and other folders that I'd prefer to not have to replace. It won't kill me not to have them, but I'm willing to invest a few hours to try to fix this rather than try to recreate all the content. I came here today to post the same request as you.
So far I've been working on getting the right fastboot drivers downloaded. I was thinking of downloading an OTA image and seeing if I could flash that. (https://developers.google.com/android/ota) I haven't been able to get the fastboot drivers to work under Win10x64 yet. If I find a solution I'll let you know. At this point I would be happy just getting the drives mounted without the OS working.
vanstrien said:
I'm in the same boat as you. It happened last night. I was playing Last Day on Earth, set it down (off) for twenty minutes, then the bootloop with the "No Command" screen. I called google and they're replacing it. However, while all my photos and videos are backed up, I have some files in my Downloads and other folders that I'd prefer to not have to replace. It won't kill me not to have them, but I'm willing to invest a few hours to try to fix this rather than try to recreate all the content. I came here today to post the same request as you.
So far I've been working on getting the right fastboot drivers downloaded. I was thinking of downloading an OTA image and seeing if I could flash that. I haven't been able to get the fastboot drivers to work under Win10x64 yet. If I find a solution I'll let you know. At this point I would be happy just getting the drives mounted without the OS working.
Click to expand...
Click to collapse
I tried everything to access my files (fastboot, ADB) but got nowhere. I tried flashing a recovery drive, no go. The problem for me, I'm sure, was that I didn't unlock the bootloader. I could not find away around that in the end. But I hope you have better luck!
I got my replacement from Google yesterday (it was 3 months out of warranty).
vanstrien said:
I'm in the same boat as you. It happened last night. I was playing Last Day on Earth, set it down (off) for twenty minutes, then the bootloop with the "No Command" screen. I called google and they're replacing it. However, while all my photos and videos are backed up, I have some files in my Downloads and other folders that I'd prefer to not have to replace. It won't kill me not to have them, but I'm willing to invest a few hours to try to fix this rather than try to recreate all the content. I came here today to post the same request as you.
So far I've been working on getting the right fastboot drivers downloaded. I was thinking of downloading an OTA image and seeing if I could flash that. (https://developers.google.com/android/ota) I haven't been able to get the fastboot drivers to work under Win10x64 yet. If I find a solution I'll let you know. At this point I would be happy just getting the drives mounted without the OS working.
Click to expand...
Click to collapse
Install the latest SDK from Google. In it should be the correct drivers for Win10. While in fastboot, open the Windows Device Manager. Note the '!' that should be your Pixel. Update the driver, using the SDK you just installed.
You should be good.
I ran into this when I updated to Win 10. Wugfresh' Root Toolkit has a pretty great driver debug section, which got me through.
Sent from my Pixel XL using Tapatalk