Database Users

[RESOLVED] HELP please!! Unable to unlock device locked by Google Device Manager

Please help me, Ive just locked my phone with the official Google Device Manager. I'm trying to put the right password (Im sure, I changed the password for "1111" and phone recognized it was the PIN) but it gives me "wrong password" anyway.
I have stock Android unrooted, no debug enabled.
ADB commands give me just "error: closed"
"
adb shell
su
rm /data/system/cm_gesture.key
reboot
"
how to unlock the device, I really do not want to wipe the device!!
please help me
will CWM recovery help me ASAP?
please
thank you!!

I cannot believe no one knows what to do here
will this help:
install CWM recovery and what's next?

so the BUG is "made by Samsung". Samsung just do not accept any correct PIN or password (maybe because of "wrong" keyboard).
could anyone tell me how to remove the lock without wipe?
thx
edit:
solution 1) just if you have debugging mode on then follow this solution
http://maxoberberger.net/blog/2013/08/unlock-android-device-using-adb/
solution 2) just if you can change your keyboard for another (if you are allowed when entering password)
solution 3) just if you have Samsung account, log into Samsung Dive >> "unlock" (my case)
solution 4) no debuging mode + no keyboard solution + no samsung account? >> just and only wipe through recovery or Google Device Manager
Happy now, but I was lucky
SAMSUNG BUG in 100 %

maysider said:
solution 2) just if you can change your keyboard for another (if you are allowed when entering password)
Click to expand...
Click to collapse
Is this a confirmed solution or a theoretical solution based on your feelings?
hence:
maysider said:
(maybe because of "wrong" keyboard)
Click to expand...
Click to collapse
I'm stuck in this boat right now and I've been hammering at workarounds for the last week. But it seems every workaround is made exponentially harder because I do not have a rooted phone / I do not have USB Debugging already on / I do not want to just delete/reformat / I do not have a Samsung account activated. If this external keyboard solution is a confirmed solution - then I might just go buy one of these Samsung dongles to connect a keyboard to give it a shot ...
Thanks

Solution 2 did not work for me.
I was able to plug in a physical keyboard and type in my Android Device Manager password that I gave it on the web interface and it did not work. I even ran through the process using the same exact keyboard on both the web interface, then disconnecting it from my computer, connecting it to my phone, and typing. Still no good.
I am unfortunately at the point of Solution 4.

Maybe i can help you

Kazama2100 said:
Maybe i can help you
Click to expand...
Click to collapse
doubt that they are still waiting for help 14 months later

Same problem (PIN). This is so infuriating! What were the #%$#% programmers thinking?
Lock my phone is not equal to factory reset!!!

Google should be sued. There's gotta be enough ppl negatively impacted to do a class action suit. Force google to address the issue!

@jr342: What issue? The issue in this thread was apparently a Samsung snafu, back in 2014! If however you're referring to Google's Factory Reset Protection, Google will never address the issue as Factory Reset Protection is working as intended. Any lawsuit brought on the topic is likely to fail, as Google has no obligation to - and I believe can't - unlock a device where FRP has been activated.

maysider said:
please help me
will CWM recovery help me ASAP?
please
thank you!!
Click to expand...
Click to collapse
Even This Thread Is Already Old... This May Help.
To Remove Lockscreen Using TWRP/ Philz
BOOT INTO RECOVERY.
If File Manager Is Applicable To Your Corresponding Recovery You Can Continue.
GO TO FILE MANAGER.
- Go to This Directory.
root>data> system
LOOK FOR THIS FILES.
*Locksettings.db
*Locksettings.db-shm
*Locksettings.db-wal
DELETE IT.
REBOOT.
ADB instructions- coming soon.

Had this exact same thing happen on our son's Moto X Pure. Works a charm! Thank you!

WELL I may have found a new exploit to bypass the FRP screen on accident

