Database Users

Can't boot into Clockwork Recovery

Hi guys,
So just received my Nexus 7, the device is rooted and i'm trying to flash clockworkmod to the device.
So far, i've tried both of the toolkits in the developement section, ROM Manager and also flashing the recovery through ADB with the images in the development section too...
With some of them, after selecting recovery from the bootloader, it just stays on the "Google" logo, on other, it just boots up.
The device has no issue's booting, it's just Clockwork that won't boot.
Any ideas please?
Thanks.

SWFlyerUK said:
Hi guys,
So just received my Nexus 7, the device is rooted and i'm trying to flash clockworkmod to the device.
So far, i've tried both of the toolkits in the developement section, ROM Manager and also flashing the recovery through ADB with the images in the development section too...
With some of them, after selecting recovery from the bootloader, it just stays on the "Google" logo, on other, it just boots up.
The device has no issue's booting, it's just Clockwork that won't boot.
Any ideas please?
Thanks.
Click to expand...
Click to collapse
Have you rebooted into recovery after flashing and made it perminent? Otherwise the stock recovery will get flashed back (immediately)..
http://www.androidauthority.com/nexus-7-root-unlock-bootloader-clockworkmod-recovery-cwm-100890/
Usually I temp boot CWM, but today I flashed it on both my GNex & Nexus7. Can easily go back to stock recovery if required...

Thanks for the link mate, hadn't seen that one before and indeed, CWM is now working.
Much appreciated.

SWFlyerUK said:
Thanks for the link mate, hadn't seen that one before and indeed, CWM is now working.
Much appreciated.
Click to expand...
Click to collapse
No problem. When you exit CWM it tries to fix it anyway. Not sure if it just moves the file or what, but the key is to boot into CWM straight after flashing it (I made the same mistake this morning)..

I'm having the exact same issue...so If I re flash the Recovery as Markey Said will I lose the contents of my Internal memory or not?

hope this helps
MassiveDRS said:
I'm having the exact same issue...so If I re flash the Recovery as Markey Said will I lose the contents of my Internal memory or not?
Click to expand...
Click to collapse
if your using cwm i found to boot into recovery you have to have the 7 plugged into your computer with the micro usb..i dont know why but it worked for me..are you using the side bottons to get into recovery..if so plugged the cable in first then try to enter recovery

Easiest way is grab quick boot from the play store and it will let u reboot to cwm.. As above said a pc is needed because of a bug.. U can also do it connected to a phone if u have otg cable
Sent from my GT-N7000 using Tapatalk 2

or you can use ROM manager and reboot from there in cwm

capoooro said:
or you can use ROM manager and reboot from there in cwm
Click to expand...
Click to collapse
That's what I do. Works great.
Sent from my Nexus 7 using xda premium

kuczmad said:
if your using cwm i found to boot into recovery you have to have the 7 plugged into your computer with the micro usb..i dont know why but it worked for me..are you using the side bottons to get into recovery..if so plugged the cable in first then try to enter recovery
Click to expand...
Click to collapse
Yup it is working now Thanx bro
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
capoooro said:
or you can use ROM manager and reboot from there in cwm
Click to expand...
Click to collapse
I already Know that
but I'm asking about the button combo approach because, it is very important ; in case you brick your device and you can't boot it and obviously you cant lauche rom manger

MassiveDRS said:
Yup it is working now Thanx bro
---------- Post added at 05:47 PM ---------- Previous post was at 05:42 PM ----------
I already Know that
but I'm asking about the button combo approach because, it is very important ; in case you brick your device and you can't boot it and obviously you cant lauche rom manger
Click to expand...
Click to collapse
You can access CWM through the power, up, down method and choosing recovery mode.... the tablet MUST be plugged in though... at least for me it does. Running CWM6 Touch....

[Q] HELP!! I wiped my whole N7 in recovery.

Hi all!!
I have a huge problem i think.
Yesterday is was rooting my device, and i was about to start flashing a custom rom.
What happened is that in the proces of wiping dalvik cache etc. I by accident wiped the whole system!
So now if i want to reboot, recovery gives the error that there is no OS is installed. If i reboot my nexus 7 keeps hanging in the startup screen wich only displays Google...
It still can reboot in recovery or bootloader, but i cant figure out how to recover. I tried with 2 toolkits, but no succes! I made a nandroid backup but this doesnt work either.
Also i tried several solutions but none of them helped.
Does someone know how i can get my N7 to work again?? :crying:

Wugfresh's toolkit allows you to flash the stock image from the bootloader. Just make sure you check the box that states you cantvpower the device up.

