I used a rooted Moto G7 on T-Mobil for quite a while. But it is now giving me some issues and I'm considering buying a 2021
Motorola One 5G Ace | 2021 from AmazonFor $299
https://www.amazon.com/gp/aw/d/B08NWD7K8H/ref=ox_sc_act_image_1?smid=ATVPDKIKX0DER&psc=1
I have a few questions.
1. Anyone using T-Mobil with this phone? Any problems? Special simcard for 5G or will my G7 simcard work?
2. Bugs or problems with the Motorola one 5G 128GB?
3. Does it come with android 10 or 11?
4. How easy to root?
Thank you.
maybeme2 said:
I used a rooted Moto G7 on T-Mobil for quite a while. But it is now giving me some issues and I'm considering buying a 2021
Motorola One 5G Ace | 2021 from AmazonFor $299
https://www.amazon.com/gp/aw/d/B08NWD7K8H/ref=ox_sc_act_image_1?smid=ATVPDKIKX0DER&psc=1
I have a few questions.
1. Anyone using T-Mobil with this phone? Any problems? Special simcard for 5G or will my G7 simcard work?
2. Bugs or problems with the Motorola one 5G 128GB?
3. Does it come with android 10 or 11?
4. How easy to root?
Thank you.
Click to expand...
Click to collapse
1. Not on t-mobile.
2.I didn't find any bugs. I bought the retail us version.
3.It comes with 10. I am running 11 from Canada.
4. Root is easy, but not complete. You also need to get r/w access which is complicated but easy. Also any debloating requires the use of pm from an ADB shell or as a terminal command. There are good guides here on how to do all of this.
Custom ROMs are available, more on the Telegram channel.
Thank you Retief.
I went ahead and bought one and am setting it up.
One problem I'm facing is the touch screen is too sensitive. If I tap too forcefully near the top of a screen everything gets minimized (I forget the correct name for it). It's most annoying. Any ideas? Sensitivity controls?
Also, any way to get rid of the notch?
Thanks.
Mine is a usa T-mobile motorola moto one 5g ace, android 10, software variant t, model number xt2113-2, purchased April 20, 2022 from a T-mobile store. My old sim card would not fit. It's loaded with bloatware. I am also trying to root but its going to take some time to gather up all the correct programs and files so it doesn't brick. There's a Noob guide on this forum that offers great advice on how to root. I'll read it 5 more times before I do anything. If you do manage to root your phone please let us know how you did it.
I am rooted, r/w access obtained and debloated. I used the three guides on here.
RETIEF said:
I am rooted, r/w access obtained and debloated. I used the three guides on here.
Click to expand...
Click to collapse
That's terrific RETIEF.
Which 3 guides in here?
Did you hit any problems and if so how did you solve them?
Thanks.
The guides are in the guides section. The ones by Artcul8madness worked. Now that there is a working twrp, other methods are possible. You must unlock the bootloader first! I had no problems following the guides.
Thanks. Still a risky thing with bootloops, etc. I think I'll wait for the ota updates to Android 11 or 12.
I picked up one of these earlier this week (variant XT2113-2, 128GB just like yours) and am using it on T-Mobile in the US. It's working really well, no issues so far, and the 5G feels incredibly fast (it's my first 5G device - if speedtest.net is reliable, I'm consistently seeing >125Mbps download speeds in Los Angeles).
I specifically bought this phone to use with LineageOS, and the bootloader unlocking procedure and rooting went very smoothly. No issues at all so far with the device, LineageOS, or the unlocking/rooting.
Just as an aside, I opted for a used model off of Ebay, and they're going for between $150-$200 with the 128GB of storage ROM if you'd like to save some money.
Thank you for getting back to me. I too am well pleased with the phone and its performance.
I have been afraid to root it yet because of problems I read about.
1. How —exactly— did you root it?
2. Ive used lineageos on a previous phone. How well is it working for you on this phone?
maybeme2 said:
Thank you for getting back to me. I too am well pleased with the phone and its performance.
I have been afraid to root it yet because of problems I read about.
1. How —exactly— did you root it?
2. Ive used lineageos on a previous phone. How well is it working for you on this phone?
Click to expand...
Click to collapse
Apologies for the delayed response, I thought I was set to receive email notifications for replies! I actually rooted it while flashing LineageOS - I first unlocked the bootloader by following the instructions on the LOS install page (https://wiki.lineageos.org/devices/kiev/install), then flashed Lineage Recovery via fastboot. From there, I rebooted into Lineage recovery (NOT the OS/system, it'll overwrite the new recovery), flashed the LineageOS ROM, then followed that with GApps and Magisk.
See the link I posted, you'll root it at step 6 under "Installing LineageOS from recovery". Download Magisk from here: https://github.com/topjohnwu/Magisk, rename the .img file it gives you to a .zip, and you'll be able to flash it at Step 6 above via sideloading or over a microsd, same with google apps.
Lineage is working well so far! The only quirk is that the lockscreen likes to randomly wake up, but I'm not sure if that's just my secondhand phone's fault. Wifi calling and VoLTE all work on TMobile.
Let me know if I can be of any more help!
Thank you for getting back to me. You are very kind and helpful.
When I get enough courage I'll follow in your steps.
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
DISCLAIMERAnything you do to your own device is your responsibility and your responsibility only. You may NOT hold me responsible for any damage caused to your device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
The only official site with proper instructions to install LineageOS is https://wiki.lineageos.org/. Any instructions that come from anywhere else is not to be trusted at all.
You should especially distrust instructions from websites that try and impersonate LineageOS. One example of such a site is lineageosroms[.]com.
InstructionsScroll down to the 2nd post in this thread for installation and upgrade information.
Reporting BugsPlease follow the instructions here to report your bug to our GitLab issues if you can, as it makes it easier for us to keep track of bugs and progress on fixing them.
However, should you be unable to do so and must post your bug report in this thread instead, then please adhere to the following guidelines:
DO NOT Report bugs if you're running a custom kernel, have installed Magisk, Xposed, or have done modifications to your device that touch any of the read-only partitions (with GApps being the only exception).
As this is an A/B device, recovery will not run addon.d scripts. As such, try undoing all the modifications by reflashing the rom + GApps (if you used them) in recovery--no need to wipe data. After that, check to see if the bug is still there.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Telegram Chat:I have a Telegram group that you can join if you prefer to chat that way, as opposed to posting on a forum thread. Join here.
Supported models:The only officially supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported, as that's what I did my device bringup against.
IN2019 (Verizon) is not supported. VZW sensor configs are not bundled in this ROM, so accelerometer/gyroscope and magnetometer readings are going to be incorrect. In addition, battery gauge reading seems to be broken, based on one user trying this ROM on their IN2019 despite it being unsupported. I am likely not going to fix this anytime soon, as I do not have an IN2019 to validate my fixes against.
LineageOS 18.1 Upgrade Notes:If you are coming from LineageOS 18.1 (and thus using LineageOS 18.1 Recovery), then follow the instructions here to upgrade. We ship the needed firmware in our OTA zips, so you do not have to worry about updating to OOS 12 firmware first. Remember to reflash Android 12 GApps if you used GApps previously.
New Installation Notes:We now ship the required firmware in our OTA zips. However, LineageOS 19.1 Recovery will likely not boot on a device that that has OxygenOS 11 firmware, due to the significant number of changes between OxygenOS 11 and 12 after the OPlus merge. Since we no longer provide images for LineageOS 18.1 Recovery, you will need to follow the recommendations below before preparing to install LineageOS. Once you follow said recommendations, then head over here to install LineageOS 19.
IN2010 (China)Ensure you've installed any version of ColorOS 12 on the active slot on your device. The bootloader passes over information to the kernel via qcom smem, but in some older versions of COS 12, the format of the sensor info being passed in may be incompatible with what the recovery's Linux kernel expects. This ends up causing the kernel to stop reading the rest of smem, meaning it won't read the device project number. As a result, the kernel will end up not loading drivers for much of the hardware, including touchscreen and audio.
Fortunately, LineageOS Recovery is still able to run even with those missing drivers. Navigate through the menus by using the volume buttons and power key.
IN2011 (India) · IN2013 (Europe/Asia) · IN2015 ("Global"/NA)Ensure you've installed any version of OxygenOS 12 on the active slot on your device. The bootloader passes over information to the kernel via qcom smem, but in OOS 12 11_C.16 and earlier, the format of the sensor info being passed in will be incompatible with what the recovery's Linux kernel expects. This ends up causing the kernel to stop reading the rest of smem, meaning it won't read the device project number. As a result, the kernel will end up not loading drivers for much of the hardware, including touchscreen and audio.
Fortunately, LineageOS Recovery is still able to run even with those missing drivers. Navigate through the menus by using the volume buttons and power key.
IN2017 (T-Mobile)Ensure you've installed any version of OxygenOS 12 on the active slot on your device. If you've been using the T-Mobile version of OxygenOS all this time, then fortunately, you can expect LineageOS Recovery to just work fine on your device with no issues.
If you did any of that EU / Global conversion previously, then check the info for IN2011/IN2013/IN2015 instead.
Spoiler: Old Info (kept for historical reasons)
IN2010 (China)Follow the instructions for IN2013. Another user (@cinnamonizer) tried running LineageOS 19 on ColorOS 12.1 C.32 firmware, and while it was working for the most part, their fingerprint sensor would periodically have trouble trying to recognize their finger. That problem seeemed to have gone away when they migrated to IN2013 firmware.
IN2011 (India)If you're coming from Oxygen OS: you need to OTA update to IN2011_11_C.33 or IN2011_11_C.35 to run LineageOS. Grab your OTA zip from this thread.
If you're coming from LineageOS 18.1: Download your firmware zip from here (thanks LuK1337) and follow this guide to flash the updated firmware.
IN2013 (Europe/Asia)If you're coming from Oxygen OS: you need to OTA update to IN2013_11_C.33 or IN2013_11_C.35 to run LineageOS. Grab your OTA zip from this thread.
If you're coming from LineageOS 18.1: Download your firmware zip from here (thanks LuK1337) and follow this guide to flash the updated firmware.
IN2015 ("Global"/NA)If you're coming from Oxygen OS: you need to OTA update to IN2015_11_C.33 or IN2015_11_C.35 to run LineageOS. Grab your OTA zip from this thread.
If you're coming from LineageOS 18.1: Download the firmware zip for IN2011_11_C.33 (not a typo) from here (thanks LuK1337) and follow this guide to flash the updated firmware. The firmware + modem partitions for IN2011 and IN2015 are bit-for-bit identical. IN2013's firmware has a different bootloader, but you can flash IN2013 firwmare on IN2015 and it will still work just fine.
IN2017 (T-Mobile)After some investigation from b`owow in the Telegram group chat, it seems that no matter whether you convert to Global/EU firmware on OOS 10, OOS 11, OOS 12, or while upgrading between LineageOS 18.1 to 19, you will have working modem functionality. Maybe something changed with 11_C.33, because both b`owow and I distinctly remember that this used to not be the case. In any case, go follow the instructions for IN2011, IN2013, or IN2015. Only thing different between the three regions' firmwares is just the abl partition, and even then, Global and India have the same abl.
Spoiler: Old IN2017 info
Note: This is old, outdated info for the IN2017 model. It is being kept here for historical reasons, and the text has been struckthrough to emphasize that this is no longer relevant information.
So, I actually did my bringup work against an IN2017, so despite this model not being officially supported, I can at least say that I unofficially support this model with our official builds. However, I migrated over to the IN2015 firmware back on OOS 10 and OTA updated to OOS 11 from there, allowing me to use IN2011/IN2013/IN2015 firmware on my IN2017. Since then, I'm currently running IN2013's OOS 12 firmware on my IN2017 right now.
I've only ever tested running LineageOS 19 on IN2011/IN2013/IN2015 firmware on my IN2017 OnePlus 8. As such, I will expect for you to run IN2011/IN2013/IN2015 firmware on your IN2017 when using LineageOS. Follow the appropriate steps based on the answer to these questions: "Did you migrate to IN2011/IN2013/IN2015 OOS back when you were on OOS 10? And if you did, did you flash the IN2011/IN2013/IN2015 modem too before OTA updating to OOS 11 or later?":
If you answered yes to both questions, then treat your IN2017 like it's an IN2011/IN2013/IN2015 (depending on which one you prefer) and follow the instructions for that model instead, as both models' firmware will work on your IN2017, modem included.
If you answered no to either question, then you can still follow the instructions for IN2011/IN2013/IN2015, even if you're migrating over form IN2017 OOS 11/12, but you will lose cellular connectivity if you try flashing the modem from IN2011/IN2013/ IN2015. Flash the firmware for IN2011/IN2013/IN2015, but skip flashing the modem. Instead, extract the modem image from the latest IN2017 OTA (IN2017_11_C.41 as of 2022-08-28) and flash that on your IN2017.
Currently Known BugsOccasional 1-2 second freezes when waking the device from sleepSometimes, when you wake the device, you can see the display seemingly freeze for 1-2 seconds while it's fading in the lockscreen. Unfortunately, I don't know why that happens, and I don't think I'll be able to fix that myself anytime soon.
HDMI/DisplayPort out does not workOnePlus seems to have changed something in the OOS 12 kernel source, since HDMI/DP out is broken on stock OOS 12 too...
Fixed in lineage-20:
https://github.com/LineageOS/android_kernel_oneplus_sm8250/commit/f72ba01bae6522fbf1fa8a11fea933df58935ba7
This will not be picked into lineage-19.1, since that will reach EOL for this device soon.
Light sensor readings do not filter out light coming from the screenThe light sensor is embedded underneath the screen. On OOS, they use some algorithm to determine how much of the light detected by the sensor is actually coming from the display itself, and then subtract that value from the reading. We currently don't have anything to handle that for this LineageOS build. Some people have tried developing their own algorithm for this on the OnePlus 7 series of devices, but apparently, it doesn't work that well, so it was never brought over to the OnePlus 8 series of devices. In addition to that, novenary was reverse engineering OnePlus's implementation, but they stopped working on that since they no longer daily drive their hotdogb.
As such, expect Adaptive Brightness to be very much unusable, as the feedback loop caused by the light sensor sensing the light from the screen will result in Adaptive Brightness increasing the brightness all the time.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 90° and 270° screen rotationsFor both 90° and 270° (both of which are landscape orientations), the HWC layer for the UDFPS circle doesn't get excluded from the dimlayer, and as such, it doesn't end up illuminating bright enough to scan your finger. The circle is still positioned in the right place, so there could still be a possibility that one could figure out how to fix this.
UDFPS (Under-display Fingerprint Sensor) doesn't work properly in 180° screen rotationFor 180° (upside-down), not only is the auth dialog window in the wrong place, but the UDFPS circle doesn't even show up. This will not be fixed.
Ambient Display (Always-on Display) may not work properly if panel can't freely switch between 60Hz and 90HzWith Ambient Display enabled, when you "turn off" the screen, the panel will first show the Ambient Display info at normal brightness before turning off for a few seconds. Afterwards, it turns back on, but in a mode that has the touchpanel running in screen-off mode. If you have your panel forced to 60Hz or 90Hz only, then the panel will not turn back on for Ambient Display.
While WiFi calling is enabled, VoIP calls (Google Voice, TextNow, etc.) starts stuttering frequently on WiFiA few hours after turning on WiFi Calling on the OnePlus 8, you'll likely notice that VoIP calls on apps like Google Voice and TextNow will seem to stutter while on WiFi, getting to the point where the call is unstable and neither party can really talk to each other. This bug is related to IMS making the cnd daemon from qcom's CNE request WiFi ext stats every two seconds. A race condition in the qcacmn kernel driver could end up happening during one of these requests, which potentially leads to every subsequent ext stats request timing out after waiting for 1.5 seconds. During that 1.5 second period, VoIP packets seem to get dropped entirely. This issue has been present since LineageOS 18.1, it seems.
I do have code that works around this race condition, but I don't think it's ready to review yet because I'm still trying to learn more about the qcacmn driver. I will update this space with more info when ready.
Spoiler: Old Bugs
Lowered brightness when switching between SDR color profilesIf you have turned your display off and back on at least once ever since booting up your phone, you will find that if you switch to any SDR or HDR display color profile at any point (such as going to Settings -> Display -> Colors and changing settings there, or watching an HDR video on YouTube), then your screen brightness will suddenly be lowered until next reboot. If you were watching an HDR video when the brightness got lowered, then you'll also find that if you switch back to an SDR color profile (by closing the video) and then switch back to an HDR color profile (by opening the video again, your brightness gets restored back to how it originally was. However, as soon as you switch back to an SDR color space (by closing said HDR video), then your brightness gets lowered again.
This issue might be related to Pixelworks Soft Iris, but I have not yet looked far enough to figure out more details about why this is broken or how to fix it. If this issue annoys you enough, you can flash a modified boot.img that contains this change. This will break the ability to change SDR color profiles, but switching to an HDR color profile will still work and will not mess up your screen brightness. Download the boot image here.
Fixed since the 2022-10-22 build with the following change:
https://review.lineageos.org/c/LineageOS/android_device_oneplus_sm8250-common/+/341740
USB-PD charging does not charge at full speedThe phone seems to end up only negotiating 5V 2A (10W) no matter what. This is broken on stock OOS 12 too.
Fixed since the 2022-11-26 build with the following changes:
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/344679
https://review.lineageos.org/c/LineageOS/android_kernel_oneplus_sm8250/+/344680
The phone will charge at full speed with USB-PD only when screen is off.
jabashque said:
(Reserved post, will contain misc info about supported models and other stuff)
Until I have the time to flesh this out, here's a quick summary:
The only official supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported; in fact, that's what I'm using right now. However, I am currently running IN2013's OOS12 fw on my phone instead of IN2017's, so if you wish to stick with the T-Mobile firmware, you will be on your own.
IN2019 (Verizon) is not supported. However, if this ROM somehow boots on your IN2019, then do let me know. I can then revert a change that dropped sensor configs for IN2019 if that's the case.
Click to expand...
Click to collapse
How did you manage to update your firmware to OOS12? I tried the instructions on the lineage wiki page for the device and it led me to links that downloaded OOS11 firmware.
DEM0N Assissan7 said:
How did you manage to update your firmware to OOS12? I tried the instructions on the lineage wiki page for the device and it led me to links that downloaded OOS11 firmware.
Click to expand...
Click to collapse
Head over to this thread and grab the OTA package for IN2013_11.C.33 to run the latest EU fw on your OnePlus 8. I would say that the oldest you can run on your OnePlus 8 is maybe 11.C.16?
(Also, note that you can run EU fw on devices from other regions.)
jabashque said:
Head over to this thread and grab the OTA package for IN2013_11.C.33 to run the latest EU fw on your OnePlus 8. I would say that the oldest you can run on your OnePlus 8 is maybe 11.C.16?
(Also, note that you can run EU fw on devices from other regions.)
Click to expand...
Click to collapse
So, for some odd reason, whenever I try to do any of the "fastboot flash __ ___.img" commands, it says "Flashing is not allowed for Critical Partitions," but I have already unlocked my bootloader and done `fastboot flashing critical_unlock` and it was unlocked (when i try to do that command it says "Device already : unlocked!"). I have been totally puzzled by this. Is there something I have to do in particular or am I plum out of luck?
jabashque said:
Head over to this thread and grab the OTA package for IN2013_11.C.33 to run the latest EU fw on your OnePlus 8. I would say that the oldest you can run on your OnePlus 8 is maybe 11.C.16?
(Also, note that you can run EU fw on devices from other regions.)
Click to expand...
Click to collapse
Just upgraded from 18.1 to 19.1 following the manual upgrade guide and the suggested IN2013_11.C.33 OTA package. No data loss and everything working at the first try, kudos for the great work
DEM0N Assissan7 said:
So, for some odd reason, whenever I try to do any of the "fastboot flash __ ___.img" commands, it says "Flashing is not allowed for Critical Partitions," but I have already unlocked my bootloader and done `fastboot flashing critical_unlock` and it was unlocked (when i try to do that command it says "Device already : unlocked!"). I have been totally puzzled by this. Is there something I have to do in particular or am I plum out of luck?
Click to expand...
Click to collapse
If you're following the instructions at https://wiki.lineageos.org/devices/instantnoodle/fw_update, you will notice that it tells you to "Go to “Advanced” -> “Enter fastboot”", along with a warning that "it cannot be substituted with “Reboot to bootloader”". The fastboot implementation in OnePlus's bootloader blocks you from flashing critical partitions no matter what, hence why the instructions tell you to tap on "Enter fastboot", which launches fastbootd instead.
jabashque said:
If you're following the instructions at https://wiki.lineageos.org/devices/instantnoodle/fw_update, you will notice that it tells you to "Go to “Advanced” -> “Enter fastboot”", along with a warning that "it cannot be substituted with “Reboot to bootloader”". The fastboot implementation in OnePlus's bootloader blocks you from flashing critical partitions no matter what, hence why the instructions tell you to tap on "Enter fastboot", which launches fastbootd instead.
Click to expand...
Click to collapse
Thank you so much man. I totally forgot about the fastbootd thing. I will flash the LOS 18.1 recovery and do that from there. That step totally flew over my head.
jabashque said:
(Reserved post, will contain misc info about supported models and other stuff)
Until I have the time to flesh this out, here's a quick summary:
The only official supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported; in fact, that's what I'm using right now. However, I am currently running IN2013's OOS12 fw on my phone instead of IN2017's, so if you wish to stick with the T-Mobile firmware, you will be on your own.
IN2019 (Verizon) is not supported. However, if this ROM somehow boots on your IN2019, then do let me know. I can then revert a change that dropped sensor configs for IN2019 if that's the case.
Click to expand...
Click to collapse
Awesome that OnePlus 8 finally has official 19.1, but why can't you flash on IN2017 if IN2017 to IN2015 firmware conversion is possible? You know what I'm gonna test this on my IN2017 and I'll tell you guys if it works or not.
jabashque said:
If you're following the instructions at https://wiki.lineageos.org/devices/instantnoodle/fw_update, you will notice that it tells you to "Go to “Advanced” -> “Enter fastboot”", along with a warning that "it cannot be substituted with “Reboot to bootloader”". The fastboot implementation in OnePlus's bootloader blocks you from flashing critical partitions no matter what, hence why the instructions tell you to tap on "Enter fastboot", which launches fastbootd instead.
Click to expand...
Click to collapse
Update: It worked, I'm sending this message using my One plus 8 using your ROM. Thank you so much for your work on this and I cannot thank you enough. Do you have a place to receive donations or anything like that?
thattechguy_69 said:
Awesome that OnePlus 8 finally has official 19.1, but why can't you flash on IN2017 if IN2017 to IN2015 firmware conversion is possible? You know what I'm gonna test this on my IN2017 and I'll tell you guys if it works or not.
Click to expand...
Click to collapse
EDIT: my apologies... I confused IN2017 (T-Mobile) for IN2019 (Verizon). In that case... my 2nd post mentions that I am in fact running this on an IN2017 w/ IN2013 fw. However, it should be noted that even then, my phone reports itself as project number 19855 instead of 19821.
Original message is as follows (now corrected):
The main reason is that for the OOS 12 kernel source, OnePlus didn't release kernel dts for project 19867, which corresponds to IN2017 IN2019. The dts in the OOS 11 kernels sources included some changes that were specific to the IN2017 IN2019, so that worked fined, but there is none for the OOS 12 kernel source.
I could look at the OOS 11 kernel dts and try to figure out what IN2017 IN2019 changes there are, and then create a new 19867 dts directory in the OOS 12 kernel source source with those changes (if any). However since I don't have an IN2017 IN2019 (and neither does anyone else in LineageOS), I can't test to see if my changes would work. As such, I can't even declare unofficial support for IN2017 IN2019.
DEM0N Assissan7 said:
Update: It worked, I'm sending this message using my One plus 8 using your ROM. Thank you so much for your work on this and I cannot thank you enough. Do you have a place to receive donations or anything like that?
Click to expand...
Click to collapse
That's good to hear! I don't accept any donations at this time.
jabashque said:
(Reserved post, will contain misc info about supported models and other stuff)
Until I have the time to flesh this out, here's a quick summary:
The only official supported models are the following:
IN2010 (China)
IN2011 (India)
IN2013 (Europe/Asia)
IN2015 ("Global"/NA)
IN2017 (T-Mobile) is unofficially supported; in fact, that's what I'm using right now. However, I am currently running IN2013's OOS12 fw on my phone instead of IN2017's, so if you wish to stick with the T-Mobile firmware, you will be on your own.
IN2019 (Verizon) is not supported. However, if this ROM somehow boots on your IN2019, then do let me know. I can then revert a change that dropped sensor configs for IN2019 if that's the case.
Click to expand...
Click to collapse
I have an IN2019 and was able to get it to boot by following the instructions on the wiki for the other models. However, RN it barely functions at all, the sim card isn't detected and if you disconnect it from power while in lineageos it shuts down because it can't tell how much juice the battery has. If you could revert those sensor changes, I'll give it a shot asap. hopefully that will at least let battery charge and mobile network function because otherwise it seems to work fine, similar to 18.1 where you could just flash the ROMs for other models and the only thing you lost was mmWave, which IDK about anyway.
Jeeves-2 said:
I have an IN2019 and was able to get it to boot by following the instructions on the wiki for the other models. However, RN it barely functions at all, the sim card isn't detected and if you disconnect it from power while in lineageos it shuts down because it can't tell how much juice the battery has. If you could revert those sensor changes, I'll give it a shot asap. hopefully that will at least let battery charge and mobile network function because otherwise it seems to work fine, similar to 18.1 where you could just flash the ROMs for other models and the only thing you lost was mmWave, which IDK about anyway.
Click to expand...
Click to collapse
When I say sensors, I'm talking about accelerometer/gyroscope and magnetometer showing the wrong orientation without the configs from Verizon Oxygen OS. If battery percentage cannot be detected, then that's a whole 'nother issue entirely.
That being said, try reflashing the modem from VZW OOS 11 and seeing if that helps for detecting the sim card. I can't do much for fixing battery detection unless I spend the time to trawl through the OOS 11 dts, which, given that I don't have a VZW OnePlus 8 to test against, that's kinda low on my priority list.
I've been using LineageOS for years now; thanks for bringing 19 to the OP8. Have you tried installing magisk yet? I can't seem to get it working. Neither flashing in recovery nor booting a patched image (extracted from installation zip) works.
Thank you!
KerbalNo15 said:
I've been using LineageOS for years now; thanks for bringing 19 to the OP8. Have you tried installing magisk yet? I can't seem to get it working. Neither flashing in recovery nor booting a patched image (extracted from installation zip) works.
Thank you!
Click to expand...
Click to collapse
I have not tried installing Magisk yet actually, and well, technically, that would be out of scope of LineageOS anyway. But since I'm curious, I'd like to know what you end up seeing whenever you try to sideload the Magisk zip in Lineage Recovery or flash the patched boot image.
jabashque said:
I have not tried installing Magisk yet actually, and well, technically, that would be out of scope of LineageOS anyway. But since I'm curious, I'd like to know what you end up seeing whenever you try to sideload the Magisk zip in Lineage Recovery or flash the patched boot image.
Click to expand...
Click to collapse
The phone gets stuck on the boot animation. Not exactly a bootloop because it doesn't restart, but pretty close.
KerbalNo15 said:
The phone gets stuck on the boot animation. Not exactly a bootloop because it doesn't restart, but pretty close.
Click to expand...
Click to collapse
As was likely the case, it was my fault. All my old magisk modules were still installed and some of them are now incompatible. I was able to install magisk after using the ADB instructions here: https://topjohnwu.github.io/Magisk/faq.html
jabashque said:
When I say sensors, I'm talking about accelerometer/gyroscope and magnetometer showing the wrong orientation without the configs from Verizon Oxygen OS. If battery percentage cannot be detected, then that's a whole 'nother issue entirely.
That being said, try reflashing the modem from VZW OOS 11 and seeing if that helps for detecting the sim card. I can't do much for fixing battery detection unless I spend the time to trawl through the OOS 11 dts, which, given that I don't have a VZW OnePlus 8 to test against, that's kinda low on my priority list.
Click to expand...
Click to collapse
actually I used an app called "Sensors multitool" to figure out the battery issue, and it showed the acclerometer and gyroscope working perfectly, as well as the magnotometer. GPS didn't appear to work though, so I think you're right about needing some of the drivers from the verizon oneplus 8 rom. However, I'm struggling to find where to download them. Oneplus doesn't offer downloads for the IN2019, and as far as I can tell, neither does verizon except through their OTA updater. is there any way you know of to find a image, or am I sol?
Edit: nevermind, may have found it in the guide for unlocking the bootloader for the IN2019. thank you so much for the advice
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.