Database Develop

Searching V405EBW owners for TWRP/ROM tests

Hello everyone
Some might know me from the V30... Also got my hands on a V40 now (which I will also give my best to develop for).
I'm currently searching for people who are capable AND willing to test different things.
With that I mean:
- You know how to take logs (logcat, dmesg)
- You know how to recover from a soft brick (either how to get into TWRP for example, or in really bad cases fastboot or flashing a kdz)
- You know how to follow orders
I currently have a (somewhat decendly) working TWRP build (cant decrypt stock encryption atm).
GSIs are a complicated thing, because of not only vbmeta but also because of our 8.1 vendor (Pie GSIs work, if you remove some sepolicies from their system, Oreo GSIs dont have that issue)
What I would need more people to test for:
- stock decryption
- trying out different ways when something (doesnt) boot (e.g. need to flash magisk for xy to not crash to fastboot)
and so on
After everything is somewhat stable (I had to reflash a kdz today, as somehow nothing, no twrp in either slot, or restored stock rom didnt wanna render anything anymore, even though usb/adb worked just fine)
Also working on LOS for this device btw (but thats far more work in progress)
If you wanna be part of this upbringing, reply here, and I'll message you via PM the details.
PS: Having Telegram would be very beneficial.

I volunteer for this. Happy to see you step up for our forgotten device.

How did you reflash the KDZ?

I`m also interested in testing.

onslaught86 said:
How did you reflash the KDZ?
Click to expand...
Click to collapse
In my case i used LG Bridge, at first it complained that MTP wasnt running, but after clicking a few times ok it was fine with that lol
but i read in another thread that a lgup_cmd is able to flash kdzs to the v40

I think I can participate in the test, I have a V405US ROOT phone。
Please forgive me for my bad English. :）

In +1

Hi, how you rooted LG V40?

Any movement on this?

Evilmonstertruck said:
Any movement on this?
Click to expand...
Click to collapse
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.

SGCMarkus said:
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
Click to expand...
Click to collapse
Any update is a good update. I appreciate all the work your doing. I know it's not easy. Thanks again

I can test out twrp and or ROM! Best regards.

Device won't be detected on QFIL/QPST, No ESN/No Phone

So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Edit : Anyone has an idea to fix this? NO PHONE / NO ESL on QPST

The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
The War Profiteer said:
So, to modify the modem of dipper in order to get VoWi-Fi on my phone, I probably need to have the aceess to 9008 DIAG port. When I enable the diag port from ADB shell, it only enables 901D which won't work with QFIL or QPST. Are there anybody succeded with this?
EDL enables 9008, but QPST or QFIL still won't let me to backup or modify since it's on the download mode.
@tsongming I believe you are experienced with this procedure, so I guess I want to tag you.
Click to expand...
Click to collapse
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Edit: If you are hard bricked and can not enter EDL, you will need to buy the EDL cable from Amazon they are cheap, like $5 or if the phone is seen from ADB you can get to EDL ( 9008) with this command : adb reboot edl

tsongming said:
I have seen this issue a few years ago and off the top of my head I don't remember. But there is a solution, and I am pretty sure that I made notes about it, give me a few minutes and I will look for it, and will be back soon.
---------- Post added at 12:31 AM ---------- Previous post was at 12:12 AM ----------
Okay, at first I thought that you are bricked and that you could not get into EDL. But after re-reading your post. I see that you are not, You are wanting to open bands using QPST. While, I have read that this possible, as far as I know you need a proprietary a proprietary tool that is very expensive.
This link describes the steps and has a broken link to an old version of the tool and a link to a current version which is very pricy
https://forum.xda-developers.com/le-pro3/help/unlocking-bands-t3565979
I have more info on this, and when I find it, I will come back and add more. I remember an article on a Miui website that had instructions step by step, so I am looking for that too. I have never personally never attempted opening bands. However, I have read stories of success and failure when attempting to do it, so it may be risky. Nonetheless, I think you are well aware of that, and I am interested to see if it can be done.
Click to expand...
Click to collapse
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?

The War Profiteer said:
Thanks for your help. I'm not trying to unlock bands, I need to merge a few files into the phone using the QPST in order to get it working, so I need to get into 9008 without having to use download mode. ?
Click to expand...
Click to collapse
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
@The War Profiteer
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Just choose the reboot to EDL option

tsongming said:
I edited the last post; EDL is port 9008 : you can get there with : adb reboot edl or worst case scenario : https://www.amazon.com/Flash-Cable-...coding=UTF8&psc=1&refRID=7ZR98PJHRW9BJE5SQXV3 Cheaper ones exist on Amazon
You can also enter EDL with this TWRP : https://drive.google.com/open?id=1eOnz-NzHkLc_UNCeD_ecE6C3sCXhwU-U
Click to expand...
Click to collapse
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.

The War Profiteer said:
I see. Some people were able to backup or modify the firmware on 901D mode apparently, but I'm unable to do that. It says No Phone/No ESN on QPST program, and QFIL will say that no phone found on that port. Do you have any idea how can I achieve this? I've been trying many drivers to be able to do it, all of them has failed.
Click to expand...
Click to collapse
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.

tsongming said:
You can use software tools such as this : https://forum.hovatek.com/thread-22384.html
This guy claims to have had some luck : https://forum.xda-developers.com/showpost.php?p=76921725&postcount=23 with his Note 5 Pro. I am not sure if it will work on newer phones with, newer SDK's especially with the massive amount of security changes in the past 6 months.
Click to expand...
Click to collapse
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone ?

The War Profiteer said:
Thanks a lot. I'm starting to think that I'm having this issue because of I'm on a custom rom. Does MIUI EU roms require wiping the data when migrating from other Custom roms? If so, I'll probably stop messing with it since I have 90 gb of data on my phone
Click to expand...
Click to collapse
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.

tsongming said:
The last time that I installed EU beta rom, I definitely had to format storage and of course the same for the Stable build.
However, there is usually no issues when switching from one custom Miui to another, sometimes all I do is wipe cache, install the new Rom, ( FYI : temporary remove root prior to switching to avoid bootloops) and usually there are no issues at all. After installing the new Rom, I check for Google updates, clean out any remaining files with SD Maid, then Root the phone. To be clear, in this example, I am talking about using Miui Pro to Mi-Globe or to Ros Miui etc.
Again, I usually will always have to wipe storage when using the beta EU builds, which is why I usually stick with Mi-Globe when using Miui. On the other hand, for a long while I was using a version of TWRP that could not decrypt data. So it possible that I would have the issue with the TWRP that I linked above.
Currently my data is unencrypted and although I really like the recent Havoc Rom that I have been using for several days, I am wanting to checkout the very latest Stable Miui build ( and manually debloat it)
I will see if I can keep my data without wiping and come back her and let you know if I have an issue. ( I keep all of my most commonly used files on a Flash drive, so it doesn't take very long to restore its no where near the amount of data that you have. Plus, one thing that is great about Mi Cloud is how it restores practically everything.
@The War Profiteer
Okay, I just installed the latest stable, its updating now and I was able to confirm that all of my data is still here. ( Nice!) Which also confirms that the last time when I had an issue and had to format user data it was mostly likely because of the version of TWRP that I was using at the time.
So it seems if you want to install Miui Stable or Miui EU, your data should remain in tact as long as you are using a TWRP that can decrypt data or you do not have your data encrypted.
Click to expand...
Click to collapse
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?

The War Profiteer said:
I'm using Pixel Experience. I'm sure switching between MIUI based roms are not an issue, but I'm afraid of AOSP to MIUI. ?
Click to expand...
Click to collapse
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.

tsongming said:
I was on Havoc, and went to Miui stable, I wrote that in my post above.
All of my data is still here. Photos, Music, Texts etc.
@The War Profiteer
The confusion maybe came from my original statement then I came back and edited the post.
So there my original was due to TWRP.
Apparently no issue going from AOSP to MIUI... Using the version of TWRP that works with encryption.
Click to expand...
Click to collapse
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.

The War Profiteer said:
That's awesome. Since I am creating backups of all of my apps, it feels safe to migrate temporarily. Still I will have NANDroid backups before I do. Thanks for the info.
Click to expand...
Click to collapse
Anytime brother, you have definitely helped me before as well

A heads up: It works on stock miui while not working on pixel experience. Please write on this thread if anyone gets it working on any other custom roms.
Edit: Apparently custom roms don't have the required tools to use the software, only stock roms will let you to modify your efs.

tsongming said:
Anytime brother, you have definitely helped me before as well
Click to expand...
Click to collapse
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".

The War Profiteer said:
Hi, if you still are on MIUI, can I have a screenshot of your /sys/devices/virtual/android_usb/android0 ? I think the required USB drivers for the communication between QPST and Phone should be in this folder, which are non-existent on a custom rom. I am expecting a folder named "f_diag".
Click to expand...
Click to collapse
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.

tsongming said:
Sure, I am using Miui Pro at the moment. Here is the screen shot.
Unfortunately, no f_diag here. But I will look for it.
@The War Profiteer
This page has some information that may be helpful, there is also a video.
http://www.99mediasector.com/how-to-enable-qualcomm-diagnostic-mode-diag-port/
It's possible that the f_diag is hidden until its enabled.
According to the linked page : The DIAG PORT Code For Xiaomi Qualcomm : #*#717717#*#* or alternately *#*#13491#*#*
I hope this helps.
Click to expand...
Click to collapse
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.

The War Profiteer said:
Thank you for the information.
The issue here is while diag port can be enabled on any custom rom using the setprop command, and will be detected by host, I believe the interface that allows the communication of the host and device does not exist on custom roms. I thought that the f_diag folder's content would be the interface and that's why I asked for a screenshot.
I am guessing that custom roms won't support modified modem/efs to get custom files for WFC and ViLTE. So to fix this, I've tried to replace priv-app content of the Pixel Experience with the ones from MIUI, and didn't succeed.
For now, I'm trying to find out which files in OS are responsible for WFC (ViLTE is not that important) and the interface of MIUI or any other stock roms that allows you to communicate with diag port.
UPDATE: It appears that diag port has something to do with the kernel, I'm still looking into it. It's possible that the communication between the host and the device may need an interface that is supported by kernel, still unsure about it. Needs more investigation. Unfortunately most of the people asking for "How to open it", but nobody asks "How does it work and communicate"", which makes it difficult to find the information I need.
Click to expand...
Click to collapse
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.

tsongming said:
I have a couple of friends who have developed Miui Roms for years, and they definitely know Miui inside and out. I haven't spoken to them for a while, but I will message both of them and ask if they can come here and help.
Click to expand...
Click to collapse
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.

The War Profiteer said:
Thanks a lot!
So I'll summarize the issue:
- The goal: My priority is to be able to use VoWiFi with the modified EFS, which works flawlessly MIUI but not on other ROMs. I'm suspecting that the ROM files aren't able to read EFS to provide VoWiFi or they don't exist at all, which means VoWiFi isn't supported by the ROM. Wanna fix this.
- Diag port seems to be communicating on MIUI while doesn't on custom roms. The reason to work with this port is to be able to edit EFS while custom rom is installed, since I'm creating an EFS backup on Miui and reflasshing it on the desired ROM.
Click to expand...
Click to collapse
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.

phonexpert_alex said:
Just to clarify things a bit (my own experience):
-on my phone I have full working VoWIFI (at least on my second SIM) on Vodafone Germany.
-I'm using PE as a ROM
-it worked with both Sphinx and Canting Kernels
-VoLTE and VoWIFI are both Carrier dependant
-in order to get VoWIFI working, I just activated the option in the settings. It just worked ootb.
And I must say sorry, because I am not able to test other ROMs/kernels. I need a stable phone as a daily driver. I'm using my phone for work stuff too, because I don't want to have to carry two phones around.
Click to expand...
Click to collapse
Thank you for additional info, surely will help a lot to my search. I'm using PE CAF too (sadly, CAF will be cancelled).
First of all, I thought PE wasn't compatible with WFC, but your statement has confirmed that it's working, so the problem is on my side.
The problems I'm guessing that could be about ROMs and/or kernels are:
1- They may be unable to recognize/read/process a modified EFS and they may be reading only modem. I've merged the proprietary files for enabling VoWiFi, which were officially extracted from a SDM845 device that is officially supported by carrier, to the EFS using QPST. It was supposed to work on MIUI, and it did when I tested it. I created a backup of EFS and did a clean install of PE CAF, restored EFS from the backup and it didn't work. I also tested the backup with a clean MIUI setup and it did work, so I don't think there is an issue about the backup or restoration process since I used the same TWRP version.
2- Diagnostics port will be enabled with "# setprop sys.usb.config diag,adb" command, but since the kernel or the ROM doesn't have the interface to establish the communication between the host and the device, I was unable to check or edit the EFS partition if everything is OK.
I'm here to look for suggestions at the moment. Modifying modem image may be dangerous since it can be signed by the manufacturers in order to prevent any modification, which can lead to an unrecoverable bricks, and I don't know what to modify and how to do it.
Thanks, again. Pardon me if I did any grammar mistakes which will lead to misunderstandings or will make the post completely unintelligible.

[HD1925]PSA: WARNING: Unlocking the bootloader or doing fastboot -w will KILL OTA!

ntzrmtthihu777 said:
The OnePlus 7t Pro 5g McLaren (at least the one from T-Mobile; I don't know about other versions) has a crucial issue
in how it handles factory resets/wiping userdata, and OTA updates.
The stock rom contains a file, `/data/reserver/reserve.img`, which is an ext4 image mounted at `/system/reserve/`.
It contains a number of OnePlus specific APKs and is not particularly required for a functioning phone (though I
believe it may have stuff which is preventing my fingerprint from working, but that is speculation), but this image
is updated by standard OTA updates. As there is no way to read this image without a rooted device, and there is
currently no way to root your device without unlocking your bootloader (which would nuke userdata), any 'master
reset' (as described here) or `fastboot -w` or `fastboot erase userdata` will kill your ability to take OTA updates.
[edit start]
Apparently the tmo method will not kill it. Only the unlocking bootloader or wiping via fastboot should.
[edit end]
The OTA updates given out are what are called `delta` updates, which are a record of changes to filesystems and
not whole filesystems in and of themselves. As such, any change to the expected filesystem images (system, vendor,
this reserve image, etc) will kill your ability to take OTA updates.
If you're having issues OTA updating, you can check if this is your problem by checking if this file still exists
(`adb shell ls /data/reserve/` should return reserve.img) or by grepping your logcat during update attempts,
checking for sha256 hash errors on the 'reserve' partition.
Click to expand...
Click to collapse
TL;DR: don't unlock or erase userdata on this image, or you'll never get another update until OnePlus fixes this.
https://forums.oneplus.com/threads/t-mobile-7t-pro-5g-usa-ota-10-0-19hd61cb.1172725/
https://www.reddit.com/r/tmobile/comments/eq4or6/security_disclosure_master_reset_procedure_on/

I sadly can confirm this. :crying:

Yes this is what it looks like. See attached.

Oh wow. Isn't that just lovely.

Can some one confirm it on hd1913 model?

sagiag said:
Can some one confirm it on hd1913 model?
Click to expand...
Click to collapse
No, I think you're good on those, as there is a full software package on the oneplus site you can use to restore.
the HD1925 models do not, so we're screwed until something gets fixed/figured out.

Thank you very much!

Finally,, I know why I can't update. Thanks.
Will TMobile tech fix this if you send them your phone?

La_anvil said:
Finally,, I know why I can't update. Thanks.
Will TMobile tech fix this if you send them your phone?
Click to expand...
Click to collapse
No idea personally. Someone has mentioned something to that effect in the telegram
chat.

Hopefully this means a MSM tool coming out faster. I'm tired of not being able to update at all.

CloseCoder said:
Hopefully this means a MSM tool coming out faster. I'm tired of not being able to update at all.
Click to expand...
Click to collapse
Hope so. honestly its just a case of bad design on OnePlus's part. What's the first thing the help desk going to tell
you to do if your phone isn't working? Exactly, wipe /data. And now no updates for you.

Just read on OnePlus forums someone called tmobile and their solution was to send out a new phone....

ntzrmtthihu777;8152337 Someone has mentioned something to that effect in the telegram
chat.[/QUOTE said:
What channel?
Click to expand...
Click to collapse

Android Police picked up the story:
https://twitter.com/AndroidPolice/status/1218982470822924289
https://www.androidpolice.com/2020/...laren-breaks-your-ability-to-install-updates/

T-Mobile get your act together and fix it! ??

ntzrmtthihu777 said:
Hope so. honestly its just a case of bad design on OnePlus's part. What's the first thing the help desk going to tell
you to do if your phone isn't working? Exactly, wipe /data. And now no updates for you.
Click to expand...
Click to collapse
Pretty sure that's on TMO not oneplus

For those who have a problem with OTA, what build number do you show on your phone ?

justthefacts said:
For those who have a problem with OTA, what build number do you show on your phone ?
Click to expand...
Click to collapse
10.0.16.HD61CB for me.

benny3 said:
Pretty sure that's on TMO not oneplus
Click to expand...
Click to collapse
Nah. its a bit of both. OnePlus was stupid for putting 'reserve.img' inside userdata,
but T-Mobile is even stupider for not implementing the fix non-TMO OnePlus
devices use, which is to switch to full OTA updates.

[[GUIDE]] Flashing Custom GSI ROM to LG G8 (LG820UMx)

This might be completely unnecessary (mods feel free to remove if it is), but I see a LOT of misinformation regarding GSI ROMs and the G8. So. Here's a guide/FAQ for those wondering if/what is possible:
***I'M NOT RESPONSIBLE IF YOU BRICK YOUR PHONE, LOSE YOUR DATA, OR OTHERWISE DAMAGE YOUR DEVICE. IF YOU CHOOSE TO FOLLOW THIS GUIDE, THE FATE OF YOUR DEVICE IS IN YOUR HANDS, NOT MINE, NOT YOUR MOTHER'S, NOT ANYONE OTHER THAN YOUR OWN***
Prerequisites (yes, these are all NECESSARY. If you don't know how to unlock your bootloader or use fastboot, there are other guides here. Go find one.)
Unlocked bootloader (and the V50 engineering abl files as well as stock, plenty of guides here with download links)
QFIL/QPST
Basic Fastboot, ADB knowledge
BACKUP. I mean ALL YOUR DATA kinda backup. This WILL wipe your phone, do NOT come crying to me if you lose the last picture of your favorite sock. Not my fault.
GSI for Treble device (ab)
GApps (optional, but recommended)
Instructions to Flash via Fastboot
WIPE YOUR PHONE
Yeah, completely factory reset that sucker. Doesn't matter if it's through recovery, settings, or adb, just bite the bullet and restore factory settings. You can technicially flash without doing this first, but you'll still have to wipe it before any flashed ROM will run. Sorry.
Boot to EDL (NOT download, your screen should be black, dev manager should show QD Loader 9008 COMx)
Use QFIL to flash engineering abl file to both a and b slots - yes, all this work just for fastboot.
Reboot to fastboot!
I just unplug my phone, use power + vol- to shut phone off and then reconnect while holding vol-, but you do you.
In case you don't remember, your touch screen WILL NOT WORK during this time, even if you fully boot to system! Completely fine and normal, means you're on the right track!
Fastboot Devices should yield "LG850UM", also good!
Open cmd prompt from platform_tools, copy path to desired GSI while you're in there
Run these commands line-by-line:
fastboot format system
fastboot flash system *Path_To_GSI.img*
This is where I usually repeat the 2 commands and attempt reboot while I still have fastboot, whether or not it changes anything I have no idea, but it's never given me problems so why fix it if it ain't broke?
fastboot flash abl_a abl_STOCK.bin
fastboot flash abl_b abl_STOCK.bin
fastboot reboot
Ta-Da! Your shiny new ROM should be up and running. Use TWRP or any kernel manager (I like SmartPak) to flash TWRP, GApps, blah blah blah.
FAQ/Troubleshooting
Touchscreen still not working? Go back to EDL and load the stock abl bin files through QFIL, then reboot as normal.
You will likely be asked to input a password upon successful reboot, just enter your PIN/password, whatever you used to unlock your phone pre-flash
The cool things like QuadDAC and LG-specific tweaks will probably not work. Weigh your options before flashing.
Magisk comes pre-installed with most GSI's, just follow the prompts and you'll be just fine.
Don't want GApps? Just sideload desired apk's via ADB, or use the browser to search for them.
Can't I just use TWRP and make this whole process a lot simpler? Yep. But some of us don't have working TWRP or prefer using fastboot commands. This is for those people, don't hate.
Which ROMs work?? Not sure, haven't tried them all. Currently running HavocOS found in Treble GSI forum on here.
Help! I broke my phone! No, you probably didn't. It's advisable that you know how to emergency restore via LGUP prior to starting this process though. Please be specific as to what part of this "broke" your phone and why exactly your phone is "broken" if you're going to ask for help- "bricked device" has never helped anyone.
Rebooting is your best friend in this process, especially during the first boot. If anything starts to hang up or act funny, just give the phone a minute to catch its breath and, worst case, turn it off and back on again
As previously stated, this is probably pointless, but given all I see on the G8 forum is "no custom ROM" or "why bother trying to *insert idea here*", I figured it might help some folks out. I'm sure I left a few things out, feel free to correct or provide input as necessary.

Works on LM-G820QM5?, I have bootloader unlocked

Elihu_GmG said:
Works on LM-G820QM5?, I have bootloader unlocked
Click to expand...
Click to collapse
Yep, it's basically the unlocking/root process only you're formatting/flashing the "system" partition instead of "boot_a/b"

Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).

AsItLies said:
Great info, thnx for the write up. But what about the totc.cfg file? My understanding is no G8 is going to boot if there's a mis-match between that file and the hardware indication of what variant the phone is?
Sorry if my understanding is misguided, new to the G8 (and all it's idiosyncrasies).
Click to expand...
Click to collapse
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.

SirOlive said:
In this case there is no tot file, no recovery, laf, or the like. GSI's are generic system images that are capable of being flashed to most Treble-Enabled Androids from Oreo on up. You do lose some of the device specific things (hence, generic), but they're a great alternative if you're like us and stuck with next to no custom anything built for your device. There's a whole forum for them on here, I highly suggest checking it out- it's a pretty awesome option to have.
Click to expand...
Click to collapse
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers

AsItLies said:
Great, thnx, sorry for being a jerk but, this does work on a G8? Tested and proven? I ask because it's my understanding that without a match between the hardware encoded variant of the device and what's in the totc file, it won't boot.
you say there is no totc? then how does the hardware encoding get verified? See, that's why there are no custom roms. LG did this to keep people from crossflashing and it killed rom development.
Hey, if I'm wrong, feel free to point that out. But as far as I've discovered so far, a GSI doesn't get a free pass to bypass this mess LG has created with this mis-match hw / totc file.
cheers
Click to expand...
Click to collapse
Sorry for being short, but a simple Google search would back up everything I've written. I wouldn't have written this up if it didn't work, or if it was just a theory... I wouldn't have said that my Verizon G8 is running Havoc if it didn't work. I was able to flash with zero problems. With the Treble Project, Google has mandated that Android devices boxed with 11+ (possibly 10?) be capable of not only recognizing, but running GSIs as to assist developers in testing apps and builds in varying versions of Android as quickly, easily, and simply as possible. This means that not only can one download and flash Android releases downloaded directly from Google, but devs can use the source code to create versions of their ROMs that will apply to a wide array of models that would never have seen development otherwise. Because these are "generic" images and are based upon system architecture type alone- not a particular make/model- there are sometimes things overlooked. For instance, in our case, the audio processing and LG's camera software are not present. These are decently made up for by the presence of flashable mods, though, and the phone remains fully functional, Google Play Certified (if desired), and as reliable as the ROM you choose to flash.
Basically, Google>LG. LG wants to use the Android platform, they must abide by Google's rules. They need not go into great detail, nor allow their devices to be changed to something fundamentally non-LG, nor divulge any potentially propitiatory subject matter (once again, "generic"), but they must allow the device to be open to a certain level of customization as designated by Google.
Is it ideal? Not if you're lucky enough to have ROMs tailored for your specific phone. But for those left behind- like the G8- it's a fantastic workaround that does, in fact, work. As I'm sure you're still skeptical, I will add screenshots tomorrow to prove the validity of this seemingly ludicrous claim. In the meantime, please do some research on the topic- or better yet, give it a shot- there's gotta be a guide around here somewhere.

It works

Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.

hooutoo said:
Of [email protected]*$king course it works. I’ve flashed it to my sprint v50 (v450pm). Had the same QuadDac problem though. Couldn’t get a sound out of it. I mean no sound of any kind. Also couldn’t get it to activate on Google Fi. Will be watching to see if someone solves the Sound problem. We could just skip on past A11.
Click to expand...
Click to collapse
Where did you get V50 engineering abl files as well as stock?, I just want to make sure to get the correct files

Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.

hooutoo said:
Guide LG G8/G8x/v50 Bootloader Unlock and Magisk Root using Firehose
Disclaimer: I am not responsible for any problems from using this guide. Works for G8, G8s, G8x, and v50 Confirmed working on G8 and v50 Requirements: Android 10 QFIL...
forum.xda-developers.com
There's no such thing, afak, of a v50 Eng abl. Read the header on the thread! If you don't have one of those phone models, don't! All of this seems to be predicated on the g8x eng abl which is the DL on that thread. READ that thread closely. I did, BL unlock and then flash A12 GSI.
Click to expand...
Click to collapse
Ok,ok

Hello, I followed your instructions as written but when I reboot my phone I am stuck at a boot logo cycle, but my comment doesnt have to do with that, I want to ask if maybe you know what could've gone wrong.
I also own a g8 from verizon, I do have bootloader unlock, and tried to install Havoc OS, I wanted to mention this in case it is useful

Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.

hooutoo said:
Dude, I have no knowledge of G8, per se. My main goal was to get away from Sprint software on my v450pm. These phones are a little touchy. I do know that if you have a proven RESTORE method then you can mess around.. If you're Qfil_ing your phone you MUST have a backup of EVERY damn partition. I trashed my ftm partition and it was bad. Use telegram group for very good info. I have yet to be able to logon to Google Fi, an mnvo of Tmob. I've crossflashed to Eu A11, no go. I'm about to try some other roms, but again a backup will be needed.
Remember, you gotta have a way out or you're gonna pay $14 bucks to a Russian.
Click to expand...
Click to collapse
Yeah, I know, like I said in my previous comment my phone got stuck in a boot loop, I fix it just by loading system_a partition in qfil, so I am gonna give it another shot and see if it works, already backed up every partition just in case anything goes wrong

If you're goona play around, this is secondary bs. My real phone is a FLIP3 and I'm not allowed to play unlesss to make/awnswer call.

Does somebody tried tp flash GSI with LineAge (A11) or Arrow(A12) vendor to g8?
I`m interesting about dt2w .. I flashed GSI`s to my G820UM on the past (A10 stock vendor) and it have no dt2w.. ((

i ended zeroing my imei from sprint G8 but thats okay i dont care for it much but what i do care is getting some LOS 17.1 on the sprint G8

where do we have any links to these so called GSI images?

blaze2051 said:
where do we have any links to these so called GSI images?
Click to expand...
Click to collapse
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
From what I remember when I tested multiple Android 11 GSIs such as Pixel Experience, I couldn't get vibration to work on my G8.

Question (Q) GSI images

Have never needed to install a GSI before but as we're kind of stuck here without a single custom ROM, I thought I'd have a look.
AFAIK installing one of these would still leave the door open for stock recovery to be used should something go wrong, so as long as you've made a back up it should be fine.
I'm just curious as to the method of installation?
Has anyone had any experience with GSI ROMs before.
How was it? Did it work?
Would DSU image loader be an option?
I've attached what treble version we have and the relevant info required from the treble info app.
Apparently we have VNDK compatibility, not sure what that is but we have it.

Hi @dladz, I ran into a similar question three years ago when I bought a Xiaomi Mi 8 Pro. I was so used to using custom ROMs that I didn't even check before I bought it whether any custom ROMs would be available.
I was honestly shocked to see that that wasn't the case - there was absolutely NOTHING available - and that I had ended up with a device that couldn't even be unlocked right away, you had to wait and open a Mi account to be allowed to unlock it. I couldn't believe it at the time, I had come from a OnePlus X and had helped others root and install custom ROMs on other OnePlus phones without any problems, so I felt like I had just thrown quite some money out the window to run around with a mobile Chinese Spyware gadget I didn't want to use.
That was the first time I ever came across the term GSI ROM and it took me several weeks to figure out how to flash a ROM that I could also use afterwards. I knew I wouldn't want to have a stock ROM by a company that has very loose data privacy standards and even clearly states they collect your data (Lesson learned, I thought, I just had to buy a "proper" phone again and no more phones from budget manufacturers).
Several weeks later, after I had finally managed to get a custom GSI ROM working on my device I posted a lengthy how-to here on XDA.
Again, it took me weeks to get everything to work that I could not go without. And even then, I had to resign to the fact that many features of the phone would not be working (The fingerprint sensor, for example. Also, the Xiaomi Mi stock rom apparently had excellent GPS support (dual GPS support) but GPS positioning is just alright on the GSI ROM I'm using, also there were many cool Xiaomi apps like a compass app that wouldn't work outside MIUI). But I was more than happy I had gotten different GSI ROMs to work in the end and settled on one that I could live with, knowing my phone wouldn't be sending data to some Chinese servers constantly.
Now that the Mi 8 Pro has become a bit slower over time with all the latest apps, I took the plunge and spent a ton of money on the OnePlus 10 Pro 256 GB version only to be disappointed again, but this time by a company that used to be the epitome of openness when it came to custom development.
I got my OnePlus 10 Pro on release in my region in April, together with the 50W wireless charger and both have been sitting here since April, I'm not touching that phone until I can remove all the Spyware it comes installed with. At this stage, I'm not yet willing to go through the weeklong trial-and-error again that it took to get the Mi 8 Pro running a custom GSI ROM (also considering that some of its features never worked...), but if OnePlus doesn't get its **** together soon with the MSM tool and some openness towards developers, I will seriously just consider selling it on eBay again (It is brandnew after all) and will never buy another phone from OnePlus again. This has been an extreme disappointment and I'm still struggling to understand why they wouldn't support custom development any more. I had checked the OnePlus 9 Pro threads on XDA just to see if there's still custom development going on for OnePlus and it seemed everything was still OK, but now... .
On a more positive note: The Mi 8 Pro did eventually get some custom ROM love and there are now several ROMS to choose from, so to answer your original question - If you ask me, don't bother with GSI ROMs until we can be sure there won't be any custom ROMs for our phone. I'm still hoping that will be the case.

Gsi will work but no fingerprint or faceunlock.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"

MrScarl3t said:
Gsi will work but no fingerprint or faceunlock. And many more visual glitches.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
Click to expand...
Click to collapse

Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro

MrScarl3t said:
Gsi will work but no fingerprint or faceunlock.
Click to expand...
Click to collapse
Unless someone posts a step-by-step guide with screenshots of a successful flash, I wouldn't believe anything.
This sounds more like it:
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .

yo-less said:
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
Click to expand...
Click to collapse
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k

Twiggy000b said:
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Click to expand...
Click to collapse
Did you try sending it in?

I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.

nah i reached out and oneplus never got back to me.

sorry to hear that :/

Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
What phone was you on mate??

MrScarl3t said:
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
Click to expand...
Click to collapse
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.

dladz said:
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
Click to expand...
Click to collapse
Yeah camera is gcam but the main sensor is fine with it.
Every OnePlus 10 pro works with gsi, and general boot images as well. I will start tomorrow making the guide.
Will test if you can use rollback zip to get back to stock

Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/

MrScarl3t said:
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
Click to expand...
Click to collapse
Legend