Database Users

Bricked after OTA..

My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.

Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app

prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.

Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.

thenewak said:
Sounds like you just need to keep messing with it until you can get it to recognize it in download mode and go back to stock. What Windows version do you have? i had some issues with 8 but 7 worked fine.
Click to expand...
Click to collapse
I have Windows 7 64bit with all the latest patches.

Utahnewbie said:
I tried, use ADB while the phone is in TWRT, went through and restarted, still boot into TWRT.
The command line in TWRT will pop up an error message saying "not enough space", although I do have enough space. So it didn't work either.
Click to expand...
Click to collapse
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.

p.valenta said:
Well, that Fix clear FOTA with zeros and it should end with "not enough space", this is normal.
I guess when your phone restarted into download mode and got stuck on 0%, it already overwrite maybe part of system partition, this is why only download or recovery works.
Did you made any nandroid backup before? If yes, restore at least boot & system from it. It should help, so you can boot normally. If you do not have any backup, well, maybe some other fellow Spring user can give u his boot & system backup files so you can restore them.
Click to expand...
Click to collapse
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.

Utahnewbie said:
Yes, I have a full nandroid backup before. I did a full restore from it after the boot-looping, but it didn't work, I still boot into TWRP and unable to boot into system.
Click to expand...
Click to collapse
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.

p.valenta said:
so you followed that fix to clear FOTA, restored from backup, but when do "REBOOT SYTEM" from TWRP it ends again in recovery?
hmmm, how about these steps:
http://forum.xda-developers.com/showthread.php?t=2432476
using Flash Tool to restore stock ROM.
Click to expand...
Click to collapse
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.

I had the same problem
Utahnewbie said:
No, it doesn't work, because my phone stuck at 0% in download mode and it doesn't show up in my device manager on PC.
Click to expand...
Click to collapse
I used the fix from http://forum.xda-developers.com/showthread.php?t=2448960
except that I used the sprint .tot file. (http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/Sprint+LS980/)
Did you try to reinstall the drivers or use a different cable?

I encountered the same issue last night. I reinstalled the Verizon united drivers and rebooted my machine. The next time that I connected the device in download mode, device manager picked up the device. I had to re-run the LG tool, but it eventually progressed past 0% and my issue was fixed. You can reinstall the verizon drivers using the following link.
http://wacomalt.com/dropbox/LGG2/StockRevert/LG VZW_United_WHQL_v2.11.1.exe

I'm having the same issues with D802b after doing the 60mb OTA update. My phone didn't get a chance to actually do the download as on first restart it just went straight into TWRP and I haven't been able to get back since.
It's just looping back into TWRP each time. I've now completely wiped all parts of the phone including the internal SD card, I've even re-installed a new kernel and rom (The custom one I was using before this happened, from http://forum.xda-developers.com/showthread.php?t=2505682) from an attached USB (sd card reader) with successful installs through TWRP (including wiping cache etc), still reboots into TWRP on restart. I've also done a hard reset that was supposedly successful, still boots into TWRP.
Same as the OP, it won't 'install itself' properly in windows while in TWRP mode or in 'Software Download' mode (turn on with up and down buttons pressed down and plug data cable in). I've tried in vain to hunt down a specific D802 inf as pointing it at the universal driver didn't detect either.
I have installed the Android SDK, LG Suite, LG Universal drivers. I've then tried the B2CAppSetup (which works, but won't detect the device). I've then tried the FlashTool 1.0.54 and it gets all the way through but can't communicate with the device.
The only thing I haven't managed to do yet is to decompress the official kdz into a zip so I can flash it through TWRP. Haven't had much luck with LGExtract as of yet.
Rather baffled actually, as I'm sure the OP is.
Any thoughts?
---------- Post added at 08:55 PM ---------- Previous post was at 08:11 PM ----------
Having just posted all that above, I look further down the forum and someone linked to this thread below.
Fixed my issue, so I imagine it will sort yours out too.
http://forum.xda-developers.com/showthread.php?t=2451696

