Hello,
My initial plan was to switch from Oxygen OS 12 to Lineageos.
As it wasn't possible to go from OOS12 to Lineage Os directly, I downgraded to OOS11.
After installing Lineageos 13, I was not able to get mobile internet connection.
This is why I tried Pixel Experience.
Unfortunately mobile internet connection is still not possible with Pixel Eperience.
It worked with OOS12 but I haven't checked with OOS 11.
My plan was now to check, if mobile network will work again when I go back to OOS12.
But the guides regarding this failed because I don't have the "oem unlock" menu option in Pixel experience. And I am not confident if I'm doing according the right guide.
...I'm kinda stuck now because I feel as I can do nothing w/o oem unlock and I failed to get that option..
Could someone give me a hint how I can:
1) Activate OEM unlock on Pixel Pxperience (Of course only if necessary at all)
2) Get mobile network working (I assume this might be a problem of some not ROM related "Piece of software"?!)
3) Get back to LineageOS with working mobile network
Thanks in advance
One time you do the OEM unlock, this will remain unlocked until you flash the stock rom with MSM option
Yeah, some ROMs hide the OEM unlock option because there is people that try to relock BL with custom ROM and this generally causes a hardbrick.
About get network working, idk if its custom rom issue, since my op7 pro is carrier locked and im unable to unlock it, sometimes custom roms shows me like i have no sim insterted (even though I have a sim put on of course)
So, if its a recurring problem, id suggest to revert to OOS first and try again.
And since you can't unlock bootloader on OOS12 due to some issues that haven't solved, you need to do it on OOS11 or lower and upgrade to OOS12, Two times (some custom ROMS needs to have OOS12 on both partitions)
Also, LineageOS is based on OOS12, the only rom i know is based on OOS11 is YAAP. So, that's might be the issue.
I'm not that kind of expert, but maybe another user can help you better, also, sorry for my english!
Good luck c:
MSM worked for me, thanks for the help. I switched back to OOS 11 successfully. Mobile data was working there, again. After installing LOS20, mobile internet didn't work again.
Did I understand your instruction correctly?
1) LOS20
2) OOS11
3) Unlock
4) OTA to OOS12
5) LOS20
How can I go to OOS12 "two times"?
leueku said:
MSM worked for me, thanks for the help. I switched back to OOS 11 successfully. Mobile data was working there, again. After installing LOS20, mobile internet didn't work again.
Did I understand your instruction correctly?
1) LOS20
2) OOS11
3) Unlock
4) OTA to OOS12
5) LOS20
How can I go to OOS12 "two times"?
Click to expand...
Click to collapse
Basically is MSM stock rom flash first, from here, the steps should be like:
1) Update to OOS11 or stay at OOS10/9 (it depends of the MSM package you found)
2) Bootloader unlock
3) Update to OOS12
4) Use the localupdate.apk found on Oneplus forums to "update" again over OOS12, this option will install OOS12 on the inactive slot, and you will have OOS12 on both slots
5) LOS20
i know you can flash OOS12 by fastboot method, but I don't know the steps to follow in this case, but it is likely that you can get a guide here
It worked! I have now mobile internet with LOS20. Thanks a lot for your help!
Related
Greetings. After trying Derpfest on my Redmi Note 7 Pro, I decided to switch back to MiUI. I wiped out the entire Custom ROM, then installed Indian version firmware, and then installed the latest MiUI ROM in recovery mode (I prefer Orange Fox). After that, I wanted to relock my bootloader so I got the latest MiUI 11 fastboot ROM and then used MiFlash and used the clean_all_and_lock option. My device relocked it's bootloader, however, it turned out that several things like sensors or Find Device service were not working correctly. It also showed a message "Find device storage corrupted, your device is now unsafe". Looking for solutions, I ended up unlocking the bootloader again, getting back OFox, and installing the persist.img file which I extracted from my fastboot ROM. This fixed the issue with the sensors. But now, I still can't get access to services like Find Device (both from Xiaomi and Google). If I have to avoid the 'Find Device Storage corrupted' error, I have to unlock bootloader. If I have to lock bootloader, I get the error message. What am I supposed to do?
I also have tried older Fastboot ROMs, although they were all MiUI 11. Should I try fastbooting into a MiUI 10 ROM and then get OTA to do everything else? If this is the case, which specific version of MiUI 10 ROM should I flash? I can't remember which version my phone came with. My model number M1901F7S. And also, I've never used Magisk. I didn't really care if I wanted to root or not. Derpfest passed Safetynet pretty nicely. But now I do not wish to root. I don't want Magisk or anything else, I want to secure the phone just as it was before.
EDIT : Turns out that Find Device (from both Google and Xiaomi) are actually working, just in a less effective scale than what I previously used to have (before getting the custom ROM). But yet, can I bring my phone back to the locked bootloader state? I want to secure it completely, just like how it was when it came out of the box. I also cannot install apps like Netflix. I would really like to know how to relock my bootloader.
EDIT 2: I've fixed it. Indeed, I had to flash a stock MiUI 10 ROM. Version 10.0.2 and whatever number ahead worked for me and gave me no problems, and then I simply updated to MiUI 11 using OTA Updates.
However, I do not recommend using MiFlash tool, and instead recommend pasting the ROM files into your platform_tools folder and then running flash_all_lock/flash_all. MiFlash may sometimes glitch and cause problems.
Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.
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 just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
drift08 said:
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. Use Swift Backup. However, you will have to move all your data to a PC because it'll wipe when you go back to 11.
2. No. You'll have to unlock it again. Don't move your data back until after you unlock the bootloader though as it factory resets as part of it.
3. I rooted. My big thing is Gravity Box and ad blockers. Stayed with OOS though. Others are too much hassle compared to previous OPs. xXx (Magisk Rom) from the 7 and 8 days still works fairly well on 11. It hasn't been updated, but it also don't touch anything underneath. If you don't like it, it's easy to get rid of. It's customizable by a text profile you edit.
4. Not that I know of. I believe OP has gone on to A12. If you root, you can't take OTAs, you have to have full images. You can download them from one of the stickies.
drift08 said:
I just brought an unlocked Oneplus 9 and using it on T-mobile network. I am having the following problems with Android 12 (OOS LE2115_11_C.61). I am wondering if Android 11 have these problems as well or not (only had the phone for less than 2 days).
1. Wifi Calling: Able to dial call but unable to hear audio from the other party. However, they can hear me w/o any issues. Tried resetting my network, it didn't resolve this issue. Currently using phone w/ wifi calling off.
2. Lockscreen Issue: There are no option to hide the actual pattern lock and also the pattern lock placement seems to moved further up on the screen.
3. Battery charging time no longer indicates on the lockscreen.
4. Sometimes the "Close All" button only closes all other apps besides the last one I were on. Sometimes it works. So, it's random.
If downgrading to Android 11 resolve some of the above issues, I have the following questions about the downgrade.
1. Is there a way to back up all my apps and app data locally and restore it after downgrade (like Tatinium Backup)?
2. Does downgrade require unlock bootloader?
3. If unlocked bootloader, would you suggest root, go for a custom rom or stay with OOS 11?
4. If downgrade to OOS 11, is there a way to keep security update w/o going to Android 12?
Thanks in advance!
Click to expand...
Click to collapse
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
DarkPaladinZant said:
1. If you use the local back up option under settings > system settings > back up and reset > local backup then most of your apps get backed up, but the downloaded data will not be saved and you have to log into the accounts on each app. I'm still looking for another way to backup, but I'm hesitant because this method of backup retains my T-Mobile SIM settings after I converted it to Global.
2. I was on OOS 12.41 on a T-Mobile branded OP9, and when I used @craznazn 's MSM conversion tool, it downgraded my phone to Global OOS 11.2.2. I suppose if you wanted to downgrade you could use his tool, or any MSM tool made for a T-Moble version on OOS 11, and it would boot that version, and then you could update to the latest 11.
3. I would suggest root if you have your bootloader and sim unlocked, if not, I would just stay on a stable version of OOS since you wouldn't be able to flash under fastboot or anything of the sort.
4 I don't think OP is doing security updates for the OP9 on 11 since it supports 12, but the option to go back is always there via MSM conversion through EDL mode on your phone.
Click to expand...
Click to collapse
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
AtoZ0to9 said:
Swift Backup is great for backing up the stuff that you'll want to save, such as Messages, Call Logs, Apps + App Data, some other things. Root is required for the App data backup, otherwise you can still use it for most functions without being rooted, or to enable more backup features without root, you can adb grant SECURE_WRITE to the app. Definitely worth checking out.
Click to expand...
Click to collapse
Oh wow yeah I'll definitely have to check it out! I've been testing my OP9 going back and forth from Tmo to Global to find the most reliable way to get there with the modem still intact, as I'm still a couple of days away from getting my unlock token.
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​