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
Related
Any way to downgrade from Nougat to MM without losing FP Sensor,Haptic Feedack&Camera
I recently purchased a new S7 not realizing that it was equipped with a Nougat OS. I would like to restore my current phone to the new one, but my current phone runs on MarshMallow. After restoring the backup, my new phone has no haptic feedback, no fingerprint sensor with "an error has occurred with the fingerprint sensor. if this message appears repeatedly, restart your phone" message and the Camera doesn't work.
I'm sure it has something to do with bootloader N using MM. Even restoring Stock Marshmallow firmware (Including BL) on the new phone removes these functions. Does anyone have any ideas on how I can get these to operate?
My current phone has
Bootloader Version: G930W8OYA2APK3 (MM)
Baseband and PDA Version: G930W8OYA2API1 (MM)
When I restore my old phone to the new one, it ends up with
Bootloader Version: G930W8OYA2BQK4 (N)
Baseband and PDA Version: G930W8OYA2API1 (MM)
EDIT: Just tried the Nougat firmware with MM Bootloader. All of the functionality is present.
Bootloader Version: G930W8OYA2API1 (MM)
PDA Version: G930W8OYA2BQK4 (N)
Just restored old backup with MM bootloader (Boot, Data, System only).
No Fingerprint Sensor or Camera.
BTW, ignore the HAPTIC FEEDBACK portion of this post. I believe it is working.
Any help with this matter would be greatly appreciated.
Not possible to downgrade since the bootloader block you from flashing lower version of that. You may try to flash without BL, but your phone will be malfunction
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Sleaze0 said:
Thank you for your reply. I don't think I'll be able to get the fingerprint wizard to work but having a functional camera would be a necessity. From the System/Priv-App folder I copied the SamsungCamera5 (from MM) and the SamsungCamera6 (from N) onto an SD Card. I guess I can try to play around with them to see if either will work, but I don't think they will since my restored backup should already have SamsungCamera5 and the SamsungCamera6 apk probably isn't compatible with MM. Kinda disappointing that I'll have to continue to use my old phone with a broken screen instead of the brand new one I purchased.
Click to expand...
Click to collapse
do not flash AP from a firmware set made prior to the bootloader youre on, it will more than malfunction, itll probably brick
i went back and read all the tl : dr stuff and saw that you seem to have got it working, oddly enough. The camera issue is likely the kernel
Thanks for the info on the thanks button. I've just about given up trying to get Marshmallow to work properly on this phone. Looks like it'll take weeks to configure my new Nougat phone to be similar to the three years of tweaks I've made to my old MM one. Oh well, first world problems I guess.
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Droiderat said:
As others have pointed out, you can't use Odin to successfully flash a ROM with a bootloader that is earlier (in version) than the bootloader you have installed. The "gatekeeper" is Odin, however, not the bootloader.
Though I haven't tried it, it is my understanding that there is a way around this. Install TWRP, and use it to install a custom ROM which uses the version of bootloader that you want/need. Once the bootloader has been rolled back, you can use Odin to reinstall Nougat (or whatever). I don't know whether this might require a particular build of Odin, but I doubt it
Click to expand...
Click to collapse
i cant even begin to imagine how/why that would work. the bootloader doesnt really care what ROM you install, its the other way around. The ROM being installed has to be compatible with the bootloader. So, installing a ROM wouldnt really do anything to the bootloader and therefore wouldnt be able to bypass the lock in knox.
The procedure I outlined apparently works where the custom ROM includes a related bootloader. Thus, when it is installed via TWRP, it replaces both the existing ROM and the bootloader. I know that TWRP can be used to install a bootloader, as I have done it (on a SM-930F). And if the gatekeeper is Odin and not the bootloader itself, then this could work.
As I stated, I haven't tried this, nor have I extensively researched it. I've only read about it, and am passing it along as a possible solution.
This post can be closed since the phone was deemed Lost or Stolen by the carrier, therefore they couldn't unlock it for me to use my SIM card. I've since returned the phone. At least I learned a few lessons for my next one. Mainly, back up the phone when you first get it. Thanks again for all of the feedback.
I have a Samsung S10e, Exynos, SM-G970F. I have unlocked bootloader, and loaded Lineage OS. I tried both Lineage 18.1 and Lineage with MicroG 18.1. I cannot place or receive calls. I am using Mint Mobile. Someone told me:
Looks like your carrier requires VoLTE which is not supported on any Samsung device running AOSP based ROMs
Is this the case?
This S10e works fine with factory firmware.
I am able to use CalyxOS on a Google Pixel 3 with the same SIM card. It works flawlessly. The S10e is much less expensive than a Pixel 5, and the Pixel 4 has too short of a battery life (unhappy with camera on Pixel 3 compared to S10e).
I am even able to root in Lineage, but not stock firmware (I cannot get the button combination right to start in Magisk root, although I have it installed). I have the August 2021 firmware, so I cannot revert back even one step. I have not found any workaround, even trying the Samsung 80% firmware (would not flash with Odin). I cannot get Flashfire to work, as the root of Magisk 23 is not supported (an earlier Magisk was, but I cannot root with that - I think 20 was the lowest that would, but it always wants to update).
I read that /e is available for my device and supports VoLTE. Is this true? It looks much harder to install - I have to use Heimdall. I used Odin and TWRP for Lineage.
Yeah, I have an SM-G970F as well, running on T-Mobile. I've loaded LineageOS with microG 18.1 on it and I also am having plenty of trouble dealing with VoLTE. I've tried so much different stuff, contacting my carrier, force enabling the VoLTE provisioning, modifying build.props - nothing. I can only receive calls over 3G, and I will get one out of every ten calls when I'm running on LTE. It's also strange to me that you can't place calls, I can do it fine, even when I'm connected to LTE - my phone just disconnects from LTE when I start the call. Does your phone not do that?
I was taking a look at /e/ OS and VoLTE compatibility myself, I couldn't really find anything about it. If you ever install /e/ OS on your S10e, please let me know if there is a VoLTE option - I'll do the same, because I'm considering installing it at this point.
Also, you don't need Heimdall to install /e/ OS. In these instructions they are just using Heimdall to install the /e/ OS Recovery onto the recovery partition, and then installing /e/ OS itself by formatting the phone and sideloading the .zip file. You can just as easily use Odin to flash the recovery partition. If you have TWRP installed you don't even need to bother with the /e/ OS Recovery (unless you really want it). You can just wipe your phone from TWRP and flash the downloaded /e/ OS .zip from there.
I just installed /e/ on my Galaxy S10e (SM-G970F) and I can confirm VoLTE isn't available. I guess it's true that AOSP ROMs on Samsung devices don't support VoLTE.
Hello,
I followed a few different guides with different methods attempting to update my Oneplus 8T KB2005 from Oxygen OS 11.0.5.6 to KB2005_11_C.11 it ending up bricking my phone and i had to Fastboot flash TWRP to get the ability to wipe my entire phone loosing all 9000 photos and other data. needless to say the phone is now working but it reverted back to 11.0.5.6 with root still just with no data apps or anything.
I would prefer to update to Oxygen OS 12 and retain root. Can someone please direct me to the best method out thats using stable build not something thats gonna potentially be causing me to send CLI commands in fastboot for next 2 hours...
Reasons for updating are the buggy VO-wifi VO-LTE and the not usable 5G.
Thanks
acidreian said:
Hello,
I followed a few different guides with different methods attempting to update my Oneplus 8T KB2005 from Oxygen OS 11.0.5.6 to KB2005_11_C.11 it ending up bricking my phone and i had to Fastboot flash TWRP to get the ability to wipe my entire phone loosing all 9000 photos and other data. needless to say the phone is now working but it reverted back to 11.0.5.6 with root still just with no data apps or anything.
I would prefer to update to Oxygen OS 12 and retain root. Can someone please direct me to the best method out thats using stable build not something thats gonna potentially be causing me to send CLI commands in fastboot for next 2 hours...
Reasons for updating are the buggy VO-wifi VO-LTE and the not usable 5G.
Thanks
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!
Sweet!I'm a newbie on the G7 side as well,and have the same Verizon variant!Sad fact,I have AT&T as my carrier and in the states I haven't seen not 1 CFW works with the service due to IMS b.s.!I did manage to switch to the Brightpoint ULM firmware and it works 100%.Good post though!Good to see others are still using the G7!
I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!
swinokur said:
I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!
Click to expand...
Click to collapse
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!
IJoxer said:
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!
Click to expand...
Click to collapse
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?
IJoxer said:
I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!
Click to expand...
Click to collapse
I wanted to add the link for the G710em30f firmware is dead in KDZ downloader.Here's an updated link to the firmware if you want to change it or if anyone else is looking for it?
LG G710EM | LG G7 ThinQ | Version: G710EM30f_00_OPEN_EU_OP_1124 | Firmware for Region: NEU from NEU/NORTHERN EUROPE - Lg-firmwares.com
LG G710EM Download the latest version of firmware | OS Version: Android 10 Q | Firmware version: G710EM30f_00_OPEN_EU_OP_1124 | NEU - Fan club LG-firmwares
lg-firmwares.com
Surgemanxx said:
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?
Click to expand...
Click to collapse
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!
swinokur said:
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!
Click to expand...
Click to collapse
It doesn't!I have have already tried it myself.Like he stated in his last post,IMS will probably never work on any custom rom.Not as of yet anyway!
Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)
swinokur said:
Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)
Click to expand...
Click to collapse
The Verizon variant is the easiest to cross flash!No partition erasing needed,and I'm using Brightpoint firmware on my Verizon variant and my carrier is AT&T.Everything works except wifi calling,but I didn't care about that anyway!As goes for CFW's,it's a lost cause at the moment in the states unless some magical trick surfaces.
First, I apologize if these answers are already posted elsewhere, in which case please point me in the right direction.
So I use to be able to root my phones with my eyes closed (back when HSPA was the fastest and I needed to overclock my single core processor to 1.2GHz because my phone didn't have 8 cores), but its been 2 years since I've rooted my one plus 9 and I was pretty rusty then so I'm pretty much lost now. I know that over the years there's been changes to the way things must be done depending on the phone, version, etc. I'm trying to update my phone to either android 12 or 13, and unless I'm mistaken, I can't just flash an android 13 custom rom over the rooted OOS rom that is stock with the exception of having Magisk of course. If that's incorrect, that would be very convenient. But if I am, what steps do I need to do to get this done? I have SDK platform-tools ready, but I no longer have backups of the stock boot.img, or anything for that matter. My mother is a hypochondriac of sorts, so I can't have my phone not work for more than a day, or I'll have the police at my door doing a wellness check. Thanks in advance for any help!
Model: LE2117
SW ver. 11.2.3.3LE54CB
Use MSM Tool to reset your phone to initial factory firmware, which is OOS11. You can then update through OTA all the way to the latest.
And next time you root your phone, DON'T flash the patched boot.img. Instead, temporarily boot by the command fastboot boot <your_patched_boot.img> and then from Magisk app, use Direct Install. That way, Magisk will backup your original boot.img which you can restore later if there is a new OTA.
Do you have a token? Get one if you dont.
unlock token - OnePlus (United States)
www.oneplus.com
Takes a couple days to a month to get it. Check back at that page, they will not notify you when its ready.
Once you get it, MSM to global base A11\OOS11 to debrand, and also allow for easier updates since Tmobile is stingy about pushing out A13 recently.
Get to latest OTA update, fastboot flash cust-unlock <unlock_token.bin> to unlock BL, install Magisk anyway you want.