Database Users

Nexus 4 stuck on boot screen after update

Need some help.
I just sideloaded the 4.3 update to phone and now it's stuck on the 'X' loading screen.
My phone was rooted, but all stock (including the bootloader). I used the sideload ADB command and everything went fine, but the phone now won't boot.
How do I fix this?

did you data wipe(factory reset) before flashing?? if not, you have too.

I applied the OTA...didn't think I had to
Any idea on how I fix it now?
Really don't want to lose all my data

Install a custom recovery and wipe or apply factory image

favaroooo said:
Install a custom recovery and wipe or apply factory image
Click to expand...
Click to collapse
Is there a way I can fix it without wiping everything?

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
I do not think because you have to change recovery you must unlock the bootloader and unlock bootloader wipe the phone

theprodigy85 said:
Is there a way I can fix it without wiping everything?
Click to expand...
Click to collapse
no, its the data(and other stuff) causing it not to boot. same thing when flashing custom rom, you wipe when fkashing different roms. and going from android 4.2.2 to 4.3, theres many changes, enough to consider it a different rom.

Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.

theprodigy85 said:
Shoot...I should have done more research before doing this.
I did a factory reset through the stock bootloader...but it's still looping on the 'X' screen.
Can someone walk me through this or point me to a guide?
Bootloader is currently unlocked and I'm able to get into the factory recovery.
Click to expand...
Click to collapse
are you flashing a zip or an img file??

simms22 said:
are you flashing a zip or an img file??
Click to expand...
Click to collapse
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...

Try to restore using the factory image

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
yea, the zip youd want to wipe data/factory reset, then flash the rom. dirty flashing wont help since the changes are big enough.

theprodigy85 said:
Initially, I flashed the OTA zip.
I'm okay with just restoring everything back to factory at this point...
Click to expand...
Click to collapse
I bought my ole lady a Nexus 4 for Valentines day, anyway, today she got the OTA update and let it install the update. Now mind you she is 100% stock, adb debugging was not enabled, and her bootloader was still locked. (She would not let me touch her Nexus 4 lol) When the device rebooted it stuck on Android Upgrading finishing boot. So I said well let me see what I can do, this is what I did to fix it.
I use only Ubuntu so this may not work on windows i do not know. I Booted the device to the bootloader, connected it to my laptop via USB. I opened a terminal and typed in "sudo fastboot devices" and entered my password when promted and this gave me the device ID and fastboot letting me know fastboot was working. I then typed in "sudo fastboot reboot" and the device rebooted but was stuck on the bootanimation. I opened the internal storage up on my laptop in my file explorer and made a copy of her internal storage. Next I booted the device back into the bootloader then opened a terminal and typed in "sudo fastboot oem unlock" and the device gave me the unlock warning and the yes or no options. I selected yes so it would factory reset. After it did the factory reset the device reboot and booted to the setup welcome screen. Hope this helps others, also thanks to my good good friend Ljjehl for reminding me to use "sudo".
Edit: If you open the command promt with Administrative permissions in Windows this will work in Windows as well. Go to C:\Windows\System32\cmd.exe and right click on the cmd.exe file and select run as administrator. Then CD to the location with your fastboot.exe command. Thanks to another good friend TheBr0ken.

Thanks for the help...
I just ended up flashing each of the 4.3 components from the factory image. Just annoyed that I lost everything...

I'm stuck at the same screen. I received the OTA update, I didn't do anything special. My phone is unlocked and rooted (or WAS) but that was months ago, the rest is stock.
I think having encryption on my phone may have made it do this. I don't think Google anticipated doing the update properly for encrypted phones. Now I fear I've lost everything because even if I could connect, all data is encrypted...

similar problem
After starting to OTA update it was going smoothly, i was making breakfast, came back to find my screen at the "starting apps" screen frozen. The little circle that rotated wasnt doing anything so i left it there for awhile longer and still nothing. It would not move off that screen so i held power button down and restarted. now its stuck at the X screen also.

Yeah, I'm stuck there too. Already tried Factory Rest, didn't work. So what can I do?

I was on stock 4.2.2 and unrooted. I used the 'Google Services Framework' hack to force the 4.3 OTA update. The update downloaded successfully, phone restarted to apply the update and then restarted again. And now its stuck at the Google screen and keeps on restarting :crying:
I dont have the USB drivers installed on my PC too.

