Database Users

[Q]LG G2 re-flashing or rooting stock 4.4.2 bad rom

Hi all,
First off I've tried now for a two days to solve this, reading as much as I could find on here and the rest of the internet.
I decided to root my LG D802 running 4.2 and install CWM recovery no problem. Next I flashed a stock 4.4.2 vodaphone img. All went well untill i tried to use the touch screen, which shows that when i press on one point on the screen it selects multiple points basically its unusable and unable to do almost anything with it, however i have managed to turn on ADB and connect to the phone. So now i have a stock recovery and an unusable ROM.
So next up I tried to rooting it since I had ADB shell working ok, using the IOROOT25. This appears to work as when it reboots and installs the kkroot.zip in the recovery it's saying it worked. Now when I reboot and open ADB shell then type SU to get root I can't press ok when superuser pops up to asking me to give it permission, because of the touch screen problem.
If i can get root in ADB then remount the files system then i will be able to DD a new recovery img??
After getting this far and loosing, I then found this: http://forum.xda-developers.com/showthread.php?t=2432476 on flashing to stock, but the program crashes every time it's about to flash, so i tried doing a fresh install of windows 7 and then tried windows 8 however the program still crashes every time and yes I have followed the instructions and tried the manual method and checking the 127.0.0.0. lgblahblah is there
So no I am turning to you guys for help.
phone details;
Model: D802 32GB
Firmware operator: VDF
sw version: D80220a
ro.build.fingerprint: lge/g2_vdf_com/g2:4.4.2/KOT49I.D80220a/D80220a.1392133741:user/release-keys
Recovery: <3e> KOT49I.D80220a test-keys

UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?

need help
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?

twon23 said:
Have you tried running IO root to again root on your device? Also do you know much about linux, command line and android tools like ADB? Or do I need to explain the commands step by step?
Click to expand...
Click to collapse
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??

Ok so your phone not longer boots, correct? Do you know what build/version plus any other details of the rom you flashed? or even a link so i can have a look at the rom you have installed. Can you get into recovery mode and is it still a stock recovery image? also what is your phone d802? 16gb 32gb?

Mustafa1 said:
i downloaded ioroot25 and extracted it and ran root.bat
Looking for device...
Make sure drivers are installed. Check Windows Device Manager.
Make sure proper USB Debugging mode is enabled.
Verizon users make sure ethernet mode is selected.
Did you check phone screen for Yes/No prompt?
(select checkbox to always remember then hit yes)
...sometimes you need to unplug the USB cable then re-plug.
Determining device model...
Rebooting into stock recovery...
When recovery loads, select: *apply update from adb* with power button...
then press Enter/Return on your keyboard.
Press any key to continue . . .
(here the phone restarts and LG logo appears with (secure booting error)message in the upper left corner, and when i press any key)
Reboot back into System after flash in recovery finishes.
Press any key to continue . . .
and when pressing any key the cmd closes and the phone stays on with black screen and the back light on
in the pc i get many windows about formating drives (from H to S)
and i dont know anything about linux or command line
would you explain it to me??
Click to expand...
Click to collapse
If you're running root.bat as an admin, try executing it without admin privileges. Dunno why, but it seemed to work for me.

Mustafa1 said:
need help please!!
i have pretty much the same as your first problem, i installed the vodafone kitkat and the touch went crazy
and the custom recovery was deleted
and the lg support tool doesnt work for me
i dont know what to do.
sorry i forgot to mention that my phone is lg g2 d802 16 GB
Click to expand...
Click to collapse
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
---------- Post added at 06:18 PM ---------- Previous post was at 06:12 PM ----------
makgun said:
Did you try to flash CWM recovery? http://forum.xda-developers.com/showthread.php?t=2582142 This thread has What you need to do .. After then you can nandroid backup after then wipe everything except EFS on twrp after that you can stock_kitkat.zip on the xda forum. Efter that restore data via twrp.
I think that It will be correct without deleting your current rom ...
Click to expand...
Click to collapse
NOT CWM , it is TWRP
Are you from turkey?

twon23 said:
UPADATE: I have root but getting this error when trying to flash the recovery:
+] loki_flash v2.0
[-] Loki aboot version does not match device.
any ideas?
Ok so i found a different aboot img pushed to the phone and flashed that using dd
Code:
dd if=/data/local/tmp/about.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
this solved the problem above and a allowed me to flash cwm recovery. This then broke the installed rom so it wouldn't boot. now I had a custom recovery i flashed a EUR open 16gb stock zip this all went well and now i have a working phone What i should of done is remove the stock recovery.img from the zip and the line to flash it in the update script so it didn't flash the stock recovery.
This now leaves me with the loki flash problem above when trying to flash a custom recovery i could flash a different aboot.img but i don't want to break the current rom.
Any one else found a way to solve this problem?
Click to expand...
Click to collapse
Hi! I've recently flashed an updated stock ROM and have the same Touchscreen issue as yourself! Can you tell me the steps you have done to fix it? I'm using windows 8.1 to flash etc, and using a stock ROM I can't seem to get it to work again

[Q] Bricked my phone???

