Lg G6 downgrade - LG G6 Questions and Answers

Hello to all. can anyone explain how to downgrade my lg g6 from android 8.0 to android 7.0. thank you all

Ala1101 said:
Hello to all. can anyone explain how to downgrade my lg g6 from android 8.0 to android 7.0. thank you all
Click to expand...
Click to collapse
Unlock BL and flash TWRP then Flash 7.0 based custom ROM
Sent from my SM-G950F using Tapatalk

Lg up e uppercat e flash 7.0 kdz.

menonmanjesh said:
Unlock BL and flash TWRP then Flash 7.0 based custom ROM
Click to expand...
Click to collapse
What are you talking about...
siggey said:
Lg up e uppercat e flash 7.0 kdz.
Click to expand...
Click to collapse
Correct, just flashing 7.0 in Uppercut. But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base.

romcio47 said:
What are you talking about...
Correct, just flashing 7.0 in Uppercut. But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base.
Click to expand...
Click to collapse
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?

amyelizabeth said:
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?
Click to expand...
Click to collapse
You may want to look into anti-rollback numbers, because if you have one at a certain value, downgrading may brick your phone. I don't remember from the top of my head. Please be cautious and do this at your own risk.
Look for "LGUP 1.14" and "LG Uppercut" on Google and download them. The first search results should be what you're looking for.
Install LGUP first. Once that's done, put your phone in download mode by powering down and then turning it on while holding volume down and the lock button (the fingerprint sensor). Next, connect it to your computer.
Open Uppercut (after extracting it) with administrator privileges. It will open LGUP. Have your KDZ ready somewhere easy to find, like your desktop.
You should have four options that you can tick off, one of which is "REFURBISH". Select it.
At the bottom, you will see a list. Select the first thing on the list and click on the three dots on the right. Select the KDZ. Finally, press start. DO NOT TOUCH YOUR PHONE WHILE IT IS DOWNGRADING! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS!
Once that's done, and ONLY when it says "finished" on LGUP's interface, your phone should boot at the set up screen.

Incidentally, I was after the exact same thing as the OP, and incidentally, my search led me to do exactly as "fegitoli" suggests: Downloaded Uppercut, downloaded the last 7.0 KDZ (H87011i_00_OPEN_EU_OP_0108.kdz), but then I tried to downgrade using the "Upgrade" option (sounds stupid when written I know). Process seemed to be complete, but since the phone started I get an error saying "Settings crashed, reopen" followed by "Settings keep stopping, close app". On the top left corner it says: "Secure start-up" and the phone is an airplane mode with no control over the notification bar or anything else minus power and volume buttons, so stuck there.
Don't tell me that in 8 years of modding various Android devices this will be my first brick?

fegitoli said:
You may want to look into anti-rollback numbers, because if you have one at a certain value, downgrading may brick your phone. I don't remember from the top of my head. Please be cautious and do this at your own risk.
Look for "LGUP 1.14" and "LG Uppercut" on Google and download them. The first search results should be what you're looking for.
Install LGUP first. Once that's done, put your phone in download mode by powering down and then turning it on while holding volume down and the lock button (the fingerprint sensor). Next, connect it to your computer.
Open Uppercut (after extracting it) with administrator privileges. It will open LGUP. Have your KDZ ready somewhere easy to find, like your desktop.
You should have four options that you can tick off, one of which is "REFURBISH". Select it.
At the bottom, you will see a list. Select the first thing on the list and click on the three dots on the right. Select the KDZ. Finally, press start. DO NOT TOUCH YOUR PHONE WHILE IT IS DOWNGRADING! I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS!
Once that's done, and ONLY when it says "finished" on LGUP's interface, your phone should boot at the set up screen.
Click to expand...
Click to collapse
Its work? I flahsed lg g6 h870ds indian nuogat to h870ds twn...
Now i think to downgrade to official firmware indian nougat
Sent from my LG-H870DS using XDA-Developers Legacy app

mclisme said:
Incidentally, I was after the exact same thing as the OP, and incidentally, my search led me to do exactly as "fegitoli" suggests: Downloaded Uppercut, downloaded the last 7.0 KDZ (H87011i_00_OPEN_EU_OP_0108.kdz), but then I tried to downgrade using the "Upgrade" option (sounds stupid when written I know). Process seemed to be complete, but since the phone started I get an error saying "Settings crashed, reopen" followed by "Settings keep stopping, close app". On the top left corner it says: "Secure start-up" and the phone is an airplane mode with no control over the notification bar or anything else minus power and volume buttons, so stuck there.
Don't tell me that in 8 years of modding various Android devices this will be my first brick?
Click to expand...
Click to collapse
Not much I can help you with there. I made the same mistake with my G4 which resulted in a brick similar to yours. Hence, why I specified you use the REFURBISH option.
I'm sure other people in the modding forum can help you out. If nothing works, I'd like to pay my respects for you and your wallet.