Update: I don't want to deal with this issue anymore.. just replaced it and got a new one

Utahnewbie said:
Update: I don't want to deal with this issue anymore.. just replaced it and got a new one
Click to expand...
Click to collapse
That is excellent, did they give you a hard time replacing it?

thenewak said:
That is excellent, did they give you a hard time replacing it?
Click to expand...
Click to collapse
No, because I microwaved it.

prking07 said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
[FIX] Installed TWRP and now you're stuck after OTA?
Sent from my LG-G2 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried that method many times and it does not work on the Sprint version. If you read through the thread you'll noticed that others with Sprint devices can not get that method to work.
The only method that worked for me was to use the LG Flash tool and flash the Sprint tot file and follow the instructions for the Verizion method for going back to stock.
---------- Post added at 01:41 AM ---------- Previous post was at 01:22 AM ----------
Utahnewbie said:
My sprint LG G2 was boot looping into TWRT after I accepted an OTA.
I've read several posts, http://forum.xda-developers.com/showthread.php?t=2477595 and this one http://forum.xda-developers.com/showthread.php?t=2448960,
the problem I get is I can not get into download mode, well, I did enter it, but it stuck at 0%, and my computer don't recognize it. Can not find the phone in "devices", installed the driver and still no avail. BTW, when I boot into TWRT, my computer can recognize the android device and ADB works then.
Since I cannot get past the download mode, I can not use the LG flash tool.. it says "LG USB/Parallel lock key is not detected".
Any suggestion is deeply appreciated.
Click to expand...
Click to collapse
Not really sure if this would've solve your problem but here's my possible theory to why you couldn't get it to work:
I was in the same situation. Took the OTA update and was boot looping into TWRP. Just like you, nothing in TWRP would fix it. I think you probably panicked and rush through the instructions and forgot some important steps. Make sure you did not install the Verizon driver by accident because that will cause problems with your Sprint phone not being properly detected by your computer. I did panicked and started to try to many things and somehow got a copy of the Verizon driver and installed it. ADB was able to see my phone but when I tried to sideload something through TWRP it would generate an error. I found out that I had both drivers(LG USB driver and the Verizon USB driver) installed and after removing the Verizon USB driver my computer was able to detect my phone properly. It's really important that after making any changes or installations of drivers you will need to reboot your PC to get the new changes to take effect.
You got the "LG USB/Parallel lock key is not detected" error is because you forgot to copy and overwrite the "MegaLock.dll" that's located at "C:\LG\LGFlashTool" directory.
To get into download mode you just need to press the +volume button only(do not hold or press the power button) and plug in the USB cable that's attached to your computer and Download Mode should come on. It will stay on 0% until the LG Flash tool flashes the Sprint stock rom onto the phone.
Once I got the phone to come up in Download Mode I had to go into Device Manager and find the device and then change the COM port to COM 41 then everything went smoothly as the instruction indicated. If you were not able to change the COM to COM 41 then it will never work.
If you're not sure that you have all the files then this is where I got mine from:
http://forum.xda-developers.com/showthread.php?t=2486738&page=7
or
http://forum.xda-developers.com/showpost.php?p=47849315&postcount=9
After I got the file above I followed the directions for the Verizon method below:
http://forum.xda-developers.com/showthread.php?t=2448960

Utahnewbie said:
No, because I microwaved it.
Click to expand...
Click to collapse
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk

RedMist said:
How long for? Thanks,
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
four seconds

Utahnewbie said:
four seconds
Click to expand...
Click to collapse
That was enough to stop it booting? Cheers,
Sent from my Nexus 7 using Tapatalk

Stuck after Verizon Update (Philz Recovery)!

I downloaded the latest Verizon OTA update--I'm rooted and have Philz recovery. All indication from other posters said it should've been fine.
However, that didn't happen to me! It either gets stuck on the LG Splash Logo or boots into Philz recovery. It won't start or update! Does anyone have any suggestions as to how to get it back up and running?

