LG update bricked the phone. Stuck at cwm - G2 Q&A, Help & Troubleshooting

I have a rooted d802 with stock rom. All was just fine and i noticed there was an update available from LG... categorized: under system/app update.
I downloaded it and as soon as it restarted my phone, it came to the recovery screen... and it is there... i tried rebooting, hard reboot, fiddle around with options that cwm offers me but nothing seems to be working...
Has anyone else had the issue? I do i get my phone to reboot ..? I know i can just download another rom and flash it through cwm but im quite happy with the stock and would like to get my phone back with minimum effort and more importantly data loss. I have no backups whatsoever.
Any help will be highly appreciated.

http://forum.xda-developers.com/showthread.php?t=2432476
Sent from my LG-VS980 using xda app-developers app
---------- Post added at 11:46 PM ---------- Previous post was at 11:45 PM ----------
Or try pushing a ROM using adb.
You won't lose internal by pushing a ROM. The flash tool will. I don't think there is a way to just make it go back to the way it was.
Sent from my LG-VS980 using xda app-developers app

Lawlrus said:
http://forum.xda-developers.com/showthread.php?t=2432476
Sent from my LG-VS980 using xda app-developers app
---------- Post added at 11:46 PM ---------- Previous post was at 11:45 PM ----------
Or try pushing a ROM using adb.
You won't lose internal by pushing a ROM. The flash tool will. I don't think there is a way to just make it go back to the way it was.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
Thank you.. I am stuck here : 4) Power off your G2, press Volume Up & and then plug in the usb cable (enter to a download mode)
As it wont take me to download mod ... no matter what combination of keys i press, it takes me to the same CWM recovery window.
I have never pushed a rom using ADB... Any tutorial for that? I tried searching but nothing relevant has came up.

[/COLOR]Or try pushing a ROM using adb.
You won't lose internal by pushing a ROM. The flash tool will. I don't think there is a way to just make it go back to the way it was.
Sent from my LG-VS980 using xda app-developers app
Click to expand...
Click to collapse
I found this,... http://forum.xda-developers.com/showthread.php?t=1667929
but i am not confident if it will work with the G2
EDIT:
Okay so i tried to push it through adb however it keeps saying device not found...

Try this http://forum.xda-developers.com/showthread.php?t=2451696
This thread helped me month ago.
1. You need to install Koush Universal ADB Driver for LG G2.
2. Connect your G2 with ADB. With that universal driver ADB will find your phone.
3. And after you have ADB access, run this:
Code:
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
4. Reboot with CWM or type reboot in ADB.

HONUS said:
Try this http://forum.xda-developers.com/showthread.php?t=2451696
This thread helped me month ago.
1. You need to install Koush Universal ADB Driver for LG G2.
2. Connect your G2 with ADB. With that universal driver ADB will find your phone.
3. And after you have ADB access, run this:
Code:
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
4. Reboot with CWM or type reboot in ADB.
Click to expand...
Click to collapse
You sir, are a legend. Thanks so much. Ended the 5 hour long struggle downloading numerous drivers, roms, trying different computers etc etc etc. :good::good::good::good::good::good:

j0sh1 said:
You sir, are a legend. Thanks so much. Ended the 5 hour long struggle downloading numerous drivers, roms, trying different computers etc etc etc. :good::good::good::good::good::good:
Click to expand...
Click to collapse
You're welcome

Related

[Q] Can't get phone to show up in My computer nor Device Manager

