So i messed up when trying to update my watch and somehow deleted the firmware so my watch bootloops upon start-up, any way to fix this?
Im have the same problem. Im stuck in bootloop after trying to flash custom kernel. I can not rech recovery. Not original recovery or TWRP. Fastboot works. What to do?
Is there any restore image to flasH?
Here are three solutions in one answer, because you did not give quite enough info.
First, try holding the button on boot up. Hopefully that will get you into usb mode. If it works, download the sony software, and go to the help section, and download and install the update.
Option two,
Code:
adb reboot recovery
Or, download the version of twrp for your build as well as your original image, and use fastboot.
Code:
Fastboot boot twrp.img
then use twrp to install the factory zip. You can do this directly in fastboot too, but it is more difficult because fastboot only installs each image separately. If I knew what versions of software you had, I could help you find the images you need.
I have tried both fastboot flash and fastboot boot for both original recovery and also TWRP, but non of the recoverys will boot, not even with Fastboot boot.
The command lines says OK on my PC, It is getting downloaded, and it says it is booting / flashed [OKAY].
But all I get on my Smartwatch 3 is bootloop.
My Smartwatch 3 is OEM unlocked. I even tried to lock it, and unlock it again.
I have full contact with fastboot on my PC, all the commands are taken in and seems to work, but my smartwatch won't boot no system or no recoverys. Only USB-mode and Fastboot mode...
I have also tried to clear cache and userdata in fastboot after OEM Unlock.
I will try the Sony Software now. That is my last way out I Think.
The Sony PC Companion software from sony's website worked for me to save my smartwatch from bootloops . I just did a update and installed it over what was already on the smartwatch.
Thanks lekofraggle for quick answeres. I had no idea the PC Companion had this feature.
SimDroid, I am glad that helped. If it hadn't, the next step would be to flash an image through fastboot. That would be scary, because it sounds like your boot loader was corrupt. It's nice to know the usb and PcCompanion piece still worked. Another reason this watch is incredible.
Cheers.
does anyone have a download for the original (5.0.2 im guessing) ROM for this watch? I want off the rubbish 5.1.1 update before i am forced to sell the watch due to the terrible battery
The smartwatch works as it should now, original recovery and everything is back!
So, if i may go back to where it started?
I noticed now that I flashed the custom kernel for the watch built for wrong firmware. Im on 5.1.1, and there doesnt seem to be a developed shared kernel with all four cores unlocked for it.
Im also interested in where I can find those images to flash via fastboot as you mentioned lekofraggle
I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.
It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.
Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...
BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?
I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.
Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.
I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?
I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?
So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...
verbage said:
So, straight to the point--anybody here have an idea about how to relock the bootloader on an H811 when ONLY download mode is available?
Over the last few days, this H811 has progressively succumbed to the dreaded G4 bootloop plague, and it is now purely bootlooping (doesn't even get to T-Mobile logo). Before it got so bad, I was able to flash it back to factory state (minus the unlocked bootloader) with the 20x KDZ using LGUP (reason why I did this will be explained below...). But this means that recovery is not available to get get into bootloader mode that way. And I have not yet had a complete successful boot after the KDZ flash to enable USB debugging, which would allow me to get into bootloader mode with the adb reboot bootloader command. So essentially, only download mode is available at this point, uggh...
The back story is that I just bought this used H811 to try out steadfasterX's LOS16, which, by the way, is fantastic! And almost immediately, the phone started displaying bootloop-ish symptoms. For example, like after the initial bootloader unlock, which I did immediately on receiving the device just a few days ago, the phone crashed during the optimizing apps step of the subsequent reboot (it probably overheated). I should have just relocked the bootloader at that point, and sent it back to the vendor for replacement. But I was anxious to try LOS16, and between occasional crashes, I eventually got it installed. But over the next few days, the crashing and occasional bootlooping became so progressively worse that I decided I really did need to send it back for replacement. So today I reflashed the 20x KDZ with LGUP, and that worked fine. But I'd like to relock the bootloader, too, so the vendor doesn't claim I screwed with it, and thus, that they are not responsible for replacing it. But as I mentioned, the only mode available at this point is download mode because it is purely bootlooping on the initial text screen without even getting to the TMo logo.
If I could get into bootloader mode, I could try to do either a a.) fastboot oem lock (given it is fully stock with the recent 20x KDZ flash, there should be no chance of bricking...), or b.) I could also flash just the misc partition extracted from the 20x KDZ. But again, without recovery, nor the possibility to enable USB debugging, I cannot get into bootloader mode. So that's why download mode is my only option.
steadfasterX's SALT works with download mode, but it cannot flash single partitions yet to follow the misc partition flashing strategy I mentioned above.
So what options does this leave me?
Option 1.) phone is in the freezer right now to see if I can get just one more good boot in order to get enable USB debugging, and thus, get to bootloader mode via adb; and from there, then relock the bootloader so the vendor doesn't see the bootloader unlocked message, and claim that I am responsible for the problems...; yeah, the freezer method is a long shot, but in the past with a VS986 that was bootlooping, I did get one final boot out of it for data rescue using this freezer method...
Option 2.) in download mode and via SALT, I can get a shell into the phone; maybe there is a way to flash just the misc partition (extracted from the 20x KDZ) via a command line in that shell, and thus, get the system back to a locked state?
Option 3.) well, send it back to the vendor as is, and hope that they do not try to claim it is my fault because the see the unlocked bootloader message...
Option 4.) if options 1-3 do not work, well, perhaps give LG a call to see if they will fix the circuit board; by the way, they did it for the VS986 I mentioned above without any questions whatsoever; but the difference is that I was the original purchaser of that VS986 whereas this H811 is a secondhand purchase, and LG might use that as a reason for not fixing it.
Any other options that I might be missing? Thanks for any wisdom or suggestions you might be able to provide!
Anyway, my learning lesson from all of this is patience--like I said, I should have returned the device immediately on seeing the first signs of bootlooping because in my experience with both the VS986, and this newly received H811, well, once bootlooping symptoms start, they progress very quickly...
Click to expand...
Click to collapse
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
For boot looping tricks see my signature while I think freezer is your best bet here .
In SALT -> advanced menu -> wipe partitions
Choose misc and wipe only that.
Locked again .
Click to expand...
Click to collapse
Ah, wonderful! I was thinking that there were some special bits in the misc partition, and thus, it had to be flashed. But if I can simply wipe it, perfect! Thanks so much, steadfasterX, for your unending generosity with helping the community here!
No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.
verbage said:
No luck with the freezer technique after several attempts. I did get as far as the T-Mobile logo on one try, but it went back to bootlooping immediately. So I proceeded with the misc partition wipe via SALT, and the operation appeared go fine with a success message. But then on rebooting, the bootloader unlocked message still appeared. Not that it should make a difference, but I repeated the operation several times and used several different reboot mechanisms--via that SALT reboot button, pulling the battery, etc., but the bootloader unlocked message still sticks. So it looks like I might have to send it back as is.
Click to expand...
Click to collapse
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd:
devinfo, misc, persist, persistent, drm, sns
Ensure you use the exact same firmware as your current bootloader stack
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Ah yea the h811 is different then the others .. I rem again.. There are also persist and others involved for the h811 . You could flash the ilapo TWRP from my leech server and flash the following partitions with dd: devinfo, misc, persist, persistent, drm, sns
Click to expand...
Click to collapse
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!
verbage said:
Hmmm, I wish I could flash the ilapo TWRP, but after recently flashing the official 20x KDZ using LGUP, I have not been able to get even one successful, complete boot to enable USB debugging. And of course, the TWRP recovery partition was vaped by flashing the KDZ, too. So the only functionality available at this point is download mode. But I have not yet found a way to flash only select partitions (like the six you mentioned) in download mode. For sure, it must be possible (maybe like by using dd for manual, command line flashing using the limited shell provided by SALT). But I am not at that level of expertise yet
This said, I have been doing some exploring regarding the six partitions you mentioned. I used SALT to unpack the original H811 20x KDZ image, and it seems that five of the six partitions (devinfo, misc, persistent, drm, sns) are just filled with zeros. So I suspect there is no real need to actually flash those directly--I think I can just wipe them with SALT for the same effect, right? This leaves just the sixth partition--persist--which is almost all zeros itself, too, with the exception of about 3,500 non-zero bytes spread throughout the file. So maybe in the long run this might boil down to simply having to flash one partition (i.e. persist) as the rest can be wiped since they are all zeros anyway? Whatever the case, whether I have to flash just one partition or all six, the problem remains--there is no straightforward path available to me for flashing a single selected partition via download mode.
-------------------------------
Okay, I have been sitting on the above paragraphs for a couple of days, which gave me some more time to ponder the situation, and make some useful observations. In particular, I have closely watched the dim screen on the H811 while using LGUP to flash the official 20x KDZ image. At one point about halfway through the process, it starts quickly flashing up the names of partitions as it presumably flashes them by name. It appears that the persist partition is one of those which is flashed... And so (maybe?) eureka--could this solve my dilemma of having to flash just a single, selected partition via download mode???
More specifically, if I just load the full KDZ image via LGUP, which takes care of the persist partition, and then if I just wipe the other five partitions (devinfo, misc, persistent, drm, sns) under SALT, well, will this effectively relock the bootloader???
Happy to hear any comments about this before I attempt it!
Click to expand...
Click to collapse
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
while doing my PoC for unlocking all g4's we found that if you backup ALL these partitions when your device is unlocked and re-flash them on the same device (h811 only) while it is locked it will be unlocked again.
the thing is lgup will never flash ALL partitions on a regular flash and thats why you keep your unlocked state (usually) after flashing a new kdz.
For sure thats the case for misc and very likely for the above mentioned.
afaik selecting the refurbish mode will flash any of them.
so TLDR; you COULD wipe the above partitions in SALT, one by one and boot after each to see if its enough.
the second option is to use the lgup developer version. it might be able to flash single partitions (havent used that for long time). would give it a try but you have to google for it.
the third option is opening a shell with SALT while in download mode (advanced menu) and see if you can do this:
https://forum.xda-developers.com/showpost.php?p=74433698&postcount=149
btw: what is the LAF protocol version shown in the SALT main window? could you pls share the debug log (advanced menu -> debug log -> upload button)
yea and the last resort would be to bring the device down to 9008 mode and using QFIL to re-flash all partitions involved (requires a lot of knowledge and preparation though)
.-
steadfasterX said:
I just know that the mentioned partitions are involved in unlocking the bootloader on a h811 - so they are involved in locking it down as well.
Click to expand...
Click to collapse
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.
verbage said:
Thanks for all the pointers and great guidance! I will see where it takes me this weekend.
For the moment, the LAF protocol version is listed as 1000001, and I posted the SALT debug log at https://bpaste.net/show/eqxU.
Click to expand...
Click to collapse
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.
steadfasterX said:
thats great. this version is fully supported in SALT for flashing!
start SALT in a terminal with
Code:
sudo ~/programs/SALT/salt --experimental
and you get new buttons in the main window.
That makes things a lot easier I guess
-.
Click to expand...
Click to collapse
Yes, I saw the flashing temporarily not auto-enabled comment in the log, and was about to hunt down how to do it, but now that I know the needed switch, perfect. In fact, I just did it, and I see the new buttons with extended functionality--great! I can't play any more now, but for sure, this weekend!
Thank you so much, steadfasterX, for your generous and unending support for the user community here!
verbage said:
I can't play any more now, but for sure, this weekend!
Click to expand...
Click to collapse
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!
verbage said:
Okay, okay, okay--I had time to play...
I first backed up the six H811 partitions in question (i.e. devinfo, misc, persist, persistent, drm, sns) just in case... And then wiped all six of them in SALT.
Now the phone reboots with no unlocked bootloader message on startup--great. Still crazy bootlooping, though, but now without the unlocked bootloader warning so I feel much more confident in exchanging it for a replacement.
In sum, wiping those six partitions does the trick--no need to flash just the persist partition as was discussed in previous postings. For sure, that might wreak havoc with the MAC addresses or similar, but in this case, it doesn't really matter because the phone is already completely disfunctional because of the bootlooping.
Thanks again, steadfasterX!
Click to expand...
Click to collapse
Haha great ! Glad it worked for you ! Hope the replacement goes fine now
Sent from my OnePlus 6T using XDA Labs