Well, I'm pretty new to this stuff but yesterday I had a friend bring me an HTC desire that she bought on CL from someone. At the time of purchase she said it worked and then not even an hour later it was locked and they wouldn't answer her calls. Well I told her I would took a stab at it, so within a short period of time I found the OTG method. Well...like I said I'm new to all of this stuff and I don't have any OTG accessories at all so I went online to see who I could buy one from retail. staples website SAID they had one in stock but they closed at 6:00pm. it was 5:10. I hopped in the car and made it with 20 mins to spare...except they didn't have it. I checked best buy, walmart, target, hell I even went to car toys. No one had one, last store I checked online was Radio shack. I hadn't even thought of them until I seen them pop up in an ad on google, They had them in stock but...FML they closed at 6 also. Well I was kinda bummed I wasn't going to get to try this out until this morning so I kept at it. I googled every damn thing I could thing of to find different results. Eventually I stumbled upon the software for XTC 2 Clip, XTC 2 Tool. I didn't honestly know exactly what it was at first because I'm new to all of this and didn't know those box deals even existed but after a few mins I did figure out what it was actually for. On the main app screen I hit "Read phone info", it pulled up the info on the phone. Then I noticed there was a tab on the side for terminal and I was like ahh that's pretty cool. Well I had the screen lit up and decided to hit the TEST MENU button. It pulled up a menu almost like settings. From there I figured out if I hit battery and then hit the back button within the menu it would take me to settings. From there I tried to do a soft reset but it grayed out the button at first. So I decided I would enable ADB since I hadn't had it before now and then I also enabled bootloader unlock. I played around in there for a bit and it eventually let me hit the reset button.
If anyone cares to try this out and see if it works for them as well that would totally be awesome and if this method was already found please let me know as well. If it was a known method I honestly didn't know at all, I was prepared to drive to radio shack at 10am PST to get a cord and connect my flash drive haha.

Do you have links for the software? I'm not unable to unlock my boot loader. Maybe this will work.
Sent from my HTCD200LVW using XDA Free mobile app

Could you possibly give more detailed instructons?

20twins10 said:
Do you have links for the software? I'm not unable to unlock my boot loader. Maybe this will work.
Sent from my HTCD200LVW using XDA Free mobile app
Click to expand...
Click to collapse
unlock boot-loader u can do via https://www.htcdev.com/
the x2 clip tool is hardware based tool that can bypass s-on on the htc hardware, so if u buy the hardware u can use or pay someone who has this x2clip to do bypass for you.

htcdev method doesnt work on the Verizon version.
Sent from my HTCD200LVW using XDA Free mobile app

We can not unlock the bootloader without disabling frp because we can not get the correct token needed to generate the unlock code. Hopefully the original poster will give a more detailed explanation.

hey sorry, I hadn't been looking at this very often. What I was referring to was bypassing an FRP lock on a phone that you did not have the info to. I have a friend who bought a desire 626s off of CL and when she reset it she ended up locked out and didn't have the guy who she bought it from's number anymore. I used just the software for XTC2 tool and a usb cord to my PC. using the XTC 2 tool program I was able to bring up the test menu while at the FRP activation screen when normally nothing should be accessible, after clicking battery under the test menu and then hitting the back button it would glitch out and I would end up in settings. The options to reset the phone from inside settings were initially grey'd out and not accessible. Trying to devise another way to reset this phone I turned ADB on and enabled bootloader unlock so that I had a backup plan just in case I couldn't figure out a way to get the phone to reset from the glitched out settings menu. I don't remember exactly how I ended up getting the reset button to become clickable, I don't actually own this phone I was just trying to fix it for a friend otherwise I'd try and duplicate it again. I suppose I could see if it works on my M8? So to clarify, mentioning adb and bootloader oem unlock was more of a backup plan to try and bypass FRP activation just in case I couldn't get the glitched out settings menu to allow me to reset the phone. (for those that are not familiar with the OTG FRP bypass method essentially you stick an otg thumbdrive in your phone and the file explorer will pop up, there is a file you run and it will allow you to access your phones settings and from there you reset the phone. It was explained to me that resetting the phone with no account synced to it will remove the FRP once the reset is complete which is why I was looking to reset the phone once I got into the settings menu) Hope this helps explain what was going on in this post and hopefully it will help at least one person. *to clarify just a little further, I only used XTC2 tool to bring up the test menu. I wasn't really sure what I was looking for when I downloaded that program, it honestly was more of a fluke thing that I even discovered it. I'm sure any computer program that can bring up the test menu over usb will work to do this exact same thing until they patch the bug hitting the back button from the battery menu.