So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there.
Anyway, I am trying to install Cyanogenmod Nightly, but I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in teh Fastboot mode. I have tried after a factory reset.
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
SO strange,
Thanks
BTW: I have tried two different win7 computers, same result
Bump*
thegreyspot said:
So my nexus 4 is rooted and unlocked. Well actually Im not sure, because after updating with the OTA it seems to have lost that capability. Even though there are SU Binaries still there.
Anyway, I am trying to install Cyanogenmod Nightly, but I cannot get my phone to show up in my computer or Device manager. I have the drivers install and all. I have tried with usb debugging on and off. I have tried in teh Fastboot mode. I have tried after a factory reset.
I'm at a lost as to what I can do....When I try to go to recovery it says "No Command" or something
SO strange,
Thanks
BTW: I have tried two different win7 computers, same result
Click to expand...
Click to collapse
thegreyspot said:
Bump*
Click to expand...
Click to collapse
Is there a way to root from the phone and not use a PC?
Have you tried going into recovery and mounting your device in recovery
Sent from my primoc using Xparent Red Tapatalk 2
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
If that doesn't work then try doing the command in command prompt using your computers emulator sudo su hit enter then do command adb devices if that doesn't show up you can try sudo adb mount and if that doesn't work im out of ideas you can always google it and I'm sure find a way
Sent from my primoc using Xparent Red Tapatalk 2
sbkjuggalo said:
Have you tried going into recovery and mounting your device in recovery
Sent from my primoc using Xparent Red Tapatalk 2
---------- Post added at 12:30 PM ---------- Previous post was at 12:27 PM ----------
If that doesn't work then try doing the command in command prompt using your computers emulator sudo su hit enter then do command adb devices if that doesn't show up you can try sudo adb mount and if that doesn't work im out of ideas you can always google it and I'm sure find a way
Sent from my primoc using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I can't get into recovery cause it says "no command", when I try to get there
Personally I would try downloading Wug's toolkit and doing a full restore that way...
http://forum.xda-developers.com/showthread.php?t=2015469
Try that out
Sent from my Nexus 4 using xda app-developers app
lsbjeep said:
Personally I would try downloading Wug's toolkit and doing a full restore that way...
http://forum.xda-developers.com/showthread.php?t=2015469
Try that out
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I gave it a try and it actually said "device connected" but when it tried to go to fastboot mode, my phone did nothing and it says it couldn't find the phone in fastboot. I went to fastboot myself, and the program still counldnt find it.
Im so at a loss on what to do!!
Kinda desperate here :/ anyone else got a guess?
Need to bump this sorry. Anyone have any ideas of what I can try? I cant RMA this cause the phone is semi rooted (although it says it isnt rooted, i just see supersu and fastbook tells me lock state is unlocked)...
Have tried uninstalling the drivers from within device manager, then unplug your device and plug it back in again?
Sent from my Nexus 4 using xda app-developers app
Yes I have tried that, I have also tried a computer that has never seen a N4 before
Can you install the Windows drivers? Do you see the drivers in the Device Manager?
Make sure you have the latest windows Media Player installed. It installs the MTP service.
Try a different USB cable and other computers.

Paranoid Android User

