So to use this, you will need to be bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled this is a must!!(its always good to make a nandroid before making any changes on your phone). What this will do is more or less provision your Lg G8x to your Desired Carrier, it will also let you change your apns, so you have volte working and also the data indicator will change to match the carrier. WIfi calling is working on tmobile, will need someone to test other carriers.
There seems to be confusion , this is only for the Stock rom. this will do nothing for GSI roms.
Instructions:
1.Extract to Content of zip to Sdcard
2.Make a copy/backup of your own files: Go to twrp and backup your product partition and your op configs in case you need to restore them
3.Copy and paste the files from my zip to:
/product/op/config
and this single file cust.prop to /product/op
make sure permissions are 644.
4.Reboot your device it should now be provisioned to your Desired Carrier.
Click to expand...
Click to collapse
Download
Sprint Untested
SPR-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
T-Mobile
Tmo-VOLTE-VOWIFI-FIx-G8x
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
VZW Untested
VZW-VOLTE-FIX
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
Credits:
vl48 this guy is awesome, and also very patient an expert in lg devices.
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
e20140 said:
Can you write a guide for ATT LG G8X (LMG850UM) on
How to bootloader unlocked, magisk rooted, and twrp installed, DM Verity Disabled? It's confusing which method is valid and which files to use.
Click to expand...
Click to collapse
There is one already made, you just need the correct twrp from telegram
siulmagic said:
There is one already made, you just need the correct twrp from telegram
Click to expand...
Click to collapse
Why not post on xda? Is everyone switching to telegram? I've read everything on xda and don't see a specific method to unlock bootloader+twrp+DM but a few failed attempts on ATT version of the G8X. I only see working solution for India, Europe, and Sprint Models. You are the only one that has successfully unlock it. I am sure more people will need help as 3G is going away and we need Volte working on this phone.
well the basic gist of it is:
This will WIpe Your Phone, make sure to backup first.
Cant post the recovery zip, but pm il send it to you. i will move this to a proper thread later today. and better formatted
1.install qpst/qualcom driver or use windows update ones
2. download firehose uncompress it somewere on your pc
3.download g8x twrp and magisk 20.4 zip also the dm verity zip
also make sure to grab the eng abl for the g8x(eng bootloader that will allow us to unlock).
4. enable oem unlock in developer settings
5. boot phone into edl mode
6.start qpst set storage type to ufs, slect built type, make sure it is flat build
7.Look for select programer then click browse, here you will chose the firehose file
8. click select port on qfil then double click 9008 com port were the phone is detected in edl mode
9.now in qfil select tools then partition manager
10. when the list of partitions show up look for abl_a,abl_b,modem a/b, and modemst1 and 2, you will right click each of them and click manage partition data then read data, this will back them up to your computer(be very careful you can wipe your whole phone if you click in the wrong place)
11.after you back up everything select load img and flash abl_a to Abl_a and abl_b. after this unplug phone and boot into bootloader mode.
To boot into bootloader mode turn off your phone and hold volm down and plug in your usb cable, this should boot it into bootloader mode .
12. if you see text that says you active boot slot, you now have successfully flashed the eng bootloader witch will allow you to unlock the bootloader.
13. now while the phone is pluged into your computer you will open a adb window and type fastboot oem unlock , the phone will ask you to agree to unlock the bootloader, select yes.
14.after this reboot your phone into edl mode, reflash your backup abl_a to abl_a and abl_b, this will restore stock bootloader you wont have fastboot anymore but no worries, also you can flash your stock rooted boot.img to boot_a and boot_b.
15. After you reboot into android, install magisk manager, flash the g8x twrp zip and without reboot, also flash magisk 20.04 zip, if you do not do it this way you will break your boot.img and have issues, like freezing system.
16 now reboot to recovery wipe data then reboot and flash the dm verity disabler to disable encryption. after this create a nandroid backup, then just reboot back to system and enjoy.
17. profit
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
e20140 said:
Nice
I need to return my G8X since it has the latest 20g firmware. If anyone wants me to try or test something, please let me know before it's going back.
Click to expand...
Click to collapse
why 0o with gpst and firehose you can root bl unlock any att g8x, unless there something im not aware of?
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
e20140 said:
I post the short error log here. The firehose we got can't read the partitions correctly. Maybe the mappings are different, IDK? If you want to read the full log, let me know.
Click to expand...
Click to collapse
thats a driver error, you need to let windows install the driver from windows update or like i did use qpst on windows 7. i never got that erro fixed, so i just used windows 7 on a old laptop i have, and it works mint.
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
e20140 said:
I don't have Window 7 to try but tried on other Win 10 PCs and Laptops, just no luck. I can use QPST to flash flat built on my G6 fine, really don't think it's driver issue.
Click to expand...
Click to collapse
well thats the error i got, with my g8 and g8x on windows 10.
wangsu10 suggested the error could be installation selection option for the QCOMM driver. Need to be install as 2nd option " ETHERNET-DHCP". I already returned mine
Maybe you can try it on your Win10 and report back. If it works, we need to have it added to the OP for all others to see.
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
nate0 said:
Thank you for sharing this. I have a sprint model that ended up with T-mobile provisioning after I boot loader unlocked it. The only issue I think I have at least the obvious is google messages will never verify and setup rcs. I suspect this will be permanent eventually as they begin to roll out their other layer of security for verifying that which would basically black list bootloader unlocked or rooted devices...will your files/instructions aid in any issues with RCS currently before before Google makes the final rollout?
Click to expand...
Click to collapse
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
siulmagic said:
Thats an easy fix search for carrier services on play store , update it and see if chat features get enabled, I got rcs working just fine on att g8x bl unlocked and rooted ofc.
Click to expand...
Click to collapse
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
@siulmagic where is the twrp image for the g8x? Did they pull it down?
nate0 said:
@siulmagic where is the twrp image for the g8x? Did they pull it down?
Click to expand...
Click to collapse
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
nate0 said:
Yeah I did this, and by default it was already installed. Still no luck. I tried clearing data while on airplane mode everything. Nothing works yet.
Click to expand...
Click to collapse
there is another app that needs updated i forgot witch one it was.
siulmagic said:
the one here never worked properlly, if you want a working one join telegram and i can send it to you,.
Click to expand...
Click to collapse
Newbie to Telegram, how does one find the group please?
mangojain said:
Newbie to Telegram, how does one find the group please?
Click to expand...
Click to collapse
LG Mobiles India š®š³
Political Discussion, Obscene material/words, Selling, Fraudulent link posting will lead to Ban SHARING COPYRIGHT CONTENT & PIRACY NOT ALLOWED, it leads to REPORT & BLOCK Photography Group: @lgg8xphotography OT Group: @LG_G8X_OffTopic
t.me
Related
OFFICIAL ONEPLUS 2 STOCK RESETā
SOURCE : OnePlus L2 Support Team
VERSION : OxygenOS 2.2.0
DOWNLOADS
1. OnePlus2 Stock Reset Oxygen OS 2.2.0 Google Drive | Mediafire
2. Qualcomm Drivers Version 1.00.11 Google Drive | Mediafire
INSTRUCTIONS
You are doing this on your own responsibility. I take no responsibility whatsoever.
(THIS WILL WIPE YOUR ONEPLUS INCLUDING INTERNAL SD)
Download both the files from above and extract them (WinRAR, WinZIP, 7ZIP etc). You should have 2 folders: "OnePlus2_14_A.11_151211" and "qc"
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
3. First click the right square Chinese button. This will perform an integrity check on the downloaded files by verifying the MD5 hash values.
4. The system will seem to hang for a bit but should give you a pop up with the results of the above verification. When everything is ok. Press the start button. and let the progress finish. (If something is not ok, you will have to re-download the images. Google Drive can help extract only the necessary files.)
5. When it's done. Disconnect the USB cable and turn on the device.
C. Reset TAMPER Flag (Optional)
(This may potentially change your SmartPhone to a rather large paperweight and I will just laugh at you bearing no responsibility)
+ This part of the guide is not an Official Procedure and is in no way affiliated to OnePlus
+ It is advisable to do this before any of the above mentioned operations.
+ Prerequisites:
Root
HEX Editor with root features
Root File Manager
+ BEWARE: You are modifying partitions which cannot be restored regardless of what you flash. You have been warned AGAIN
1. In File Manager browse to the devinfo partition (dev/block/bootdevice/by-name/)
2. Open devinfo using the HEX Editor.
3. Modify the TamperBit (attached screenshot) from 01 to 00.
4. Save and reboot to fastboot.
5. Type fastboot oem device-info to confirm.
CREDITS
OnePlus Team for the Files.
@paultje162 for adaptation of Instructions. Refer his thread here if you are looking for an older version of stock reset (2.1.1).
@thedropdead for his work on Tamper Reset
If this thread has helped you, do press the THANKS button. Should you have issues, questions or doubts, write in this thread.
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Edit:- file confirmed legit ! Totally official, way to go, @fareed_xtreme !
[emailĀ protected] said:
Just need to confirm that these files are actually official
Pm me the s3 support link
---------- Post added at 13:14 ---------- Previous post was at 13:10 ----------
And my friend
You need to install the test certificate first !
Click to expand...
Click to collapse
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
fareed_xtreme said:
Thanks for spotting the error. I have fixed the heading. S3 Link PMed.
Click to expand...
Click to collapse
Whenever you get drivers like this, dig into their folders and you'll find important documents and instructions to use
That is how I found out about this certificate
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
xbit said:
Is there any similar process por ONEPLUS ONE?
I only have fastboot mode, without recovery and bootloader locked (fastboot oem unlock doesn't work)
Click to expand...
Click to collapse
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
beaverhead said:
http://forum.xda-developers.com/showthread.php?t=2970390
@xbit
Click to expand...
Click to collapse
This didn't work for me:
fastboot oem unlock didn't work because I had a corrupt bootloader.
Spannaa said:
Quick search and: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
But this was great! My OPO is alive now. Thanks
Thank you!!!! this worked.
I was eventually able to get the restore program to recognize it and restore it so it could boot normally. Thank you!
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Wagi99 said:
Download from your Link
https://drive.google.com/folderview?id=0BxFd4Zc3_d1CWDdOSFFIVG42VTg&usp=sharing
the File:
OnePlus2_14_A.11_151211.rar
Extract it.
But where is the "QC Folder"
found only "OnePlus2_14_A.11_151211"
Your Link to:
http://forum.xda-developers.com/show...1&postcount=46
is wrong. (Not complete) Error 404
Click to expand...
Click to collapse
Thanks for spotting the errors. I have updated them. It is indeed a miss on my part in regards to the QC. Hence I have uploaded it separately and updated the instructions.
Spannaa said:
Yep, the qc folder is missing from the zip.
The link should be: http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46
I suspect these are both down to copying & pasting the instructions from @paultje162's thread and I'm sure @fareed_xtreme will sort it out when he gets the chance.
Click to expand...
Click to collapse
Yup, A copy paste is not the right way to copy a link. Haven't been around these threads for quite some time and guess i did not remember that the links are trimmed down. Thanks for the correct link.
Updated Information with UnTamper Guide
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
albertocastillo2001 said:
Hello
Doing the anti tamper method you did. Shouldn't this be easier by doing "fastboot oem lock" ?
I think it should have the same effects. Of course, this command must be done when an official ROM is on the phone, doing this in a custom ROM can cause unexpected behaviour, including bricking.
Click to expand...
Click to collapse
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
fareed_xtreme said:
From my personal experience, if the Tamper Flag trips, then no matter how official you go it will not go back to Device Tamper= False.
The files in my First Post restores your phone back to an out of box phone state even locking the bootloader but it will not change the tamper flag. Those files are used by OnePlus Support to fix OS issues. Also the fastboot oem lock has not managed for me personally to get the tamper flag back to default (Same as in OPO once down, its down). So the only way for now for the OPT is by modifying the bit that handles the tamper flag.
You are right. Tamper Flag usually trips when you try to relock the bootloader when having root and other non-stock partitions (custom kernel, recovery etc). (Learned the hard way with my old OnePlus 2. Got it swapped for a new one though as the old one was faulty )
Hope this helps.
Click to expand...
Click to collapse
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
albertocastillo2001 said:
Thanks for your reply. I noticed that these are the files that OnePlus team sends you when they want to remote into your device to flash the system. I noticed these are password encrypted. I have a session with them on Monday 6th.
I sent the files they sent me to decryption to get the password to a website that does this. However, they couldn't. My other plan was just to catch the password when having the remote session with them.
Since you already posted the files here, this is no longer needed. Seems you did this earlier than me.
The reason they want to do a full flash on my phone is due to the fact that I have a dual SIM issue. At the beginning both SIMs worked until I had to do a change on the second SIM network (it's an international SIM card that works in every country so you must set up the network manually). Since I tried to change the network. Something got messed up and now only one SIM works at a time. I tried restoring the network settings to automatic with no go. And I also tried to do hard restore on the phone to start over to ensure this would solve the issue.
This didn't solve the issue. So it probably means the settings were done in a partition which is not "/data". So a hard reset obviously wouldn't work. But a full flash surely will.
I asked them if I could do this myself by just sending me the files. I have a good expertise on fastboot, ADB and Linux, and I also understand the partition list and partition images. However, since the phone is not rooted or modified in anyway. I decided I will let them do it for me.
I do have a question thought. How did you find about the anti tamper thing? I assume you had remote session with them, and this is why you have those files. Did they "relock" this for you?
I assume they look at this when they get defective devices returned.
Thanks
Click to expand...
Click to collapse
Please note that the Tamper part of the guide is NOT done by OnePlus. Please note that OnePlus is in no way affiliated to the Tamper part of the guide. The Tamper guide is a result of comprehensive research conducted by thedropdead (information provided in the First Post). The guide is an easier interpretation of all the research that went in there.
OnePlus will only reflash this package which will re-lock the Bootloader only. Tamper Flag is not modified. So sit tight and let them reflash it for you.
You are right to assume I had a session with them earlier and that's how i have the files.
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
albertocastillo2001 said:
Thanks for your reply.
I would say that if the remote support doesn't untamper the device then it might mean they don't even look at it if the device is returned.
Thanks!
Click to expand...
Click to collapse
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
fareed_xtreme said:
Remote Support didn't look into mine. However, not very sure about whether it is checked on returning it. Mine went untampered.
Click to expand...
Click to collapse
Oh, then what happened? I thought the remote support tried to fix your phone. Since you said they didn't untamper the device after I expected they remoted to your phone. What happened then?
Thanks
FOR MOTO G7 PLUS ONLY!!!
Hello, everyone.
I created a .bat file "executable " For those who want to flash the stock rom on your Moto G7 Plus.
Just put it in the stock Rom folder along with the fastboot files and run the file.
For those who want the file, just download it by the following link or download the file that is on the thread.
http://www.mediafire.com/file/q836uaerr17pn0f/Flash_ROM_G7%252B.zip/file
Could you share where to get the Stock ROM fein?
---------- Post added at 11:13 PM ---------- Previous post was at 10:25 PM ----------
Tried the same sequence with a Stock ROM last week, but didn't achieve to get back to original ROM. I always get the prompt in the initial boot, that a different OS is installed than the original. This has the consequence that I cannot upgrade wit OTA anymore. And there is an upgrade already available (Jan security patch)
moto g7 G7........
any one have a flash rom.bat stock rom for moto g7.......
Which stock rom did you flash on your Moto g7 plus?
Where can I find the stock rom?
Nes.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Didn't you just find it yesterday on the telegram group?
What was the problem that you asked again here today?
Latest Stock ROM RETAIL at that link is the one we have all been using.
You'll need to download it to a computer, unzip it in a folder with the fastboot/ADB files, then fastboot flash it with phone attached in bootloader mode.
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your last firmware.
"Your device has loaded a different operating system."
baikal0912 said:
You have a model of the XT1965-3 smartphone and region of the software is reteu? Then this your ā¦ .
Click to expand...
Click to collapse
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
NesNol said:
Thank you very much!
I guess that the software channel was reteu.
A second moto g7 phone I bought - and is unmodified - says "software channel: reteu".
The information on the package of my phone says XT1965-3.
I flashed this image already, the result is a 'working' system except for the message at the start "Your device has loaded a different operating system." .
Click to expand...
Click to collapse
This will get rid of that message we all got too:
[Bootlogo] Modded Bootlogo from unlocked bootloader
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Dahenjo said:
This will get rid of that message we all got too:
The new RETEU stock version was just updated in last few days, before that not available and you could have used the RETAIL channel that I mentioned above, it worked fine for several users on RETEU channel.
Click to expand...
Click to collapse
Get rid of the message?
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Thanks!
NesNol said:
Get rid of the message?
Click to expand...
Click to collapse
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
Does that also mean that OTAs will work? That banking apps will not complain about the integrity of the system?
Click to expand...
Click to collapse
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
ā¦
ā¦
Click to expand...
Click to collapse
Hi,
thank you very much for your elaborate answer!
I will come back on it soon.
Nes
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
After unlocking bootloader there is some message like this on starting device, keep in mind we all got these too and everything is fine but we like to cover it up with a different bootlogo, just looks better that is its only purpose. This message is because you also upgraded the firmware, meaning it's not really a different OS but only a different version of your correct OS.
For G7 Plus we are not getting the OTAs properly after unlocking or rooting, I was originally rooted on PPW29.98-28 and repeatedly got the notifications of upgrading to 29.98-66-2 but it kept failing, the only way to stop it was freezing the Moto Update Process using Titanium Backup. So my only remaining option to upgrade was to fastboot flash the full firmware, as you just did, it wipes your data but gets you to the same place.
With future updates we may be able to capture them and then a dev can make them into a TWRP flashable zip with no wiping of internal data. We had that on G5 Plus which was a nice thing and they are still doing that. But until that might happen the best we can do is the same for now - when your channel has an update just get it from lolinet (these are all official stock firmwares there) and fastboot flash after backing up your data.
Usually it is more from the rooting (if you did that too) that may mess up your banking or other apps, but in Magisk there are settings that may work on that, you'll just have to try and see but there are mixed results. My choice is to not use banking apps on my devices anyway even if not unlocked or rooted, I just do it from home on a computer that I won't forget and leave out in public somewhere. :crying:
Click to expand...
Click to collapse
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
ā¦
ā¦
ā¦
ā¦
Click to expand...
Click to collapse
I have replied to this messages twice.
None has arrived?!
Nes
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
Dahenjo said:
Yes, you said: except for the message at the start "Your device has loaded a different operating system."
ā¦
ā¦
ā¦
ā¦
Click to expand...
Click to collapse
I have replied to this message twice.
None has arrived?!
Nes
NesNol said:
So you expect that in future my phone will be OK again? And receive OTAs while having Magisk installed.
I tried indeed to Magisk my phone, as I did with my old OnePlus One.
Which leads to TWRP, but then I discovered that the recovery has disappeared on this Moto!?
Then I was lost, and read about A/B and treble(?).
Concerning the banking applications: Even if I handle the banking transactions on my Mac, I still need the banking app on my phone for authentication.
Which is also true for accessing my medical data (GP, hospitals, etc), insurance companies, taxes, etc.
Last question: Is there a full description of how to magisk my phone?
Click to expand...
Click to collapse
Sorry not to reply yet, I sometimes have other things going on besides my phone. Also I thought I gave you a good answer on the situation, based on what I know as just another user (not a dev, not with Moto).
Yes, there have been changes since your last phone, it was the same for me. So it's good to find out as much as possible before deciding to unlock & root again, because the results may not be like before. We used to unlock and flash TWRP directly but we can't do that now or maybe brick the phone. It is always the risk when choosing not to remain fully stock/locked/etc as when you bought it, and with that is a responsibility to do the research first and not just expect other users to tell you every step.
So I don't know if things will change, but for now we can't get OTAs anymore after unlocking. For me I didn't mind and I am willing to upgrade manually if that let's me work with the device the way I like with root & using custom ROMs etc. I didn't plan to ever go back to how I bought it and don't need banking apps or other types that rooting might mess up. For others that may not be the case so they must learn the situation then decide for themselves.
As for installing Magisk, now we have TWRP working enough to just put the Magisk zip on your SD card and install it in TWRP. Before we had a functional TWRP we had another method by installing Magisk Manager and using it to patch the boot.img then fastboot flash that, but it's not needed anymore since TWRP, just do it the old way now.
Flashing the roms from lolinet, in my case ( RETEU[/URL) is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Woif said:
Flashing the roms from lolinet, in my case RETEU is a complete reset of the phone, I assume.
To flash, these steps should be right:
Copying the firmware to sdcard.
Boot in TWRP
Flashing the lolinet firmware.
Delete Dalvik Cache.
Should TWRP and Magisk be reinstalled immedeately after this procedure? Or renew the developer mode, reinstall twrp and magisk?
Click to expand...
Click to collapse
It won't work to flash full firmware in TWRP, so far the only way is using fastboot with phone connected to a computer in bootloader (unlocked) mode. Unzip firmware into your fastboot/ADB folder and also the batch file available in this thread, then run the batch file.
Yes this will reset/wipe your phone (except for SD) so backup your data first, and it will be like when you first bought it. You can reinstall TWRP and then Magisk, but boot to system first and set things up including enabling USB debugging setting in developer options again.
I am going to try and update now as the notifications are much too annoying.
Moto G7 Plus - lake Stock rom / firmware download here
NesNol said:
Where can I find the stock rom?
Nes.
Click to expand...
Click to collapse
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
XT1965-2 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-2-stock-rom/
XT1965-3 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-3-stock-rom/
XT1965-4 > https://boycracked.com/2019/02/11/official-motorola-moto-g7-plus-xt1965-4-stock-rom/
XT1965-6 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-6-lake_retcn-stock-rom/
XT1965-9 > https://boycracked.com/2019/07/26/official-motorola-moto-g7-plus-xt1965-9-lake-stock-rom/
XT1965-T > https://boycracked.com/2019/07/26/o...-g7-plus-xt1965-t-lake-us-t-mobile-stock-rom/
Remove the line
'fastboot erase userdata'
from the flashROM.bat file and it won't factory reset. It will act like an upgrade.
Sent from my Moto Z (2) using XDA Labs
vickbuitenzorg said:
Moto G7 Plus - lake
Download the Moto G7 Plus - lake stock firmware according to the Country/region/retail/carrier for example US Retail > T-Mobile, Verizon or Amazon, and everything is flashed through fastboot mode
Click to expand...
Click to collapse
Can I use a different retail code than current stock? My phone is XT1965-2, PPW29.98-28, RETLA. The system reminders are all in Spanish. Could I update to PPW29.98-66, EEGB (UK English) without a problem?
Also, if this is possible, could I update by removing the 'fastboot erase userdata' line from the BAT file, or, due to the language change, would I need to leave that line and do a factory reset?
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
I got it to fastboot mode, but there's no boot image for 11.0.0 available, right? Please help
Is it T-Mobile version or unlocked?
There's MSM tool for T-Mobile version and you can download full ROM for unlocked
If yours is unlocked and you can access recovery, use sideload
Code:
adb sideload
Press spacebar once and drag and drop the ROM onto command window and press enter
This can fix boot as well as making version update
bouyakasha said:
I bricked my phone by flashing a patched boot image from 11.0.2 to a phone with 11.0.0 and I can't get to fastboot mode - etc. I think MSM is my only way back?
Click to expand...
Click to collapse
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
amboyscout said:
I have no idea how to send it, but I have a boot.img from my factory unlocked N200 (Model DE2117) on firmware Oxygen OS 11.0.0.0.DE17AA. I also have a magisk patched copy of that boot.img. Let me know how to send it and you can give it a shot.
Click to expand...
Click to collapse
wow .. please upload it to google drive or mega (dot) nz and post the link here .... honestly this gets me very excited ...
mingkee said:
I have found fastboot flashing method for 8T to flash unlocked ROM on T-Mobile version (unlocked bootloader required).
Since T-Mobile version MSM is available, I can use it if anything goes wrong
Stay tuned
Click to expand...
Click to collapse
my bootloader is locked .. thats why MSMDownload tool is a must
edale1 said:
T-Mobile Variant MSM Tools:
[OPN2005G] [OOS TMO DE18CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: I hope you don't break your phone, but if you do, it's not my fault. Since you are choosing to modify your phone, you accept full responsibility for whatever happens to it, including any damage that may have occurred as a result of...
forum.xda-developers.com
Do not use this on any other variant.
Click to expand...
Click to collapse
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a maual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Dimitrimem said:
I tried that on my full paid one from oneplus.com and it dont work ... so yes its a waste to download it for nothing
Click to expand...
Click to collapse
If you use the "+ Quote" button, rather than the reply button, it'll create a multiquote, letting you quote and reply to multiple posts all at once (it'll add a "insert quotes" button to the reply box). This eliminates double-posts, which most forums frown upon.
@Dimitrimem here ya go https://drive.google.com/drive/folders/1DzR0uEdyFeBeID4sVaT96z0Y88sMaomL?usp=sharing
Dimitrimem said:
there is no msm tool for the full paid version from OP store .. only for T-Mobile .. but if you phone is still under waranty please get a hold of tech support and tell them you request a remote session and that your phone is seen by your computer . they will have you fill up some forms via email and send you the link to download the tools .. if you do please share them here .. when i had my issue they didnt have the tools available and chose not to send my phone back so i am like you with a briked phone
Click to expand...
Click to collapse
Tried this today. Now waiting on OnePlus to respond.
bouyakasha said:
Tried this today. Now waiting on OnePlus to respond.
Click to expand...
Click to collapse
Don't wait to long for their reply .. if they don't answer call them on the phone.. it takes less than a minute to have them speak with you ... I dragged it for too long with them waiting 7 days to send me a shipping label than another 5 for another try at it .. another 4 to get the link for download ..after all that they said they don't have it... but this was a while back ... I'd be on that phone fast.. tell them you need your phone as it's the only one ... honestly if you can get the msm tool it would be amazing
mingkee said:
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
There's a manual method.
If you're familiar with fastboot flash with Moto phone, yes, similar commands.
Download full ROM and unpack with payload dumper, and flash every .img one by one
Click to expand...
Click to collapse
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
darkghost568 said:
I am familiar with this from Moto, and some previous manual flashes with my OEM OP5. However, after extracting the partition .imgs from the OOS OTA via this tool when I try to `fastboot flash logo logo.img` (among others), I get hit with `FAILED remote: flashing is not allowed for critical partitions`, even after having unlocked with `fastboot flashing unlock_critical`. How were you able to get everything to work?
I also tried flashing the OTA zip via the TWRP, but it seems like the current dev version of TWRP in that thread is completely borked for N200 as far as ROM flashing goes ://
Click to expand...
Click to collapse
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
mingkee said:
You have to flash in fastbootd (... reboot fastboot) as instructed in 8T forum
Click to expand...
Click to collapse
Ok so now I'm stuck here as well (saw your comment in the other thread):
mingkee said:
I attempted to flash unlocked ROM on bootloader unlocked T-Mobile version phone
It stuck on products.img. The error stated "not enough space for the partition"
What happened?
Click to expand...
Click to collapse
Any luck getting past this?
darkghost568 said:
Ok so now I'm stuck here as well (saw your comment in the other thread):
Any luck getting past this?
Click to expand...
Click to collapse
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Towards the bottom of that post it talks about getting past that error.
Honestly found it on XDA of all places after looking for it all night
What does 1.16 give us that 1.14 doesn't? Everything honestly. Could not get my Wing recognized to flash with 1.14. No 1.15 Patched exists either
We can downgrade with ChipErase (and restore IMEI), we can modify PDM, we can dump the entire phone (will do tomorrow), can upgrade.
See link here for link: https://forum.xda-developers.com/t/...er-w-fastboot-drivers-and-common_dll.4304181/
This was the only working LGUp_Tool that worked outside of LGUP CMD
I wanted this to try other countries firmware files to see if we get other weird results. This should also allow custom KDZ files? from my understanding
ADDED INFO Nov 8, 2021
How to use LGUp Tool From this Download
1.) Download the LGUp 1.16.03 Patched from the XDA Link above
2.) Run the EXE as admin so it can install Drivers and the software properly
3.) Go to the install directory and run the 2 Bat files that are in the folder as admin
Code:
Default: C:\Program Files(x86)\LG Electronics\LGUp
-- Running LGUP_UI-fixer.bat -- run as admin, follow instructions, run the software when it says to, then close it
-- Run LGUP_UI-Fixer-addon.bat -- run as admin, follow steps, then run LGUp.exe when patch complete
You now have a working LGUP Tool 1.16 Patched for the LG Wing
Explaining the functions of LGUP Tool
Code:
REFURBISHļ¼ You will lose all user dataļ¼KDZ or TOTļ¼
UPGRADE: Keep data and update your phoneļ¼KDZ or TOT) - Select Upgrade to flash kdz firmware to unbrick/restore your phone back to stock.
Chip Erase: Dangerous, This will erase IMEI/efs, do not try this if you do not have a NV backup. - Chip Erase can also remove the Google FRP on many LG devices with Android 5.0, 6.0.
PARTITION DLļ¼Flash the single Partition or selected partitions onto your phone. - This feature can solve āunknown modelā issues. This feature can be used to bypass Google FRP by flashing specific tot firmware.
DUMPļ¼Dump all partitions of your phone as backup. - Dump the stock firmware from a working phone as back up and use Partition DL to restore phones.
FOTA Upgrade: This can be used to flash OTA Update file that comes with dot up file extension.
PDM: Change imei, wifi address, bluetooth, mac address
video for how to use LGUP Tool to flash the Wing
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
kaluna00 said:
Awesome! I just DL'ed.. don't know when I'll have time to mess around with it. Or if I have the skill set to help. But I would definitely try to help out if I can and be excited for rootable firmware.
Click to expand...
Click to collapse
I plan on making a video I'll put on the post explaining the tool
KaptinBoxxi said:
I plan on making a video I'll put on the post explaining the tool
Click to expand...
Click to collapse
Holy cow I canāt believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
twocans said:
Holy cow I canāt believe it. You actually found the exact tool that we needed! I went ahead and did a chip erase on my demo model, which had previously been flashed with the Korean firmware from the previous tutorial, and flashed the T-Mobile Firmware. IT WORKED! To get rid of the error at that shows up every time you reboot it, I accessed the hidden menu and changed the TN number to the one associated with TMO_US, as shown in this post.
Thank you!
Click to expand...
Click to collapse
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
Where did you get the Verizon firmware?
kaluna00 said:
Where did you get the Verizon firmware?
Click to expand...
Click to collapse
I found a site that had a "KDZ Downloader" and used that to download it. I can upload it here for those who need it once i redownload it here at work
or you can yourself from this post. Just need the LG URL to the firmware
[LG TOOLS] LG-KDZ-dll-Tool/LGUP_UI-fixer/LG-Kdz-downloader
Please, do not share elsewhere as I want to be able to update if necessary ! LG-KDZ-dll-Tool/KDZ dll extractor (=old version) : this message actually, scroll down a bit... LGUP_UI-fixer LG-Kdz-downloader Share this thread or my blog instead...
forum.xda-developers.com
KaptinBoxxi said:
I still can't get mine to accept a sim card and get data but I can make calls/text and use wifi, which is nice.
I wish Partition DL worked, we'd have the boot.img
I flashed Verizon Firmware and put the Verizon NT Code using PDM Mode, still didn't work. Going to try others later
Click to expand...
Click to collapse
I bought a mint mobile trial sim from amazon and Iām getting calls, text, and 5G data.
twocans said:
I bought a mint mobile trial sim from amazon and Iām getting calls, text, and 5G data.
Click to expand...
Click to collapse
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
KaptinBoxxi said:
I get calls and text, no cell service at all. I had to manually program in an IMEI. My IMEI comes back as 0 if I just flash it without PDM. IMEI doesn't apply via the service menu either
Click to expand...
Click to collapse
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesnāt really matter to me. (Too bad the fingerprint scanner still doesnāt work though. Thatās the only thing left that still isnāt working after all of this.)
twocans said:
Interesting. I was able to generate an IMEI in the hidden menu after the chip erase and it worked fine. I did also have to re-add my CSN, because that was also removed, and then my phone did an unprompted factory reset and rebooted.
By the way, when you flashed it, did you use Refurbish? Because with my demo unit, it refused to let me do that and would only allow chip erase. I was reluctant, but it turned out fine. And, the only important thing I was unable to reprogram afterwords was the S/N, but it doesnāt really matter to me. (Too bad the fingerprint scanner still doesnāt work though. Thatās the only thing left that still isnāt working after all of this.)
Click to expand...
Click to collapse
I plan on testing every function to document what happens, so far I've done Refurbish, Partition DL, Dump, PDM and ChipErase. only Dump didn't work
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
kaluna00 said:
Nice work fellas!!! Exciting to see some movement towards being able to root/development.
Click to expand...
Click to collapse
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
kaluna00 said:
@KaptinBoxxi
BTW... How do you get to the hidden menu on the Verizon Varient?
Click to expand...
Click to collapse
I think its the same dial code. I don't have the device in front of me at the moment to say
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
kaluna00 said:
I tried this earlier...
Post in thread 'LG Wing 5G Network option activation' https://forum.xda-developers.com/t/lg-wing-5g-network-option-activation.4285275/post-85116977
Am I using the wrong dial code for Verizon?
Click to expand...
Click to collapse
I have yet to have network work on my demo device regardless of what firmware is on it because my Serial Number and IMEI always come back at 0 and even if I manually enter new ones, it doesn't acivate, although i was able to get to the menu just fine with the standard code in that post.
Interesting, I wonder if there's something different in your firmware or kdz...
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
kaluna00 said:
looking at the software version. mine is on
F100VM10i
maybe they (Verizon) patched out the hidden menu. your KDZ is labeled
F100VM10d
???
Click to expand...
Click to collapse
I'm not sure what the final letter signifies, but F100V is verizon, yeah
KaptinBoxxi said:
I'm not sure what the final letter signifies, but F100V is verizon, yeah
Click to expand...
Click to collapse
think that represents the SW iteration identifier between updates... bit of a guess, but i believe that character has changed with updates.
Check your OnePlus updater.
mingkee said:
Check your OnePlus updater.
Click to expand...
Click to collapse
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
S build based on Color OS and even the font changed.
I think I can deal with mine, but the most important of all, there's no player error on rooted N200 with S
Scragge said:
Yes, A-12 has been released for the N200, but it may screw up your phone. I bought three of the unlocked US market 5g N200s due to the 3g phase out. Yesterday two of them updated to A-12 and now neither of them will work for voice /mms/sms. The phones detect a SIM installed but will not access the mobile network at all. I'm using Consumer Cellular which in turn uses At&T towers. Nothing I've tried makes any difference, can't even place a call on my brand new phones. OnePlus tech support is useless, their solution is send the devices to them for "repair" after their update broke my phones. After chatting with their rep I have 0% confidence they will actually do anything except keep my phone for a month or so and send it back in the same condition. According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
The12thJuror said:
THANK YOU for posting this!! My mom purchased an N200 for the exact same reason and after the A-12 update she's having the same issues with her device. All her voice, sms, and mms transmissions go through Cricket wireless (which also uses AT&T network) She contacted OnePlus customer service and they said they'd get back to her within 48 hours. It's now been 48 hours but with it being a weekend, she's hoping to hear back from them by Monday. She went to the Cricket store yesterday and they cleaned and tried a new SIM card to see if that might fix the issue but it didn't.
While it doesn't sound like there's any fix available yet, it's helpful knowing that this issue is affecting someone else using the AT&T carrier network. Hopefully between OnePlus and the AT&T wireless carriers they'll figure out a solution sooner rather than later.
Best of luck with your devices.
Click to expand...
Click to collapse
Yeah, I called OP three times got the same promise from OPs customer service and they never got back with me. I've never dealt with a less enthusiastic company when dealing with a serious product defect. The tech support people at first acted like the didn't believe me when I described the problem. Then once I had (I think) convinced them the problem was real, their response was like "oh well, too bad, so sad". OP offered no solutions or even ideas of what to try to do to fix the problem.
Do they test anything before pushing out an update?
I had a two day window left for returning the devices for a refund so now they're gone, and I'm gone as an OP customer, I can't just do without a phone while they fumble around trying to figure out the details for some (maybe) upcoming patch.
Good devices, terrible customer service. Never settle, nope, never again.
Scragge said:
According to their tech, no roll back tool exists for the unlocked variant.
Click to expand...
Click to collapse
Try this
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
forums.oneplus.com
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Travisholt92 said:
For those of you who want to downgrade from 12 to 11, use fastboot enhanced/payload dumper, boot fastbootd, delete all of the "my_" partitions, flash android 11 ROM zip (payload.bin button). Reboot bootloader, use the command fastboot -w to initiate a factory reset, reboot recovery and wipe data (this fixes mismatching metadata/userdata partitions) reboot device and voila you're on Android 11 again. Confirmed on my converted TMobile variant.
Also T-Mobile variant got official A12 OTA with the same C.15 build number.
And AT&T doesn't play nice with OnePlus, their new sim cards will not let you use a OnePlus device at all because they are unsupported.
Click to expand...
Click to collapse
Do you know where to download the A12(or at least the latest A11 update so I can update to A12 via OTA) stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Tyreethetruth said:
Do you know where to download the A12 stock firmware/update or could you upload it for the T-MO(metro) variant or show how to update OTA even when I unroot both slots the OTA still fails
Click to expand...
Click to collapse
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Travisholt92 said:
I'll get the link scraped today. To fix OTA you have to reflash the stock build to restore avb (android verified boot / vbmeta verification). Without this being restored you can't flash OTA's using the normal methods. But once I get a link to the T-Mobile/metro update, you can use fastboot enhanced to manually upgrade like I did. I'll make a tutorial for the manual upgrade/downgrade process. I first have to downgrade from OxygenOS 12 to 11, then use the MSMtool to restore stock T-Mobile software. Easy stuff
Click to expand...
Click to collapse
Thank you! I been stuck on the same update like 4-5 updates ago
On this build (metro/TMobile version converted. I can't keep android auto connected. I went into developer options and selected the default to transfer files/ android auto and all the other options but it just connects for a few and then disconnected and says device unsupported.
Rooted device and using a alpine iLX-w650
Tyreethetruth said:
Thank you! I been stuck on the same update like 4-5 updates ago
Click to expand...
Click to collapse
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Travisholt92 said:
The link to the download is literally a https link in the logcat when downloading the OTA. In case you're wondering how to manually download the zip onto a computer, that is how to get the link. If anyone else beats me to sharing the link it would save me from having to downgrade to get the link for the T-Mobile variant myself
"adb logcat > logcat.txt"
Click to expand...
Click to collapse
So I get on computer and go on bootloader and type "adb logcat"?
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Travisholt92 said:
Negative, while booted and after you start to download the android 12 OTA you can run the adb command to get the link while the OS is running.
https://android.googleapis.com/packages/ota-api/package/7cd89efc84e6db817ed16b59b0af3120521ab323.zip
(Shout out to @lzgmc )
I dirty flashed this (DE2118 T-Mobile/Metro) build over the leaked unlocked variant (DE2117) OxygenOS 12 build most are running and did not have to factory reset after flashing with Fastboot Enhanced.
My TMobile variant is now running the T-Mobile firmware. No downgrade required for that.
Downgrade process is download the android 11 build from OnePlus, boot fastbootd, use fastboot enhanced to delete all of the "my_" partitions, flash "payload bin" (full android 11 ota zip from OnePlus), make sure to tick ignore unknown partitions. After that is done shut the phone down and boot to fastboot/bootloader using the key combo, and flash the same payload again with ignore unknown partitions ticked. This will update the partitions that were inaccessible in fastbootd (such as modem). After this you will have to use a terminal with adb/fastboot to run "fastboot -w" this will wipe metadata(encryption key for userdata) and userdata. Reboot to recovery and perform factory reset there as well. After that you should be good to reboot to OxygenOS 11. To return to stock T-Mobile after that just use msmtool
Click to expand...
Click to collapse
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Tyreethetruth said:
Alright cool thanks for the download so just go to twrp/orangefox and install it or do I get on pc and flash it via adb? Does it have to only be fastboot enhanced?
Click to expand...
Click to collapse
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Travisholt92 said:
PC and flash via fastbootd then again in fastboot after fastbootd. Fastboot enhanced is the easiest way to do it, otherwise you will need to fix custom recovery to support android 12 or use command line tools to unpack the oneplus ota file to manually flash each partition.
Click to expand...
Click to collapse
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Tyreethetruth said:
Gotcha, how do I go to fastbootd and fastboot? Its confusing me which one is which
Click to expand...
Click to collapse
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Travisholt92 said:
fastboot = bootloader
Fastbootd has access to more critical partitions and can be accessed by the command "fastboot reboot fastboot" at the bootloader or by hitting the "reboot to fastbootd" button in fastboot enhanced. Make sure to flash it in fastbootd BEFORE flashing it again in fastboot
Click to expand...
Click to collapse
Gotcha, one last thing how do I flash using fastboot enhance? Idk what to pick to flash the A12 OTA
EDIT: Nvm I extracted the update and found the payload
Magisk patched boot.img for this release: https://drive.google.com/file/d/1A2x8YbnnO6SJq-R-1rdZZ18CU673Z2-Y/view?usp=sharing