Hi,
Can anyone help me please.
I have twrp on my phone and used this to flash xtra smooth. Since i have done this it will not boot, i just get a black screen. I took a backup before i did the flash so just went back into twrp and tried to restore but it fails. It then just gets stuck on the liquid smooth boot screen.
I have tried to then go back to twrp and wipe everything and then install xtrasmooth and when i go to reboot it says i do not have supersu installed, if i chose to install it or not the same result happens, a black screen.
Iknow of adb but not sure how to do this properlly. if i open cmd prompt and type adb devide while phone attched i get that adb is not a recognised command.
Please can someone help, treat me as stupid, help me

foxguard said:
Hi,
Can anyone help me please.
I have twrp on my phone and used this to flash xtra smooth. Since i have done this it will not boot, i just get a black screen. I took a backup before i did the flash so just went back into twrp and tried to restore but it fails. It then just gets stuck on the liquid smooth boot screen.
I have tried to then go back to twrp and wipe everything and then install xtrasmooth and when i go to reboot it says i do not have supersu installed, if i chose to install it or not the same result happens, a black screen.
Iknow of adb but not sure how to do this properlly. if i open cmd prompt and type adb devide while phone attched i get that adb is not a recognised command.
Please can someone help, treat me as stupid, help me
Click to expand...
Click to collapse
Sounds like you have a lot of issues going on. I'm not sure what you're trying to do with adb but Google 15 second adb install xda. That'll install adb and fastboot on your device and allow you to use it from any directory. But I'm thinking you're going to have to flash the factory image.
Sent from my Nexus 9 using XDA Free mobile app

Thanks for this, will give it ago.

[VS995] Unresponsive touchscreen after dirtysanta, corrupt fastboot and recovery

After flashing dirtysanta successfully I wanted to move over to the magisk installation. Following the steps and attempting t use magisk I must have mucked something up very well.
after flashing the initial boot image and twrp from fastboot I hoped that it would fix these issues. Instead it seems to have corrupted fastboot. I did a kdz restore with reset hoping this would help but the touch screen still doesn't work and now I cannot setup the phone to allow adb. Booting from the system menu into usb-debugging mode just boots the phone normally
Currently I can boot into only into android but because I am stuck at the setup screen I can't connect through adb. I am not sure where to go from here.
The only thing that I can think of is getting a usb-otg adapter and connecting a mouse and attempting to allow adb by setting up the phone that way but I still cant flash anything from adb so I wouldn't know what to do from there. Does anybody have any suggestions?
Is there a way to install a boot image without fastboot?
I was very excited to start using this phone and this sucks. Any help would be appreciated

Do u have twrp at all? Some guys used a mouse and got threw the setup with it.
Sent from my LG-H918 using Tapatalk

I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot

I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot

tgtrottier said:
I can't access twrp at all attempting all methods leads to a normal boot routine. It doesn't even go to the stock page where it asks to wipe data. Just LG logo, black screen (assuming it crashes and restarts), then regular boot
Click to expand...
Click to collapse
I guess U didn't wait more than 30sec during the step 3, this is crucial.
---------- Post added at 05:09 PM ---------- Previous post was at 05:07 PM ----------
tgtrottier said:
I have successfully restored touch functionality by reflashing multiple different kdz files over and over again.
This has not fixed my inability to enter fastboot. I can enter the default android recovery from the no command screen after using adb reboot recovery but any other command just restarts the phone. Rebooting into bootloader from the default recovery just restarts the phone. I am not sure where to go from here, really upset because any fix requires fastboot
Click to expand...
Click to collapse
Get into download mode and Use LG bridge to upgrade

hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse

tgtrottier said:
hoi_lai said:
I guess U didn't wait more than 30sec during the step 3, this is crucial.
Is this afternoon running step 3 and waiting for boot? Because when I did it I waited around 30 min on the Verizon boot screen before pulling the battery to reboot.
In reference to LG bridge. Is this different than LGUP?
Click to expand...
Click to collapse
I mean you have to wait at least 30 sec for the step "fastboot flash recovery twrp-3.0.2-1-xxx.img", & also have to do it multiple times in order to load the TWRP successfully.
Click to expand...
Click to collapse

The strange thing is that I could access twrp for a while but then after restoring with LGUP I can't access even stock recovery. And flashing the notsostock kernel messed up the ramdisk it seems, because it said it couldn't write over it. The thing that concerns me is restoring with LGUP doesn't make any difference to these two thiñgs

I am suffering with a similar issue, VS995s model. The touchscreen stopped working after the TWRP flash, using OTG I was able to access TWRP. I restored both the dec16 kdz and the feb18 kdz with no affect on the screen. I was able to use OTG mouse and bluetooth mouse to reflash TWRP with dirtysanta and used OTG mouse to flash lineage OS v14.1 this did not solve the issue either. I re-flashed stock and am at a loss on the next possible step.
tgtrottier, you mentioned that it worked again after flashing a bunch of different KDZ files, do you know the specific one? I am looking for a useable touchscreen at this point and can deal with no root.

@frownyface
Did you discover the solution to the touchscreen not working? After flashing TWRP I have the same issue.

Nope i used an otg mouse and reverted to stock and returned the item.
I felt super bad about it, but i didnt have the time to invest in disassembling it to find the cause which i suspect was a loose connection due to the extended vibration during the root process.
Thumbs down sorry i could not be any help,

Moto E4 Woods TWRP flash "orange state device cannot be trusted" result

Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!

[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.

madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....

You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files

KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!

[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07

twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself