Related
Good evening XDA,
I've got a Nexus 6p (obviously), and can't get it to boot. Unfortunately, I don't know the exact history as to how it's in this state.
I've tried everything I can think of and read every guide/steps/forums I can find that relates to my situation.
I can get to the bootloader and issue Fastboot commands. I've got adb/fastoot/drivers installed via the sdk/platform tools, and drivers are up to date as far as I can tell.
-I'm using the OEM cable attached to my computer (Surface Pro3, Windows 10)
-I can unlock/re-lock the bootloader as I wish.
-I've tried WugFresh toolkit, flash factory + unroot. All completes, but phones continues to loop even after leaving it for an hour+.
-I've tried Heisenbergs guide for manually flashing stock google images via fastboot to no avail. Tried several different google images. Everything completes, but it still just loops.
-I can get all fastboot commands to complete with no errors, but the phone just simply bootloops at the google logo, or if I leave bootloader unlocked it loops with the orange triangle & google logo. I have left it looping for at least an hour+, but it doesn't finish:crying:
-Stock recovery or a fastboot flashed trwp recovery simply won't boot, it just goes to the google logo and loops, I don't get the dead android w/triangle. "Recovery" in the bootloader selections is RED, if that means anything. Tried fastboot commands to boot recovery, but just sends it to the google logo and loops.
-Adb commands don't work, only fastboot commands.
-During flashing a google stock image with fastboot, the only thing that stands out is "max download of ####### reached", or something similar, but it still completes.....?
Seems to me that I've got a true brick (first ), and just need to send it in for repair.
Any help would be greatly appreciated. TIA.
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
TnT_ said:
Well, personally I believe it is a brick. Because I had something similar and it was fixed by a simple complete wipe of the phone - did you try that, and follow the order for fastboot flashing?
As for replacement. I have a dent in the frame that effected the volume button until I pushed it back in. I contacted google support and they told me since it was physical damage. That I would have to contact Huawei for repairs, and they promptly gave me their number. As for your case it could be a board failure and could go under warranty through google. Good luck! Off to help more people.
PS: Use a twp version higher than 2.x.x, that was what my issue was.
Click to expand...
Click to collapse
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Dhickory said:
Thanks for the reply. I thought (hoped) it might be a button issue too, but there is no damage to the phone, and buttons work as they should in the bootloader. Gave them a slight tap, but same results.
As for the "complete wipe", I can only erase/format via fastboot (or WugFresh ToolKit) since I can't get to recovery, and that hasn't given me any different results.
Click to expand...
Click to collapse
Does all the data in the bootloader look fine? The storage size etc?
TnT_ said:
Does all the data in the bootloader look fine? The storage size etc?
Click to expand...
Click to collapse
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Dhickory said:
As far as I can tell, everything looks normal. Is there anything you know of that would raise suspicion? I'll post exactly what it says when I get back to it.
Click to expand...
Click to collapse
Usually with board failure - that I saw in other threads - there are missing fields. My phone had a little glitchyness after I accidentally flashed the userdata.img - which caused my 128gb to become 32gb, which I found amusing - Other than that, I don't know. I'm sure others would reply.
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Dhickory said:
I powered the phone off via the bootloader menu. Came back to the phone and powered it on, and it started the bootloop. I only held down the volume down button (during loop), and it booted to the bootloader. Is this normal? I realize I'm probably grasping at anything, but I've got some time to kill and just curious if it loops and only the volume down button is held should it go to the bootloader?
Click to expand...
Click to collapse
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Jammol said:
TWRP 3.0.2-1 may have been used on this device and a restore may have been attempted, causing the EFS partition to be damaged. There a thread in this qna section by the tittle of Lets get this......I don't remember the rest, but it has a post concerning what to do to fix the bootloop.
Edit
Here you go: http://forum.xda-developers.com/showthread.php?t=3453119
Sent from my LG G4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the link, and I've been reading the "Let's figure out this brick together" thread. The link you posted requires ADB commands to work to fix the EFS partition, but I can only run fastboot commands. ADB nor Recovery work on my device. Still reading...
Woohoo! Huawei replaced the phone, no questions asked. I think the saving grace was being able to flash stock images, and relock the bootloader. May be helpful to anyone else in this situation that can only run fastboot commands, and no recovery.
Through my searches I couldn't quite find a problem like mine.
Here goes.
My device will not reboot into fastboot mode, using adb reboot bootloader or restarting and entering recovery mode it just restarts the system.
If I instead enter adb reboot recovery it shows a black screen with the android droid laying on it's back with a yellow triangle with an exclamation mark. text on the screen reads waiting for command but fastboot commands do nothing.
any help would be appreciated.
is your v20 a VS995
LASERWOLF452 said:
is your v20 a VS995
Click to expand...
Click to collapse
No, it is an LS997 the sprint us model.
MadnessChi1d said:
No, it is an LS997 the sprint us model.
Click to expand...
Click to collapse
Hold volume down while plugging in the usb cable. With the other end of the cable plugged into your computer.
tymestopm said:
Hold volume down while plugging in the usb cable. With the other end of the cable plugged into your computer.
Click to expand...
Click to collapse
It just shows the lg screen then the charging screen.
I am having the same issue with the LG V10. There are very few mentions out on internet of the software version I have on my phone (21J). Maybe T-mobile is silently patching with and OTA to remove fastboot access?
I have the same issue. I'm on the December 2016 security patch.
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
runningnak3d said:
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
Click to expand...
Click to collapse
ls996 sprint i have the same problema ....there anyway to get fastboot please
I am having the same issue on my VS995, and I was wondering if there was anyone that has found a fix/work around? This post is literally the only mention on not having fastboot, or not being able to boot into fastboot. Any help is greatly appreciated.
LG V20 Fastboot
runningnak3d said:
Fastboot was pulled by the carriers (except TMobile, but even their fastboot is only good to unlock the bootloader).
-- Brian
Click to expand...
Click to collapse
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Fyrebaugh said:
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Click to expand...
Click to collapse
Because the carriers are wicked and want to control what you do with your phone
Sent from my LG-H910 using XDA Labs
Fyrebaugh said:
Why on earth would they remove fastboot? Currently I am having an issue with texting, I can text everyone except my wife... I have cleared the cache, rebooted the device, removed the years of text message thread that we had on it.. Since I can text others and get no failure to send messages, (most of the time), and can make calls to my wife, (and everyone else for that matter), I believe it to be a software issue, resetting the phone to factory default I think would be a good troubleshooting step.. Also if I were to sell the phone I would love to be able to reset it to factory default, and clear all my data off the phone???
Click to expand...
Click to collapse
You can do that in recovery. Hold volume down press power until the screen turns on then tap power repeatedly and itl prompt you to factory reset. It does this in stock recovery, if you're rooted itl boot into twrp (and youll have to manually enter the wipe menu and format data)
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
(but "adb reboot recovery" seems to go into recovery ...)
pierro78 said:
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
Click to expand...
Click to collapse
PS : I was fool enough to try DirtySanta for Newbies ( https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278 ) and it worked - at one step I had to go into fastboot with the buttons and this one time I was lucky enough and fastboot mode worked
pierro78 said:
just got an "h910" from aliexpress (it says v10l), can't go into fastboot mode using the buttons or "adb reboot bootloader" ...
(but "adb reboot recovery" seems to go into recovery ...)
Click to expand...
Click to collapse
Read the thread you just posted in. Post 8 in particular.
Dirty Santa replaced aboot (the part of the bootloader that provides (or not) fastboot) with an engineering one that does have fastboot with the ability to flash and also doesn't care if the bootloader is unlocked or not.
As much as this intrigues my curiosity, I'll take a pass for now........... I've rooted and TWRP'd phones in the past, but my past was a more simple time, with phones like the Droid, Droid-x, and those variants............ you just rooted it and it worked, simple. Nowadays, you have to jump through so many hoops, and if you miss just ONE, you probly brik'd yer phone. Nah................ will just wait some time, non rooted phones seem to do more these days
All I wanted to do was unlock bootloader and install twrp. what a bunch of bullcrap! Screw you Sprint for removing the bootloader and trying to control our phones. This phone is complete trash. I can't even install project treble for android 10.0 Q. I'm thinking about just getting an xs max and jailbreaking it. Forget android and all these fragmentation issues. At least iPhones receive updates past 2 years.
Having the same issues as everyone else. VS995. At first I thought it was only verizon... Just ordered a OnePlus 7 Pro. Hoping for something better than what the carriers can lock down.
Hey all! Hopefully you can help with this issue. I have had this phone through T Mobile for a few months now, and am stuck in a real bind. As the title suggests, I have a boot loop issue and Device is Corrupt issue as well. The red Triangle is an issue with the OS. I cannot get the phone to boot to Android, nor get into recovery. I can however bring up the IMEI menu, which displayed the IMEI. I really need help, as this is my main contact for job search and family.
Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.
elijah420 said:
Im on sprint so this method is unavalable to me.
Tried LGUP? you have the ability to shoehorn a KDZ file in whicj will bring your phone to stock
As this is a no go for the ls997 i have no idea how this is accomplished. Check the forums for said method.
Click to expand...
Click to collapse
I will definitely look into this. I just want my phone back TT.TT lol
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...
Griever0 said:
So, I jinxed myself. I did in fact get the phone back up and running. But its not working correctly. I have a black home screen and the Recommended apps keeps popping up... THis is going to be a long night...
Click to expand...
Click to collapse
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!
HELP
Griever0 said:
Scratch that, I just had to pick my home screen loader. Phwew. I did it and I feel Happy. THANKS For the help!
Click to expand...
Click to collapse
How did you do it, I'm currently having the same problem with a phone that's on T-mobile
questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see
chuckyanutsup said:
Were you ever able to get this resolved? I'm having the same problem, except it's not showing anything about the bootloader that I can see
Click to expand...
Click to collapse
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.
this might work for you!
questionblock said:
I wanted to chime in, I've got the same issue as OP.
What's broken:
turning the phone on normally - displays an LG logo; gets stuck, won't proceed past this point
holding VolUp while connected to PC - displays IMEI; won't enter download mode
holding VolDown - displays IMEI; won't enter fastboot or recovery mode
So, there's no way to get to recovery. I'm stuck with a $400 brick that displays a logo or an IMEI number.
LGUP w/Uppercut doesn't work either, shows up as an unrecognized device, and it wouldn't matter if it were recognized, because I can't get the phone to download mode to restore a stock .kdz.
I just ordered the phone on the 4th from Amazon, so I'll see if I can return it/get a replacement, but I'm guessing I won't be that lucky. It does display the orange "WARNING: Bootloader Unlocked" screen, meaning it's very easy to see that the warranty has been voided, so I guess whatever support I get is a crapshoot.
Again, since I can't get to fastboot mode, there's no way to restore to stock and relock the bootloader before returning it. Kinda dug myself into a hole here with no other options.
Click to expand...
Click to collapse
okay so holding VolUp while powered down and plugging into pc will bring up download mode if its still there,
if you have twrp installed prior to this red triangle then pull battery/put back battery. hold VolDown and power at the same time, as soon as LG logo comes up release power button (fast) and then hold it back down again while never letting go of VolDown. this is the factory reset hit yes for both questions and it should reboot phone into Recovery mode. some times you have to do it twice to get recovery (twrp) to pop up! i hope you have bootloader unlocked and twrp.
---------- Post added at 06:13 PM ---------- Previous post was at 06:07 PM ----------
Griever0 said:
I got it to install! Now to just play the waiting game and see what happens. I had to do some finagling to get it to work, but it works.
I found a H91810 KDZ, I started Uppercut which loaded LGUP, click on UPGRADE, then selext the KDZ file from where you saved it. Should work. Also make sure all of your drivers are up to date.
Click to expand...
Click to collapse
If using the LGUP you must get the G4 Dll file for it to read the phone and com its on. i believe its a common.dll file i cant really remember...
chuckyanutsup said:
Ok, I seem to have my device back up and running. The step I was missing was to remove the battery, disconnect the USB cable, put the battery back in, hold volume down but don't press power, instead connect usb cable. This got me into fastboot and I was able to recover from there.
Click to expand...
Click to collapse
Awesome! Glad to hear it!
my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.
weirdomane said:
my lgv20 is supposed to be on the corrupt screen but it looks like a glitch happened or something and the corrupt screen is all messed up it has the red warning signs across the top of the screen and it just says giberish and it keeps bootlooping. ive tried everything i can only get to imei display if im lucky and it tells me "press the POWER key to exit and restart the phone" but when i do it just takes me to the messed up corruption screen and stays bootlooping someone please help.
Click to expand...
Click to collapse
What model do you have?
You can put the phone to download mode (even if screen displays glitchy gibberish screen) by taking out Battery first, put battery back in after 10 seconds. Then just press Vol up and while keeping it pressed, connect to USB. If you have drivers installed, your phone will get recognized by LGUP. Now from here you can flash the stock rom.
when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian
Hello, while removing dirty santa on my v20 h990n I bricked it... hard. I am in no rush I have a V30 but I would still like this functioning as a spare. I was wondering what the test pins are that need to be shorted in order to force it into download mode. I have done extensive searching and have seen it mentioned in v20 posts but never details given.
For the curious I followed the instructions on the dirty santa post but I was accidentally in USB mode when I did the DD command that copied the abootbackup file I created when I first installed root.
It will not boot or even power on the screen. It will only give the power on vibrate when you press the power button after the battery/cable have been disconnected.
not seen by device manager, ADB, or LG programs.
The only thing it will display on the screen is a blinking battery ! when the battery is removed and usb connected.
My first brick in about 10 years of rooting phones, hopefully I can get it back. I am hoping the test pin will force it into a download mode so I can use LGUP or ADB to get it working again.
r4736 said:
Yeah, it's fun. I wasn't paying attention and used did to restore the aboot backup while in USB mode. So it does practically nothing. Detectable by nothing, nothing on the screen. The only signs of life are it doing the power on vibrate, and the creek will only come on to blink a ! Battery warning if plugged in with battery removed. Thank goodness it's just a spare, v30 visits my daily.
I'm half thinking about taking it to a LG repair center here in Hong Kong. If it's not expensive if like to have it working.
Click to expand...
Click to collapse
I'm quoting you from the other thread here as it's best not to muddle up runningnak3d thread.
When I first responded to your question I did not consider such a scenario. Normally the V20 goes automatically into 9008. I do now after reading your case, remember another person who had the exact same symptoms. He too had failed during dirtysanta root procedure. I'm not familiar with that procedure myself. I had a H918 and I didn't use the engineering aboot.
So it would seem you have a blank 'aboot' partition? In any case that is very unusual brick.
I would try the lg repair like you said, or 3rd party service with "box" (you know like, infinity, octoplus etc).
askermk2000 said:
I'm quoting you from the other thread here as it's best not to muddle up runningnak3d thread.
Click to expand...
Click to collapse
I appreciate that.
I had assumed I was sol, but still had to check. And I didn't fail rooting it, I was actually returning it to stock. It seemed pretty simple but after running dd and powering off to go into download mode that was all she wrote.
Method 1b: (TWRP, with file from another source)
This is simply a tweak of the above resulting from recalling there is a backup of aboot already on the phone itself.
Boot into TWRP (DOWN + Power with a brief release during LG logo).
Run `adb shell` and type (or copy&paste) the following commands:
Code:
dd if=/dev/block/bootdevice/by-name/abootback of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
Get into Download mode. Power off phone from TWRP. Press and hold UP, then power phone on (no need to hold power).
Load the appropriate KDZ file onto your phone via LGUP.
Thanks again for responding and thinking about my problem.
r4736 said:
dd if=/dev/block/bootdevice/by-name/abootback of=/dev/block/bootdevice/by-name/aboot
Click to expand...
Click to collapse
That command is wrong. It's supposed to be "abootbak", without the c. But I'm not sure if that had anything to do with it. Though it's strange that the instructions seem to re-lock the bootloader while still having twrp on recovery partition.
BTW, did you try to enter fastboot mode? I believe there is a key combination for that but I don't remember it now. Though if aboot is erased that shouldn't work since that's where fastboot is.
Edit: Combination is: Press and hold VOL down + insert usb cable.
askermk2000 said:
BTW, did you try to enter fastboot mode? I believe there is a key combination for that but I don't remember it now. Though if aboot is erased that shouldn't work since that's where fastboot is.
Click to expand...
Click to collapse
I can't go into any mode. Nothing comes up on the screen. I've tried all the key combos but nada. Just does the power on vibration. Nothing shows up when connected to the computer in adb, device manager, or lgup.
It's the damnedest thing, never screwed up a phone that bad before.
Also I think it's named abootback because that's the name of the backup of that partition created when doing the root process.
r4736 said:
It's the damnedest thing, never screwed up a phone that bad before.
Also I think it's named abootback because that's the name of the backup of that partition created when doing the root process.
Click to expand...
Click to collapse
No, its abootbak. The command is not pointing to a backup. It's pointing to a partition, and there is no partition called "abootback", only abootbak, xblbak, recoverybak, lafbak and so on. These are part of the stock partition layout. I'm positive the dirtysanta root procedure does not include creating an additional partition on the device. That certainly would be hilariously risky and unnecessary.
Anyway, sorry I couldn't be of more help to you.
askermk2000 said:
Anyway, sorry I couldn't be of more help to you.
Click to expand...
Click to collapse
It's no problem, thanks for pondering my peculiar predicament.
Have you tried volume down and plugging in usb.....
stinka318 said:
Have you tried volume down and plugging in usb.....
Click to expand...
Click to collapse
I had the same issue . Literally nothing I could do. Only time screen turns on is when battery is out and you plug in a USB cable. Had to send it to Lg