E36Nick90 said:
hey sorry, I hadn't been looking at this very often. What I was referring to was bypassing an FRP lock on a phone that you did not have the info to. I have a friend who bought a desire 626s off of CL and when she reset it she ended up locked out and didn't have the guy who she bought it from's number anymore. I used just the software for XTC2 tool and a usb cord to my PC. using the XTC 2 tool program I was able to bring up the test menu while at the FRP activation screen when normally nothing should be accessible, after clicking battery under the test menu and then hitting the back button it would glitch out and I would end up in settings. The options to reset the phone from inside settings were initially grey'd out and not accessible. Trying to devise another way to reset this phone I turned ADB on and enabled bootloader unlock so that I had a backup plan just in case I couldn't figure out a way to get the phone to reset from the glitched out settings menu. I don't remember exactly how I ended up getting the reset button to become clickable, I don't actually own this phone I was just trying to fix it for a friend otherwise I'd try and duplicate it again. I suppose I could see if it works on my M8? So to clarify, mentioning adb and bootloader oem unlock was more of a backup plan to try and bypass FRP activation just in case I couldn't get the glitched out settings menu to allow me to reset the phone. (for those that are not familiar with the OTG FRP bypass method essentially you stick an otg thumbdrive in your phone and the file explorer will pop up, there is a file you run and it will allow you to access your phones settings and from there you reset the phone. It was explained to me that resetting the phone with no account synced to it will remove the FRP once the reset is complete which is why I was looking to reset the phone once I got into the settings menu) Hope this helps explain what was going on in this post and hopefully it will help at least one person. *to clarify just a little further, I only used XTC2 tool to bring up the test menu. I wasn't really sure what I was looking for when I downloaded that program, it honestly was more of a fluke thing that I even discovered it. I'm sure any computer program that can bring up the test menu over usb will work to do this exact same thing until they patch the bug hitting the back button from the battery menu.
Click to expand...
Click to collapse
anyone that has access to xct2clip can bypass s-off security system and is able to turn s-off on any htc phone so anyone that got such tool could make a copy of system.img and make availible to others as this as far as i know is the file i need to continue to cook a new custom room to get full root control to our phone if anyone has such tool please could they make a copy of their system files for htc 626 a32_ul qcom 410 64 bit system to be precise as i possible can not the htc626s a32e_ul qcomm 210 type phone, i think with system files for htc 626 qcomm410 type i can build a custom rom for this phone. but is a catch 22 cant copy files without root, or without this xct2clip that is able to bypass s-on .
---------- Post added at 10:46 PM ---------- Previous post was at 10:24 PM ----------
and this exploit isnt no accident it is a method junnipter took advantage of in past by shorting a contact between sdcard and circuit board to gain access to bypass s-on, which i think is no longer available without device such as xct2 clip. that has taken advantage of this bypass, probability the contact that was used to bypass s-on has now got plastic undercover over it . would be my guess.

