Develop Bugs

[Q]Damage/Flaws

1st [Q] Did someone experienced bricking m2?
2nd [Q] Do you have a white spot on your m2? (not a dead pixel)

2nd: no visible issues

I!??!?! why!?!?!?!??!

Caelestiel said:
1st [Q] Did someone experienced bricking m2?
Click to expand...
Click to collapse
Depends on the definition of "brick".
As explained in this thread, I had a situation where the main ROM would not boot; it would just be stuck at the Mediapad M2 boot logo. However, I was still able to access recovery and fastboot modes. So I was able to recover from the brick situation by flashing the BOOT.img, DATA.img and SYSTEM.img from an 801L on my 802L ( I had not yet found an official 802L ROM). Even though my phone model became "801L", it still worked for me. Later, after much hunting around I found an official 802L ROM (B003), flashed it on my phone and got back to a standard stock phone configuration.
In another situation, I had a constant boot-loop problem after installing SuperSU 2.79 as the root app on Marshmallow ROM build B207. The phone would boot up, show the "Mediapad M2" boot logo, then reboot immediately. This kept on happening. However, like before I was still able to access recovery and fastboot modes so I was able to repair the situation in the same manner as described above. That is why I finally wrote this guide - to help other people who may be in the same situation.

[Solved] Was updating to Lineage OS 17 but now I'm stuck on stock Android 8

I have the G710EMW variant. As the title states, I was trying to install Lineage OS following sirbow2's thread 'Lineage OS 16/17/GSI Install Guide for LG G7 ULM'. Using the universal unlock method, I unlocked my phone. Next step was installing 21d ULM firmware; this is where I am stuck. When I begin the installation using LGUP, the phone boots into the rooted fastboot mode instead of the download mode. I even tried switching slots but it still boots up in fastboot mode.
Also, when I am able to load the download mode, it stays at the download mode screen & doesn't actually proceed further & neither is the device detected in device manager when it is connected in the download mode.
I've rooted quite a few phones in the past but this one has troubled me a lot. It is very difficult to find time for all this when you're working a full-time job. Please help me fix this. I'm happy even just to return to the stock LG ROM (which reminds me that the same thing happens when I try using the LG Bridge tool).
Thank you!

use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.

sinkoo1979 said:
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
Click to expand...
Click to collapse
Already tried that method. Everything works fine until the phone boots to start installation. Ideally it should start in download mode but in my case, it boots into the rooted bootloader.

@Awesomeslayerg was kind enough to message me this link (https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841) which helped me fix my problem.
Not only was I able to revert to stock; I went ahead to install LineageOS 17 which is amazing!
Thank you, Awesomeslayerg.
This thread can be marked as fixed now.

Unable to boot phone once TWRP installed?

Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.

KiwiNote+ said:
Hey guys,
So I've been trying for days to get a custom Ron installed on N975F.
Right now I'm on completely reflashed stock Rom. With stock recovery et al. No root.
I am able to flash Magisk with Odin. No trouble. And my phone continues as usual without issue.
However, once I install TWRP, no matter where or how I install it, once I restart my phone it will boot past the warnings without issue, then go to the screen that just says "SAMSUNG" and the phone will never actually boot up.
I can still boot into TWRP recovery without issue, but system itself will never boot, it will just sit on the "SAMSUNG" screen forever.
In fact, it seems like as long as TWRP is installed to recovery, my system will never boot with any Rom. It can be fixed by reinstalling stock recovery, or by reflashing stock in it's entirety (which I have now done before I try again).
Has anyone got any ideas why this might be occurring or how I can address it? I saw some threads about 'rollback protection' but it seems like that is for people who are not even able to boot into TWRP, or get stuck on the first "Samsung Note 10+", screen rather than the system booting "SAMSUNG" screen.
Click to expand...
Click to collapse
i am guessing try ADB commands see this link! https://www.koskila.net/how-to-use-twrp-to-flash-an-android-device-that-refuses-to-boot-to-twrp/

Many N975 users have reported this issue and I have forwarded concerned to ian as well. What I believe is formatting on latest (last few) twrp causing issue.
If you have N975/N976 then, visit xda My rom thread - Download area - you will find a folder "for stock rom & bootlooped device" download instructions and follow it, I have wrote guide with or without flashing my rom
Edit :
here is direct link, you will find all required file
https://www.mediafire.com/#0urfw8g1gx630
This guide is stop solution to root/root with twrp/fix Samsung roll back bootloop everything. And yes you don't needs to patch anything yourself, all files available are ready to use

Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.

KiwiNote+ said:
Hi Dr Ketan,
Thanks for the response.
I actually solved the issue simply by using the version of TWRP and following the install instructions on your basic "How to Root and Install TWRP" for Note 10+ guide.
So I think this is a problem relating to Ian's latest TWRP. TWRP linked from your thread
is working fine (but leads to issue with Camera in GSI/Lineage OS ROMs).
I will have a look at your special guide relating to Samsung logo/rollback stuff and see if it will allow me to install latest TWRP from Ian and bypass these issues! Thank you.
Click to expand...
Click to collapse
Yes, As I said issue is related to newer TWRP only. If you use old TWRP, camera will not work. My above link guide is for latest base and you can get latest TWRP only (Included package are having latest available TWRP & Kernel)

OP3 bricked and now won't boot after MSM

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

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