Database Users

Was on CloudyG2 2.2 and Used Autorec and bricked phone. Even download mode is broken

I know there are tons of threads on this, but I think my phone is fixable and I want to make sure I use the right method so I dont permantely brick it. Here is what happened.
1) I was on CloudyG2 2.2 which I believe is a Kitkat rom.
2) Used Autorec and rebooted.
3) Standard boot gets me a Fastboot Started screen.
4) Holding down and powering on gets me to the Factory Reset screen. If I use power button twice to proceed, it goes to a Fastboot screen.
5) Holding volume up and plugging in my phone, it hsows Download Mode for a second then shows a fastboot screen. I do get Windows 10 to ding when I plug it in during this time and the screen changes to fastboot: processing commands.
So, it seems I fubared both download and recovery. I believe I need to get download mode fixed first before I can fix recovery and reinstall a rom. Is that a correct assumption? If so, can someone point me to the correct guide for this specific situation? I see a lot of threads, but I am not sure which pertains to me and I dont want to do anything I can fix.
Thanks, I really do appreciate it!

lg g2 stuck on fastboot mode
shaxs said:
I know there are tons of threads on this, but I think my phone is fixable and I want to make sure I use the right method so I dont permantely brick it. Here is what happened.
1) I was on CloudyG2 2.2 which I believe is a Kitkat rom.
2) Used Autorec and rebooted.
3) Standard boot gets me a Fastboot Started screen.
4) Holding down and powering on gets me to the Factory Reset screen. If I use power button twice to proceed, it goes to a Fastboot screen.
5) Holding volume up and plugging in my phone, it hsows Download Mode for a second then shows a fastboot screen. I do get Windows 10 to ding when I plug it in during this time and the screen changes to fastboot: processing commands.
So, it seems I fubared both download and recovery. I believe I need to get download mode fixed first before I can fix recovery and reinstall a rom. Is that a correct assumption? If so, can someone point me to the correct guide for this specific situation? I see a lot of threads, but I am not sure which pertains to me and I dont want to do anything I can fix.
Thanks, I really do appreciate it!
Click to expand...
Click to collapse
bro just use srk tool 2.1 ,ur problm will be solved 100%.....good luck.

kalpesh patil said:
bro just use srk tool 2.1 ,ur problm will be solved 100%.....good luck.
Click to expand...
Click to collapse
Thanks! I will give it a try!

LG V20 Device is Corrupt and BootLoop

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.

Test Pin Location

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

HELP! Stuck in Boot Logo w/ no Recovery Mode

Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!

theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?

try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool

Thanks guys, got it working using MSM Tool!

regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!

frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.

No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!

Question adb & fastboot not detecting phone. Bootloop w/ "--any key to continue"

Context
I was attempting to root my nothing phone (1). I initially got stuck into a boot loop after Flashing the patched boot image & rebooting the phone. I was following the tutorial here. I then followed this guide to attempt to get my phone out of the bootloop. I was able to access the adb & fastboot commands but the phone would keep restarting. I then started "STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands" and failed to flash the odm partition. I stupidly ignored the very important warning to not exit the process halfway. I fastboot rebooted and then was greeted with a screen with: the nothing logo in the middle unmoving, the "powered by android" phrase, and nestled into the top left corner in very small font, "--any key to continue". The front of the text was cut off from the rounded corner of the screen.
Now:
When I press any of the buttons on the phone, the phone will go black and then immediately do a short vibration and turn right back on to that screen. If I hold the power and volume down buttons, the same thing happens even after holding it for almost 5 minutes. I can shut off the screen by holding just the power button for a few seconds but the phone will only turn on with the original error I had. When accessing the console on both my windows 10 PC and Linux laptop, the adb and fastboot commands are no longer able to detect a device. Neither of my computers can detect that the phone is even plugged in.
What I've tried:
I tried using a USB 3.0 fix: but failed
Running the commands on Linux: failed
nothing phone(1) fastboot flash by @sh4tteredd: failed
a slew of others that I've forgotten by now.
A common theme between the failures of all of my fixes is that the phone will not be detected by my computers. This was not a problem before I bricked the phone.
What are some solutions that might help me here?

Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.

coomac said:
Don't blame yourself. The phone hard bricks if you look at it wrong. This forum has several posts about the issue. Only solution is to send it to a support center.
Click to expand...
Click to collapse
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl

Gamer_Mida said:
no, this isnt hard brick. hard brick= no recovery, no fastboot, only edl
Click to expand...
Click to collapse
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.

coomac said:
Did you read the post? There is no recovery or fastboot in this state. There are several posts and videos of this on this forum. I even posted one myself.
Click to expand...
Click to collapse
if it appears on the screen in fastboot press any button to turn off, it means that the bootloader is accessible, even if attached to the pc it does this thing, it is always accessible, therefore, it is not in hard brick

anyway it happened to me too, I know you also tried the usb 3.0 port, but this thing happened to me on another phone, I just changed the port and it worked (on the same pc)

It doesn't appear on the screen in fastboot. It's not the same as what you got on your Xiaomi phone even though the text is the same. Here you go. I don't mean to be rude but a quick search would have saved us this discussion.