Mskips toolkit, chose the option to flash Google image, it will download, and flash for you, if not your doing it wrong, push comes to shove your going o have to download a custom ROM and use adb to to push it on to your nexus 7 then fire up cwm and lash the rom, your nandroid will be gone unless you took it off/copied to a PC before you messed up.
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Wugfresh's toolkit allows you to flash the stock image from the bootloader. Just make sure you check the box that states you cantvpower the device up.
Click to expand...
Click to collapse
This^ i have done it a few times. When i flash a new rom i wipe all including system. Sometimes i get a bad download and i dont realise until i try to flash. Do as poster above says and you will be ok
Sent from my Nexus 7 using Tapatalk 2

leelaa said:
This^ i have done it a few times. When i flash a new rom i wipe all including system. Sometimes i get a bad download and i dont realise until i try to flash. Do as poster above says and you will be ok
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I tried all those things named above with both toolkits..
When i try to flash to stock it keeps hanging at some point, or i get errors. What am i doing wrong?
I will try again what jordaanooo mentioned.. hope this time it will work.
If it doesn't work, does it help to post some screenshots with the error i get, or where it gets stuck??

Yeah, try it, make sure you state you cant boot it, and tell us what parts it stops/fails at

SMH dont use toolkits -_- so you're saying you "could" get into recovery? Why didnt you just adb push a rom
Code:
adb push name-of-rom.zip /data/media
Then flash that rom?

ÜBER™ said:
SMH dont use toolkits -_- so you're saying you "could" get into recovery? Why didnt you just adb push a rom
Code:
adb push name-of-rom.zip /data/media
Then flash that rom?
Click to expand...
Click to collapse
Yes recovery does work. How do i push that? i have never done that...

TouchHD said:
Yes recovery does work. How do i push that? i have never done that...
Click to expand...
Click to collapse
he just mentioned it in the post. do you know how to use adb? do you have it installed?

Fufu_the_Great said:
he just mentioned it in the post. do you know how to use adb? do you have it installed?
Click to expand...
Click to collapse
i used it before for rooting my htc one x, so i think i have the needed files. but i don't know what i need for the n7 and how to start. I have been searching, but can't figure it out..

Jordanooo said:
Wugfresh's toolkit allows you to flash the stock image from the bootloader. Just make sure you check the box that states you cantvpower the device up.
Click to expand...
Click to collapse
done something like this yesterday,worked :good:

TouchHD said:
i used it before for rooting my htc one x, so i think i have the needed files. but i don't know what i need for the n7 and how to start. I have been searching, but can't figure it out..
Click to expand...
Click to collapse
pretty simple. if you know how to use adb then you just need to just a ROM to apply. wether it be the stock or a custom. once you know what ROM, the easiest thing is to paste it into your adb folder (usually platform-tools) and just push it onto your sd card

Fufu_the_Great said:
pretty simple. if you know how to use adb then you just need to just a ROM to apply. wether it be the stock or a custom. once you know what ROM, the easiest thing is to paste it into your adb folder (usually platform-tools) and just push it onto your sd card
Click to expand...
Click to collapse
Thanks will try that this evening when i get home!

Jordanooo said:
Yeah, try it, make sure you state you cant boot it, and tell us what parts it stops/fails at
Click to expand...
Click to collapse
I'm trying to flash to a stock rom at the moment with the wugfresh toolkit. it seems the process is stuck at the point where it is "sending 'system' to the device. it's "sending 'system'" for more than an hour now... is that ok?? or is there something going wrong?
the picture show's where it gets stucked

Fastboot flash bootloader bootloader-grouper3.34.img
Fastboot flash all nakasijroo3d.IMG w/e its called

Do you have cwm or twrp installed? If so you can mount the 7 like a mass storage device to your computer. This will give you access to the SD card where you can transfer a ROM from your computer to your tablet....I'm not sued where the setting is.....just go into your recovery and dig around....I think its under advanced...
Sent from my Galaxy Nexus using xda premium
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
I just checked...if u go under the mount setting. There's a USB mass storage option......def the easiest route....adb is easy ...if you know how to set it up right
Sent from my Galaxy Nexus using xda premium

TouchHD said:
I'm trying to flash to a stock rom at the moment with the wugfresh toolkit. it seems the process is stuck at the point where it is "sending 'system' to the device. it's "sending 'system'" for more than an hour now... is that ok?? or is there something going wrong?
the picture show's where it gets stucked
Click to expand...
Click to collapse
are you familiar/comfortable with the command prompt?

Fufu_the_Great said:
are you familiar/comfortable with the command prompt?
Click to expand...
Click to collapse
no not really.. i'm a real noob with that.

TouchHD said:
no not really.. i'm a real noob with that.
Click to expand...
Click to collapse
do you remember where you installed android sdk?

Fufu_the_Great said:
do you remember where you installed android sdk?
Click to expand...
Click to collapse
Yes i do. C:\SDK

***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

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

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: