Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
If you haven't updated it (software version 1.015AT), then we're both in luck. If it's on anything newer than 1.017AT there's no way for me to do what's necessary to determine/enable crossflashing or downgrading between versions or, in your case, simply enable radio bands 12, 66 & 71... although you could try asking AT&T for the carrier unlock code, which will probably allow at least partial functionality w/a T-Mobile SIM. I might be able to determine the code for your device myself otherwise, but I'll need details you'll have to get from files you can only hopefully access without root, as those kernel sources are mostly useless as far as providing the information needed & nobody gives af about this phone, aside from the handful of people who have posted on here about it that at best don't seem to get what (short of leaked engineering files) it takes to modify something this locked down & recent. In short, "no." E6810 is the only one with consumer flash restore, E6830/E6833 is the only one with provider available OEM service flash ability, and E6820 (your version, if it's an earlier one) is the only one that shipped with firmware which isn't too recently patched to get root without using a yet published exploit or methods that first require files nobody but factory techs & provider/OEM engineers have, or at the very least what you might well be holding (if older & not updated) plus a lot of work & luck on my part or probably eventually some 14yo in Russia, but so far I don't think anyone's even managed to get temporal root on it aside from myself & while you could technically, maybe, hot-flash from that, if it still works on newer builds, it's unstable & there's no image for you to flash unless I can get recovery imageloading over usb or from SD working enough someone can dump one. The only image available is 5.420VZ & that won't flash on anything but E6810 because, if nothing else, you can't get it to where it'll enter the mode to receive it & do so. Likewise, I don't have the Sprint service utility, but it won't work on anything other than E6830/E6833, so I don't even know what means is used on E6820 at all w/o looking at files contained in areas completely inaccessible without root. I might, however be able to get that information from the OTA update file or just get root, depending on your current version
Diactoros said:
Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
Click to expand...
Click to collapse
Did you find a way?
chikosneff said:
Did you find a way?
Click to expand...
Click to collapse
Unfortunately, no. It works on T-mobile with the AT&T ROM, but wifi calling doesn't work, which is really a problem. I'd still be glad of any insight anyone could provide.
Hey All,
Like many unfortunate souls out there I updated my device to Oreo via T-Mobile OTA and instantly my device slowed down with odd behavior. Given I have G930T model which cannot be rooted (be very honest I am confused between the models and why G930T can't be rooted), I am desperate to make this posting hoping someone can help me a bit.
My simple goals:
- Get stock Android on my device and have it running faster, all features working and extend my battery life.
- Keep my phone/app settings
- Not have T-Mobile bloatware.
My concerns:
- Will I lose features such as camera not working in a text message app, WiFi calling, etc.
- Is it better to go back to Nougat or install Oreo? (this is once I figure out all the jargon and many guides)
I refuse to upgrade to a newer device because of stupid software updates and I love this phone too much. This phone is causing me issues professionally such as speaker turning off in the middle of the call, call volume is too low, outgoing text messages failing, sluggish performance, freezing, and horrible battery life. Beside for battery issue, everything else started to happen after software updates.
My Device/Setup:
- Samsung Galaxy S7 - T-Mobile - G903T
- Current stock version R16NW.G930TUVU4CRF1
- macOS with Samsung USB cable
Before there is an outcry on why I didn't search for and find a previous thread that can easily explain, I did and found this amazing write up (it took me a while to even find this):
https://forum.xda-developers.com/tmobile-galaxy-s7/development/rom-t3846694
However, there are a few things that I use daily such as visual voicemail and WiFi calling in an office where I had a bad signal. I really hope this post gets me some specific pointers and not get removed from the site for posting this. I am a beginner so please be gentle.
Thanks!
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues https://www.reddit.com/r/Android/comments/5xzbo3/qualcomm_s7_engineering_boot_images_leaked_root/
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Beanvee7 said:
The main difference between models and why some can't be rooted is the SoC, all USA models use Snapdragon and come with an locked bootloader that can't be unlocked. All other models come with Exynos with an unlockable bootloader. The bootloader needs to be unlocked for root.
There are root methods for the G930T, but it involves using engineering bootloaders to get around the lock, which is in that thread you linked (AP_SM_G930_OREO_ENG_BOOT.tar), since it's an engineering bootloader and not 'production' it comes with its issues ...
Unfortunately if you want the best performance, keeping app settings isn't likely. The best approach would be a clean flash of stock firmware using Odin with a full wipe. If you use the G930U firmware, which is the carrier unlocked version of your phone, it won't have bloatware. But this may impact WiFi calling since that's part of your carriers firmware.
Because of the locked bootloader, you also can't downgrade, so Nougat is off the table.
Here's a pretty easy to follow flash guide ...
You can use the same site to download the firmware files, or use samfirmtool or sammobile.com. Just put the AP, BL, CSC and CP files in their respective slots and hit start.
Flashing stock firmware with Odin doesn't void warranty or anything like that.
EDIT: The guide also links an older version of Odin, you'll want 3.13.1 for flashing Oreo
Click to expand...
Click to collapse
Thanks for such a detail accurate answer I was looking for. Sorry for the late reply as work has been crazy. I will go through to install Samsung stock firmware and see if it improves performance and battery life. Will try to get G930U and see if I can go without WiFi calling. First, I am trying to do a backup using SmartSwitch (will dig around for more backup option if this one doesn't work). Will update here once I am finished and any lesson learned to help someone else in the future.
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Dishe said:
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Click to expand...
Click to collapse
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
loonycgb2 said:
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Click to expand...
Click to collapse
Wow, that's some good info right there, thank you for sharing!
Hmm- messing with nvdata though? So you're saying the SN missing is some sort of accident or goof? That doesn't sound so cool. Should I be concerned anything else is messed up? There's a ton of these in the wild now and it seems the SN is the only weird side effect that has been noticed.
As far as I know the IMEI is fine (looking it up reveals it is a PM imei, which is correct, and it does work with voice over Wifi and VOLTE, which I think wouldn't work if the IMEI was messed up). In fact, it's interesting because when that screen loads in Settings>About, etc, it shows "checking" under S/N, then checking goes away and it comes back blank. None of the other fields seem to need any sort of checking first. There's something fishy about how the S/N is stored that it has to check it first and then error out.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Click to expand...
Click to collapse
Hmm. It came with Oreo, and I used 1.15 to flash to Pie. So you're saying I should flash another Oreo kdz with my LGUP and it will magically fix any corrupt NVdata?
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
Click to expand...
Click to collapse
Oh, that is unfortunate. And that value stays with it forever, even if you go back to it's native firmware? I'm assuming that value can't be manipulated with any of the tools we have available.
Thank you so much for sharing this knowledge. Any insight on how the bands work? Is that from nvdata as well, and completely independent of firmware? So essentially, I have whatever band support a G710pm has? Or perhaps was it manipulated by the seller/refurbisher, who possibly used some nvram voodoo tricks which killed the S/N as a result?
Even tho the s/n is blank and at time if you try to show the imei it might also be blank, it is still stored internally and not lost forever.
There is multiple oreo's which for ulm is 10g and 11g, but i would have said flash to the original firmware but you cannot as sprint kdz is not available and the people who have an Original firmware still on device cannot or will not back it up for us.
The value for certified device returns to normal when flashed to the original firmware as lgup has an internal database used for identifying models.
As far as the basebands, all g7 thinq's come with the same bands no matter the firmware or region. The difference is the kdz gives band priority to the ones prefered by the carrier.
All of that can be changed by getting into the lg data secret menu or the dialer code menu
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
netookska05 said:
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
Click to expand...
Click to collapse
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
netookska05 said:
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
Click to expand...
Click to collapse
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
loonycgb2 said:
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
Click to expand...
Click to collapse
Can you please elaborate for those unfamiliar with this?
Dishe said:
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
Can you please elaborate for those unfamiliar with this?
Click to expand...
Click to collapse
Using TWRP to create a backup of efs. Sometimes the restore is faulty.
EFS partition holds up the unique IMEI number of the device, also other identifying numbers like MAC address, MEID, and ESN are stored up in this partition.
Check you IMEI with this.
https://imeipro.info/check_lg.html
To get your sn.
Oh ok.
So I don't actually need to know my SN but I'd like it to not be blank if flashing back to a previous version would restore it... Especially if there are possibly other parts of nvram that may be corrupt that I'm unaware of?
Thanks for the info. The one I got said it can't work on Sprint or Verizon networks, and is missing the serial #, as you said.
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
vishal198900 said:
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
Click to expand...
Click to collapse
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
I just got a 710pm off ebay. I unlocked the bootloader, crossflashed to ulm pie, and rooted. It works just fine. [emoji106]
Sent from my LM-G710 using Tapatalk
netookska05 said:
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Click to expand...
Click to collapse
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
netookska05 said:
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
Click to expand...
Click to collapse
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
vishal198900 said:
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
Click to expand...
Click to collapse
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
netookska05 said:
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
Click to expand...
Click to collapse
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
vishal198900 said:
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
Click to expand...
Click to collapse
Yes it will work.
I'd also like to add that Google Pay will not work, at retail brick and mortar stores.
A pop up says device may be rooted or modified.
I have magisk installed and it seems to trick Schwab banking app.
Edit:
Edit: I followed the instruction from the following video, and was able to get GPay to accept the card. Also Gpay needs to be manually hidden in magisk, be sure to select 'display system apps' to find it.
https://www.youtube.com/watch?v=wKYC0r-m0Mo
Click to expand...
Click to collapse
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
captain barbosa said:
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
Click to expand...
Click to collapse
If you're on Pie, I doubt you have one of these Sprint phones. Check if you pass SafetyNet and if so, you have a native ULM model. Most G7 variants receive very few updates (including the ULM).
i've never flashed firmware partitions before on my other 2 moto devices, i understand having read the install of lineage that this step is req'd for this model.
i'll be using the lineage recovery to install the rom flash, this is the method ive done before. My question is once i sideload the firmware partitions, will this automatically asign which partion the rom will be written too or do i have to tell it which one, im understanding that it will be either A or B partition??
I'd like to wipe/erase as much of the stock rom off the phone, remove everything and then flash the operating rom to a clean phone. Am i understanding this correctly or missing anything? Is there anything that i need or should know or do when at this step? any help/advice would be greatly appreciated.
This is a brand new phone out of the box, is there other ways that any of you would approach this phone to totally wipe it, i'm hoping that ill get the android 11 update immediatley over ota, i understand that i will have to go through intial setup, to get to unlocking the bootloader, wish i didnt have to do that, also i dont believe kiev has an official android 12 oem/factory rom but lineage has 19.1, im thinking install 18.1 and then later reflash android 12 when it comes out. Im talking to much.... any advice be great. TIA
First things first, know your device. Is it an XT2113-2 RETUS variant or something else? As long as the bootloader can be unlocked, it seems any kiev (qualcom) variant should work with lineageos - just best to know what you started with in the event you need to ask for assistance or you want to revert back to stock.
My suggestion assuming you are starting from a new phone out of the box with the plan of putting official lineageos (either 18.1 - android 11 or 19.1 - android 12) on it:
Have the phone ota update to the most recent stock firmware. For XT2113-2 RETUS at the time of this post, this is android 11 version RZKS31.Q3-45-16-8-3 released 2022.06.30. Lineageos currently uses the binary blobs from this version. I suspect having the latest stock radios and bootloader on your device will result in fewer issues and may likely make your life easier later.
After updating to the most current stock version, request the bootloader unlock key from the moto www site. You may need to wait 24-72 hours or longer before the phone will allow unlocking. Leave the phone on, connected to your (primary) carrier, and use your carrier data (i.e. not wifi) during this time.
After updating to the most current stock version, put all the sims in the phone for the carriers you plan to use and let the phone provision the carriers (I've read this can only be done on stock firmware - switching carriers without having done this step apparently requires going back to stock). Test that you can swap sims and use the phone as you need to (e.g. wifi calling, try visual voice mail, try 5 G, etc).
Unlock the bootloader. Be sure to leave the oem unlocking toggle to allow after unlocking the bootloader.
Most important: when coming from stock (either now or in the future), follow the instructions on the lineageos www site. In particular, flash the copy-partitions.zip following the sequence described in the lineageos instructions. Don't worry about the A/B partitions for now, the device will take care of itself. You only need to flash the copy-partions.zip when comming from stock (either now or if you reflash stock in the future and then want to go back to lineageos).
Flash official linageos 18.1, android 11 (not 19.1- android 12). 19.1 is the newest version; however it may have issues. 18.1 works great (for me) and it will likely be easier for you to check if everthing is working as you expect. Upgrade (via ota) to lineageos 19.1 in a month or two.
Updating official lineageos via ota, the device will flash to the appropriate A or B partition. You should not need to do anything unless there is an issue.
I'd like to wipe/erase as much of the stock rom off the phone ...
Click to expand...
Click to collapse
Following the lineageos installation instructions will accomplish that.
Good luck.
notmyrealhandle, thanks for your time and reply, perfect write, i understood everything you said. i never thought of doing ota via data as opposed to wifi, thanks. perfect​
Hello,
I recently upgraded my Note 20 Ultra (N986U) (ATT) (unlocked) from Android 11 to Android 12 (N986USQU2EVA9) by dirty flashing via Odin. I followed a guide on this forum and thankfully, my phone updated with no issues whatsoever with my data and apps intact. This basically means that I flashed normally except I used the HomeCSC and I left "userdata" empty at Odin.
I just realized that SamFW posted the new ATT firmware, Android 13 (N986USQU3GVK5) and I wanted to update to it via Odin.
The reason on why I want to update it via Odin instead of OTA is simply because I don't live in the USA and I don't have an ATT Sim/network in my country. Can I still follow the dirty flash method for this? I'm just a bit afraid that since it uses a different bootloader version or maybe because of the android version difference I may go into bootloop with no way out. Has anyone tried this?
I would like to apologize if this question has been asked before. I tried scrolling through the depths of XDA forums for answers but I can't seem to find any answers. Thank you for your time!
Hey there just wanna give a quick update.
Yes, it works fine. I've done it personally and every apps, data etc. is intact.
I hope this is useful for anyone who is in the same predicament as me.
yousof577 said:
Hello,
I recently upgraded my Note 20 Ultra (N986U) (ATT) (unlocked) from Android 11 to Android 12 (N986USQU2EVA9) by dirty flashing via Odin. I followed a guide on this forum and thankfully, my phone updated with no issues whatsoever with my data and apps intact. This basically means that I flashed normally except I used the HomeCSC and I left "userdata" empty at Odin.
I just realized that SamFW posted the new ATT firmware, Android 13 (N986USQU3GVK5) and I wanted to update to it via Odin.
The reason on why I want to update it via Odin instead of OTA is simply because I don't live in the USA and I don't have an ATT Sim/network in my country. Can I still follow the dirty flash method for this? I'm just a bit afraid that since it uses a different bootloader version or maybe because of the android version difference I may go into bootloop with no way out. Has anyone tried this?
I would like to apologize if this question has been asked before. I tried scrolling through the depths of XDA forums for answers but I can't seem to find any answers. Thank you for your time!
Click to expand...
Click to collapse
Which guide did you use ?
jez17 said:
Which guide did you use ?
Click to expand...
Click to collapse
OTA and Non-OTA Firmware for N986U and N986U1
See Post #2 and #3 for the Links to the Firmware ALL of the firmware posted here can be flashed on any N986U/N986U1 Device. The firmware is NOT carrier dependent and is only listed next to some of them in order to have an idea if you might get...
forum.xda-developers.com