Develop Bugs

Downgrading K428 (T-Mobile) to Root it

There is good information on this forum on how to root your k428 (https://forum.xda-developers.com/lg-k10/development/root-twrp-rom-t-mobile-k428-k10-t3582493)
This however, is not possible on anything later than the 10f(?) firmware, due to there being a December 15, 2016 security update.
Firmwares I am pulling from: https://lg-firmwares.com/lg-k428sg-firmwares/
My K10 is on the most recent update 20h(?), the only thing I've done is unlock the bootloader. I'm trying to get it down to an earlier firmware version to be able to root. I have tried:
Uppercut with LGUP:
There are two separate errors I get with this. One is when I select refurbish and it gets to about 4% (On LGUP, not the phone) and it says my ".kdz does not allow refurbishing" or something along those lines.
I have tried update as well, and I get an error at 14%(on LGUP, 10% on device) and I get "invalid command response code" (image attached)
I have tried both of these options with 3 different .kdz files, so the problems aren't just unique to one file.
LG Flash Tool 2014:
When I start there is an error saying no connection to the server and no progress indicated on the phone or computer, even after maybe 1/2 hour.
After LGUP, I do have to bring my phone back with LG Bridge Update Error Recovery, but interestingly no data is lost at all so clearly my phone is not being wiped at all.
How have people successfully downgraded their k428 and how do I?
Also, is the k428 the same as the k428sg? I can't seem to figure this out and the firmwares website has slightly different specs.
I have another phone, just really hoping to switch to this one is it seems quicker, isn't running Touchwiz, has a decent camera, more storage... I won't be switching if I can't get this rooted because I have been spoiled by rooted devices.

der_cobester said:
There are two separate errors I get with this. One is when I select refurbish and it gets to about 4% (On LGUP, not the phone) and it says my ".kdz does not allow refurbishing" or something along those lines.
I have tried update as well, and I get an error at 14%(on LGUP, 10% on device) and I get "invalid command response code" (image attached)
I have tried both of these options with 3 different .kdz files, so the problems aren't just unique to one file.
[...]
After LGUP, I do have to bring my phone back with LG Bridge Update Error Recovery, but interestingly no data is lost at all so clearly my phone is not being wiped at all.
[...]
Also, is the k428 the same as the k428sg? I can't seem to figure this out and the firmwares website has slightly different specs.
I have another phone, just really hoping to switch to this one is it seems quicker, isn't running Touchwiz, has a decent camera, more storage... I won't be switching if I can't get this rooted because I have been spoiled by rooted devices.
Click to expand...
Click to collapse
Having very similar issues, at the moment stuck in a "Firmware update" loop with a T-Mobile K10 K428, after trying to downgrade from 7.0 to 6.0.1.
How are you reverting it to useable form with the LG Bridge app?
It only tells me I have the latest update then goes away.
[nevermind, this part worked]
Managed to bring the device back to functional 7.0 state, but have found no way to downgrade back to 6.0.1.. the regret I feel for allowing the update to happen before rooting the device is indescribable in frikkin words.

Hopefully someone somewhere is working on the root of this computer in Android 7.0, I have 3 of these and I need to do the root to unlock them

last Friday I could downgrade a version 10R to 10G and rooted .
but since yesterday I'm with another to downgrade but am getting error while modem part flashing .
version was 20H , I noticed once upon 20 no possible to back In 10 .

psytr0nic said:
last Friday I could downgrade a version 10R to 10G and rooted .
but since yesterday I'm with another to downgrade but am getting error while modem part flashing .
version was 20H , I noticed once upon 20 no possible to back In 10 .
Click to expand...
Click to collapse
i have been trying to make nougat downgrade to marshmallow for months. still no results. most i get is phone simply not booting OS.

SO,there is no way to downgrade from 20g?
what about about using special tools like Octoplus Box andZ3X Box?
anyone tried?
---------- Post added at 07:54 PM ---------- Previous post was at 07:53 PM ----------
SO,there is no way to downgrade from 20g?
what about about using special tools like Octoplus Box andZ3X Box?
anyone tried?

Worked Fine, min was a K428 with build number MMB29M, sec patch 2016-08-01
I did it as its posted step by step.
Nice Job!

Question Stuck after Tmobile upgrade to 12, can't MSM

I have a tmobile oneplus 9 pro. I converted it to remove tmobile branding months ago but recently couldn't get it to take ota updates anymore. I did local updates to get to 12 yesterday. It was successful but the modem wasn't working so I flashed a tmobile modem image. After I did that, it bricked. Now, when trying to restore to ANY MSM download I've found on here, it fails with an error along the lines of "Unsppported Target IN". I've been at it most of the day. ANy help would be really appreciated.

Also, I'm not even sure there is an option for the tmobile modem on 12 yet. maybe someone can confirm

ctosborne said:
I have a tmobile oneplus 9 pro. I converted it to remove tmobile branding months ago but recently couldn't get it to take ota updates anymore. I did local updates to get to 12 yesterday. It was successful but the modem wasn't working so I flashed a tmobile modem image. After I did that, it bricked. Now, when trying to restore to ANY MSM download I've found on here, it fails with an error along the lines of "Unsppported Target IN". I've been at it most of the day. ANy help would be really appreciated.
Click to expand...
Click to collapse
Try to boot twrp in fastboot and sideload Android 11 oos or look through xda for the patched MSM for tmo. But sideloading is easier than msm

Question Convert back to T-Mobile firmware? + Additional Questions

This may seem like a weird question, but is there is way to convert back to the T-Mobile firmware? Mostly I would like to avoid having to install the modem manually with every update. If this is no longer the case and there is a permanent modem solution then that's all I would need. I found a lemonade tar.gz for the T-Mobile firmware supposedly, however, I don't know how to make that a installable ROM. The link is a github link here, OnePlus 9 Pro Firmware. I've never swapped off of the carrier firmware and had to manually reinstall the modem with every update before. The most annoying part of that for me would be keeping the bootloader unlocked. That's only a minor issue for me as I play Pokemon Go and unlocked bootloader/root can cause issues with that. I don't generally tweak my phones much anymore. I prefer the non carrier ROM to have more current updates. To recap, is it possible to either go back to T-Mobile ROM or is a permanent modem fix for the conversion?

MSM is the easiest way. Just use the MSM tool for LE2127 and you'll be on your way.

I have a flash-all script that you put in a fastboot flashable stock rom zip, and it'll make it so the radio (modem) persists through OTA's. Just gotta dig around for it and see what I did with it.

Thank you both. If I could get back to T-Mobile firmware then swap back to global again that would be great. I think I may be up the proverbial creek though. In my search I came across what seems like an older thread first and I used the India MSM to flip to global. This unfortunately means the T-Mobile MSM is unable to flash to my phone as it sees it as an India phone. I found the other global MSM, and I am able to see the Target directory and choose O2, however, the MSM fails to download. Param Preload error, device not match image.

I've made peace with not being able to get back to T-Mobile firmware, I may have to research the persistent modem more for a fix that will work with India. Is there a modem install for OOS12 that doesn't brick the phone? I use the ones I have from the T-Mobile files, and they work fine for OOS11, but they immediately brick 12 after install.

Bumping this post to ask again about the modem for Android 12. Also, my Bluetooth audio cuts in and out, it's very crackly. This only started after jumping from the T-Mobile ROM.
Edit: Also the voicemail doesn't show in the Phone app. Voicemail service is listed as "Your Carrier" and I can't do anything with it. There are no options that I can toggle at all.

I was looking at the repo of builds for the 9 Pro. I see there is an Android S for all regions in there. Could that possibly change the region of the firmware to, more or less, not associated anywhere and allow a restore to the T-Mobile firmware?

I'm not entirely sure how, but I did manage to get off of the India firmware and onto the EU firmware. At least from there I should be able to get the persistent modem. Working on that process now.

All right, everything has been running fine on the EU firmware, the only thing I'm still having an issue with is Bluetooth. Not connectivity at all, just on phone calls and in one vehicle for audio. It's incredibly choppy. It didn't used to be an issue, it only started after I left the T-Mobile firmware. Is there something I need to flash for the Bluetooth or a setting I'm missing?

Question LE2127 + Microsoft Intune problems

Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.

razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?

SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.

If I have no sims detected am I able to flash something to regain sim detection and data?

OnePlus 7T Wifi broken after re-flashing stock rom

So I tried rooting my OnePlus 7T yesterday and first downgraded from android 12 to 10 (build number Oxygen OS 10.0.13.HD64BA), then tried to root it and I ended up getting a screen that said QUALCOM Crashdump Mode. After trying to search for an answer how to fix it, I tried to re-flash the phone with the stock rom, which I got from here taking the latest Europe version - https://forum.xda-developers.com/t/...t-stock-fastboot-roms-for-oneplus-7t.3979213/
I entered fastboot mode, and ran flash-all but when I watched a video on how to do it, I was taken to a different screen. I think I was maybe the advanced boot options screen (I had to pick a language then reboot to fastboot or recovery). After rebooting, I unlocked the phone and the wifi is now broken.
I saw a guide on here that said I had to do something about important partitions (not sure what that means), so I'm not sure I am correctly re-flashing the phone from the correct stock rom and can't find a thread that makes total sense to me. Any help would be great

MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .

Tomcar said:
MSM Tool
After restoring upgrade to the last OOS 11 (11.9.1 I think)
Then follow the links I gave you on your other thread .
Click to expand...
Click to collapse
Thanks for the help again.
I've downloaded the EU 10.0.13 MSM tools (as I downgraded my oneplus 7T to this) and it told me "device not match image"
What version of MSM do I need? I checked other links attached on similar forms and more often I only see an option for 7T for 10.0.03 or 10.0.15. I don't know what I'm doing wrong.

https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.3994835/
One of them should fit.
Or, if only WiFi is broken, upgrade to 11.0.5.1. and use the MSM Tool for that.
What's you're phone? HD1903?
I think you've flashed the wrong Firmware like India on Europe or vice versa.

Ignore me, I got it to work using a different MSM version (10.0.15). Will go back and try follow your instructions to root as best I can