Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
AndyYan said:
You don't have A11 firmware anymore, which I guess is also why you can't boot stock A11 now. Updates can update more than what the A/B slots cover.
Click to expand...
Click to collapse
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
androidloyal said:
you mean a11 just disappeared from the other slot? i could reflash it but i'm scared, i guess if everything is in separate slots then i can't mess up alot tho
Click to expand...
Click to collapse
Only some partitions remain, not enough to cover the "firmware" part. Just find a Windows PC to MSM with.
androidloyal said:
Hey, I'm trying to downgrade my phone so I can use Lineage. I only have access to Linux and can't get Virtualbox to work, so I'm pretty sure MSM tool is out of the question. I've updated my phone to Oxygen 12, but Oxygen 11 is still in the other slot. I did try switching slots to get on Android 11, but it wouldn't boot, even after I cleared the userdata partition. Now that I think about it, would I even need to boot the device to install Lineage, or would I just need to have Android 11 installed and be able to use the bootloader with fastboot commands? Or if I would need to boot, how would I get Oxygen 11 fully working?
(Also, it's T-Mobile firmware, so I also can't downgrade with their official app)
Click to expand...
Click to collapse
you should downgrade with the T-Mobile MSM tools. Note that your data will be wiped, so make sure you have a backup if you want one!
Related
So I just unpacked my MOTO Z with great anticipation.
However, I immediately ran into the issue where I can't backup my old phone using TiBU and restore it on my new shining gadget. I was VERY unsuccessful rooting the device.
So I went all in and installed RR which I'm using on all other devices as well. Used this TWRP to do it.
While RR is working well, it doesn't have some of the nice things stock ROM had, like the keyboard adjustability, screen on on hand-over and some adjustments in the camera app. Doesn't really matter, but I'd like to give stock another try before I inevitably commit to RR which will no doubt improve in the mean time as well.
Now, for my problem:
Using the recovery mentioned above, I made a full backup of the phone before I messed with it. Now that same recovery doesn't properly restore that backup: the phone doesn't boot when I restore that backup. it never leaves the bootloader unlocked warning screen.
So I figured: bad backup, let's get a stock image. Eh, again no go: motorola doesn't even publish those. So I grabbed the XT1650-03_GRIFFIN_RETEU... from here.
That one again doesn't even fully flash: I tried partial flash (system partition + recovery partition) - which flashed but didn't boot; then tried full flash, starting with the gpt.bin - but this one didn't even flash. reported some errors and that was it.
So, while not bricked, I'm far from any degree of control over my new phone. I'd like to improve that!
Any advice?
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
lollyjay said:
@velis74 to flash firmware you must use adb/fastboot. Is that what you mean by "flashed"?
Click to expand...
Click to collapse
Yes, "flashing" of the "stock image" I tried to do with fastboot - that series of commands flashing one partition after another with images in the archive. I just didn't want to list all those commands in the post because there's more than 20...
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
doree said:
If you´ve already updated your Stock, untouched and locked ROM from Marshmallow to Nougat, then you won't be able to Flash back to Marshmallow Stock ROM, because your Bootloader was already updated to Nougat. That's why the whole process fails. Since there's no official RETEU Nougat Stock ROM yet, use the RETBR one. It's practically the same and works as it should: https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
But keep in mind that you won't be able to relock your bootloader, since Motorola/Lenovo haven't released signed Nougat Stock ROMs yet.
Click to expand...
Click to collapse
Yep, was just about to post how this thread helped. I'm back at stock and seriously contemplating not rooting. I pretty much only need it for one app where I forgot the password and they make it REALLY hard to reset it
Hi!
I have a VS996 with an unlocked bootloader and TWRP. I went from stock, did a full wipe (Dalvik, System, Data, Internal Storage, Cache), and tried flashing Havoc-OS (Android 10) and had issues with connecting to Wifi. So I went back to JohnFauxes VS996 flashable and now I don't have data or a working camera. Not sure what's going on here. Ideas?
TheCoryGuy said:
Hi!
I have a VS996 with an unlocked bootloader and TWRP. I went from stock, did a full wipe (Dalvik, System, Data, Internal Storage, Cache), and tried flashing Havoc-OS (Android 10) and had issues with connecting to Wifi. So I went back to JohnFauxes VS996 flashable and now I don't have data or a working camera. Not sure what's going on here. Ideas?
Click to expand...
Click to collapse
Went from stock what? Stock Oreo, Stock Pie? You have to be on stock Pie to go to LOS-17/Android 10 ROMs. LOS-17 requires LG stock Pie blobs (drivers). Yes, some have Wi-Fi connection issues. There are workarounds.
Went back to JohnFauxes VS996 flashable what? Last Pie, last Oreo? Something in between?
Going from LOS-17 back to stock you will have sensor issues which can be overcome by running in permissive mode. Other ways to overcome it is to Partition DL back to Nougat to scrub the device of all lingering LOS-17 ROM scentk, then upgrade back to newer firmware. If you don't want to do that then you need to run in permissive mode for camera to work.
I don't know what's wrong with your data.
ChazzMatt said:
Went from stock what? Stock Oreo, Stock Pie? You have to be on stock Pie to go to LOS-17/Android 10 ROMs. LOS-17 requires LG stock Pie blobs (drivers). Yes, some have Wi-Fi connection issues. There are workarounds.
Went back to JohnFauxes VS996 flashable what? Last Pie, last Oreo? Something in between?
Going from LOS-17 back to stock you will have sensor issues which can be overcome by running in permissive mode. Other ways to overcome it is to Partition DL back to Nougat to scrub the device of all lingering LOS-17 ROM scentk, then upgrade back to newer firmware. If you don't want to do that then you need to run in permissive mode for camera to work.
I don't know what's wrong with your data.
Click to expand...
Click to collapse
Went from stock Verizon Pie ROM, to Havoc 10 Q. Then from Havoc 10Q to latest John Fauxes Verizon Pie. I'm not sure how to run in permissive mode or the partition DL I'm afraid.
Glad to have you replying. My goal is to have Android 10 Q on my wife's Verizon phone. Not sure if the 'call to activate modem' bug still exists, to where you can't receive texts unless you call after reboot.
TheCoryGuy said:
Went from stock Verizon Pie ROM, to Havoc 10 Q. Then from Havoc 10Q to latest John Fauxes Verizon Pie. I'm not sure how to run in permissive mode or the partition DL I'm afraid.
Glad to have you replying. My goal is to have Android 10 Q on my wife's Verizon phone. Not sure if the 'call to activate modem' bug still exists, to where you can't receive texts unless you call after reboot.
Click to expand...
Click to collapse
* Here's the Wi-Fi workaround for V30 LOS-17/Android 10 ROMs.
* Here's how to change to Permissive mode, even on stock firmware.
* Yes, LOS-17-based ROMs (Android 10) still have the Verizon reboot bug. < There's the current V30 LOS-17 based/Android 10 ROMs bug list, and possible workarounds.
(Ignore that in some of those posts they are are calling it Q ROMs. It's Android 10. Q was merely the beta letter name for what became Android 10, and some people don't want to give that up for some reason. "N" letter beta became Nougat, "O" letter beta became Oreo, "P" letter beta became Pie, "Q" letter beta became... Android 10. Yes, Google ditched the dessert name, but STILL you no longer use the beta letter name when it graduates and gets a statue in the Google Android Park. Call it "10" if you wish, but don't call it "Q." That's like calling a butterfly a "caterpillar". That was just the beta stage of the butterfly!)
____
The major problem you are going to have with V30 Android 10 ROMs is VoLTE -- or rather the lack of it. Read #5 of the V30 Custom ROMS FAQ. End of this year -- 2020 -- Verizon is dropping CDMA. They were supposed to do it end of 2019, but delayed a year. I don't see them delaying again. This means when you make a phone call you will not be able to drop down temporarily from 4G LTE to 3G CDMA for the phone call. You will need VoLTE (Voice over LTE) for all phone calls. Stock firmware has this capability. However, no V30 LOS-based custom ROMs have VoLTE for any carriers.
On V30 you can only get VoLTE on stock firmware or custom ROMs built on stock firmware.
This is September 2020. So, while you can use V30 Android 10 ROMs, in about 3 months you will have to go back to at least rooted stock Verizon firmware to get VoLTE.
T-mobile is dropping 3G HSPA in January 2021. Of the major U.S. carriers, 0nly AT&T is holding out. They will drop HSPA in February 2022.
Discussed in depth here:
All U.S. V30/V3O+/V30S will need stock firmware, not LOS-based custom ROMs. When?
ChazzMatt said:
* Here's the Wi-Fi workaround for V30 LOS-17/Android 10 ROMs.
* Here's how to change to Permissive mode, even on stock firmware.
* Yes, LOS-17-based ROMs (Android 10) still have the Verizon reboot bug. < There's the current V30 LOS-17 based/Android 10 ROMs bug list, and possible workarounds.
Click to expand...
Click to collapse
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
And setting permissive mode is done through a separate APK? Your link went to a post talking about how they used an unlinked APK to get camera and flashlight to work.
TheCoryGuy said:
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
And setting permissive mode is done through a separate APK? Your link went to a post talking about how they used an unlinked APK to get camera and flashlight to work.
Click to expand...
Click to collapse
Yes, SElinuxModeChanger.apk.
You can get it here
https://forum.xda-developers.com/showthread.php?t=2524485
or here:
https://f-droid.org/en/packages/com.mrbimc.selinux/
The other ways to change permissive mode is to use a custom kernel that works with stock firmware. This apk solution is easier.
TheCoryGuy said:
Thanks for all the info. So I think I should go for your clean flash method by setting a partition, because I tried the WiFi fix and it forced me into Safe Mode and wouldn't otherwise boot. I think I found a flashable stock Nougat ROM, after which I intend to flash MSM Extended and get that working hopefully. So do I create a new partition in TWRP, use that for Nougat then empty the previous partition, flash Android 10 to it and get rid of Nougat again after that? Never done this before.
Click to expand...
Click to collapse
I can't say I'm familiar with that MSM Extended ROM. I do see it listed in the LG V30 Telegram Update channel.
If you found a working flashable stock Nougat ROM (there were two versions floating around -- one that kept TWRP and one that replaced TWRP with stock recovery) which keeps TWRP, then after using that you can flash back to stock Pie with TWRP flashable zip (you need Pie blobs for LOS-17 based ROMs), then install the LOS-17 based ROM/Android 10 ROM of your choice.
I'm confused about your question of creating a new partition. All you will be doing is flashing back to Nougat to ostensibly repair previous LOS-17 effects. Then flashing back to stock Pie firmware, then flashing your choice of LOS-17 based ROM.
The only people who create new partitions are those who want to use GSI (Treble) ROMs. Those ROMs are inferior and rely upon a user-created "Treble" partition since V30 never had official Treble. Those GSI ROMs lack many stock V30 features which "regular" LOS-based ROMs have.
ChazzMatt said:
Yes, SElinuxModeChanger.apk.
You can get it here
https://forum.xda-developers.com/showthread.php?t=2524485
or here:
https://f-droid.org/en/packages/com.mrbimc.selinux/
The other ways to change permissive mode is to use a custom kernel that works with stock firmware. This apk solution is easier.
I can't say I'm familiar with that MSM Extended ROM. I do see it listed in the LG V30 Telegram Update channel.
If you found a working flashable stock Nougat ROM (there were two versions floating around -- one that kept TWRP and one that replaced TWRP with stock recovery) which keeps TWRP, then you can flash back to stock Pie with TWRP flashable zip (you need Pie blobs for LOS-17 based ROMs), then install the LOS-17 based ROM/Android 10 ROM of your choice.
I'm confused about your question of creating a new partition. All you will be doing is flashing back to Nougat to ostensibly repair previous LOS-17 effects. Then flashing back to stock Pie firmware, then flashing your choice of LOS-17 based ROM.
Click to expand...
Click to collapse
I'm hoping I found the Nougat ROM that keeps TWRP here. When you mentioned "Partition DL back to Nougat" I took that as me needing to create a partition somewhere. Also I did indeed find MSM Extended on the Telegram Channel here.
All's I know is I need to get my wife's phone working before I go to bed (night shift), else she's gonna kick my ass for wiping it in the first place thinking I could just pop Android 10 on there. Ha. So whatever I need to do, I'll do it.
TheCoryGuy said:
I'm hoping I found the Nougat ROM that keeps TWRP here. When you mentioned "Partition DL back to Nougat" I took that as me needing to create a partition somewhere. Also I did indeed find MSM Extended on the Telegram Channel here.
All's I know is I need to get my wife's phone working before I go to bed (night shift), else she's gonna kick my ass for wiping it in the first place thinking I could just pop Android 10 on there. Ha. So whatever I need to do, I'll do it.
Click to expand...
Click to collapse
When I mentioned going back to Nougat via Partition DL I was talking about going back to full stock KDZ, not using a Nougat TWRP-flashable zip. Doing it the old-school way I was suggesting is harder but more thorough. You would use Dev Patched LGUP to go back to Nougat, wiping out TWRP. You would still have unlocked bootloader. Then you would LGUP to a Pie KDZ which has fastboot flash commands, then reinstall TWRP, reformat internal memory, then flash an Android 10 ROM.
Your way is easier.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
TheCoryGuy said:
I'm hoping I found the Nougat ROM that keeps TWRP here.
Click to expand...
Click to collapse
That link is to JohnFawkes 20k, which is Oreo. Nougat starts with 10 then letter.
Nougat = 10 + letter
Oreo = 20-something + letter
Pie = 30-something + letter (except for Sprint which didn't go by the LG naming rules)
The Nougat TWRP flashable zips were released in the Telegram thread.
ChazzMatt said:
When I mentioned going back to Nougat via Partition DL I was talking about going back to full stock KDZ, not using a Nougat TWRP-flashable zip. Doing it the old-school way I was suggesting is harder but more thorough. You would use Dev Patched LGUP to go back to Nougat, wiping out TWRP. You would still have unlocked bootloader. Then you would LGUP to a Pie KDZ which has fastboot flash commands, then reinstall TWRP, reformat internal memory, then flash an Android 10 ROM.
Your way is easier.
Click to expand...
Click to collapse
Okay... I'm nervous. So you think I can do it without messing up recovery? Darn it.
Could I be so bold as to ask you if you have an instant messenger of some sort? I would greatly appreciate it!!
TheCoryGuy said:
Okay... I'm nervous. So you think I can do it without messing up recovery? Darn it.
Could I be so bold as to ask you if you have an instant messenger of some sort? I would greatly appreciate it!!
Click to expand...
Click to collapse
Flash back to 20K Oreo for now. Use the Permission changer app to make it be "permissive" so camera works OK.
That Oreo is stable. You don't need Pie for now -- if you just want to make the phone work.
If it works, then you can flash back to Pie TWRP flashable zip later if you wish.
In the future you can find the Nougat TWRP flashable zip posted in the Telegram thread.
I'm about to take a shower and go to work. Sorry I can't do Messenger app.
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
So I have a moto g power (2021) and the model is XT2117-1 and I've been searching for a clear way to install Android 11 and one way I saw I needed root so I decided to try too root my phone and spent hours just trying to get twrp to work and obviously to no avail and I was going to try a GSI but now I'm even more confused since I need twrp again so help me please I just want to try Android 11 idc if it sucks since I can always go back
COWLORD2000 said:
So I have a moto g power (2021) and the model is XT2117-1 and I've been searching for a clear way to install Android 11 and one way I saw I needed root so I decided to try too root my phone and spent hours just trying to get twrp to work and obviously to no avail and I was going to try a GSI but now I'm even more confused since I need twrp again so help me please I just want to try Android 11 idc if it sucks since I can always go back
Click to expand...
Click to collapse
You can use twrp from an adb shell nowadays. That's how I use our twrp since I don't have a mouse.
TWRP Commandline Guide
</style>CLIENT SIDE/SCRIPTinstall FILENAME : install FILENAME zip file.
twrp.me
BUT You don't need twrp to install a GSI ROM.
You can fastboot flash it to System after wiping System. These guys came a long way on this phone in this thread. It has a lot of details. Take special note of what to do if it says partitions full or whatever. That's very important. And be prepared before you start to flash back to stock if it fails for any reason.
Anyone try any GSI ROMs on the G Power 2021?
It's pretty standard hardware as far as phones go. No weird under display fingerprint reader or anything. Anyone try a GSI ROM? It might "just work" or "almost just work but you need to run a few commands to fix something".
forum.xda-developers.com
I may flash the Resurrection Remix Q GSI tonight to try it out, but I expect to flash back to stock because, from what I've read, it's very likely not everything will work in a GSI and I need most things to work.
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.