E36Nick90 said:
Well, I'm pretty new to this stuff but yesterday I had a friend bring me an HTC desire that she bought on CL from someone. At the time of purchase she said it worked and then not even an hour later it was locked and they wouldn't answer her calls. Well I told her I would took a stab at it, so within a short period of time I found the OTG method. Well...like I said I'm new to all of this stuff and I don't have any OTG accessories at all so I went online to see who I could buy one from retail. staples website SAID they had one in stock but they closed at 6:00pm. it was 5:10. I hopped in the car and made it with 20 mins to spare...except they didn't have it. I checked best buy, walmart, target, hell I even went to car toys. No one had one, last store I checked online was Radio shack. I hadn't even thought of them until I seen them pop up in an ad on google, They had them in stock but...FML they closed at 6 also. Well I was kinda bummed I wasn't going to get to try this out until this morning so I kept at it. I googled every damn thing I could thing of to find different results. Eventually I stumbled upon the software for XTC 2 Clip, XTC 2 Tool. I didn't honestly know exactly what it was at first because I'm new to all of this and didn't know those box deals even existed but after a few mins I did figure out what it was actually for. On the main app screen I hit "Read phone info", it pulled up the info on the phone. Then I noticed there was a tab on the side for terminal and I was like ahh that's pretty cool. Well I had the screen lit up and decided to hit the TEST MENU button. It pulled up a menu almost like settings. From there I figured out if I hit battery and then hit the back button within the menu it would take me to settings. From there I tried to do a soft reset but it grayed out the button at first. So I decided I would enable ADB since I hadn't had it before now and then I also enabled bootloader unlock. I played around in there for a bit and it eventually let me hit the reset button.
If anyone cares to try this out and see if it works for them as well that would totally be awesome and if this method was already found please let me know as well. If it was a known method I honestly didn't know at all, I was prepared to drive to radio shack at 10am PST to get a cord and connect my flash drive haha.
Click to expand...
Click to collapse
Just wanted to let you know that I tried this as well and "SUCCESS" so thank you for the help and Happy Holidays!:good:

I just used this on an HTC OPM9200 (Desire 626) and it worked like a charm. I was having a Helluva time until I stumbled across this thread. Thank you!

Same problem, no dice
I'm working on a Desire 626s with the same problem and have installed the XTC2 program as suggested by the op, but clicking "Test menu" under the terminal tab doesn't seem to have any effect, so I'm guessing this is just another dead end. I heard that this device's original stock ROM was a Kitkat one, and since Kitkat doesn't have any of this nonsense, would flashing the original stock ROM effectively sidestep the problem?
Any ideas?

I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.

getting to the bottom of this
723i said:
I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.
Click to expand...
Click to collapse
What did you have in mind? Would downgrading to a KitKat Rom work or can Roms not be flashed when the phone is in that state?

723i said:
I figured out a way to get past frp but I'm still deciding weather I should share how to or not... I don't want the exploit to be used wrongly.
Click to expand...
Click to collapse
if you are able to gain root access to your phone you should share, root access i think is fundamental right one should have to make use of the hardware we have paid for , instead of the limited use of the availible hardware set by htc, if u are not able to gain access to rooting your phone then you have found nothing and just leading ppl down a path that doesn't do anything to gain root access, as for your part saying ... I don't want the exploit to be used wrongly. wtf almost every android phone and iphone has root access too root do you think the other 99% phones that have root access availible are being used wrongly.
rofl you either found root method or you found nothing.

It just uses adb I never needed root access.

Can eny one creat a cm rom 4 htc d626p

