Database Develop

[STOCK] [H872] [11g] T-Mobile G6 Stock Collection

T-Mobile G6 H872 11G Stock Collection
Based on OEM 11g KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
SysBoot ROMs were test flashed over 11g and 20a bootloaders. 11h has not been tested.
11G Firmware is ARB01
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
​
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
TWRPLAF: Individual LAF image for replacing stock DL mode with TWRP
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
INSTRUCTIONS​
Make a FULL TWRP Backup using 3.2.3. Link to thread is below.
Boot to TWRP and do a Format Data to remove encryption from your device.
Reboot back to Recovery after Formatting in order for TWRP to mount System.
Advanced Wipe - System, Data, Cache and Dalvik
Flash your chosen Zip using TWRP
You must have TWRP on recovery to flash LAF images.
It is recommended that Sysboot Images be flashed AFTER Bootloader or FullStock
If you Flashed SysBoot with Patched Kernel and Root, you are good to go. Otherwise, flash Magisk to maintain root access.
Wipe Cache/Dalvik
Reboot to system.
Your phone may reboot once or twice during the initial boot to system. This is normal.
Your phone may hang a while on the boot logo. This is also normal. If hang persists for too long, hold vol-down+power until phone powers off to reboot.
DOWNLOADS
Stable v1.0
Project Files have been moved to SourceForge​
TWRP 3.2.3 for H872 by @Eliminator74 - Thank you for all the work you have done for the G6!
Magisk + Magisk Manager
Bootloader - md5:43dcc7f82c501147da6500efdd594d5c
SysBoot ROM - md5:2ac20008794eb74523a442da7b8bafdc
SysBoot Deodexed - md5:b92fcb7649bddf934ff9be0246c9fab6
SysBoot w/Patched Kernel + Magisk Root - md5:ae4bab194a69b2044f3aee69ba495464
FullStock ROM - md5:e919fe16852b5f0b830a48cda914003a
StockLAF - md5:ce70b36e4d293e183544a18409a526de
TWRPLAF - md5:f8ea4e93dc417d2d31f5cb8b77530bfa
These files are long overdue. I hope you all find them helpful. Please let me know if you run into any problems with them. Thanks!​
Other H872 Projects
H872 11H Stock Collection
H872 20A SysBoot ROMs (Stock and Rooted)
H872 20D Stock Collection
Announcement
I have officially moved to the V30 and no longer own the G6.
I will still be active in this community, but since I don't have the device any longer I will not be able to test any packages or issues that might arise.
All of my current projects have been tested. If anybody runs into problems, you can still let me know and I'll do my best to support my stock packages.
Thanks guys!
-weakNPCdotCom​
XDA:DevDB Information
[STOCK] h87211g, ROM for the T-Mobile LG G6
Contributors
weakNPCdotCom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.2.3
Based On: 11g KDZ
Version Information
Status: Beta
Current Stable Version: 1.0
Stable Release Date: 2018-09-30
Current Beta Version: 0.9
Beta Release Date: 2018-09-30
Created 2018-09-29
Last Updated 2018-10-19

Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?

DmytroPitenko said:
Thx))) I was very much waiting for this.
I'm now at 20a. if I flash the bootloader only, then the fingerprint scanner will work on custom firmwares? Does the custom LAF work?
Click to expand...
Click to collapse
very welcome. if you flash the bootloader only it will leave whatever laf you have untouched, and yes fingerprint scanner will work with custom ROMs like AOSP Extended.
However, I have not tested running stock 20a with the 11g bootloader. But it doesn't sound like that's what you are wanting to do
*edit*
if you have already flashed a custom Rom and FP doesn't work, simply flashing the 11g bootloader zip will fix it. it is not necessary to reflash the rom
also, not sure why anybody would want to, but 11g bootloader with stock 20a rom will not work. it will hang on the boot logo indefinitely which can be dangerous for your phone. so please make sure you are using a custom Rom or stock 11g with this bootloader

Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Sent from my XT1575 using Tapatalk

Ken C said:
Any way to flash one of these stock images. Rom itself. If you can't get into twrp? Check my post from last night in the root thread and you'll see what I'm on about.
Phone boots but system ui stops which keeps me from getting in. Lost twrp from recovery somehow. All I did was apply a then through substratum and it all went South from there.
Not hounding ya just thought I'd prefer over here and see what you been up to.
When I run step 1 in that root thread I get no hash match and something about with laf or lafbak not being present. Haven't fully fired up the pic too see if I can post the output from that here. (Honestly, was never that good with logs lol)
I'm curious though if flashing your laf (how in the heck it happened is beyond me) if it's possible through adb or lgup would put me back to right.
Click to expand...
Click to collapse
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file on your sdcard and rename it to laf.bin, and run these
adb shell
su
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/laf
dd if=/sdcard/laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf

weakNPCdotCom said:
Do you still have root? if so you can extract the laf.img file from the StockLAF zip and use adb shell to push it to the dev blocks
put the laf.img file in the folder with adb.exe, rename it to laf.bin, and run these
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/laf
adb shell dd if=laf.bin of=/dev/block/bootdevice/by-name/lafbak
that will restore stock laf
Click to expand...
Click to collapse
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk

Ken C said:
Have to have root eh? So I'd need dl mode back to flash the kdz to get root but can't unless the kdz restores laf in the process which if it did this wouldn't be required I'm thinking.
Sorry man just thinking through things.
When y'all are putting in " /by-name/ " it would be h-872 right? Stupid question I know but I've never seen it mentioned straight out anywhere
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak

weakNPCdotCom said:
Yeah you need to restore stock laf another way if you dont have root. Root is needed for ADB shell.
and no, /by-name/ is the actual folder name. I think it's a directory of symlinks, but i might be wrong. Basically it lets you access a partition or mount point by name. in this case the names of the mount points would be laf and lafbak
Click to expand...
Click to collapse
Ok. Figured it was something like that. Always meant to ask somebody, just never did
Sent from my XT1575 using Tapatalk

weakNPCdotCom said:
FILE BREAKDOWN
The following Zips DO NOT include stock LAF.
You must flash the provided LAF separately if you wish to go back to stock DL mode
[/CENTER]
Bootloader: 11g Stock Bootloader ONLY
SysBoot: 11g Boot and System ONLY (Modem, Bootloader not included). These zips are adb sideload compatible.
FullStock: Full 11g Firmware Installation
StockLAF: Individual LAF image for returning to stock DL mode
Magisk: You know. You must flash this after flashing any of the above packages if you want to stay rooted.
Click to expand...
Click to collapse
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).

ryanrod said:
Thank you for this weaknpc! This is really saving my a*s. Quick question. If I flash the FullStock version, will I have to unlock the bootloader again? I am using the AEX rom (have twrp 3.2.3 on laf and recovery I believe) and just want to go back to the full 11g firmware. If this works I wont even worry about flashing the laf partition (I would only do that for using LGUP+11g kdz).
Click to expand...
Click to collapse
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.

weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
Awesome. Yeah, I am going to give it a flash tomorrow morning. I do not think I will need the stock recovery at this time, but thanks for offering! I have been stuck with the whole twrp on LAF issue, not being able to use LGUP, and this just a godsend to get back to 11g. Thanks again! :good:

weakNPCdotCom said:
Glad I could help, man. No, none of these will lock your bootloader. They wont touch your recovery partition either. If for any reason you want to go back to stock recovery let me know, I can pack a zip to flash that from your LAF TWRP if you still have it.
Click to expand...
Click to collapse
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.

ryanrod said:
IT WORKED!!!! THANK YOU :good::good: This phone is finally fully useable for me again!
I also saw your post about moving to the V30. Will be investigating that phone at some point.. You rock my friend.
Click to expand...
Click to collapse
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.

If I were to downgrade if able to, would that have a chance? I still am getting stuck in fastboot mode unless I'm hooked up to the pic and let lgup do it's thing.
It detects the device, does it's thing, reboots it and gives me a factory reset phone back just no dl mode.
It's not bricked yet lol.
Sent from my XT1575 using Tapatalk

weakNPCdotCom said:
You are most welcome! But important FYI, I discovered an issue in the original FullStock zip that was causing the laf partition to be flashed over with stock. I am posting an update to the project with another handy file for people with TWRP on recovery. If you downloaded FullStock prior to this morning, you will probably want to reboot to recovery and flash it.
Flashing h87211g_TWRPLAF.zip from custom recovery will put TWRP back on your LAF partition.
Click to expand...
Click to collapse
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:

ryanrod said:
Ok, so the flash did not go exactly as planned, there was some issues getting into recovery. Let me give you a run down of what I did.
1. Boot into twrp recovery using a reboot app (requires root) from a working rom. (This is really the best way I can get into recovery besides using adb) 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the FullStock zip. 4. Flashed magisk and it was unsuccessful (it was not able to mount system or vendor partiton I believe).
I did not realize you need to reboot into recovery from twrp recovery, then flash magisk for it to work. I thought it may have flashed anyway. Needless to say I booted into the system and I had no magisk so no root. When trying to boot back into recovery using the hardware buttons, I could not get into recovery. It took me to the factory reset screen. Usually at this point if you select, yes factory reset the device, it would boot into twrp (I think this is some initial mask that lg puts on the recovery partition? ), but this time it was just a orbiting rainbow colored cicle animation. At this point I was saying "oh fu*#!". Then once that animation was over the phone began boot looping. I thought I bricked the phone at this point. Then I tried getting the phone into download mode by holding the volume up and inserting the usb cable. I got the download mode graphic, and then a second later, bam I was back into twrp! Lol. Crazy. I guess twrp was still on laf after flashing FullStock! So, I think that maybe your FullStock zip flashes the stock recovery partition and not the stock laf partition.
Now I was in twrp I was back in business. This time I did the steps correctly and magisk did flash, however I did not format data so now I was getting the encrypted data issue when booting into the system. Then on the third attempt I booted back into twrp using the download mode trick and this time I got it all right. 1. fully format data partition to clear encryption 2. wiped the system/data/cache/dalvik cache partitions. 3. Flashed the fullstock zip. 4. reboot into recovery using the option in twrp 5. Flashed magisk successfully. 6. Reboot into system 7. Phone booted fine, no encryption issue, magisk manager sees magisk is installed and I have root.
So this is where I am now. The phone works fine and I have root. I am afraid to flash that laf zip with twrp becuase if I am correct, there is some specific hash that has to match the device when twrp is on laf. There are steps regarding this for the root method for the H872. Maybe it works on your phone, but I don't want to assume it will work on mine. I would not like to brick this thing, lol. Maybe I don't know what I am talking about...
Also, everything on this rom works great except for bluetooth audio! For some reason bluetooth audio is super super low even at max volume. When I had 11g before, it wasn't like this so I don't know what the heck happened! Through the headphones you get a prompt asking if you want to raise the volume above the limit but nothing like that for bluetooth. Does anyone know how to fix this? (Btw, I thought magisk viper4adroid might solve the issue but it does not work for me with this rom. I tried it and it just crashed system ui after reboot, almost got in a bootloop from it. Luckily I was able to disable the module after another boot)
So, if I can't fix bluetooth volume, I will be running this for a while, then I will flash the stock laf to get real download mode back and do a full kdz flash using lgup so I am truly back to stock. Then I will follow the H872 root process from the ground up, etc.
Either way thanks for this npc. At least I am able to have 11g! Thanks for your hard work. :good:
Click to expand...
Click to collapse
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.

weakNPCdotCom said:
I'm sorry that you had a little trouble. It actually makes sense that you needed to format data. I will update the instructions to start things off with that step.
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm glad you still had TWRP on laf. Maybe I was looking at an old updater-script. I do know, however, that I removed the recovery flash from the rom so that never should have been replaced. What I think might have happened with you is the Stock firmware's recovery repair feature. Since Magisk didnt flash correctly and you booted to OS, it would have tried to repair stock recovery.
As for the TWRP LAF zip, it is an exact image of the LAF partition after it was processed by @runningnak3d's root procedure. So there shouldnt be any checksum issues at all. It should be totally safe.
The bluetooth thing is probably the most puzzling to me. I extracted all of the images in these roms directly from the stock KDZ. Your system should be a mirror image of any device flashed with LGUP.
Try flashing the SysBoot ROM on top of what you have now. The file structure in that rom is different. Instead of extracting a system image to your system block (the way fullstock does) it actually flashes all of the individual system directories to their designated blocks. I have a feeling that it may fix your issue.
Thank you very much for the information. If you end up doing anything else let me know how it turns out. If I can help you not have to flash the KDZ then I'll be happy. That was my main goal in creating these packages.
Click to expand...
Click to collapse
Ahh yes this makes sense. Maybe it was a stock recovery repair due to magisk failure as you mentioned? I still don't understand why with these LG phones (ever since the G3 I think), when you boot into recovery using the hardware buttons, it asks if you want to factory reset the device. Then if you say yes, it doesn't reset/format anything, and it boots right into twrp recovery after that. So weird. I can boot directly into recovery just fine from a reboot app or adb from a running system without getting that factory reset screen...
I'm sure your laf zip with twrp works for the reasons you mention. Luckily I don't have to find out since my laf partition is fine and still has twrp!
Regarding bluetooth, I will give the sysboot flash a try and update you with the results. First I want to wait until my backup phone is running again. I bent the sim pins on the backup phone due to those ****ty plastic adapters that catch the pins (an old E980 w/ the larger sim size) so I ordered another sim reader to fix that. I also read in some forums that wiping cache and dalvik cache resolved others bluetooth issues with the G6. I will try that too.
Either way, I will update soon. I am happy to share my notes as I really appreciate the help!

@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk

Ken C said:
@weakNPCdotCom
The actual, proper procedure, would be to format data, reboot back to recovery, wipe system, data, dalvik and cache and then flash FullStock and Magisk.
I'm rooted and running an old version of aex. I'm still getting the encryption message anytime I try anything without that rom. These last two posts. When you talk about formatting your saying in twrp correct? Or that forced format you can do with the buttons?
Basic point is I'd like to get rid of that encryption message and it looks like your instructions take place after we achieve root. I'm wondering if I should just kdz to 11g and root from there. Or would just flashing your full stock zip do it? I seem to be the only one having such an issue with it so I'm figuring I'm missing something somewhere that y'all are doing or whatever that's getting by me.
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.

weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
weakNPCdotCom said:
What Encryption message are you talking about? The one in TWRP where it asks you for a Passcode?
So far, I have tried removing dm-verity and force-encryption from both the 11h and 20a kernels, but I have not been successful. The OS always ends up encrypting data. However, after I flash Magisk I no longer get any passcode prompts in TWRP. I am able to backup and restore system and data no problem.
The only thing I have not tried is a rom packed with dm-verity and force-encrypt removed and root built in. That is the next thing on my list once I get a deodexed 11h rom done.
Click to expand...
Click to collapse
Yes that's the message I get. So your saying not to worry about it for the moment? I only see it regularly on a stock rom when going into recovery not aex.
I just wanted to make sure. With the mess I been going through.
So, I can flash this stock build you have and if I wanted normal download back flash the laf zip and I'll have DL mode on laf, twrp on recovery and everything should Mount correctly and all that?
And if I go to flash something custom FP will work? I know I'm a pain I just want to "know" my setup isn't weird somehow. Probably over thinking it, but I think I'm good, except that when I rooted I was getting that message off & on, on the stock build of 20a. I'm hoping that running this build I can get that worked out. Maybe that deal is a 20a thing? Reading through the root thread it seemed to happen less to people on a lower numbered build and it would stop after the format.
I can make backups Burt I've yet to try to restore one.
Sent from my LG-H872 using Tapatalk

Mi 8 soft brick

Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro

You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2

tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due

ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.

tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem

ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot

ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.

tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again

Is it possible that this is part of the problem..!
I can't check it
@tsongming

ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img

ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.

tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?

ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..

For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.

[GUIDE] Back to stock ROM howto / Downgrade howto

There maybe a number of reasons to go back to the stock ROM. We do not discuss them here
But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.
The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.
The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.
Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.
Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
Start (reboot) phone into fastboot mode
From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
Here it is. Enjoy (or sell your Realme X2 with its shiny stock experience...
If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.
2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post

I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).

So this method works if you brick your phone trying to install a global rom to china variant..

Hi,
does only works with SDcard insert.
Because the internal storage is decrypted.
And it does not work on X2.
But why?
Installation failed?

This method will bring back my FP working again right?

Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/

SkyeJace said:
This method will bring back my FP working again right?
Click to expand...
Click to collapse
You have to lock bootloader for this. See the very last part of the howto, post #1

AldRezaine said:
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
Click to expand...
Click to collapse
The site provides generalized instructions for everything
As for Realme X2, there are two methods claimed, one is for ozip file, another for ofp file; last one is not yet publicly available somewhere (the link is replaced by the Coming soon promise).
If you find there something certain regarding ozip procedure for Realme X2, give me the link, please. I couldn't

why I back to stock rom, apps i uninstalled it is don't auto reinstall?

hello guys, how can i get the 1993ex stock recovery? i screwd up big time !

hammerheading said:
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
Click to expand...
Click to collapse
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it

BaDuc said:
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
Click to expand...
Click to collapse
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.

yakovpol said:
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
Click to expand...
Click to collapse
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).

yakovpol said:
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
Click to expand...
Click to collapse
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?

hammerheading said:
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
Click to expand...
Click to collapse
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.

BaDuc said:
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
Click to expand...
Click to collapse
Those I have are uploaded to here.

yakovpol said:
Those I have are uploaded to here.
Click to expand...
Click to collapse
thanks you very much

yakovpol said:
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
Click to expand...
Click to collapse
Thank you so much, that did the trick!! i was able to flash the a17 and the phone is working fine now . But i'm not trully satisfied, i can't find a away to flash a GSI rom successfully, but that's another topic ... Thank you again and keep up the good work !

can u plsss provide stock recovery for realme x2 rmx1992, i bricked my phone trying to install stock os since 2 days, cant find a way..if some has the recovery pls provide it. im able to boot to twrp, bootloader is unloced and with the other recoveries im not able to intsall the stock rom.pls help.

Can send me 1992 stcok recovery file ozip please.

corrupt to the core

heya people! my razer 2 is screwed. I had trinity kernel originally, and i saw arter's was updated to april and trinity was march so i flashed arter's, someone else did it with no issue.
K so i flash arter, go to system, reboot, someone in tg group told me arter is sketchy and known to brick phones, so i wanted to go back to trinity, before tho, someone said i should clean flash my stock, so i tried. The thing is, the file comes from razer, and is a flash_all.bat the only problem was i couldnt use fastboot, so after talking to them i tried to just flash the boot.img to boot slot in twrp. Big mistake. Twrp no longer is a thing, fastboot doesnt work, cant go into download mode, when i boot up my phone it tells me my phone is corrupted and may not function, after that it takes me to default android recovery screen.
if i hit apply via adb, i get sys errors and **** and according to nfs group, my partition is completely corrupted (device not found) or something like that
so i called a repair place and explained it to him and he said hed have to look at it, so im gonna probably have to drive down there for him to tell me its screwed.
I tried applying via sd card, but when i insert the sdcard to my pc and try to write files, it says its write protected, and i dont see anything in properties about making it r/w so im really at a loss.
Is there ANYTHING i can do or am i gonna have to pray that this guy knows something?
dont thikn i can send to razer since i broke my warranty unlocking bootloader and rooting.
anything would help guys, i dont wanna have to go back to my razer 1 ;_;

ok well i didnt get any replies so i took it to a repair place, he said his tech guy wasnt in but he'd call me with updates as to whats happening. Shouldnt cost more than $75 so thats great.
if you have any ideas on what could be wrong id love to hear, maybe i can learn from my mistakes and be able to recover next time.

I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).