Same Problem
I have a nexus 4 (stock and unrooted),after 4.3 update,it is lagging during phone lock on/off (2 sec/5 sec).Hence I restarted my phone,and it stuck at "x" logo.Did clean data 3 times and then its working.
The problem is,in 2 days,I have experienced and done above thrice?
What could have gone wrong?

Hi guys,
I've just found how to correct this problem. All you have to do is to correctly wipe your phone before flashing factory image.
So :
Fastboot erase boot
Fastboot erase recovery
Fastboot format cache
Fastboot format system
Fastboot format userdata
I've just unbrick a n4 this way 15 minutes ago.
I have found the problem in recovery where you can see error log saying "cannot mount cache"
So formating correct the issue.
Hope it can help, fingers crossed.
Sent from my Galaxy Nexus using xda premium

[Q] Stuck in bootloop after flashing factory image

I have no idea how to fix this. I downloaded the factory image and extracted everything and manually flashed the images with the exception of userdata so I don't lose my info. Reboot to a bootloop (the 4 colored dots). Go back and try it again, but the bootloop happens again. Then I go back and try to use a modified flash-all.bat (so it doesn't erase my data) but it doesn't even execute the update portion, just bootloader, radio, then 'press any key to exit'. I then execute the unmodified .bat file and it still only flashes the bootloader and radio images. So I go back and manually flash every image including userdata and reboot to the same bootloop.
I honestly have no idea how to fix this because I am literally flashing the stock image and it's not working. I did this same process with 4.2.1 and 4.3 without any sort of problems and now 4.4 suddenly soft bricks my phone. Each bootloop I have given 10 to 15 minutes to see if it does anything but it never progresses. Can anyone help? I didn't flash anything incorrectly and I even double checked with the '[HOW-TO] How to flash a factory image / return to stock / unlock / root #' thread to make sure I was doing things right. What are my options when the factory image doesn't let my phone boot??

I'm experiencing the same problem... thought it was something i did wrong.
I'll try to boot the recovery (stock) and see if wiping will do something.
It did for 4.3...
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
Indeed! It worked! (enter Recovery Mode and wipe EVERYTHING)

Awesome, it worked for me too!

boolean22 said:
I'm experiencing the same problem... thought it was something i did wrong.
I'll try to boot the recovery (stock) and see if wiping will do something.
It did for 4.3...
---------- Post added at 08:25 PM ---------- Previous post was at 08:21 PM ----------
Indeed! It worked! (enter Recovery Mode and wipe EVERYTHING)
Click to expand...
Click to collapse
I'm also getting bootloops but when I enter recovery I get the Android on his back with a red triangle with ! in the center... like there is no recovery. I was running bone stock 4.3 when I flashed the flash-all.bat.
EDIT: Sooo in the time I was writing this post I had it sitting on this error screen. Well I guess it timed out and rebooted, only this time it booted all the way. I'm not complaining, but now I'm REALLY confused.

jkhtx said:
I'm also getting bootloops but when I enter recovery I get the Android on his back with a red triangle with ! in the center... like there is no recovery. I was running bone stock 4.3 when I flashed the flash-all.bat.
EDIT: Sooo in the time I was writing this post I had it sitting on this error screen. Well I guess it timed out and rebooted, only this time it booted all the way. I'm not complaining, but now I'm REALLY confused.
Click to expand...
Click to collapse
The Android on his back is the recovery, you have to press a certain combination of keys (I can't remember which because I just mash them all) and eventually the menu will pop up that gives you the option to wipe things. But that's good it's working for you now, I just have no idea why some of us are unlucky with this update

Try doing a
Code:
fastboot oem lock
followed by
Code:
fastboot oem unlock
and flashing again ... worked for me!

buffalolsx said:
Try doing a
Code:
fastboot oem lock
followed by
Code:
fastboot oem unlock
and flashing again ... worked for me!
Click to expand...
Click to collapse
I had the bootloop issue earlier as well and was able to use the lock/unlock method with success. However, I didn't have to flash anything again afterwards. Once I was in the bootloop, I just turned the phone off then booted into fastboot mode. After that, I typed in the lock/unlock commands then did a simple restart. Fired right up.

Thank you guys!. ```fastboot oem lock``` did the trick

Unable to boot without hooking up USB cable

Having a bit of bother getting my nexus up and running again. woke up in the morning and realized the phone boot-looping at Google logo. Powered it on but it wouldn't get past Google screen. steps that i've taken;
1) fastboot oem lock/unlock
2) unroot and flash stock 4.3 using wug's NTK
3) unroot and flash stock 4.4 using wug's NTK
4) flash stock using fastboot command
i did everything exactly the same as the instructions provided from other threads/forums.
the ODD thing was, i need to hook up the N4 with the USB cable plugged into the computer in order to boot into OS. else the phone will bootloop. the battery is not empty on each occasion.
no errors, no nothing came out during each flashing process.
and i cant even get into stock recovery. i can see the android with red exclamation mark but the phone will power off after hitting the Vol Up + Power keys.
previously the phone was running PA 3.99, worked fine for the past month or so.
any suggestion?