http://forum.xda-developers.com/showthread.php?t=2451696
You should never do an ota update while having a custom recovery. You can only take the ota if you are stock, stock rooted with stock recovery.
Sent from my LG-LS980 using Tapatalk

oldpreowner said:
http://forum.xda-developers.com/showthread.php?t=2451696
You should never do an ota update while having a custom recovery. You can only take the ota if you are stock, stock rooted with stock recovery.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
I don't have access to a terminal, though. It appears Philz doesn't have this ability! UGH. I don't know what I was thinking.

coolkatz321 said:
I don't have access to a terminal, though. It appears Philz doesn't have this ability! UGH. I don't know what I was thinking.
Click to expand...
Click to collapse
You can do these commands on a computer, do you have access to a computer?
Sent from my LG-LS980 using Tapatalk

oldpreowner said:
You can do these commands on a computer, do you have access to a computer?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Yes! It's plugged in now. I'm having trouble enabling ADB, though (it's not recognizing the device). Any help you can offer will be absurdly appreciated.

You will have to search xda, there are many threads started by people in your same situation. There will be drivers you will need to install.
Sent from my LG-LS980 using Tapatalk

oldpreowner said:
You will have to search xda, there are many threads started by people in your same situation. There will be drivers you will need to install.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
But they aren't. The issue is that I can't get it to recognize the phone in ADB mode. I can't boot back into Android and change the settings to get it to work. It's simply not finding the phone as an ADB device. I've installed the drivers. None of the other threads are helping, and it's tough to get it to recognize ADB from recovery...

Can you get into download mode?
Sent from my LG-LS980 using Tapatalk
---------- Post added at 01:21 PM ---------- Previous post was at 01:20 PM ----------
Try this if you can.
http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my LG-LS980 using Tapatalk

Well, I managed to get ADB working but that code didn't work. Sigh. Guess there's never been a better time to upgrade to CM 11, right?

And, nevermind, I'm officially ****ed.
The terminal command didn't work, I tried to install CM 11 and it still keeps rebooting back into (now) TWRP. I have no idea how to revert back to stock, especially since I can't get into download mode. I think my phone is ****ed.

If you can get into TWRP, use usb drive formatted to fat32 and drop image on it. Use OTG cabled with drive and flash image from twrp over otg. It appears you have a driver issue pc side. Not recognizing, so. no dl mode switch. Uninstall ALL lg related drivers. Find universal ones(here on forums somewhere from a dev), try abd again. There are multiple ways of fixing this on forums. You still have recovery and soft bricked. Patience buddy, you are in a better solution then others have been. Search, be patient, try and lose some frustration, it will screw you up the ass, your brain will kick in and you will fix this.

coolkatz321 said:
And, nevermind, I'm officially ****ed.
The terminal command didn't work, I tried to install CM 11 and it still keeps rebooting back into (now) TWRP. I have no idea how to revert back to stock, especially since I can't get into download mode. I think my phone is ****ed.
Click to expand...
Click to collapse
If you power the phone completely off, then hold volume up while plugging in the USB to your computer, does it go into download mode then?
Verizon G2 VS980

I was in the same boat but couldnt even get to recovery or download. It seems the OTA is screwing up the cache partition if you have a custom recovery or root.It took me a long time and lots of help from @Shelnutt2 and [MENTION=1850677]autoprime on irc #lg-g2 to get it working. With adb working though- it was just a couple of dd commands to fix, but it was beyond my scope-- these guys helped me tremendously and I am back to life.
once in adb- these were the commands that fixed it:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

spontaneous boot loop?

my rooted G2 with stock 4.2 suddenly quit accepting a charge and appears to be caught in a boot loop. when I have it in via usb to my laptop it (laptop) responds by recognizing 12 different devices while saying they they all need to be reformatted. when I unplug the device they go away on the laptop. when I hold power (device) the LG logo will appear then quickly disappear leaving only the very dim backlight as proof that it isn't completely dead. any ideas? thank you
one more thing, the fiddling I have been doing is xposed modules. the last one I think I activated was xblast tools (very cool sh*t by the way).

You need to flash the xposed disable zip that's automatically put on the root of the storage directory. The latest module or change you added is most likely the cause. After flashing the zip, you'll need to reinstall xposed. Remember to disable the module that caused the bootloop.
Sent from my phone using some app

You dun got ATT'ed.
They're pushing OTA's out without asking now.
http://forum.xda-developers.com/showthread.php?t=2647654

Do one thing flash the .tot file for your phone if you can get to download mod, it should bring it back to factory defaults but it will format your sdcard as well so all personal data will be gone.
Here is the link to instructions:
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/

se1988 said:
You need to flash the xposed disable zip that's automatically put on the root of the storage directory. The latest module or change you added is most likely the cause. After flashing the zip, you'll need to reinstall xposed. Remember to disable the module that caused the bootloop.
Sent from my phone using some app
Click to expand...
Click to collapse
I can flash even though I can not enter download mode?

abhinav.tella said:
Do one thing flash the .tot file for your phone if you can get to download mod, it should bring it back to factory defaults but it will format your sdcard as well so all personal data will be gone.
Here is the link to instructions:
http://www.droidviews.com/how-to-restore-lg-g2-to-stock-firmware/
Click to expand...
Click to collapse
I cannot enter download mode I'm afraid.

khaytsus said:
You dun got ATT'ed.
They're pushing OTA's out without asking now.
http://forum.xda-developers.com/showthread.php?t=2647654
Click to expand...
Click to collapse
What exactly do you mean? I glanced at the link and either your joke went right over my head or I missed it in the lot her thread.

pollutedmuse said:
I can flash even though I can not enter download mode?
Click to expand...
Click to collapse
can't you enter recovery?
If you can't enter recovery or download mode, you have a softbrick. Search on how to solve softbrick issues. Im sorry I cant help you any further if it is a softbrick, as I am completely new to LG

se1988 said:
can't you enter recovery?
If you can't enter recovery or download mode, you have a softbrick. Search on how to solve softbrick issues. Im sorry I cant help you any further if it is a softbrick, as I am completely new to LG
Click to expand...
Click to collapse
Do you mean hard brick?

pollutedmuse said:
my rooted G2 with stock 4.2 suddenly quit accepting a charge and appears to be caught in a boot loop. when I have it in via usb to my laptop it (laptop) responds by recognizing 12 different devices while saying they they all need to be reformatted. when I unplug the device they go away on the laptop. when I hold power (device) the LG logo will appear then quickly disappear leaving only the very dim backlight as proof that it isn't completely dead. any ideas? thank you
one more thing, the fiddling I have been doing is xposed modules. the last one I think I activated was xblast tools (very cool sh*t by the way).
Click to expand...
Click to collapse
When you plug it into your computer do you see a yellowed out device in Windows device manager?
If so try this - http://forum.xda-developers.com/showpost.php?p=48361867&postcount=68
or alternately, install the pdanet drivers.
If you can then get adb access to your device there are several paths you could take.
I used this thread (I had recovery but not twrp), as it's the least destructive - http://forum.xda-developers.com/showthread.php?t=2451696
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/show....php?t=2582142
(actually kind of sounds like fun to me)

pollutedmuse said:
Do you mean hard brick?
Click to expand...
Click to collapse
No, hard brick is when the device won't even turn on. OPs device turns on, but is stuck in limbo.

se1988 said:
No, hard brick is when the device won't even turn on. OPs device turns on, but is stuck in limbo.
Click to expand...
Click to collapse
Oh, F'n sweet! Thank good sir! I am gonna work on your advice immediately.

CxanDroid said:
When you plug it into your computer do you see a yellowed out device in Windows device manager?
If so try this - http://forum.xda-developers.com/showpost.php?p=48361867&postcount=68
or alternately, install the pdanet drivers.
If you can then get adb access to your device there are several paths you could take.
I used this thread (I had recovery but not twrp), as it's the least destructive - http://forum.xda-developers.com/showthread.php?t=2451696
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/show....php?t=2582142
(actually kind of sounds like fun to me)
Click to expand...
Click to collapse
Thank you my friend!

pollutedmuse said:
Oh, F'n sweet! Thank good sir! I am gonna work on your advice immediately.
Click to expand...
Click to collapse
Good luck!!
Sent from my phone using some app

Persistent problem

Hello,
SOOOOooooo I posted a thread a few days ago. Bear with me, this introductory post is long BUT it is worth including all details I can right from the start to cut down unnecessary communication.
Here goes the continuation in some kind of a bullet form timeline format:
-Bought fully functional d801
-rooted (using ioroot) and unlocked succesfully
-attempted to install twrp using freegee (it didnt work giving me comparable results to this: http://forum.xda-developers.com/showpost.php?p=50501346&postcount=867)
-went on to install it manually from terminal emulator (I installed the rogers version as suggested by another user here as this is exactly my situation: http://forum.xda-developers.com/showpost.php?p=50502408&postcount=869
***
PROBLEMS STARTED HERE
***
-Tried many things
-Lost sleep
-Flashed succesfully using flash tool to the original firmware (D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone) I even flashed it twice. (still had the exact same issues
-Hard resetted countless times
-lost faith in humanity
Thats basically it so far.
Here are the symptoms:
-Imei = null
-Phone resets/reboots randomly and consistently every 5 to 15 seconds
-I can get all the way through to the android os all seems normal Except:
-No keyboard. ever.
-no wifi
-camera even works
-cant get into security and settings (crashes automatically into reboot)
Very good recent news thanks to advice from a memeber on here:
I tried in vain connecting to adb (always giving "offline") until someone suggested trying a different architecture (x64vsx86) or just different pc altogether.
It worked. Now the device is recognized and it says : "some serial number" device
and not "offline" as before
inputting "adb shell" yields: "[email protected]:/ $"
I am open to answer any question.
I am open to try anything.
This phone is a total loss right now so I am obviously open to anything. :laugh:
Phone is still rooted according to "download mode" interface.
Stock recovery installed right now.
I have what I believe to be EFS backups outputted by the initial Ioroot rooting automation (modemstat1.img and modemstat2.img)
You folks are the best.
Much peace and love.:good:

Your t-mobile, right. D801? (Not 100% on that) if you are, you need lg flash tool. I don't have a link because I'm on my phone but it's around. You need to download the T-Mobile files in the 1st post of the thread. Just follow the directions. Wish I had links
Sent from my LG-D800 using xda app-developers app
---------- Post added at 07:35 PM ---------- Previous post was at 07:32 PM ----------
Using that will bring you back to stock. From there you can root, twrp, and flash custom rom. Good luck
Sent from my LG-D800 using xda app-developers app

I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:

zprovo said:
I am not with t-mobile.
Phone is from Videotron (Canadian phone)
I have reinstalled the stock .kdz using flash tool and am also already rooted.
Still have the same issues.
I cannot install anything from wifi since it isnt working...
Any guides on how to install twrp using adb interface?
Or any other suggestions?
Will a custom rom really solve these kinds of issues?
Thanks a lot for the advice I really appreciate any input at this point.:good::good::good:
Click to expand...
Click to collapse
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670

andro ninja said:
Have you tried this http://teamw.in/project/twrp2/197 method.
Initially I tried almost everything but only this worked after couple of tries. http://forum.xda-developers.com/showthread.php?t=2449670
Click to expand...
Click to collapse
Ok really good news :laugh::good:
Making slow but certain progress here.
So just to update also: I now CAN acces the phone from my computer when I put it in PTP (camera) mode.
First I realized that root was installed but that I did not have the supersu installed. I realized this because I could not access "su" in adb shell.
So I reinstalled the ioroot. Complete success. Super su is in the apps and su commands work.
Next I went on to download the rogers TWRP file (even though my phone is a videotron phone) and install it using this:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Which worked!!!
I went to hard reset data and booted into the twrp interface.
I wiped everything from within twrp and went to reboot. it then informed that supersu was NOT installed on my phone and to slide the bar over if I wanted to install so I said yes...
But kind of bad news now:
Stuck at lg logo...:silly: Stays at lg logo and led is lit up changing from blue to green.
So what now?
Any suggestions?
Thanks a lot for the help everyone.:good:

See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app

andro ninja said:
See if you can get into recovery using adb or the holding the vol+pwr keys
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
(it also seems I can no longer access the internal storage from windows explorer, although the phone is being recognized in devices and printers as "modem LG G2"... It attains this status when it is stuck at the lg boot loading screen)

zprovo said:
Like into the TWRP interface?
Easily yes, I absolutely can.
Next?
Click to expand...
Click to collapse
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.

andro ninja said:
Did you take any backup using TWRP earlier? If yes then restore it.
If no then you can push another ROM for your device on to sdcard using ADB and install it and see.
Click to expand...
Click to collapse
Ok I will try this now.
If you could provide with adb code example for copying a file to /sdcard i would really appreciate it.
Where do I go within the twrp recovery afterwards?
Thank you so much.:highfive:

adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app

andro ninja said:
adb push <local> <remote>
Sent from my LG-D800 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:

zprovo said:
ooouuuufff.
New problem
Houston we have a problem:
adb devices = nothing.
How can I get adb devices to work if I cant boot into os and it is not recognizing it when in recovery?
Ahhhhhhhhhhhhhhhhhhhhhhhhh:silly:
Click to expand...
Click to collapse
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.

andro ninja said:
Windows ****!! Follow this thread http://forum.xda-developers.com/showthread.php?t=2263822 and install that driver and try.
If not then find yourself a linux box and try. I am sure It'll work.
Click to expand...
Click to collapse
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:

zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
You don't really have to burn a CD/DVD, you can use a USB drive.
I don't know much though. I've been doing these things for quite some time now so have experience and I am totally free now so helping you here.

zprovo said:
Ok trying this now. Dont have acces to a linux right now so i hope I wont have to burn a live cd and all that fun stuff...
Thank you again. You seem to know a lot about this phone/android in general:good:
Click to expand...
Click to collapse
It WORKED!
Awesome fix.
adb devices now gives:
(device number) recovery
Ok going to copy a rom and kernel and try to install.

Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.

zprovo said:
Tried two different roms. Same result
Failed.
set_metadat_recursive: some changes failed
E:Error updating updater binary in .zip '/sdcard/...zip'
Wow just wow.
Any ideas?
This was with omni and cm11. Going to try with a stock rooted rom as soon as it finished downloading.
Click to expand...
Click to collapse
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.

andro ninja said:
look here http://forum.cyanogenmod.com/topic/86979-cm-11-20140124-set-metadata-recursive-some-changes-failed/
---------- Post added at 11:57 PM ---------- Previous post was at 11:23 PM ----------
Just get a latest version of the recovery for your device and install it.
Click to expand...
Click to collapse
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)

zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
I remember I had same problem. I use to restore only the boot partition from a backup of a stock rom.
So try installing a stock rom like this one http://forum.xda-developers.com/showthread.php?t=2595586. If it works then boot into recovery and take a backup then install whatever you want to and the just restore the boot partition if your are stuck at boot logo.

zprovo said:
Ok so I managed to update the recovery to TWRP v.2.6.3.4
Installing all zips is working now.
I tried many combination of cm11 with kernels from this page: http://forum.xda-developers.com/showthread.php?t=2611749
Furthest I got was cyanogenmod logo on bottoms of screen for 10 seconds then boot and looping of the same thing over and over.
Omni rom also loaded up til the logo same thing though after.
Bell stock rom is still downloading I will update when I have tried it.
Any reason why the roms would bootloop like this?
Thank you again. I cant believe the progress you have helped me make...:good: I feel like it is possible I am very close to a functional phone again (maybe just maybe hehe)
Click to expand...
Click to collapse
Ok just finished installing the stock bell rom from the site I linked in a previous post.
Stock D803 rom with stock D803 kernel, both installed succesfully.
Phone is back to exactly how it was when I started this thread. EXCEPT that I now also have TWRP running alongside it.
So that includes:
-*#06# = IMEI Null
-phone reboots randomly every 5 to 15 seconds
-keyboard never comes up
-widgets always have a "loading" circle spinning on them
-trying to enter security and settings = auto reboot
-all other options are accesible and useable as long as no keyboard is involved since it never comes up
-no wifi
Wow, this is one hard to fix phone.
Or it simply has hardware damage. but I doubt it since it has no issues running recovery.
Any ideas?:laugh:

Random bootloops! Fastboot detecting device but not adb!

Hey there,
My phone started bootlooping this morning out of a sudden.
Tried going to recovery to wipe cache etc but not booting in recovery.
Tried adb commands but the phone doesnt detects itself.
Surprisingly/be default the phone is recognised by fastboot commands.
I have some important data in my phone would be glad if it is saved.
Else have to make do with whatever is necessary to bring the phone alive.
When connected this is what it looks like.
Please guide .
Thanks in advance.

You just described the legendary Boot Loop Of Death or more commonly known as BLOD. In my experience with my phone, no way to get anything from the phone once it's in this state. There is a great tutorial by Heisenberg on here. Maybe on of the chapters addresses saving data. Once you give up on the data, do a flash-all.bat using a factory image through fastboot. If you get no errors but continue to boot loop with no access to the recovery, your most likely looking at RMA as your only option.
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
You just described the legendary Boot Loop Of Death or more commonly known as BLOD. In my experience with my phone, no way to get anything from the phone once it's in this state. There is a great tutorial by Heisenberg on here. Maybe on of the chapters addresses saving data. Once you give up on the data, do a flash-all.bat using a factory image through fastboot. If you get no errors but continue to boot loop with no access to the recovery, your most likely looking at RMA as your only option.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
I did tried getting it to restore it to stock.
followed https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 post 10.
Still bootlooping.
My phone is out of gurantee so rma is out of question!
Any other suggestions?

divyanshu308 said:
My phone is out of gurantee so rma is out of question!
Any other suggestions?
Click to expand...
Click to collapse
Try pressurizing Huawei and hear what they say.They should be knowing about the issue.

Several people have talked then into doing the RMA by referencing the hundreds of people talking online about it. Just ask them how they can sell a faulty device and not support it.
Sent from my Nexus 6P using XDA-Developers Legacy app

divyanshu308 said:
I did tried getting it to restore it to stock. followed https://forum.xda-developers.com/showpost.php?p=62924118&postcount=2 post 10. Still bootlooping. My phone is out of gurantee so rma is out of question! Any other suggestions?
Click to expand...
Click to collapse
It's normal for ADB to not work unless you are in recovery mode. Without ADB you cannot push/pull files from the device. Try to fastboot flash or fastboot boot a TWRP recovery image from your PC. Any errors? Sorry, but If you cannot access recovery mode you are "dead in the water". Options are to start over with a new phone or source a used 6P and swap the motherboard. One guy in Korea found a used one for around USD $60.

v12xke said:
Try to fastboot flash or fastboot boot a TWRP recovery image from your PC. Any errors?.
Click to expand...
Click to collapse
It does flashes fine without any errors.
Doesn't boot into it though!
I was able to boot to recovery mode for once last night but didn't do much help although made me more optimistic about it.
Will try tinkering around more before giving up.
I'm actually flashing every google official image to see if it works on any version.
Will post the result soon.
One more thing if you see the screen shot I posted originally the last shows "Connect USB data cable" but it doesn't shows connected status even though it does gets detected and fastboot command works well.