Related
Hi all,
I'm new to this Xoom and I just bought it yesterday!
To be honest I don't know where to start!?
I want to install custom recovery, unlock, and install a custom ROM!
If that is difficult/unfeasable I only want to install the latest JB 4.1.1 rooted! Stock.
I have the following:
Model number:
MZ604
Android Version:
4.0.4
Firmware configuration version:
GAS_ASIA_UCAHUBLWFRTIRD_P011
GAS_ASIA_UCAHUBLWFRTIRD_A029
GAS_ASIA_UCAHUBLWFRTIRD_M007
Kernel version:
2.6.39.4-00033-gbd0e533
[email protected] #1
SMP PREEMPT Thu Jul 5 04:25:57 CDT 2012
Build number:
I.7.1-45
Please help me where to start?! What is fastest way?! Or the safest way?! Is this a US or non-US xoom?!
Thanks,
You have the Asian model (not a US one) which is the same as mine.
I turned mine into a 'Google Experience Device' by unlocking the bootloader, installed the US images, re-locked bootloader, then it OTA'd up to Android 4.1.1 Jelly Bean courtesy of Google.
The US images are available here at the link below from Motorola. You may need to register to download 'Build HWI69 for US Retail'.
http://developer.motorola.com/products/software/
xdatastic said:
You have the Asian model (not a US one) which is the same as mine.
I turned mine into a 'Google Experience Device' by unlocking the bootloader, installed the US images, re-locked bootloader, then it OTA'd up to Android 4.1.1 Jelly Bean courtesy of Google.
The US images are available here at the link below from Motorola. You may need to register to download 'Build HWI69 for US Retail'.
http://developer.motorola.com/products/software/
Click to expand...
Click to collapse
Thanks bro for that info!
can it still be rooted under JB?!
i've never rooted android so im not 100% sure. someone should reply soon with the answer otherwise im sure the info will be available on this forum somewhere.
xdatastic said:
i've never rooted android so im not 100% sure. someone should reply soon with the answer otherwise im sure the info will be available on this forum somewhere.
Click to expand...
Click to collapse
Well I've never owned android without rooting! It's unusable to me! 1st reason to do so is to remove ads!
General info on how to unlock, get a custom recovery and flash a custom ROM.
1. Set up android SDK and get fastboot and adb working.
2. Unlock: fastboot OEM unlock.
3. Custom recovery: fastboot flash recovery recovery.img
4. Download ROM of your choice, boot into recovery, create backup, and install.
There are plenty of guides that cover these individual concepts in detail. Good luck.
Sent from my Galaxy Nexus using Tapatalk 2
Removing changes to update purchased M9
Hi guys, apologizes in advance for the (potentially) stupid questions. This is the first time I've had to work backwards so to speak...
I purchased a M9 from eBay in the US a few days ago. Everything is working fine, up until I tried to install the lastest software update (1.32.617.30). I get the error "htc system has been remounted r/w reflash the device to re enable ota updates". Digging a little deeper I find the bootloader is locked but it does have S-off. Not finding any evidence of a root but obviously it has been at some point. My question is, is is possible to restore the blocks to original (or force the update through) without any previous backups or even knowing the history of the phone? Would RUU developer edition work without knowing if it came from AT&T/factory unlocked ect?
Some other info if it matters:
Android 5.0.2
Software # 1.32.617.6
Kernel 3.10.49-gc7c4f20 [email protected] #1 SMP PREEMPT
Baseband 01.01_U11440221_59.04.50303G_2F
Build 1.32.617.6 CL493992 release-keys
Thanks in advance
Hi.
You can run the RUU. It's unlocked to work on all carriers, so don't worry.
Also, 1.31.617 isn't the latest software update, 2.11.617.15 is.
You can download the official RUU from HTC's US website.
Scroll down to the Manual System Update Instructions and read them. The RUU is at the end of the instructions.
This will return you to stock, and IT WILL also WIPE YOUR PHONE, so backup anything important to you.
All -
I have a pair of G900V (Verizon Galaxy S5, his & hers) phones that I bought unlocked, both running G900VVRU2DPF4 build.
I'd like to dump the OEM Verizon apps - I don't want them, don't need them, and they're taking up space I'd like to use for something else, but I can't find them easily in the App Manager (I'm still fairly new to Android - I've been working in Windoze for years, and came up in Unix yonks ago...)
1) Can I strip these apps w/o root access?
2) If I need root access, is there an easy way to do it w/o having to change the firmware rev back & forth? (I did search for the PF4 build, but found minimal to no support on that particular topic WRT rooting.)
Environment:
- Samsung Galaxy S5 SM-G900V
- Android v6.0.1
- Security Patch Level: 01JUN2016
- Baseband Version: G900VVRU2DPF4
- Kernel Version: 3.4.0 ([email protected] #1 SAT 18JUN2016 085000KST)
- Build Number: MMB29M.G900VVRU2DPF4
- SE for Android Status: Enforcing. SEPF_SECMOBILE_6.0.1_0011, 18JUN21016 085445
- Hardware Version: G900V.05
- Security Software Version: MDF v1.1 rel 6; VPN v1.4 rel 6.0
- KNOX Version:
-- KNOX 2.6
-- Standard SDK 5.6.0
-- Premium SDK 2.6.0
-- Customization SDK 2.6.0
-- Container 2.6.0
-- CEP 2.0.1
-- Enterprise Billing 1.2.0
-- OTP: 2.6.0
-- SE for Android 2.4.0
-- SSO 2.5.0
-- Shared Devices 2.6.0
-- TIMA 3.2.002
-- VPN 2.2.4
- Configuration Version: 313.SAM.SMG900V.1
(I've done tech support - I'd rather give you too much information than not enough. But, if I've missed anything you need to know, ask! I'll look it up for you, if you tell me where to find it...)
JDK
EDIT - Although, I just saw the post on FolderMount - I may want to get root access just for that anyhow, even if I don't need it to strip the OEM Verizon apps....
JDKelley said:
I'd like to dump the OEM Verizon apps - I don't want them, don't need them, and they're taking up space I'd like to use for something else, but I can't find them easily in the App Manager
Click to expand...
Click to collapse
So, I don't believe you can remove them without root and unfortunately the Verizon version this phone makes life a little more difficult. You can't root 6.0.1 without unlocking your bootloader, which can only be done on certain variants (there's tons of info/threads in this forum). You can, however, downgrade, root, and then flash a debloated, nonrooted, 6.0.1 ROM. It's a pain in the ass, but not all that difficult and of course you'll lose your settings and have to set everything back up. Again, there are multiple threads with detailed instructions in this forum.
If you go that route, you should definitely check and see if you're able to unlock your bootloader and do so if possible.
tsew2674 said:
So, I don't believe you can remove them without root and unfortunately the Verizon version this phone makes life a little more difficult. You can't root 6.0.1 without unlocking your bootloader, which can only be done on certain variants (there's tons of info/threads in this forum). You can, however, downgrade, root, and then flash a debloated, nonrooted, 6.0.1 ROM. It's a pain in the ass, but not all that difficult and of course you'll lose your settings and have to set everything back up. Again, there are multiple threads with detailed instructions in this forum.
If you go that route, you should definitely check and see if you're able to unlock your bootloader and do so if possible.
Click to expand...
Click to collapse
Oh, FFS. You're telling me that the only way (at present) is to roll the OS /back/ to a previous version, /then/ root them phone, then roll the OS /forward/ again - and all that is IFF the "bootloader" can be unlocked?
Why do people insist on making things so bloody difficult?
JDKelley said:
Oh, FFS. You're telling me that the only way (at present) is to roll the OS /back/ to a previous version, /then/ root them phone, then roll the OS /forward/ again - and all that is IFF the "bootloader" can be unlocked?
Why do people insist on making things so bloody difficult?
Click to expand...
Click to collapse
Yeah, it's frustrating because this would be a decent phone and is capable of much more than Verizon is allowing it to be. Again, it's possible to get to same state that you're currently in (6.0.1, no root) without the oem apps, but you'll have to downgrade, root, then flash a debloated rom. If you're lucky enough to have a phone with a code that starts with 15, go ahead and unlock the bootloader and flash something current.
tsew2674 said:
Yeah, it's frustrating because this would be a decent phone and is capable of much more than Verizon is allowing it to be. Again, it's possible to get to same state that you're currently in (6.0.1, no root) without the oem apps, but you'll have to downgrade, root, then flash a debloated rom. If you're lucky enough to have a phone with a code that starts with 15, go ahead and unlock the bootloader and flash something current.
Click to expand...
Click to collapse
Which code would I be looking at/for?
JDKelley said:
Which code would I be looking at/for?
Click to expand...
Click to collapse
Check out the first post of this thread, it's got all the information you are looking for.
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
tsew2674 said:
Check out the first post of this thread, it's got all the information you are looking for.
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Click to expand...
Click to collapse
Sorry been away so long, been busy.
Gah, what a headache this is turning out to be! Now, I'm not sure I want to go thru with it all - perhaps I'll wait until someone comes out with a rooter for 6.0.1, instead. I'm fairly sure I'll screw something up with the rollback-root-rollup process (I think of myself as fairly technically inclined, but I've been known to screw things up on occasion. HARD. Kinda like, "You did /what/ to the entire RAID array? Really? How'd you manage /that/?")
Still says 2017-08-01 security patch, but now with Blueborne and Krack patched as well.
https://www.verizonwireless.com/support/galaxy-s5-update/
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar .md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_ Aboot.tar.md5.zip
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
stormified said:
I also received the software update notification. Now hoping someone will be able to make the bootloader friendly/no aboot version to flash...
Click to expand...
Click to collapse
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Dudash said:
Been a while since I've been to this section of the forums but I'm already uploading a Dev Friendly version and the untouched one right now.
EDIT:
@Silent Patriot
Feel free to add this to the OP.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Hi, I am running the Resurrection Remix Final N ROM on my g900v and I have this bootloader (g900vvrs2dqb2). I looked it up and saw that it was from February 2017.
I would like to update my modem and boot so I am ready for Oreo but I'm not sure best way to go about it,(Odin)?
I know this information is available on XDA and probably in this forum, but I am paranoid because I had a hell of a time unlocking the bootloader because I was fallowing old directions.
I would be very grateful to anyone willing to point me towards simple, but accurate directions.
Thanks in advance, and apologize for my ignorance!
Sent from my kltevzw using XDA Labs
Awesome! Thanks very much. I'm gonna give this a shot like the previous install/upgrade some time Friday afternoon PDT.
Jeebus I need sleep....
Can I flash this over LOS in TWRP to return to stock or do I have to use Odin?
Once flashed will the bootloader remain unlocked to allow me to reinstall LOS?
I got a new screen installed and it appears there may be an issue with how the digitizer interfaces with the software/kernal and going back to stock should update the software to allow the screen to function normally then allowing me to reflash LOS.
Hey Everyone,
Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days. The time has come to finally update my phone because some of the apps won't work anymore. I'm not into ROMs and stuff, I just want the latest firmware without all the bloatware. I had originally gone the TowelRoot method because people were having such a hard time with battery life (me included) with Lollipop. I was fortunate enough to get TowelRoot before updating to the newer version of Lollipop and went back to KitKat and I've been there ever since.
I'm currently on G900VVZW1ANCG (Kitkat 4.4.2) with root access and superuser. I have a CID 15 emmc which is a good thing from all the research I've been doing on XDA.
That's where I get stuck and confused with the newer stuff that's going on. Do I even need to unlock the bootloader?
In the end, I don't mind wiping the entire phone, I just want to get to the latest Marshmallow (which this thread seems to have) without all the bloatware or the ability to delete all the bloatware.
nickbike1 said:
Hey Everyone, Thanks for all your great work on the Galaxy S5. This thing is still kicking! I know I'm way behind on what's been going on. I'm still back on the TowelRoot days...
Click to expand...
Click to collapse
Welcome back!
You had asked some questions that is actually 2 separate ones upon themselves and I'll, hopefully, try to answer them...
Question 1: Should you unlock the bootloader?
Answer 1: The only need for anyone to require this is if they want to perform something outside the scope of just Rooting a device.
What I mean is... for example, if an individual would like to install a Custom Recovery and/or Firmware then you will need to unlock the bootloader.
Question 2: You would, ultimately, like to just debloat the Firmware?
Answer 2: Debloating Stock Firmware only requires root and not an unlocked bootloader.
The proper rooting of a device just means that you will be able to modify areas of the root directory that's restricted for devices without root and Debloating falls into this category.
Just an FYI regarding the following 2:
1) The 2 differences between the CID11 & CID15...
GS5 with CID11 = Toshiba EMMC
GS5 with CID15 = Samsung EMMC
2) There are a handful of Custom Firmwares that are based upon the stock Firmware that is already Debloated. Some of them only requires a Rooted device and Some requires an unlocked bootloader and recommends a Custom Recovery like TWRP.
This is just a brief summary to help you further but, I would recommend that you take note of/highlight the following 2threads that would be a bit more helpful depending on what your looking to do.
https://forum.xda-developers.com/showthread.php?t=2700073
https://forum.xda-developers.com/showthread.php?t=3561529
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Full System Backup method needed!
BigBird9906 said:
From this post here, I think the way to get this done for an unlocked bootloader is:
- flash the HOME_No version using Odin 3.12 AP option
- flash TWRP via Odin AP
- reinstall Magisk from TWRP and Magisk Manager.
1) Will that work?
2) What’s the most reliable tool for creating a backup—a) in case I screw up, AND b) in case everything goes well, so I can restore my apps and data into the new clean phone, preferably without screwing up the new clean phone?
I have a G900V.05 on QB2, rooted and unlocked bootloader and custom recovery, that I got to using this method by jrkruse and a false start via another method. So I’ve got Titanium Backup, TWRP, and FlashFire all in play. I'll probably shoot out backups from all of them, not sure which one restores best or if FlashFire survives the update.
Click to expand...
Click to collapse
1) -Yes, I just tried it, and it works perfectly! The only correction - you have to unzip
G900VVRU2DQL1_G900VVZW2DQL1_G900VVRU2DQL1_HOME_No_Aboot.tar.md5.zip file and flash md5 file with Odin (Odin won't work with that zip file).
2) -I have exactly the same question to fellow members - what is the current most simple and reliable method of full system backup (like ghost image for PC)? I want to try Lineage, but I already spent many hours on system customization (applications, app settings, accounts with login names/passwords, etc.). I really need some fast method to revert phone back to QL1 with all my current setup. I will flash again System and TWRP from Odin, and Magisk from TWRP. How can I then restore my full setup with one click? I used to use 'Titanium Backup' in the past, but that is not an option anymore. It freezes every time when I try to restore 'All apps with system data'
Thank you for reading that and for any possible advices.
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Nerva said:
So, if I have an unlocked bootloader, will it stay unlocked if I flash the boot from the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" version? Will it upgrade the baseband to the latest version as well?
Click to expand...
Click to collapse
If your looking for the Baseband Modem Firmware, the following link has them all for the G900V and won't affect what you have (i use them on my Unlocked G900V to update the Modem Baseband Firmware and I've got TWRP and LineageOS).
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Thanks. Are the baseband modem firmware also included in the QL1 "Developer Bootloader Friendly/No Aboot No-Wipe Firmware"? I've been told I should upgrade both my modem and bootloader, but I don't want to re-lock my unlocked bootloader.
WTF?? I was running TWRP 3.2.1.0 and crDroid 7.1.2, and I used Odin to flash the "Developer Bootloader Friendly/No Aboot No-Wipe Firmware" and checked the BL and CP options, which I thought should update just the bootloader and modem, and now it boots up with the Samsung logo and then the Verizon logo, and then just sits there. I tried to go to recovery so I could restore a backup, but it looks like the stock recovery. What did I do wrong and how do I fix it??
Since crDroid 7.1.2 is older than the bootloader, I'm wondering if that's the issue. I do have crDroid 8.1 on the microSD card. I also have TWRP 3.2.1.0 on the microSD card. So I'm wondering if I can use the stock recovery to flash TWRP. I haven't played around with custom ROM's in four years, but prior to that I did it all the time, so apparently I now remember just enough to be dangerous...
@Nerva, I apologize for the delay but, I'm curious to know where, why and what gave you the impression that you were/was required, on your your working device, to update your devices bootloader???
I'm just perplexed about this...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I went back and tried to find where I read it, and at the very least it was in this post:
godofsalt said:
Yep all true. .... But....
Once he sends you the info (model numbers and such) might want to also double check that he is on the latest firmware, for his devise. Important!
All reads good. If it's rather, "New" then, I would keep it as well.
Click to expand...
Click to collapse
I think I saw it someplace else as well, but I haven't stumbled across it -- I was posting a lot of questions in a lot of threads as well as PMing people.
Nerva said:
I went back and tried to find where I read it, and at the very least it was in this...
Click to expand...
Click to collapse
Your situation prompted me to confirm what I knew and others that you can see on the recent posts on the following thread...
https://forum.xda-developers.com/showthread.php?t=2259645
... I just wanted to state that if your devices bootloader was already unlocked and the device wasn't bricked (or similar) then you should not need to update the bootloader or it'll lock it up again and, potentially, can even cause FRP issues as well. Luckily your FRP didn't trip and the device was able to be unlocked again.
I have the same device that was unlocked a long time ago and never ever needed its bootloader updated.
Your question regarding the Baseband Modem Updates...
Those are the Modem files extracted from the stock Firmware and only updates the devices Modem. That controls the WiFi, Carrier Data, etc...
This is similar to updating the Drivers for something specific on a PC (like the PC LAN, WiFi, Video Card, etc... ).
When you had flashed what you did on your device, you basically flashed an optimized version of the Stock Firmware. This is why you saw the Samsung Boot Screen.
I hope that I had explained this okay via text...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?
It looks like this website will generate a cf-auto-root package for QL1:
https://desktop.firmware.mobi/device:840/firmware:14884
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Nerva said:
I'm curious, if the bootloader version has so little importance for us custom-ROM users, why does Samsung/Verizon update their bootloader versions -- to what purpose?...
Click to expand...
Click to collapse
I'm not stating that Bootloaders doesn't get updated upon themselves but, they specifically seldom require it.
One way to look at it is that the function of the bootloader is allot like the BIOS of a PC. They both handle the boot process and seldomly require to be updated specifically.
When a new Stock Firmware version is released, the bootloader is only updated accordingly to reflect the updates of the firmware. This reflection is to protect the device from being updated to an incompatible firmware version.
In short, when the bootloader is unlocked, the bootloader still protects the device from an incompatible firmware from being installed but, it being unlocked just bypasses the "Samsung Stock firmware only" restriction.
TWRP is just the conduit between the Firmware and the bootloader that just handles the communication between the bootloader and the Firmware.
.
I'm wondering if I flash that with Odin, would it upgrade my current unlocked QB2 to an unlocked QL1?
Click to expand...
Click to collapse
If you flash the firmware, your just going to relock your bootloader and be back to stock.
To get the QL1, just flash the Baseband Modem Update from the following link and you'll be good to go and you'll see this in your device info.
[BASEBAND-FIRMWARE-MODEMS]Verizon Samsung Galaxy S5 {SM-G900V/KLTEVZW}[ODIN] by Ibuprophen
Have I clarified this okay?
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
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