So I'm new to rooting and custom roms in general and excuse my language but kind of a *****. I have the files to root my G2 and it shows up on adb devices. I'm only doing this because my battery life is really subpar and I'm hoping a root and custom rom will help me with this.
Now once I was rooted I was thinking of installing Malladus. I am having a little trouble figuring out the safest way to do this. I was told to root then download and flash a custom recovery using GooManager. How exactly do I do this?
Once that is done the instructions say:
Instructions
1. wipe data (if coming from ANY other rom)
2. wipe cache
3. flash ROM
4. flash LG Apps
5. flash GApps
6. let phone sit for a few minutes once booted to settle (a lot is done on first boot)
Now what exactly does the first instruction mean? Should I wipe my data if coming from a stock LG that is just rooted? After that I just select the option "wipe cache" on GooManager and make sure those downloads are in that order and hit flash no?
Thank you in advance. I have searched the forums but haven't found the exact answers I was looking for.
I would go to the twrp thread in the LG g2 original dev forum first
Sent from my VS980 4G using XDA Premium 4 mobile app
jrgilbert79 said:
I would go to the twrp thread in the LG g2 original dev forum first
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm still a little confused. I did some research on TWRP but still don't know exactly what it is. Also to install it I put it on the (by the directions)
Download the above file and place it in /sdcard on your device. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Make certain that you get this command right. Typing the wrong number could result in a brick!
Click to expand...
Click to collapse
What exactly is that doing? Also were is the /sdcard on our device? Thirdly... lol what do they mean by typing the wrong number?
Thank you for your response. Sorry for being new to this.
First that thread should take you to a root method once rooted we can install twrp which allows you to make backups of your current ROM. And more importantly try out new ROMs on your system. It's like saying once I'm tired of Windows XP I can flash/install 7. If I don't like it I can restore the old backup. Except in this case it's versions of android or modified android os that allows for new and exciting options. Root allows you to modify your cutrent ROM choice further. You can install fonts,themes, control battery draining applications, hide your nav buttons for more screen when you don't use them. If you are not in the know I suggest you do lots of research. In some cases we will be able to use applications we normally couldn't even applications from other phones once they are ported. ...essentially it's your ticket to be able to do the magical things the normal consumer says" " I wish my phone could do that" but except they can't because they don't have root or a custom recovery to make it happen. Step one is baby steps because brick is a nasty word you don't want to mutter.
Get rooted. Install a program called adb and install the LG drivers for your phone. There are step by step guides on how to do this and you might need to follow them into other links for guides to get from a to b. Once adb can see the phone. ..warning this is command line. Then you can download twrp IN SOME CASES YOU NEED TO ONLY DOWNLOAD AND INSTALL FILES BUILT FOR Your PHONES MODEL/Carrier and push it to the phone. Install it with ADB. Once you're there your fairly safe. Now your boot into recovery and make a backup reboot your phone and at least go visit a stock ROM thread for your model phone. There should be a development thread for each carrier.
Sent from my VS980 4G using XDA Premium 4 mobile app
jrgilbert79 said:
First that thread should take you to a root method once rooted we can install twrp which allows you to make backups of your current ROM. And more importantly try out new ROMs on your system. It's like saying once I'm tired of Windows XP I can flash/install 7. If I don't like it I can restore the old backup. Except in this case it's versions of android or modified android os that allows for new and exciting options. Root allows you to modify your cutrent ROM choice further. You can install fonts,themes, control battery draining applications, hide your nav buttons for more screen when you don't use them. If you are not in the know I suggest you do lots of research. In some cases we will be able to use applications we normally couldn't even applications from other phones once they are ported. ...essentially it's your ticket to be able to do the magical things the normal consumer says" " I wish my phone could do that" but except they can't because they don't have root or a custom recovery to make it happen. Step one is baby steps because brick is a nasty word you don't want to mutter.
Get rooted. Install a program called adb and install the LG drivers for your phone. There are step by step guides on how to do this and you might need to follow them into other links for guides to get from a to b.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I already am rooted. That part was easy. It was basically run adb devices, make sure device was there, run root.bat, follow instructions, and boom. The flashing a recovery and flashing a custom rom is what really confuses me. I have done research but have not found a step by step guide (that I understand well enough) yet on how to install whatever I need to do this.
What carrier you have?
Sent from my VS980 4G using XDA Premium 4 mobile app
jrgilbert79 said:
What carrier you have?
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Verizon Wireless VS98011A
http://forum.xda-developers.com/showthread.php?p=45870947
This thread really breaks it down. I think you should download the Verizon twrp. In the original android development thread post 3 first. Then follow the guide posted after the root video in the link above. Its the guide I followed. If you have working adb you got the hard part done bro ?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
http://forum.xda-developers.com/showthread.php?p=46300156
My suggestion and safest ROM yet for vzn. Follow the directions and when u wipe don't freak out ..this takes forever so it's ok to sweat.
Sent from my VS980 4G using XDA Premium 4 mobile app
jrgilbert79 said:
http://forum.xda-developers.com/showthread.php?p=45870947
This thread really breaks it down. I think you should download the Verizon twrp. In the original android development thread post 3 first. Then follow the guide posted after the root video in the link above. Its the guide I followed. If you have working adb you got the hard part done bro ?
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 09:24 PM ---------- Previous post was at 09:21 PM ----------
http://forum.xda-developers.com/showthread.php?p=46300156
My suggestion and safest ROM yet for vzn. Follow the directions and when u wipe don't freak out ..this takes forever so it's ok to sweat.
Sent from my VS980 4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Again this is my paranoid self speaking. It says I want adb working. If I was able to open the command window within my root folder on my desktop and run "adb devices" and see my LG then I have adb working? If so how is that the hard part, all you have to do is download and install the drivers for the phone to get that to work.
I plan on making my own step by step guide on rooting and flashing a custom recovery after this (with pictures) for people like me.
After that the commands to run the twrp install ate not that much more complicated
Sent from my VS980 4G using XDA Premium 4 mobile app
---------- Post added at 10:29 PM ---------- Previous post was at 10:17 PM ----------
http://bit.ly/1ihhiPu
1st link there really couldn't be a better resource.
Download Verizon twrp. Open adb folder. Find the adb in sdk or bin run as administrator. Copy and paste the commands. You should put twrp in the same folder adb cmd prompt is ran from after downloaded. That's it. I'd use option 2. Afterward you'll,learn you can download goomanager from market and do it with 1 click. ..
Sent from my VS980 4G using XDA Premium 4 mobile app
I thought this was about Paranoid Android rom... (i'll see my way out)
locoface said:
I thought this was about Paranoid Android rom... (i'll see my way out)
Click to expand...
Click to collapse
Sorry about that haha.
I have read through the instructions multiple times.
and I quote
Click download zip on the right. and go into the bin folder of the zip. push loki flash and the img like so:
adb push loki_flash /data/local/tmp/loki_flash
adb push openrecovery-twrp-2.6.3.2-g2vzw.img /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
adb shell
(IF YOU DONT SEE A # prompt, type su to get it.)
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery /data/local/tmp/openrecovery-twrp-2.6.3.2-g2vzw.img
exit
adb reboot recovery
Click to expand...
Click to collapse
Where exactly do I put these files? Inside the folder that has the root.bat file I used to originally root my device? Also once I execute these commands what is going to happen?

***need help, may have bricked my g2***

i did something stupid... lol. was running PA 4.4 rom with no troubles, had a backup as well. in preporation to sell this thing, i restored my stock backup , and noticed there was an update from att. so i decided to try installing it. well it downloaded fine, but when i tried to install it, it rebooted into twrp recovery. now i cant get it to boot into the OS. i tried restoring backup again but it still boots into recovery. any help?
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
lingarajug said:
At this point sideload pa 4.4 or return to bone stock they are described in the forums clearly.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
ssreynolds said:
i am trying to return to bone stock, but i cant get it to boot in to download mode? it still boots into recovery? can you elaborate or point me in the right direction of how to sideload ?
Click to expand...
Click to collapse
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
MalignantQuechnitlan said:
To get into dl mode....turn off the device....then hold ONLY the volume up button while putting in the usb cable...it will go into dl mode.
Click to expand...
Click to collapse
thanks for the reply... i know how to do it, but its not working because i screwed my device up by trying to insall an ota update with a rooted device and a custom recovery. so my only option now is to sideload, which i am working on... hope it works...
cant get adb to recognize my device, maybe because i dont have usb debugging enabled? which i cant enable because icant boot into os... what do i do to get this thing working again? i have android sdk tools installed
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
I had the same thing happen today, couldn't get into download mode. I followed the fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2477595 and it worked great.
He has links in that window to the specific file to flash.
lingarajug said:
Omg I can't believe tons of people are having same problem, ok here u go stock lg drivers don't seem to help pc recognize phone in recovery mode what I did was downloaded pdanet on pc and connected phone to pc in recovery mode and then opened pdanet in pc and installed lg drivers through it and then my pc recognized my phone as adb sideload when adb was run hope it helps you too.
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
I tried this, along with everything else, and my phone is still stuck in a boot loop. I cannot enter download mode. I was rooted with custom recovery, but i could never get the recovery to work. I tried to update to the OTA (i know, i know) and it killed the phone. Now when I connect it nothing happens other than a bunch of drive popups asking if i want to format. No download or recovery mode. only the LG logo screen and then a quick flash of the "Secure booting error Error: Boot Certification Verify!" screen, and nothing else since.
The main issue is that i cannot get my phone to be recognized by the computer for any type of reflash. If I could get into download mode, I could handle it from there. I hope I don't have to buy a new phone. Im not sure how verizon would feel about it if I took it back to them and it shows as rooted.
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
lingarajug said:
Can u at least get into twrp recovery using key combination
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Roninceo said:
No, I cant get to recovery mode either. I think this is a hard brick. I've only had it for one day. Something told me not to mess with it.
Click to expand...
Click to collapse
hei.connect to pc you can see a lot of drive to format?sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
hei.connect to pc you can see a lot of drive to format?sorry my poor english
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Roninceo said:
Yes,
When I connect it to my computer I see a large list of drives to format. the messages keep popping up from G: to V:
Click to expand...
Click to collapse
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc?
来自我的 Galaxy Nexus 上的 Tapatalk
pageniao said:
maybe i can help you.
can you see a new device called "QHSUSB_DLOAD" on PC "device manager" when you connect your phone to pc?
来自我的 Galaxy Nexus 上的 Tapatalk
Click to expand...
Click to collapse
Mine says "QHSUSB_BULK"
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
pageniao said:
see this
http://forum.xda-developers.com/showthread.php?t=2477595
---------- Post added at 02:16 PM ---------- Previous post was at 02:13 PM ----------
see this
http://forum.xda-developers.com/showthread.php?t=2477595
and from chinese
http://bbs.gfan.com/android-6728131-1-1.html
Click to expand...
Click to collapse
Ive seen the pages. Thanks for the help. I cannot get into recovery mode and unfortunately I can't read Chinese.
i dont know if you have tried this but i hear it works. it didnt for me, i keep getting a no memory error but if you get it to work can you please let me know how http://forum.xda-developers.com/showthread.php?t=2451696
on chinese .this problem so easy.
来自我的 Galaxy Nexus 上的 Tapatalk
this worked for me, and will work for those of you who are stuck in recovery boot loop... this is caused from installing an att update on a rooted device with a custom recovery and or rom. so heads up, if your rooted and you have a custom recovery and or a custom rom, NEVER install a OTA update!!!
so folow the instructions in the link, basically while in twrp, you use the amazing terminal emulator feature to type in the foillowing command, and viola! your phone will boot into the OS!!! make sure to type it in exactly as shown , with spaces and all... good luck!
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
http://forum.xda-developers.com/showthread.php?t=2451696

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

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:

Categories

Resources