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.
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
jbradshw said:
2125 AA model OPO9
So my phone has been nagging me to upgrade to A13 for awhile now and I decided to finally bite the bullet and do it, so I backed up everything before I did it.
Now previously, to keep Magisk, I was following the guide to restore the image, do the upgrade, then flash magisk in the inactive slot. But from reading it sounded like after I upgraded to A13, I needed to go into fastboot and boot off the magisk'ed boot image. So I restored the image in magisk and then upgraded to A17 and rebooted, then to A18 (as I had the A18 boot images) and rebooted. Everything came up fine. However, as soon as I boot into the bootloader, I see if for a split second and then it immediately crashes into the Qualcomm crash dump screen. I can still reboot into the OS but I'd really like to have Magisk back if possible.
Edit (More info): When I reboot, I do get a new notice on the pre-boot screen that the device is unlocked that I didn't see before when I was on A12. In addition, in the OS, the OEM unlock is greyed out (with bootloader unlocked) and will not let me lock it again.
My current state is a working phone on A17/F18 with no root but would like to get root back (and a working bootloader for peace of mind).
So I guess my questions are:
1) Is there still a way I can get Magisk in my current state. Without the bootloader I'm assuming I'm SOL...
2) Would a factory reset from within the OS fix the bootloader?
2) If I need to use the MSM tool, where can I find the qualcomm drivers? I found one link but it was a CAB file and I could not get anything working out of that.
Click to expand...
Click to collapse
Google for latest Qualcomm 9008 USB drivers
TheGhost1951 said:
Google for latest Qualcomm 9008 USB drivers
Click to expand...
Click to collapse
Is MSM my only option here then?
jbradshw said:
Is MSM my only option here then?
Click to expand...
Click to collapse
If you want a fresh start and try all over again with less hassle!