http://forum.xda-developers.com/showthread.php?t=2010312
https://developers.google.com/android/nexus/images if you want kit kat 4.4 image

mickey1999 said:
http://forum.xda-developers.com/showthread.php?t=2010312
https://developers.google.com/android/nexus/images if you want kit kat 4.4 image
Click to expand...
Click to collapse
i did everything exactly as above, but to no avail. i've followed numerous threads and forums but they dont suffer the usb always-connect issue
Sent from my iPhone using Tapatalk

That's a weird one!
Can't really think of anything for you to try, only maybe try and format your partitions.. I know twrp recovery has a format data partition option, but I don't know how you would do the others. Then there's that recover from brick mode guide from download mode as a last resort maybe.
Hopefully someone will have better suggestions.

meangreenie said:
That's a weird one!
Can't really think of anything for you to try, only maybe try and format your partitions.. I know twrp recovery has a format data partition option, but I don't know how you would do the others. Then there's that recover from brick mode guide from download mode as a last resort maybe.
Hopefully someone will have better suggestions.
Click to expand...
Click to collapse
very weird indeed.
fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked
Click to expand...
Click to collapse
i wonder if this flash option formats the data partition of it just re-writes?
i'll try that recover from brick guide before sending it out to manufacturer. thanks for the input :good:

Reboot loop, can't access Recovery

This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.

StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk

StarShoot97 said:
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?

theesotericone said:
That vid you linked is an N5 with a stuck power button. It'll do the same thing and reboot recovery as well. It could be your issue but if it is it'll be the first stuck power button I've heard of on a 6P.
When you access fastboot does it stay on in fastboot or does it reboot from it?
Click to expand...
Click to collapse
I said it looks like this, I did not say the button is the reason
When I access fastboot it stays there until I manually select an option

ultyrunner said:
If you can get fastboot commands to work, just flash the factory image per Heisenberg's guide. Toolkits are more trouble than help. Return it to fresh stock with a full wipe and start fresh.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.

StarShoot97 said:
This is my last viable option, as I'd like to somehow pull my stuff from the phone. Afterwards I'd clean install it anyway.
Click to expand...
Click to collapse
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk

ultyrunner said:
You contradict yourself a bit so it is difficult to help you. You got to stock recovery but you can't boot into TWRP? If you have stock recovery, of course you can't boot into TWRP. You have wiped your data but you still want to preserve your data ... Huh?
Your phone isn't working so just nuke and pave with the command line and avoid toolkits. They are sometimes part of the problem.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
When stock recovery is installed, I am from time to time able to access it (most of the times it just ends in a bootloop)
If I flash TWRP I can't access it, no matter how often I try
I have factory reset my phone, the stuff on the internal is still there and I want to reach this, as I have my chats, SMS, university stuff and so on backed up on the internal storage
I am trying everything - all the regular adb methods, toolkits, every driver, nothing is working
Sorry if you don't understand my situation, but I am in a pinch right now

You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery and cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Edit2: wrong, see my latest reply