fegitoli said:
Not much I can help you with there. I made the same mistake with my G4 which resulted in a brick similar to yours. Hence, why I specified you use the REFURBISH option.
I'm sure other people in the modding forum can help you out. If nothing works, I'd like to pay my respects for you and your wallet.
Click to expand...
Click to collapse
Ha! It was close but still my "Brick counter" reads zero The answer lied a couple of posts above in @romcio47 's post: "But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base."
I entered in stock Recovery and did a Factory reset from there, then the phone became again accessible from LGUP so I re-flashed the 7.0 KDZ and this time it booted fine!

Can i downgrade LS993 from android 8 (ZVB) to Nougat?

From today i am a happy Nougat user again for my H870 EU model
I've followed the exact instructions from @fegitoli,and i fortunatelly had the perfect result.
Here i have to mention one detail that probably gave me the desired result..
As it is mentioned in the instructions,i selected the "Refurbish" option,but when i pressed the start button,i got an error notification in LG UP display,saying that my kdz file can not be used for refurbish,so i cancelled the whole process without disconnecting my phone from the pc,but i closed the LG UP and opened Uppercat again.
Probably the "refurbish" option is something like a hard(factory) reset mode for the existing ROM.
Then i choose the "Upgrade" option and started the process again until i got the notification "completed" in LG UP interface.
After the phone started rebooting,i disconnected it from pc,waiting to complete reboot.
When completed reboot,i got an error saying "settings are not complete" and "safe mode start",but giving me the option "reset phone"..
Then i pressed "reset phone" and a second reboot followed..after that,it opened the first set up screen and everything went fine.
BE CAREFUL WHAT YOU DO AT YOUR OWN RISK..
I AM NOT RESPONSIBLE FOR ANY DAMAGE ON YOUR PHONE!!
P.S: Many thanks @fegitoli for his valuable help with his post!
Sent from my LG G6 using XDA Labs

granazias said:
Many thanks @fegitoli for his valuable help with his post!
Click to expand...
Click to collapse
No problem! Glad my instructions helped, because if they didn't, I would have caused a lot of trouble. Hopefully everything is working fine for you!

fegitoli said:
No problem! Glad my instructions helped, because if they didn't, I would have caused a lot of trouble. Hopefully everything is working fine for you!
Click to expand...
Click to collapse
Be sure that if one on a million something was going wrong,i was not intented to blame you..
What is everybody doing with his phone,is on his own responsibility.
After a lot of reading here and in other forums,that a lot of people had problems with bricking their phones,i was prepared for the possibility to brick mine too,but i was decided to take the risk.
Oreo,and especially the last June update,had disappointed me with the battery times,so i didn't have other option than to try the downgrade,and i am really happy that everything went fine.
Maybe more people now can do the same and take the most from this wonderful G6.
Regards!
Sent from my LG G6 using XDA Labs

granazias said:
Be sure that if one on a million something was going wrong,i was not intented to blame you..
What is everybody doing with his phone,is on his own responsibility.
After a lot of reading here and in other forums,that a lot of people had problems with bricking their phones,i was prepared for the possibility to brick mine too,but i was decided to take the risk.
Oreo,and especially the last June update,had disappointed me with the battery times,so i didn't have other option than to try the downgrade,and i am really happy that everything went fine.
Maybe more people now can do the same and take the most from this wonderful G6.
Regards!
Click to expand...
Click to collapse
Very glad to hear that!
Here's a little disclaimer I'd like to add. This should go without saying: YOU are responsible for what YOU do to YOUR phone. If you bricked it because you missed a step, it's not the instructor's fault. If everything is okay but the screen shuts off randomly, it's not the instructor's fault. Please mod responsibly and be prepared for failure, because things don't always work as they should.

mclisme said:
Ha! It was close but still my "Brick counter" reads zero The answer lied a couple of posts above in @romcio47 's post: "But Factory Resetting might be needed, Oreo data might be incompatible with Nougat base."
I entered in stock Recovery and did a Factory reset from there, then the phone became again accessible from LGUP so I re-flashed the 7.0 KDZ and this time it booted fine!
Click to expand...
Click to collapse
Please can you tell me how to return Nougat from oreo. I have LG UP and I have official Nougat H870DSU10f_00_OPEN_HK_DS_OP_0803.kdz firmware downloaded. How to avoid brick and factory reset? Can I just refubrish from LG UP or I will have to do factory reset of the phone and "brick" at first?

