Relock bootloader via download mode (only) for bootlooping G4? - G4 Q&A, Help & Troubleshooting

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

Related

[help] [oneplus3] [stuck in boot logo] [softbricked] cannot boot into system [solved]

Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.
i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
I think, I have solved it guys. I'll let you know once completely under control
So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..
I am glad it helped. That's the power of Xda.
My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.

Issue booting LGG4 after UsU unlock

steadfasterX said:
Well first of all your issue is not an UsU issue .
This thread is only about UsU so this is going more and more off topic .
I would suggest you open an own thread for your specific issue and we continue there.
You wrote you flashed all partitions of that kdz. Write down (in that new thread ) which partition names exactly.
Click to expand...
Click to collapse
Lets start from the beginning then, shall we;
I have a LG G4 H815 TWN variant. It was on LP for the longest time because it had root, and there was no chance for an official unlock.
My phone WAS on LL/LP because the phone suffers ILAPO but was recommended I upgrade, so I use a KDZ i found [H81520e_00_0818.kdz][9C861EA87A0E07C873A7835ABF21A5CE]. flashed through LGUP. (unsure where I originally found this file)
fine and removed the battery when it attempted to reboot the phone (still saw the LG logo)
I presumed all was fine then followed the guide to install UsU, which went fine (used option 3, files from PC)
Flashed a '4 core fix' version of TWRP
Formatted Data, after the phone showed 0 bytes free. After formatting, everything seemed fine.
Installed LOS 15.1 UsU version from SFXs website
Now here is where it went pear shaped.
Booting would always result in TWRP being launched, no matter what.
I was told it may have been ILAPO catching the boot of the new OS, so i should patch my boot.img.
I patched the boot.img, but accidentally flashed aboot due to unclear instructions and an incorrect guess on my behalf.
I was then told to use some specific QFIL guide to recover from my brick. The process succeeds.
But I am back to square one. Booting only to TWRP
Follow FAQ #20
-Downloaded this KDZ this time, instead of using my original KDZ from before
-Downloaded newest current version of FWUL (v3)
-Ran KDZ extract via SALT
-FASTBOOT flashed extracted files. (All finished OK)
Code:
fastboot flash factory factory.image
fastboot flash hyp hyp.image
fastboot flash modem modem.image
fastboot flash pmic pmic.image
fastboot flash rpm rpm.image
fastboot flash sbl1 sbl1.image
fastboot flash sdi sdi.image
fastboot flash sec sec.image
fastboot flash tz tz.image
-Rebooted. (boots only into TWRP)
- - - - - - - - - - -
SALT says the firmware is still: LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0 - which to me looks like its still LP firmware.
- - - - - - - - - - -
I tried flashing a different OS (after formatting of course), for the sake of it, maybe it'd be different somehow, i tried; RR-O-v6.0.0-20180622-h815-Unofficial.zip
then flashed H815_UsU_baseband_flash-in-twrp.zip too.
still only boots to TWRP.
steadfasterX said:
Also let it bootloop and when back to TWRP :
adb shell
strings /dev/block/bootdevice/by-name/misc | head -n 6
Write the output in your new thread as well
Click to expand...
Click to collapse
Code:
BSP Forever
SM03s151212002753
0,1111111111111111
LGH815AT-00-V10f-TWN-XX-JAN-13-2016+0
LGH815AT
LGH815AT-00-V10f-OPT1-YT-JAN-13-2016+0
QFPROMalreadyblown
1,12,0212,21,2011,201,1,111,1,331122,10,0,1200,2,1,1,1,213,10222,0,2,2,0,2,2,2,2
"1","fff,fff,ffffffff,ffffffff,55"
not sure if this is the sort of stuff you wanted. I couldnt get adb shell to work from within TWRP so i just used the terminal from within TWRP and wrote out the output here instead.
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
tim455 said:
I hope this is enough information for @steadfasterX
I thank him for all his time and effort on the unlock and also the time on the forums helping dummies like me.
Click to expand...
Click to collapse
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Download & flash:
http://leech.binbash.it:8008/lineage/nougat/h815-UsU/
--> lineage-14.1-20190120-UNOFFICIAL-h815_usu.zip
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Flash this one in TWRP:
http://leech.binbash.it:8008/stock/LG/h815/
--> h815_20p_bootloader_29a_modem_TWRP-flashable.zip
Wipe -> advanced -> select system and wipe it
Reboot -> recovery
Click to expand...
Click to collapse
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
tim455 said:
Thanks for the simple instructions. Turns out I couldn't follow them through to the end.
I wiped my system so it was clean prior to this, so I didnt mess anything else up. (I've done this before with no issue)
Flashed the bootloader/modem zip, then restarted (to recovery).
black screen, and a hard brick.
- - - - -
after that. I "played around" to see if i could maybe fix the issue myself and try again. using that same qfil guide as before. but this time, ran into an error..
Code:
COM Port number:4
Sahara Connecting ...
Download Fail:Could not connect to the COMPORT
Download Fail:Sahara FailValue cannot be null.
Parameter name: key
Finish Download
Device manager shows the little orange warning sign, but the drivers appear to be correctly installed.
EDIT: needed to be in unsigned driver mode. phone booting in TWRP again.
EDIT2: tried installing the LOS zip and get an error
E3004: This package is for device: g4,p1,h815,h815_usu; this device is []ro.product.name ----(a square box with a character it couldnt read)
I can try restoring an old backup I have if you think that would be wise, but I dont think I will play with it any more before hearing from you again. It's definitely the bootloader/modem zip thats causing the brick btw.
Click to expand...
Click to collapse
I am soooo sorry dude.. I wrote the wrong file name. You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
,.-
steadfasterX said:
I am soooo sorry dude.. I wrote the wrong file name.
sorry again.. I am doing all this in parallel of my work and private life which both are continuously stressful since years and well yea I haven't thought before writing, that can even happen to me..
Click to expand...
Click to collapse
It's okay dude. I can understand your mis-concentration due to stress. Don't worry about it. :good:
You're always helping others.
steadfasterX said:
You have to flash ofc an UsU zip not the other.. I have corrected it above but here again:
--> h815_UsU_20p_bootloader_29a_modem_TWRP-flashable.zip
That one does not cause a brick!
Your current state means you have to use SALT to flash UsU again. Afterwards you should be able to install the LOS zip without an issue
Click to expand...
Click to collapse
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
tim455 said:
I flashed UsU again via SALT (although it still said UsU was installed correctly) and got a weird message saying that something didnt work (attached)
tried to install LOS after, but was hit with teh same error message. had to reflash TWRP in order to get it to continue.
Installed LOS and.................. always boots to TWRP :\
I've attached logs again.
Click to expand...
Click to collapse
Yes that message is normal in your case . No need to worry.
So it let you flash LOS now without an error?
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1 ..
Sent from my OnePlus 6T using XDA Labs
steadfasterX said:
Yes that message is normal in your case . No need to worry.
Click to expand...
Click to collapse
great.
steadfasterX said:
So it let you flash LOS now without an error?
Click to expand...
Click to collapse
Yes. It now installs fine and finishes without any errors.
steadfasterX said:
Well if you can come to IRC from Monday to Friday , 9am-5pm UTC+1
Click to expand...
Click to collapse
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
tim455 said:
great.
Yes. It now installs fine and finishes without any errors.
Sure. Not really used to IRC. I'm taking a look now (even though its after those times) and just asking which channel should I join to talk to you about this? (what should I say or ask?)
Click to expand...
Click to collapse
All my main threads have a topic for
"support/irc "
like the SALT one:
https://forum.xda-developers.com/android/software-hacking/tool-salt-lg-revolution-t3717864
Sent from my OnePlus 6T using XDA Labs
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
robles4242 said:
I just got a Sprint LS991, i have a VS986 that i Was used to where all the way up to 2BA Firm ware i could go all the down to 13B firmware and root. Now with this LS991 i am at ARB4 right off the bat on ZVI firmware. I cannot even do the USU method to unlock the bootloader. I really want to Sim Unlock this device and gain root.
Is there any possibility of wiping out the partition that contains the ARB somehow so a downgrade can be preformed? Or any method of any way shape or form. I also have a H810 main board G4 with H811 stickers and firmware (Bootloader Unlocked) but it is stuck in a bootloop and i only got it to turn on once since that happened with the oven method and now its stuck at the boot screen only and freezes.
Click to expand...
Click to collapse
you are out of luck dude. ARB is no partition - consider to read the technical details if interested ( https://bit.do/antirollg4 ).
It is a physical fuse and so irreversible (means it requires to replace parts on the mainboard to make it work again - nobody knows which/what though).
No root as you are on MM as well and you cannot downgrade due to ARB.
.-

(Urgent Help!) bootloop after normal update, bootloader locked. no ADB, no OEM unlock

I recently found a moto g5 in one of my fellow "old tech" drawers and decided to turn it on, it was on the
1. May 2018
Security patch on nougat, I decided to use the inbuilt system updater to go to Oreo, and now....it crashes during flashing process after about 25-30% completion,
Now im guessing boot or System is not properly installed due to the zip file having aborted mid-flash
Recovery doesn't properly boot as that is used to install the update and thus imidiately goes to doing that
Also, it hang up during installation on random times, it basically has a record of 2mins of not crashing whilst still being stuck on 30%
I got it to "boot" when trying factory mode, yeah it crashed mid boot animation...not a help
Any suggestions? EDL mode maybe?
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
TheFixItMan said:
Can you not flash firmware via fastboot
In theory as long as firmware is signed you don't need an unlocked bootloader to flash firmware
Firmware can be downloaded from https://mirrors.lolinet.com/firmware/moto/cedric/official/
You can also try the lenovo moto smart assistant to flash the firmware
https://forum.xda-developers.com/g5/how-to/guide-how-download-official-fastboot-t3916778
If not you will most likely need a motherboard replacement or jtag firmware flash at a repair shop
Click to expand...
Click to collapse
SOMEHOW it just decided to boot, I have never seen such behaviour, even on my g5s which I had for a while, (and am currently daily driving to school if it wasn't closed....NEVER
Maybe I'll unlock it and try somehow recreating it? Well it's in physically rough shape but all components inside are fine...so that can't be the reason....?
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
anonymous724 said:
My g5 got stuck in a bootloop without an update, no root or anything modded. Is there any way to recover the data if its stuck like this?
Click to expand...
Click to collapse
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
riyan65 said:
Flash the stock rom and boot the device. But this will format the device.
To save data, remove the command fastboot erase userdata
Fastboot erase customisation.
Apps may be gone, but files In internal storage will be safe, like download,photos, music.
Click to expand...
Click to collapse
no luck on this front, gets to the passcode screen, write in passcode then motorola logo shows and screen keeps on turning off and on.
Thanks for the effort though, much appreciated
Mine is similar to yours. Initially was on permanent loop of the following:
1. Boot to moto g splash screen... Repeat
2. Boot to lock screen then usually a few loops of 1. (after entering the patter or left Idle)
The phone initially didnt have any developer options enabled.
I wiped cache using recovery mode. Restarted and pretty much the same thing except that it would on rare occasions actually fully boot up usually only last a few minutes before cycling between steps 1 and 2 above.
I used those rare boot ups to backup all files and enable any USB debugging /oem unlock (incase I need to use a solution dependent on these being enabled.)
Factory resetted it and its still the same with the random successful boot amongst the numerous failed ones.
I managed to hook it up to Lenovo's Lmsa and flash the latest ROM. Now I get a lot more successful boots but still loops every so often. The downside is that I can no longer do any functions that make use of the audio/ mic/ video (can take pictures). If I do then it will crash and loop.
The hardware test on the LMSA passed for every component before flashing to the latest version. Post update it predictably fails on the audio/ mic components.
I guess I'll have to go back to the old version to see I get the audio back.

Bricked LG G8 after flashing ARROW OS & TWRP

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

Question [lineageOS][Recovery]Stuck with fastboot bootloader bootloop

I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Hi.
I have been looking into lemonadep a bit lately.
I found a (renewed) 9 Pro a few days ago.
Should be here by the end of the week and I test more then. ​
Might want to ask your question in the LOS 20 thread.
Development [ROM][OFFICIAL][lemonadep][13] LineageOS 20 - Link
Cheers.
MintyFreshSocks said:
I had lineage19.1 working and a respective custom recovery with it. That was cool. Then I got dumb...
I proceeded to flash the new custom recovery for lineage-20.0-20230103-recovery-lemonadep.img. I am still not sure if the recovery needs updates or how to do so anyway. Can I still upgrade to version 20.0 with a recovery from 19.1? Regardless I am stuck in fastboot loop.
I am lost. I can't get to recovery mode anymore. How do I check things and see what to do next?
Click to expand...
Click to collapse
I suppose you are about to flash lineage20,
if so, search "payload-dumper" tool
from the rom's payload.bin extract dtbo, vendor_boot and boot img files, flash them to the related partitions, and your phone should be ready to load the new rom via sideloading it
Thank you for your time and consideration.
I have lost track of my own efforts here. Basically I'm right where I left off, with a little less battery. I am now onto the process of using MSM tool from this place. I get things started and then I reach "param preload failed" under the status, in the MSM tool. Is there any hope? I get scared when reading this disclaimer...
"If you modified any partition not touched by MSM, namely param and persist but there are others, you face a possibility of a hard brick. MSM will reset your "Enable OEM Unlocking" in dev settings and you might get a corrupt boot. Restore your backups before attempting. That said, If all you just tried to convert a ROM using OTA payload.bin, you should be fine."
...because yea I'm a curious kitty. I think I was messing in just about everything dangerous that I could... I still have a bootloader screen, thats fun to play with... I've got the right driver from qualcomm and it says the proper "QDloader 9008." But still no dice with MSM.
Is MSM the only option? I found this other OEM reFlash tutorial. I have questions tho...
Step 4: Gives me a prompt that says "Server Busy" "This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem."
I'm gonna stop running through the dark and hope someone can be my savior. A wing and a prayer.
What phone you got tmo,global EU?
I always assumed it was the global version. Bought it in the USA. Model LE2125
Host Machine is a Legion 7 16ACHg6.
Perhaps "New generation USB 3.0/3.1 ports may not allow the QPST tool to recognize your phone and could also cause problems during the flashing process."
Q1. Would there be a way to test and verify this possibility with my current machine? I am using the factory "red" usb-c cable.
Q2. How to verify no other drivers are causing issues simultaneously. (I went through quite a number of drivers before this)
Alas, my previous question regarding this "alternative MSM tutorial" and what the Server Busy means, should take precedence I think.
I am new to XDA and the android community and I truly love and thank you all. There is so much here and so much more opportunity. Thanks again.

Categories

Resources