LSS4181 said:
I'm not sure about the comments in the telegram group, but I don't think it was necessary to flash all the stock stuffs. Factory images may contain stuffs that you should never flash on a device that has already left factory and packaged. Usually you should only be flashing boot, system and vendor (plus userdata, if you want to wipe existing data as well). You may also consider flashing modem, dsp, bluetooth if baseband/firmware update on certain parts are needed.
Recovery is now part of the kernel image, so flashing stock kernel means you have stock recovery. Stock recovery is only useful if you accidentally issued Factory Reset from system, or pressed "Wipe user data" from bootloader (which happened when I was preparing the device for unlock/rooting for the first time), and got into an endless loop after that (since TWRP may not properly handle /misc stuffs).
Again, **NEVER** use Factory Reset from system, or Wipe user data from bootloader, if you use TWRP. Always wipe data from TWRP if you intend to do so.
At one point (r13) arter97's kernel had some issues which is supposed to have been fixed in r14. I haven't updated my kernel yet since last Trinity nightly (it's working great even after flashing MR3 vendor stuffs).
Click to expand...
Click to collapse
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.

hadtosignuptoreply said:
hmm, im not understanding how flashing stock boot.img to boot partition would make recovery part of the kernel image? boot.img is the literal only thing i got to flash in twrp before it just died.
Like i said fastboot didnt work, and oddly enough, it doesnt work on my old razer 1 either, i tried rooting it the other day and it wont go to fastboot
Edit: according to an admin in magnetar group, dm-verity could be the reason, and he said i should've flashed something called "lazy flasher" after flashing the boot img. Never heard of it and never used it.
Click to expand...
Click to collapse
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.

vnb
LSS4181 said:
Recovery is built into the kernel (which is common for recent devices). arter97 (or Trinity) kernel image includes TWRP in place of the stock recovery, so you get TWRP when you flashed the kernel. Stock boot.img comes with stock recovery, so if you flash stock kernel you lose TWRP.
Also, keep track of your reboot count and your current active slot. If your system fails to boot multiple times in a row, the bootloader may consider it damaged and switching to another slot (which usually contains the previous version of system/vendor/modem etc.) and may cause some issues if you're unlocked (or you were previously on a GSI).
As for fastboot issues, I once had a time that I could only conduct flash commands within a very tiny time window right after the phone booted to bootloader, although the problem has been lessened after reboot and I could now flash properly again. It's unknown when the problem would resurface that I'd need another reboot (given the distro I use, Manjaro, is constantly updating, I'd just update the system and reboot anyway if that happens).
Some fastboot versions may be buggy, or maybe USB interactions under Linux can be problematic in general (especially in handling plugs and unplugs). This is more apparent if a system is running constantly for a long time and a lot of devices has been properly (or improperly) plugged or unplugged over the course of its uptime. Maybe it's better if one conducts fastboot using rear USB ports (as front USB ports tend to have less voltage).
I never bothered with dm-verity and hardly ever had problems with it.
Click to expand...
Click to collapse
ah ok. Well the repair guy called and said they didnt know what was wrong or how to fix it, i know i can at least get to bootloader, and to root my razer 1 again, i went to bootloader and fastboot worked. Before work tomorrow im gonna get that phone from the place and hope that i can flash what i need to get it working again. Assuming it will actually be able to read the device. Thanks for your input

Question NV data corrupted each time I install LineageOS 20 via TWRP

I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!

Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.

newboihere said:
I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!
Click to expand...
Click to collapse
I was able to boot other GSIs as well.
but I'm using the evo x custom rom published on the telegram group.
There are plenty of smarter people out there than me, so I encourage you to take a look there too.

kousuke5555 said:
Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.
Click to expand...
Click to collapse
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)

newboihere said:
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)
Click to expand...
Click to collapse
I don't know what your situation is.
It seems that it can be solved by flashing the firmware with sp flash tool using the auth bypass tool.
Isn't gpt table a scatter file in the firmware? I think you can get it by extracting the .tgz.
If you use the sp flash tool, be sure to select "Download Only Mode". Do not choose anything else.
There seems to be an error in "combo_partsize_check" when flashing with miui13rom. Please rewrite the corresponding part in the scatter file to false with Notepad etc.
There seems to be a tool that makes bypassing and flashing easier, such as "act unlock tool", so use whatever you like.
If the situation cannot be resolved with sp tool
I can't solve it with my knowledge level.