Ferovac said:
Please can you tell me how to return Nougat from oreo. I have LG UP and I have official Nougat H870DSU10f_00_OPEN_HK_DS_OP_0803.kdz firmware downloaded. How to avoid brick and factory reset? Can I just refubrish from LG UP or I will have to do factory reset of the phone and "brick" at first?
Click to expand...
Click to collapse
I did as described above. I was with Oreo 8.0. I downloaded LG UP with Uppercut, downloaded: H87011i_00_OPEN_EU_OP_0108.kdz, (Nougat factory image) then using Uppercut I selected "Upgrade" and pointed it to the downloaded KDZ. The flashing starting normally without any warnings, completed but then on first boot the phone kept crashing (I guess because Oreo data is not compatible with Nougat base as romcio47 says).
At that point I thought I had a brick because the phone could not complete any action other than crash continuously. Then followed the instructions for booting into Bootloader: (volume down + Power for 10", keep both buttons pressed, when you see the LG logo immediately release and re-tap again the Power while volume is always pressed). There it only gives you one option: "Factory reset", selected YES, rebooted and then phone started normally into the Nougat setup.

You can "upgrade" to 7.0 in lgup but after flash you must manually boot to recovery and do a factory reset. I've done it a lot on my H870
Sent from my Nexus 6P

ARB1 Problem
fegitoli said:
Very glad to hear that!
Here's a little disclaimer I'd like to add. This should go without saying: YOU are responsible for what YOU do to YOUR phone. If you bricked it because you missed a step, it's not the instructor's fault. If everything is okay but the screen shuts off randomly, it's not the instructor's fault. Please mod responsibly and be prepared for failure, because things don't always work as they should.
Click to expand...
Click to collapse
Just got my G6 a week ago and there is considerable scroll lag so I'm trying to get back to stock using LGUP. I am getting "0x81000402 fail tot header antirollback". I am on ARB01 and cannot for the life of me get around this. I've tried LG Flash tool with no luck either.
Any insights??

amyelizabeth said:
What are the steps to downgrading? I just bought my g6 and loved it. then i upgraded to oreo 8.0 cause the notifications were annoying me. but i HATE it and now im sad any help?
Click to expand...
Click to collapse
Simplest way is
Take backup if you want
STEP1: download .KDZ file from https://lg-firmwares.com/lg-h870ds-firmwares/firmwares/
STEP2: LG up from here https://www.filedropper.com/g4
SETP3: In dev option open Enable OEM unlock and USB debugging
STEP4: turn off the device and long press vol up + and connect data cable to PC
SETP5: Open LG up S/W it will show your device then select location of KDZ file go
you are done :good:
By the way why you want to downgrade

Related

Rooted my H915 (Somewhat I guess)

So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
TheDantee said:
So was following the guide to root with the Step Bat Files provided by
HTML:
http://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
using the Dirty Santa Guide for Unlocking the Bootloader and Rooting the device. Yes I Already know the H915 is not listed but worth a shot anyway..... to me at least. So after finally going though each step bat file multiple times and it failing several times I finally have TWRP Loaded as the Recovery on the Device I can access the Bootloader however when I check the Bootloader it does say it is locked and fastboot oem-unlock gives me the error remote: unknown command. Note that fastboot oem device-id also gives me the same error. Therefore I can't unlock he Bootloader I can reset the phone through the stock method of holding down the power button and volume down button when booting the phone after resetting it each time It boots me into TWRP I can flash all the files I have tested such as BOOT Images and new system images.... I have been working on this since the guide was posted yesterday and been up since 2 (6 Hours now) trying to get this to work today.... I would like to just get into the phone to access ADB so I can possibly revert to stock or keep trying to root. I can flash anything and wipe anything to the device throughout what I have tested I'm an idiot and did not backup the Stock H915 Files once getting into TWRP..... yes I'm Dumb IK (But I also tried rooting my H915 for a Verizon/ATT Root so what do you expect). thanks again to anyone who can help!
Click to expand...
Click to collapse
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
Already picked up another just forgot to update this post thanks for the help though
Lonewolf17a said:
Try this
Power Off
Hold Vol Down
Hold Power
When The LG Splash Screen Appears Release Power for 1 Sec then Re-Press
Answer Yes 2 times
Yep. I was having the same problem with TWRP. The above was the only fix I found and it took me a solid hour to get the button combo just right. If you still have the red triangle like myself, the button combo happens before that pops up. To clarify, so you're not wasting your time like I did. You'll try the button combo listed in the quote as soon as the LG logo pops up. If it goes past that to the red triangle, you missed your shot. Pull the battery and try again.
Also. It should be noted once you get into that separate menu and answer yes twice to wipe the phone. It will throw you back into TWRP. Dont be discouraged! In TWRP go to reboot>system.
Hope this works for you bud!
Click to expand...
Click to collapse
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
Sorry, I should have clarified my friend. I have a VS995. Deleted everything without making a backup so now I am running US996 stock deodex rom with konverged kernel.
However if your stuck in a twrp loop, the instructions in the quote is what I'd try first as I seemingly exhausted everything else to no avail. And it turned out to be the easiest of the solutions and the only one that worked haha.
SHABBA JOTS said:
So is it safe to say you have an H915 successfully rooted? Are you using it with Freedom Mobile?
Click to expand...
Click to collapse
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
TheDantee said:
The H915 is flashable to the H918 System Image allowing you to access things like the Bootloader and TWRP I just F**ked mine up.... if your willing to try and get super su on there go for itim sure it is possible to get a root working for it.
Click to expand...
Click to collapse
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
SHABBA JOTS said:
my only issue is the cellular signal, in the dirtysanta thread, they mentioned that it worked for the h915, but that the dev was having signal issues. I'm not inclined in this sort of thing so I can't really try until someone on the same carrier can confirm.
I'm in no rush tho
Click to expand...
Click to collapse
Could you not just reflash a H915 modem from a backup?
TheDantee said:
Could you not just reflash a H915 modem from a backup?
Click to expand...
Click to collapse
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
AllGamer said:
this should theoretically work.
I know for Samsung phones that was possible.
I had a Note phone from Rogers, and flashed it with a Galaxy S modem for Wind / Tmobile and it worked to unlock the AWS signal, that was not supposed to be supported officially.
I'm hoping LG phones are similar in that way, in which files / modems / boot can be transplanted from one phone model to another.
I'm just not familiar enough yet with LG phones, first time switching away from Samsung after soooo many years.
Click to expand...
Click to collapse
LOL yeah i came from a Note 7 to a G5 to the V20 so idk much about LG Phones yet...
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
SHABBA JOTS said:
Is flashing the h915 modem confirmed to work? I havent seen any posts about anyone with this varient being successful, but maybe most are like me and too incompetent to take the first step lol
Sent from my LG-H915 using Tapatalk
Click to expand...
Click to collapse
I took many steps and got a Working TWRP Recovery and had a bootloader however when i went to flash in the ROM and then reset the phone it failed and I got stuck and had to get the model replaced... However I do know for sure that you can get TWRP and a bootloader working on the H915 using the DirtySanta Method from there is the hard part if your willing to take those steps lol.... MAKE BACKUPS! I have not tried to root my New V20 yet... If I get around to it I will be sure to let you know, some people have confirmed it has rooted but you do need the modem all high risk for the reward lol

[Dirty-Santa Root] Bricked Verizon LG V20 Please Help!!!

I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was the first boot I expected a decently long wait, after about 25 minutes I followed the guide's instructions for Verizon since it did say some Verizon users were experiencing long first boot times. I took the battery out like it said, put it back in, then proceeded to fastboot boot2.img, like the guide said. After letting it sit for an hour this time, I got the idea that something was obviously wrong. After multiple attempts with no success I tried to fix it myself. So far I have learned that on the fastboot screen it says my bootloader is locked again, even after unlocking it. I have tried flashing TWRP as a recovery, just to at least have a recovery boot, that does not work either unfortunately. So as of right now, all I have is a v20 that has no OS, a locked bootloader, no way of booting recovery, I can fastboot with no ADB, and its virtually a paperweight. If anyone has a solution to at least get back to Stock, I would greatly appreciate it! Thanks!
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Did you get it fixed?
frome901 said:
Did you get it fixed?
Click to expand...
Click to collapse
He has not responded to my pm
What roms can we use with dirty santa root?
me2151 said:
First off. It will say: Bootloader Unlocked: No
Thats normal. 2nd. you are not bricked. You have TWRP installed. You just need to redo some steps.
PM me. and I will help you.
Click to expand...
Click to collapse
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
TheDantee said:
Bricked 2 LG V20s this way any help would be appreciated lol what steps do I need to redo...
Click to expand...
Click to collapse
In his case we needed to redo from step 3.
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc) http://www.hardreset.info/devices/lg/lg-v20/
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Bricked T-Mobile v20
I have rooted many phones before without an issue, and during the root process for this phone, everything was going great, I flashed SuperSU zip in TWRP and rebooted, since it was flash a new rom on it then i get boot loop with TWRP. so i decide to OEM LOCK again after that everything was stuck on my phone just boot loop with LG so any solutions please help me...... THx u for help me.
Kinda nerve wrecking to read about all these "bricked" phones popping up after trying this method lol.. Perhaps I'll just wait until a more tried and true way comes out...
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
For anyone that isnt on sprint that has "bricked" their phone. There are kdz's that will allow you to reflash back to 'stock". Someone had an issue with the kdz, but it was an easy fix. If you failed the process, it can be restored. Just if it doesnt want to boot, just lock and unlock the bootloader...
If your phone doesnt have a kdz, I know TeamDev is working on a custom kdz for such phones. Don't bug him if it isn't finished as I type this.
Anyone that can't get into TWRP, or has failed the process. Either start back at step 3, or if you have TWRP installed but can't get to it, the manual way to get into TWRP is a pain.
Keep your back cover off and hold the volume down button for ease. Now press the power button and as soon as you see an LG logo, let go and repress the power button. Its tricky.... If you get the corrupted screen, pop your battery out and put it back in quick and repress volume down and power. Usually if Im quick enough the first LG logo will hang a lot longer than usual and that gives me time to enter TWRP. A factory reset screen will pop up. Hit Yes twice.
Please help urgent
lcovel said:
I managed to un-brick mines after returning sadly from the Sprint store.
First, get to the boot loader screen and try running thru the steps again, especially step 3. You need to make sure you have TWRP.
Use this link to make sure you can get into the different modes (Download mode, fastboot, etc)
Once you can get TWRP to show up,then you are good. In the mean time I downloaded "LS997-deODEXd-signed"
When I got into TWRP, I transferred the file to my phone. Rebooted from TWRP back into TWRP and flashed the ROM.
During my reboots, I do get a message saying my phone is corrupt, blah blahblah, but I just wait a few seconds and it will boot up.
Hope this helps.
I had managed to brick mines only 3 hours after upgrading from my Note 4. It took me from 9pm to almost 2am to get it back up again. I can live with the message about my phone being unbootable until someone comes up with a work thru.
Click to expand...
Click to collapse
Please can u help ke unbrick mine i bought this mobile in my country its expensive and has no support. I have tried all tools but still getting the error model unknown please help sir
Jaistah said:
Dirty Santa root is not for the average user who has a couple of experience in rooting.
You have to at least have background on Hard bricking phones to fully understand what you are getting yourself into
Click to expand...
Click to collapse
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
yuppicide said:
What does that mean? Not for the average user who has a couple of experiences in rooting.
I've only rooted 2 phones, this is my 3rd (maybe 4th). I am on Sprint. Instructions worked fine for me. I did have one hiccup, but it was my fault, and I was able to root just fine. I've been running for a few months now.
I have not flashed any custom ROM yet, I'm going to wait for the next major version of Android to come out. The only mods I've done so far are Titanium Backup install so I can remove Sprint crap.
Click to expand...
Click to collapse
it means dirty santa root got a high posibility rate of bricking a device compared to other root methods for other devices and if you have no experience in bricking phones before then you're screwed if it happens to you
Actually, if you follow the directions, almost none of the problems create a true brick-- which means unrecoverable. For most of the cases, you might get a soft brick, meaning you have to back out, use a KDZ to repair it or reflash something else, or start over from scratch and try again-- but usually (maybe with some help from here) you can pull the phone back into a usable state.
I would hazard to guess for the vast majority the process works fine, maybe with a hiccup, but I've not seen many reports of a truly unrecoverable brick from this method. It's complicated, yes, and you need to be ready to read a LOT to understand what's going on, but it seems pretty difficult to end up with a $700 paperweight with this.
So i have been trying tonroot my sprint lg v20 and everytime i try and go to the phone on mobile terminal to enter id
Then enter the apply patch /system/bin/atd /storage/emulated/0/dirtysanta i get this message and i cant go to step 2 to boot into recovery
Any help would be appreciated: i have a sprint v20 and i wanted to know if i have to flash the stock sprint rom or can i just flash lineage rom following this guide? I have it running on AT&T and i want to keep it on AT&T...
can you please assist
Could you help out, please? I don't believe I have hard bricked my LG V20 H910. However, I have read and tried all of the unbrick info out. It seems my screw up is unique. I completed dirty Santa then went to flash a custom. in the boot between that. I get a black screen and cant do anything even download mode will not come up. My PC does make its usual noises when i connect or disconnect, but my phone does nothing.
Ok, I managed to brick mine too. It's a VS995, it was running stock 1AC. I used the LGUP tool to downgrade it to VS99512A, and then did Dirty Sanata and TWRP. After booting into TWRP I decided to try lineage OS with Android 8.0, I did not make a backup of the Stock ROM, which was very stupid. Lineage OS 15.1 flashed but I had no cell service so I panicked and instead of wiping it in TWRP and using the backup of stock I should have created, I just opened LGUP and tried to downgrade it back to stock VSS99512A. Well LGUP said it worked, but when it went to boot it would hang at the Verizon logo with 4 pastel dots. Device manager could see an ADB device and I could connect to it with ADB. So I did and read the logcat. I could see it was trying to update as part of the rollback, but it appeared that some components from Android 8x could not be "upgraded" to Andoird 7.x. There was a repeated error about failing to update SQLite instance version from 3 to 1.
The one feature that could fix this is if the refurbish function worked with any of the VS995 KDZ files we all have access to. But alas, none work instead we only get the upgrade function... or so I thought. Somewhere in my search for the past 2 weeks I found a modified LGUP https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
**Please be warned what I did was absolutely ****ing stupid, and it was sheer luck I didn't screw anything up.**
From what I can tell if you only flash ("LGUP Upgrade") the KDZ from the same model it never clears the partition it just adds to it. My problem was there was stuff from lineage OS 15 stuck on one of the partitions that was making the rollback to stock fail because it kept saying it couldn't update the SQLLite DB from 3 to 1. So no "upgrade" within LGUP would work because the upgrade function does not clear internal storage. But the link above is to a version someone modded so you can force a partition update from any KDZ onto the system. So I started playing around with forcing KDZs from other models onto my VS995, and I noticed when using the Partion DL function with non-VS995 KDZ files it would say something about the partition changing. All I can assume is that the partition layout is so different on each model and it forces LGUP to re-partition the storage.
**Again I state for the record this was stupid, and I'm only fortunate it worked.**
I forced Partion DL of H91510d_00_VTR_CA_OP_1110.kdz, then H990N10b_00_OPEN_HK_DS_OP_1017.kdz, then back to VS99512A_06_1114_ARB00.kdz, then when it booted it gave the Verizon hello, and moved on finally but the setting service kept crashing while it was trying to load the Secure Boot screen. So I yanked the battery and went into the boot menu and did the Factory Reset function, and it worked.
Lesson learned, always make a backup and don't be so hasty to use tools that aren't fully functional (LGUP).
Perhaps what I've done may help others, maybe I've found out how to reimage or unbrick our V20s. Or maybe I just got really stupid lucky.

