Related
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
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
AnnoyingZlatan said:
Few months ago I flashed some stuff on my phone which I shouldn't have, I guess. In the meantime I got a new one but now I'm trying to recover my OP3. I tried all sorts of MSM tools, (from Marshmallow to latest Pie that OP support provided me with) and in best case I could get it to bootloop and then throw me a dm verity warning screen after that (screenshot below) After that it only can throw me in a generic chinese OP recovery which fails to do anything. MSM runs fine, loads up as HS 9008 Qualcomm device and gets it's job done in 5-6 mins. I can't do anything in fastboot since bootloader is locked after MSM. Is there any help because it seems to not be completely dead?
Thanks
Screen after bootloop:
https://imgur.com/a/R1lJTjX
Click to expand...
Click to collapse
If you can get to bootloader, download and flash OOS 5.0.6. If not, try one of the MSM Tools on XDA. There are quite a few of them, search. Please also note that the Tool is different for 3 and 3T.
I had used one of the oldest Tools here on XDA a couple of times without any hiccups.
Did you get a solution to this? I am struggling with the same issue.
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
myserver57 said:
Another OP3 user here with the same problem as you guys.
I tried all of the MSM tools posted here, with no success and varying responses from the phone.
One of them does let me actually boot to recovery, but it's the generic one that only has install from adb (and sideloading always fails at 47% - haven't found a solution around that yet either). From inside recovery, attempting to wipe cache or wipe system gets about 3/4 of the way then the device reboots on its own.
I was also on occasion able to boot to the decrypt password entry screen, but no password is valid and attempting to issue a reset from there (from Forgot password) doesn't seem to do anything.
No issues getting to fastboot or qs9008 serial mode, but bootloader is locked also so kind of stuck.
In my case, phone was working fine, but the OTA update caused a brick so I've been trying to recover it since then.
Maybe somebody else has an idea here..
Click to expand...
Click to collapse
Did you try to sideload OOS using adb? Try the various versions of OOS.
TNSMANI said:
Did you try to sideload OOS using adb? Try the various versions of OOS.
Click to expand...
Click to collapse
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
myserver57 said:
Thanks, yes I did. Stalls at 47%.
Also tried every version of OOS that I could find (5.04, 5.05, 5.06, etc from https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722)
Also tried the versions from https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
(this one is the one that sometimes lets me get to recovery, the others don't).
Click to expand...
Click to collapse
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
TNSMANI said:
If you are able to use fastboot, try flashing TWRP or atleast boot TWRP and then from TWRP flash OOS or one of the custom ROMs.
If this also fails, I am at a loss for ideas. May be you have a hardware fault.
Click to expand...
Click to collapse
Thanks again for trying to help.
Sadly, bootloader is locked so flashing TWRP or even booting to TWRP is a no-go.
I don't think it's a hardware fault since it was working fine before the OTA update, but I guess you never know. Damn, if only sideloading would work, darn thing...
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
JuSkoch said:
Howdy all, hadn't done rooting/etc in a long time as my past several phones didn't have much support for them but got the LG G8 and was excited to possibly root it and also install a custom rom. Went with Arrow OS which seemed to run fine and I decided I wanted to get TWRP as a custom recovery instead of the one that comes with ARROW OS. I flashed it but now it get stuck on fastboot and constantly loops to it (and no longer shows the boot a/b.... which probably isn't a good sign). After leaving it alone for some time, I booted it up and now it gets beyond the the fastboot loop but I can either try to boot it up which only gets me the code red warning or go to download mode. I tried to use LG Bridge and download mode on my phone but the Bridge software doesn't detect the phone.
I realize some of this is probably because of my stupidity and I should've been more careful but anyone got any ideas on what could be done to get the phone back to a stable working state so that it can function again? I know there are some more "difficulties" because of the boot a/b partitions and having to handle that stuff properly. If it isn't possible, that sucks I guess but anyone who wants to chime in - thank you for your help!
Click to expand...
Click to collapse
Sounds like you might just need to reverse what you did to try to get twrp. If you have the boot partition for Arrow flash that back, if you don't have it should be pretty easy to get it from someone.
If that doesn't work can always use qfil and flash the necessary partitions to get LGUP to work, then flash or crossflash to a kdz and start again with stock.
You're in good company. I went down the same path and have become adept at repeatedly bricking and un-bricking my G8. (LM-G820QM5) I picked up 2 tidbits of info that have been helpful. The first is that my G8 ThinQ will not boot Android when the engineering abl_a.bin has been flashed on to it to enable fastboot. Sure it will fastboot, and go into EDL or download mode, but in order to boot the OS, I have to put the normal abl_a.bin and abl_b.bin back.
The second lesson I learned the hard way is that sometime LGUP fails to flash when the phone is in download mode. I was searching around XDA and came across a very helpful post from starlyn1232. They posted a command line utility that has been successful in un-bricking my G8 when LGUP failed.
I downloaded the appropriate kdz from lg-firmwares.com and the starlyn1232's utility from https://forum.xda-developers.com/t/lgup-flash-utility-based-on-lgup-1-16-cmd-and-lgup-1-17-lgup_common-dll.4112121/
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
JuSkoch said:
Well thankfully, i still had the original files from the unlocking thread in this forum and I also apparently did make a backup of my files right before I installed TWRP 3.4 or whatever and was able to get my phone working again - which is awesome! Also, what's the best way to back up everything on the phone (or at least the essentials) in case of flashing situations like this? I in the past would just use TWRP to do a backup/restore but since I flashed ARROWOS and it has its own recovery and doesn't seem to have a backup option - asking if any one has a recommendation. Thanks!
Click to expand...
Click to collapse
I would highly recommend looking at bkerler edl utilities. You can easily find his git page which has the download option for an iso linux boot which has everything installed.
It's a bit involved / complicated figuring out the command line interface, but once done you can backup everything and it will create the xml files needed to reload it.
I would suggest this for everyone but especially for those with sprint or att devices, as there is no kdz available for them.
I've recovered from various issues too many times to count with backups I've made for v40, v35, and now G8 (2 of them).
cheers
Could you pass the tutorial on how to install TWRP?
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Ashfaq Ahmed spsc said:
Does anyone have rawprogram0.xml
Patch0.xml for lg g8
Click to expand...
Click to collapse
So the rawprogram xml will be for ea lun, and it will vary by which rom you're trying to flash, it will also vary by segment starting positions for the partitions. IE, there is no generic version of it.
2nd, you don't need a patch xml, just click cancel or skip for that entry. Note; the rawprogram xml is usually generated when a backup of the binaries is made, and it will be for that specific backup.
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
MR_ZenR0 said:
Hello there sorry to pop in unannounced I would like to interject briefly and please pardon my ignorance I'm still a noob.
I have a similar issue, but I'm a little bit confused as to what I should do. In my Case i have a SOFT brick.
(G8 ThinQ VERIZON LM-G820UM (Model) ---- G820UM20j (Software)).
I unlocked the bootloader and rooted with magisk successfully, Still running STOCK OS
Then I Flashed TWRP.zip and some version of Magisk.zip with the magisk app, Then I Rebooted to Recovery.
Inside TWRP i Wiped, Format and then I flashed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
This process Finished without any errors, however, after I rebooted i now cannot go past the Verizon Logo and it's stuck there.
Fortunately, I have All the Original files backed up (abl_a.bin, abl_b.bin, boot_a.bin, boot_b.bin)
And TWRP also managed to create a Backup beforehand.
I can go easily into EDL mode and i also have the engineering abl_a file on hand.
i can also get to the built-in Stock factory reset / safe mode but I'm unsure if I should use it.
So my question is if i would be correct in loading ALL of the original Files using QFIL, or only the boot_a boot_b files ?
or if i should do something else like getting the firmware in my case?
thank you for your time in advance.
Click to expand...
Click to collapse
Hello, I Managed to Fix it by loading my backed-up original boot_a.bin and boot_b.bin using QFIL, I have successfully passed that Verizon logo now and should be able to go from here, not that anybody asked, I just thought someone in the future might have some use out of this information here. so if you are from the future and you read this, you are welcome and good luck
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
You must have the firmware requested by the OP, flashed it if necessary.
See this rom below where everything is explained.
https://forum.xda-developers.com/t/rom-13-official-pixelos-aosp-unified-11-09-2022.4237791/
Other TWRP/OF.
https://sourceforge.net/projects/recovery-for-xiaomi-devices/files/willow/
Regrettably, my telephone is now hard-bricked. Recovery and Fastboot modes also not possible, so back to stock-ROM is no longer possible either. Only a flashing screen, and - when trying to enter fastboot mode, only short showings of the word fastboot, but no response in MiFlash. I think that a new phone is unavoidable.
Meanwhile, I've tried to enter EDL mode. Troed various fastboot commands, but no response from the telefone. Ultimately, I've tried to open the backcover (in order to reach the so-called "test points"), but that's easier said than done.
Website
is pretty clear, I know where to find those test points, but I'm lacking a 'heat gun', demonstarted in the youtube film. I tried it with a hairdryer, but that proved ineffective, moreover, the hairdryer stopped working (overheating?). Still need to check a possible fuse in the hardryer. Anyway, I'm awaiting a Redmi Note 11...
gjongbloed said:
I have a Redmi Note 8T (willow) - unlocked - TWRP installed - rooted with Magisk 25.2. When I try to flash a custom ROM, all seems to go well. However, after reboot, the telephone reboots in TWRP, and keeps rebooting in TWRP. The only possibility left open to me, appeared booting in Fastboot mode and flash the stock-ROM with MiFlash.
This happened on a few occasions. Yesterday, I tried https://private.projectelixiros.com...2_ginkgo-13.0-20221025-1529-BETA-OFFICIAL.zip with the same result. Sofar I've only been able to successfully flash lineage-18.1-20221024-nightly-ginkgo-signed.zip, using the associated recovery, (But with that ROM, the phone-function didnt work with an MMI-code error.) So, at present, I'm again on stockROM, bootloader locked again - unrooted - back to day zero...
Click to expand...
Click to collapse
But what went wrong in the first place?
The flashing instructions quoted
Flashing Instructions
Clean flash (coming from a different ROM):
• Flash recovery (links above)
• Download ROM from the link above
• Download Magisk v23.0 or newer (optionally)
• Reboot to recovery
• Format data (if encrypted)
• Wipe system, vendor, cache, dalvik, data
• Flash latest android 11 global stable firmware (link above)
• Flash ROM zip
• Reboot and voila!
It mentions "flash recovery". The only method to install TWRP that I know, is through fastboot commands (fastboot flash recovery twrp.img, after having renamed the latest twrp image file), and then "fastboot reboot" while keeping Power + Volume Up pressed.
Prior to this, I had placed the firmware-, ROM- and Magisk-files on the phone.
After installing TWRP and Magisk, I wiped cache and Dalvik.
Then, when tried to flash the ROM, apparently that was wiped too. I think that it would have been better to reboot the phone after installation of TWRP and Magisk, then transfer the firmware and rom-files to the phone, and then boot into recovery again.
Anyway, that was not what I did...
Right after installation of TWRP and Magisk, having seen that the files to be flashed, were no longer there, I tried to install the firmware- and ROM-files with 'adb sideload' commands from TWRP. The flashing process seemd to go well, but booting to system proved disastrous...
A 'lesson learned' - at least for me: do not proceed if you - for some reason - can't follow the instructions. but break off, so that you can still reflash the stock-rom!
Sometimes, flashing the firmware with the Twrp does not work and you have to flash the complete rom with Miflash.
For EDL mode you will not have the necessary authorization.
See my PM.
gjongbloed said:
But what went erong in the first place?
Click to expand...
Click to collapse
1st
2nd
what brick your phone is relocking the bootloader
never do that on a redmi note 8 !
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
gjongbloed said:
I certainly did not relock the bootloader. After re-installing stock-ROM, unlocking the bootloader was always the first action before doing anything else...
Click to expand...
Click to collapse
Redmi note 8t(Willow).
Anyway, even if you had done it, it wouldn't have changed anything,except that you would have relocked the bootloader, since this model is intended for the global market with roms, Global, EEA, Russian, no CN roms.
Situation at present (4-11-2022): I have succeeded in opening the telephone in order to make the 'test points' approachable and to disconnect the battery. In the 'device manager', I've seen 'Qualcom' appearing on one of the com-ports. To continue, I now have to await a 24 hours break after too many times of opening my Mi-account during earlier attempts of flashing with the MiFlash tool .
.....
Well, 24 hours later, I've come to the conclusion that my brick definitively remains a brick. Tried again and again, but each time received an error "Cannot receive hello packet. MiFlash is trying to reset status.". And that's it...
Meanwhile, I had the impression that I might have better results with the Qualcomm tool QPST. The telephone - in EDL mode - was observed in QPST Configuration all right, but the flashing with QFIL failed with a consistent error: Unable to read packet header.
I've seen many reported occurrences of this error in various XDA fora, but nowhere a conclusive remedy. I'm out of options now...
Now, I get the information that the file that I want to flash, is too large. If only there could be a smaller file, only to restore the part of the os, through which to activate the fastboot and recoverymodes...
Well, after many tries, searching for solutions for the various Sahara fails that I encountered while using QFIL, I found a solution that really worked:
[GUIDE] How to unbrick RN8 (won't boot only backlight turns on for a second) using EDL
Hi all, after lots of trial & error, I would like to share how I managed to unbrick my Redmi Note 8 original thread: https://forum.xda-developers.com/t/need-redmi-note-8-firehose-without-authentication.4031513/ many thanks to dxD7 who provided...
forum.xda-developers.com
I could use the patched firehose file also on an older Global EEA version of the stock-ROM, and then everything worked fine... It took a while, updating the phone to the latest version, but that doesn't matter...
Well... the phone is working again with MIUI Global 12.5.5.0 (RCXEUXM).
Working, but... both IMEI's are null, therefore SIM cards are no longer recognized, which means that I can't use the dial function and can't use a mobile network. WiFi is working.
Moreover, the bootloader is locked again, but I can't unlock it with MiFlash Unlock, because this procedure requires connection via a mobile network. And without an unlocked bootloader, any possibility to root the phone, flash a repaired qcn file (with proper IMEI's), try out custom ROMs or whatever, is blocked...
Any option left? (Fastboot and EDL mode still possible).
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
gjongbloed said:
Meanwhile, problems are solved to some extent:
Phone is unlocked, stock ROM re-installed, IMEI's are again reading correctly. Only problem remaining: network is not detected, i.e. dial-phone and mobile data not possible. Probably hardware-problem. (Tried all options I could find, but 'no joy'.)
Meanwhile, I have installed an SD card, and that makes all the difference. Tried installing PixelOS and PixelExperience: both installations problemless. Off course, still without dial-phone and mobile data. But, good enough to be confident to install a custom-ROM on my wife's Redmi Note 8T.
Click to expand...
Click to collapse
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Cristina.D.M said:
How to unlock without connection via a moble network since your phone lost IMEI?
I read every word you typed, and feel the mood you was at,
But in the end, a sad story.
I did flash my phone before I understood every procedure and knew how to fix or recover from it.
luckily things work as I expected.
Thanks God.
Click to expand...
Click to collapse
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
gjongbloed said:
Thank you for your sympathetic response.
My answer to your question: Indeed, I don't have connection via a mobile network, and can't use dial-phone, but WiFi is all right.
When I started, trying to flash a custom-ROM, I did so with my experience of some years ago with my former phone: a Google Nexus (maguro) from 2011. Things were so much easier then, no data-encryption or whatever. As said earlier, the turning point was when I placed a cheap 32GB SD-card in my Redmi Note 8T. Now I could place all the necessary files on that SD card, which made the flashing (with OrangeFox) much easier. So, I'm not sad... The moment, my phone got hard-bricked, I bought a new phone (Redmi Note 11) for daily use. And then started learning: how to open the phone, where to find the "test points", how to get the EDL mode working, how to restore stock-ROM via EDL mode, how to restore IMEI's etc. etc. I have learned a lot, and every step was a question of try - retry - retry differently - retry again etc. But the ultimate success (with the exception of the "no network" problem, for which I couldn't find a solution) is quite rewarding. Of course, it took quite some time, but time is no problem for me. I'm retired a long time ago (I'm almost 80), so "it keeps me off the streets"...
Click to expand...
Click to collapse
WoW, It is boomshell, Now I do know what is "One is never too old to learn".
Thanks ever so much for your reply.
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here
RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know
You have to download the firmware and paste it into the platform tools folder and click flash all.bat