Getting to recovery WITHOUT ADB comment on vs995 with dirty santa root - LG V20 Questions & Answers

I am trying random things on my V20 VS995
I am rooted Dirty santa style. the issue is that i cannot get the recovery buttons to work to get back into twrp when i do something that causes me to get stuck at the verizon boot screen. I could use ADB reboot recovery IF the rom has already been started and debugging has been turned on and authorized, but when its a clean boot, i no longer have that option as when stuck at the verizon screen the device does not show up in ADB.
I have direct access to fastboot and download mode.
The reason this is a problem is that from what i can gather, when i cant get into recovery, i have to kdz flash and redo dirty santa, and i find getting dirty santa to work first try is extremely difficult.
Also because of modded boot image Fastboot boot recovery.img wont work
Any input is appreciated!
****EDIT****
Figured out i was repressing power way to fast, waited about 1.5 seconds and got it to work. my bad.
thanks!

Related

ATT D800 Fastboot Loop No Recovery No Download Mode

Hello All,
I've been searching for hours. I had rooted my LG G2 weeks ago with no problems. I then un-rooted it and I thought reset it to factory. Today in Target I pulled it out of my pocket to make a call and it was black screened to Fastboot.
I have tried holding down Volume - and Power and entering recovery to reset to factory but it immediately goes to Fastboot loop.
I have tried holding down Volume + while plugging in USB for Download Mode but it immediately goes to Fastboot loop.
I have tried adb commands, error: device not found.
I have tried manually updating the Android drivers through Computer Management and selecting many of the Android Platform Sooner versions. My Win7 PC recognizes the phone as ADB Interface > Andriod Sooner Single ADB Interface in Device Manager.
I have tried this http://forum.xda-developers.com/showthread.php?t=2477595 and flashed both laf.img and I cannot get into Download Mode.
What else can I do? Does anyone have any other ideas?
Thanks for your time!
hey same exact thing just happened to me. i had it rooted from earlier, but ended up keeping the stock rom on my AT&T LG G2 D800. What I think happened was ATT just pushed out an OTA update (not sure about other carriers), supposedly some small 15mb update to prepare for upcoming releases and despite declining the install, the phone of course did it anyways.
No recovery, no download mode, factory reset doesn't do anything.
Thanks AT&T! :good:
Are we completely boned here?
This worked for me
http://forum.xda-developers.com/showthread.php?t=2451696
Follow this thread, I tried the TWRP terminal code and it worked. Let me know how it goes
Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.
sniffs said:
Did anyone figure this out? I am stuck in fastboot mode. I can run fastboot commands, but thats about it.
I can't get to ADB, I can't get to recovery, I can't get to download mode. I reboot the phone and it goes immediately back to fastboot.
I've tried flashing recovery, the laf.img, and even rom's inside fastboot and nothing is seeming to work.
Click to expand...
Click to collapse
If you can't get adb access with either single sooner or pdanet drivers, you may have to resort to this..
http://forum.xda-developers.com/showthread.php?t=2582142
(actually kind of sounds like fun to me)
if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.
autoprime said:
if you're stuck in fastboot mode then you can simply use the fastboot commands to write the aboot, sbl1, boot, recovery, laf, rpm, tz and dbi partitions.
you can substitute stock recovery.img for a properly patched twrp/cwm img (renamed recovery). from there you should be able to boot into download mode... custom recovery.. or boot back up.
Click to expand...
Click to collapse
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!
im onthe verizon variant and stuff like this just annoys me to no end you say no lg pushes it to your device anyway its wrong not even samsung stoops this low i am glad i have a custom rom
sniffs said:
I found a site that had the backed up D800 .img files. I had to use Ubuntu to write them back to my device.. after like 15hrs of googling/writing on forums, I finally got my device to boot back up! lol..
of course there was a popup saying that my device was suspected of rooting and it won't update.. but who cares, it works now!
Click to expand...
Click to collapse
what site?
Sorry for comment this old post, but i need help with my D800 y cant unbrick it
Keep trying flashing the D800 file or what?
Hello friends to see if I draw from this setback. My situation is that I have no recovery or download, but when trying to get the img fastboot does not exceed by "erasing" or "writing" who knows how to solve this please !!
Thank you :good:

Am I bricked?

I tried rooting my phone and think I bricked it. I followed the instructions here:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
I got to the
I got as far as booting into TWRP for the first time and did the format. It wasn't clear to me where I could flash SuperSU.zip. Even though I had previously downloaded it, I couldn't find it. I presume it got wiped out when I formatted.
I then tried to reboot and it got to the Verizon flash screen and would go no further. ADB saw the device so I ran ADB reboot recovery and it got to the same spot.
Then I tried fastboot flash boot bootbackup.img and fastboot reboot. It then booted to a screen that is just a bunch of gray lines (I can see the VZ splash screen behind it) but ADB does not see the device.
This is where I'm at and can't seem to get back to TWRP or anywhere else. Is the phone hosed?
okay so I got to the same exact spot and got stuck for a while I believe. when it allows adb support on the verizon screen, preform the adb command for booting to the recovery and it should boot into twrp if you flashed it right ealier, just flash weta or lineage os on the rom slot. if not, download the kdz for the phone, lgup and uppercut and start fresh
Only advice i have is this: Keep trying all the steps untill you can flash raid your system..... and keep formating your phone (volume/power, untap-power at logo, volume/power) until all the steps have worked.
Disregard
h910 user....

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

Hard/soft brick

I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.

US996USA lost root and TWRP - No fastboot

My V20 was unlocked via factory method and rooted in2017. I had xPosed framework installed. One morning in Dec. 2020 I woke to an unrooted phone. I tried to install my latest TWRP backup but TWRP was gone. The hardware button combo that always got me TWRP did a factory reset instead. Now I cannot get fastboot. Both ways of entering fastboot produce a regular boot. The bootloader unlocked nag screen still appears on boot up. I don't know what happened but I want root back. What can I do?
I am not XDA lingo savvy so forgive me if my answer does not apply.
I recently tried roting US996 with Magisk vs 21.4 but got a loop start up.
I then noticed Fastboot would not find the device.
However if I hold vol up and plug in the USB cable to the computer it will go into fastboot. I can type Fastboot devices and it will show my device. That was how I was able to start the process to restore the phone to stock.
If that helps great, if not , sorry I am just trying to give back something as I try to get this to root in Magisk 22. (still learning)

Categories

Resources