Just wanted to say a big thanks! As a metro employee I had a customer bring me in an FRP locked Desire 626s. I tried USB-OTG to no avail.. After a few days of scratching my head and trying to figure out how you got the XTC2Clip software to recognize your device (when on the home setup screen) I had about given up.
Thats when I found out opening the RUU executable (flashes the stock metro rom) automatically puts the phone into debug mode before flashing it.
BINGO! After opening the RUU to flash the phone I kept it open in the background, clicked read phone information on the software, a usb debugging window popped up on the phone and from there it was gravy!
On a side note: The option to reset the phone is grayed out when entering the settings menu. You need to click Okay as quickly as possible upon entering the factory reset screen (before it grays itself out), a prompt to factory reset will very quickly pop up and disappear, so also be quick to click confirm on this prompt as well. (I'm talking trigger finger fast, it took me like 25 tries.)

no go
revulv said:
Just wanted to say a big thanks! As a metro employee I had a customer bring me in an FRP locked Desire 626s. I tried USB-OTG to no avail.. After a few days of scratching my head and trying to figure out how you got the XTC2Clip software to recognize your device (when on the home setup screen) I had about given up.
Thats when I found out opening the RUU executable (flashes the stock metro rom) automatically puts the phone into debug mode before flashing it.
BINGO! After opening the RUU to flash the phone I kept it open in the background, clicked read phone information on the software, a usb debugging window popped up on the phone and from there it was gravy!
On a side note: The option to reset the phone is grayed out when entering the settings menu. You need to click Okay as quickly as possible upon entering the factory reset screen (before it grays itself out), a prompt to factory reset will very quickly pop up and disappear, so also be quick to click confirm on this prompt as well. (I'm talking trigger finger fast, it took me like 25 tries.)
Click to expand...
Click to collapse
Could you be more specific about what you did in the XTC Tool because this is not working for me?
Couldn't this just be fixed by flashing a stock KitKat ROM for this phone? If so, where would I need to go to find one of those?

I Found another way to disable FRP.
I downloaded the XTC 2 V 1.17 but that didn't work. So the software told me to update it to V 1.19.
But this time while on the setup screen i had accidentally left it on the emergency call screen.
So launch XTC 2 v .11.19(Run as Administrator) then as soon as the software turns on. Look at the phone screen. while on the emergency call. It will ask you for "Allow USB Debugging" Just check mark Always and then OK
If it doesn't. just try clicking for read phone info. then it should ask for USB debugging.
Next Open up the ADB Folder ( Need to have ADB installed on the computer)
Then Run the Following commands in adb .
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
then reboot and you have just bypassed FRP on HTC Desire 626s running 5.1 Firmware

FIXED!!!!
djkid said:
I Found another way to disable FRP.
I downloaded the XTC 2 V 1.17 but that didn't work. So the software told me to update it to V 1.19.
But this time while on the setup screen i had accidentally left it on the emergency call screen.
So launch XTC 2 v .11.19(Run as Administrator) then as soon as the software turns on. Look at the phone screen. while on the emergency call. It will ask you for "Allow USB Debugging" Just check mark Always and then OK
If it doesn't. just try clicking for read phone info. then it should ask for USB debugging.
Next Open up the ADB Folder ( Need to have ADB installed on the computer)
Then Run the Following commands in adb .
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
then reboot and you have just bypassed FRP on HTC Desire 626s running 5.1 Firmware
Click to expand...
Click to collapse
Ah ha! That did it! Excellent work.

PIN not working after flashing new rom

Hey guys, I am having a huge problem with my PIN. I've been using the same pin for a very long time so I know for a fact that it's right. Now I cannot boot the phone, or get into TWRP.
When I boot the phone it's asking me for the PIN and it just keep saying that it's wrong which I know it's not. When I try to do a hard recovery into TWRP it's asking me for the PIN and then just sits at "trying decryption".
Anyone have any thoughts with where I should go from here? There's nothing on the phone that I need in terms of data so if it needs to be completely wiped out I don't care.. just looking for some guidance.
Thanks in advance.

Seems like you had your phone set up to require a pin even before it starts, which is why you can't even get into TWRP. It's a problem with the 6P, I'll link the thread in a bit if I can find it but basically when you back up a ROM, always remove ALL pins and passwords to unlock the phone first.. There's an issue that if you back up a ROM and keep it password protected, it won't let you get back into it even if the pin is correct, UNLESS you go in your file explorer (in TWRP) and delete a specific file that pertains to the the security features AFTER you restore it, but BEFORE you reboot the phone.
In your case it's worse because you had the device set up to not boot unless a code is entered. Don't ever do that, especially when flashing ROMS. The standard security on the lock screen when you boot the phone up regularly is enough. Had you not did that you'd still be able to boot into TWRP, delete that file, to get access to your back up.
There's nothing you can do now. I had to learn this the hard way too just like you. Load up your laptop and completely restore the phone using Nexus Root Toolkit or something similar, you'll most likely lose all data too. Sorry pal.
Edit- found the thread
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070

Hey it's no problem I don't mind losing all the data on the phone I everything backed up elsewhere.. as long as I can get it back running again it's all that really matters to me.
I'll give Nexus Root Toolkit a shot right now and let you know how it goes.. I appreciate the input.

Where would I go to be able to have the toolkit recognize the phone?

Got it all squared away.. I was able to get the phone recognized by just booting it and letting it sit at the PIN screen. Again I appreciate all your input it was very helpful.

Lg G6 downgrade

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

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