LG G6 H870DS stuck at bootscreen, kill switch on

So here is the lowdown, I just updated my LG G6 H870DS using uppercut+LG UP. The phone updated successfully.
So now, the phone got stuck at the LG boot screen. And I know that updating to a new version usually requires a factory reset for the phone to boot normally.
And this part, I did not anticipate, I booted to the factory reset mode for the device, only to find out about this 'kill switch' thing.
I've flashed other phones, though not recently. So I am stuck at the boot screen, with no way getting past it. As of now, I am downloading a Nougat firmware to downgrade it, but I am worried that downgrading back to Nougat will still yield at a stuck screen with no ways of a factory reset. Now, I've learned that I need to check whatever lock I might encounter before sideflashing firmwares.
I need all the help I can get mates, I had to use my S3 because my G6 is a paper weight currently.
UPDATE: So whenever I downgrade using LG UP, it would downgrade successfully, then the kill switch prompt would appear, but the factory reset would go through, so I end up okay on a Nougat downgrade. Now, upgrading to Oreo, the firmware would flash successfully, but it would not initiate a factory reset, it would just be stuck on the kill switch screen.
I didn't know the H870DS worked with uppercut+LG UP!
When you say 'updating' do you mean official updates that you can do with LG Bridge or what?
Just curious and hoping someone knows the answer to your question.
I had the same issue after rooting for some reason from 20a on the h872
I could hold vol - , and the power button. It would force a reboot that would eventually get it to boot sometimes. (Needed that in there) I ended up having to flash another, non stock ROM to get it to start acting right.
Don't know how much that'll help you but thought I'd throw it out there just in case.
Sent from my LG-H872 using Tapatalk
bick said:
I didn't know the H870DS worked with uppercut+LG UP!
When you say 'updating' do you mean official updates that you can do with LG Bridge or what?
Just curious and hoping someone knows the answer to your question.
Click to expand...
Click to collapse
Ken C said:
I had the same issue after rooting for some reason from 20a on the h872
I could hold vol - , and the power button. It would force a reboot that would eventually get it to boot sometimes. (Needed that in there) I ended up having to flash another, non stock ROM to get it to start acting right.
Don't know how much that'll help you but thought I'd throw it out there just in case.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I never tried LG Bridge, the download for the firmware there would take a lot of time on my connection. So I just download official/stock firmware from LG's website. If nothing else works, LG Bridge would be my last option.
I know it just needs a factory reset after the update, but I don't know how to disable that kill switch. Already tried the OEM unlock on the options, and also removing my Google account; both of which are futile. So I'm using Nougat as of now. Too bad the H870DS don't have root/UBL.
jephimax said:
I know it just needs a factory reset after the update, but I don't know how to disable that kill switch. Already tried the OEM unlock on the options, and also removing my Google account; both of which are futile. So I'm using Nougat as of now. Too bad the H870DS don't have root/UBL.
Click to expand...
Click to collapse
Ya that kill switch thing I've never seen. I thought y'all with h870ds had already achieved root?
Sent from my LG-H872 using Tapatalk
Ken C said:
Ya that kill switch thing I've never seen. I thought y'all with h870ds had already achieved root?
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
I think the H870 has root, not the H870DS. So I guess I'll be trying LG Bridge when I get my type-C cable replaced. Will report back if successful.
jephimax said:
I think the H870 has root, not the H870DS. So I guess I'll be trying LG Bridge when I get my type-C cable replaced. Will report back if successful.
Click to expand...
Click to collapse
I've noticed myself that the stock cord seems to matter. My wife has the stylo4 and the cord is thinner and I was getting connection issues for data transfer through it.
Can you get the phone into dl mode? (I'm going off my H872 experience) that's how I was able to flash completely back to stock. May be worth looking into those threads. Reinstalls everything, you'll lose root of you have it and twrp also. Overwrites everything. Research first though because I haven't paid attention to your model.
There's one specifically on using laf in lgup, but I think it may talk about more than just that. Don't know how it would apply to you work your version but it couldn't hurt.
Just passing thoughts along.
I borked the heck out of a phone the other day and after finding bits here and there and taking all day I was able to bring it back from the dead after wiping system. Boot.Img, and the bootloader. Dummy, What a nightmare that was to get back
Ken C said:
I've noticed myself that the stock cord seems to matter. My wife has the stylo4 and the cord is thinner and I was getting connection issues for data transfer through it.
Can you get the phone into dl mode? (I'm going off my H872 experience) that's how I was able to flash completely back to stock. May be worth looking into those threads. Reinstalls everything, you'll lose root of you have it and twrp also. Overwrites everything. Research first though because I haven't paid attention to your model.
There's one specifically on using laf in lgup, but I think it may talk about more than just that. Don't know how it would apply to you work your version but it couldn't hurt.
Just passing thoughts along.
I borked the heck out of a phone the other day and after finding bits here and there and taking all day I was able to bring it back from the dead after wiping system. Boot.Img, and the bootloader. Dummy, What a nightmare that was to get back
Click to expand...
Click to collapse
Cord was just replaced, I had no problems using my girlfriends cable. So I already tried LG Bridge, and it seems to be not working because it cannot find a software version for my device (H870DS). I was thinking also of putting it in download mode then trying to restore it using LG Bridge if it would download and flash the Oreo rom or not.
LG Bridge would not work, so I am stuck on Nougat for now. Tried changing regional firmwares, hoping for OTA to work, but still it prompts me that the latest version is installed. So any help would be appreciated.

US996 stuck in recovery bootloop. None of the tricks found on internet worked. Help?

So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Also I made a Reddit post about this before, if it helps: https://www.reddit.com/r/lgv20/comments/ac6apr/got_stuck_in_an_endless_twrp_bootloop_tried/
phamanhvu01 said:
So yeah, that's the title. Stupidly tried to force my US996 to take the Oreo update by flashing the stock recovery (while using a rooted system) and installing the OTA afterward (which results in an error). At this point I started screwing things up by flashing TWRP (using fastboot) immediately after that (without booting to the system again) and ended up in a loop as a result.
Screwed mine up even further later on by using a misc partition-wiping command (from here: https://forum.xda-developers.com/lg-g5/help/stuck-twrp-recovery-t3587077/post71796008#post71796008) and ended up locking the bootloader + making TWRP unusable. Now, only fastboot and download mode works, and I'm seriously out of idea at this point.
I guess there's not much that can be done, but any help would be appreciated.
Click to expand...
Click to collapse
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
clsA said:
Start over with lgup and the oreo.kdz
Theirs forum post on both of these here, search or look around
If you can get into download mode your phone is not bricked
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
phamanhvu01 said:
I've already tried that when I locked my bootloader accidentally, and just tried it once again - doesn't work. The phone still boots into the recovery, with the "no command" error like before. I suppose that the phone is still trying to initialize the OTA update process at this point.
If it helps, flashing using DL Partition didn't work either. Still more or less the same.
Click to expand...
Click to collapse
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
txenglan said:
I'm in exactly the same boat. Let me know if you figure anything out and I'll do the same. Really frustrating problem.
Click to expand...
Click to collapse
I have a potential solution for you. I'll PM you.
Have you guys tried to wipe data from recovery
Did this solution work? Can you share it?
txenglan said:
I have a potential solution for you. I'll PM you.
Click to expand...
Click to collapse
merrickville said:
Did this solution work? Can you share it?
Click to expand...
Click to collapse
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
txenglan said:
Yes, what I did was religiously follow what was posted at:
https://www.reddit.com/r/lgv20/comments/8b0c44/quite_hard_bricked_what_can_i_do_now/
Try that and let me know what happens.
Click to expand...
Click to collapse
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
merrickville said:
Already tried that. My issue is 'no command', I can boot into Download Mode, and I can flash H915, US996, they all flash if I choose the Partition DL.
No matter what I try, LGUP reports my phone as US996, even after successfully flashing H915.
I'm stuck at 'no command' (without a recovery cuz I tried to get to it) and US996 apparently.
Click to expand...
Click to collapse
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
txenglan said:
Strange. For me, the only thing that solved the issue was to purposely flash the wrong KDZ. I don't recall which one it was exactly but that's definitely what the solution was. Flashing the right ones lead to what you are describing.
Click to expand...
Click to collapse
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
merrickville said:
My Hardware the U.S. AT&T H910, so both the H915 & US996 are both the wrong KDZ's
Okay, I'm not relegating this to a paper weight just yet.
Click to expand...
Click to collapse
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Edit: Here is the what I tried, not Reddit, but here. But, no LGUP_US996.dll. LGUP_common.dll, no, that does not work either.
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
txenglan said:
Definitely don't throw it away just yet. I'm certain it can be salvaged. I even had to save mine using the test points and qfil at one point and I've been so close to throwing it away on so many occasions. It's basically impossible to brick these phones
I just went back and re-read that Reddit post by that guy. It's all coming back to me. I have the US996. His post was more inspiration if anything. I think what I did is download every single firmware I could find on lg-firmwares.com (both before and after the Oreo update) and went through them until I hit the "right" wrong one lol. It took me hours but I eventually got one that magically got the phone or of the bootloop so that I could tell move on to flashing something else.
Click to expand...
Click to collapse
merrickville said:
I can't find it now, but I followed a post Reddit post like that, and I had to use a LGUP_Hxxxx.dll file, his instructions were for two others (which provided the DLL's for), so I stopped there, because of the missing DLL file that I can't find with a search>
My phone is stuck at US996 (even when I sucessfuly flash H915 back to it, LGUP still shows it as US99610f).
Do you think I can find a LGUP_US996.dll file anywhere? No. And this post looked promising for getting me out of the 'no command' fix I'm in.
Click to expand...
Click to collapse
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
Make sure you install it in C:\Program Files (x86)\LG Electronics\LGUP or it will either read the wrong model file (if you had a previous installation of LG UP), or it will not be able to find the model file at all.
Click to expand...
Click to collapse
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Damn....getting the right dll was also part of what I did IIRC. It's too bad it was such a long time ago else I'd have a more clear recollection of the exact steps I took. All I can say for sure, is that if you don't give up, you'll eventually stumble on the right solution.
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
clsA said:
A couple of things come to mind
First off their only one patched LGUP for the v20
it works for all versions but maybe the H918 or Sprint LS997 model.
After using the H915_10e.kdz you have to flash the Full H910 rom on the phone
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
your choices are the rooted 10r rom or the unrooted 10q Stock rom
I also posted a back to stock Oreo 20G rom here > https://www.androidfilehost.com/?fid=1322778262903991071
Be sure and use TWRP for Oreo to flash it
After flashing those be sure and Format Data / Clear Cache and reboot
Click to expand...
Click to collapse
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I have never seen the screen or error you described. Having a total of 4 v20 I thought I had seen everything.. guess not
Sent from my ONEPLUS A6010 using Tapatalk
merrickville said:
Thank you for the suggestions.
This is the sequence I just did again as per your suggestion.
Install Patched LGUP (Phone recognized as US996 cuz I flashed that a while ago)
Flashed: H91510e_00_VTR_CA_OP_1205.kdz
Phone reboots to 'no command', injured reclining robot 'quick flashing'
At this point, both adb and fastboot do not see any devices.
End of story. I'm unable to sideload or flash the *.zip files, factory reset, wipe cache, all these options are not available to me due to 'no command' and no access to recovery, adb nor fastboot.
No matter which KDZ I flash, I only get 'no command', and I can always go into download mode.
Thanks again for the tips. I'm sure something will happen.
Click to expand...
Click to collapse
I wonder if this might work for you:
https://forum.xda-developers.com/v20/how-to/9008-test-t3855777/page13
It's an annoying process to have to go through but I revived mine when it was completely bricked (I couldn't even get as far as you because the phone wouldn't even turn on).
couple of thing that may help
No command screen is stock recovery being confused.
Try doing a factory reset using the volume - and power method (hold volume -, press power until the screen turns on, then tap power repeatedly until the menu appears)

[RE-OPENED] Possibly Bricked My Phone. AGAIN.

Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Car Transport in mumbai
Car Transport In Mumbai[/URL]
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:
..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
You'd probably be better off seeking support in the mod thread.
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.
..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..
F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:
Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.

Categories

Resources