RoyJ said:
You said you have fastboot working?
Download the factory image zip file. Extract it. Extract the zip file from inside that as well. Move the img files to your platform-tools folder.
Reboot your phone to the bootloader. Hold volume down+power from a powered off state.
Plug into PC, open command line from your platform-tools folder.
Type, fastboot devices
Does it show your serial number? If so, start flashing the following images;
Bootloader-angler-angler-xx.xx.img, radio-angler-angler-xx.xx.img, vendor.img, system.img, boot.img, recovery.img
Flash with fastboot.
Code:
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
Code:
fastboot flash radio radio-angler-angler-xx.xx.img
(Substitute "xx.xx" for the version number shown in the img files you unpacked)
Reboot bootloader
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Once you do that, boot to stock recovery. Perform a factory reset again like you already mentioned you did as well as a cache wipe. Reboot and you're stock. If you're still not able to boot after that post back.
Edit: You said you wanted to avoid flashing factory images to keep internal storage in tact. Do it this way and you can have your cake and eat it too.
Click to expand...
Click to collapse
I did this already exactly like you wrote, did it again now, and I am still stuck in the reboot loop (boots up to Google Logo, then shuts itself down; repeat)
Can't reach recovery mode either

You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.

Fastboot twrp 3.0.0-0 then try to access it

RoyJ said:
You said you had access to stock recovery before?
You already did this?
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
If you flashed the factory images and still boot looping you may need to RMA.
Did you restore a TWRP backup?
Edit: Sorry, it's late and I have no sleep. I was wrong. I was thinking TWRP. Factory Reset from TWRP before my steps will keep internal storage I'm tact. Factory Reset from stock recovery will wipe internal storage. Everything. You mentioned you did that already from stock recovery before i made my reply. Your data is already gone as soon as you did that. If not, your emmc is likely corrupted and you need to RMA.
Click to expand...
Click to collapse
Yes, I think so too. I flashed the phone with the full Stock image, the bootloop is still there.
Looks like my precious is dead
At least I have my most important data like phonenumbers, pictures and SMS saved to the cloud
Gonna RMA it tomorrow
Goodybe my precious, I hope you'll be fine :crying:

Got my device back today, the mainboard was damaged, so I had no chance to get my data from the phone
Hey, at least my warranty has been renewed 'till 2018

StarShoot97 said:
This is the whole situation:
I have Pure Nexus installed on my 6P, running great for months. Suddenly yesterday it rebooted while I was using it and sticking in a bootloop. "No problem", I thought, and wanted to reboot into recovery - but nope, can't access it anymore. So I tried to reflash the recovery when I got home, but I only get errorors
When using the command adb devices the line just stays blank. The same with fastboot commands, besides "Fastboot devices"
After messing around a couple hours with the drivers and so on, I managed to somehow get the fastboot command working again. But no sign for the ADB commands, probably because I didn't turn on USB-debugging.
I am now at the point, where I have reflashed Stock Android with the Nexus Root Toolkit and managed to get back into stock android recovery, but still can't get TWRP to boot. I didn't want to delete my personal data, but I saw no other way and formatted /data in stock recovery. But the problem with the bootloop is still there.
It's not the classic bootloop, it boots as far as the Google Logo, then shuts itself down and begins again. I have now reached the point where I have to say, that the hardware might be damaged too. I'd love to somehow get access to the internal storage at least, but I can't without a working ADB.
Reinstalled TWRP with every available version, none of them worked. I am able to access stock Android recovery, but adb commands aren't working from here anyway.
Is there an option to fix the recovery mode? If I could get this working, the rest would be easy for me.
Edit: The reboot looks like in this Link. Only difference is, my device doesn't even the reach the dots.
Click to expand...
Click to collapse
Try flashing TWRP 3.0.2-3 or boot into twrp through fastboot. Using
fastboot boot recovery <twrp filename>.img
I think booting to twrp using this command will work.
And here's the link to Twrp 3.0.2-3 , as its not available on Official Twrp page.
https://idlekernel.com/twrp/nexus/twrp-3.0.2-3-angler.img

I had the same problem with my 5X, nothing worked I tried every possible solution described above and more. Nothing. I figured out that there was nothing to loose and followed directions from YouTube videos (links below) and it worked. Used heat gun at max temp for about 2 mins from each side. It's been about 12 hours since then, phone works flawlessly. Here are the links:
https://www.youtube.com/watch?v=SD25mdrgAys
https://www.youtube.com/watch?v=Cqh2x-TGnCY
Be careful handling the motherboard after you heat the first side, let it cool first before you start working on the second side. The same with the second side do not pick it up until it's cool.
5X, Pure Nexus Rom 7.1.2 June 5th security update, Elemental X Kernel,

has anyone found solution to this?????

[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,