Related
Hello developers,
I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones.
Now, after struggling for 3 days to install lineage, I decided to post here.
First some information about my phone:
Device: Huawei P20 lite dual SIM, 4GB RAM, 64GB internal (ANE-L21, i guess?)
Fastboot Info (I ran those commands when creating this post):
fastboot oem get-build-number: ANE-LX1 9.1.0.257(C432E6R1P7) (from what I understood, ANE-LX1 and ANE-L21 Firmwares are the same?)
fastboot oem get-product-model : ANE-LX1
fastboot getvar version: FALED, Command not allowed
fastboot getvar vendorcountry: HW/EU
When I got the phone, I got my bootloader unlock code first.
I then successfully updated the phone to the newest version (the official Huawei approach, using HiSuite).
After that, I unlocked the bootloader with no problems and flashed TWRP.
I needed to try a few versions to find one that's working as the official ones for that phone kept freezing, I finally found one by Pretorian08 that's working).
Then I formatted to get rid of encryption, did the wipe procedure, cleared the cache, data and system partition and installed the newest lineage build and GAPPS.
After rebooting, the Phone showed me the usual "your device has been unlocked and can't be trusted"- dialog, and tried to boot then.
From here on, nothing happened.
I tried every build I could find, including the most actual one from tonight (lineage-16.0-20201214-nightly-anne-signed.zip).
Some builds would reboot after some time and show the shortened warning message, then boot directly into Recovery.
I totally bricked my phone somewhere on the way (multiple times I think), but could unbrick it by flashing rescue_recovery_kernel, rescue_recovery_ramdisk and rescue_recovery_vendor with appropriate img files extracted from a "Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8)" - Firmware and then going back to zero by installing a stockrom via dload and unlocking the bootloader again.
I then tried several other custom Roms, but the outcome is always the same: The phone just freezes with the warning message still visible while trying to boot up, or it boots into TWRP.
ROMs I've tried (I'll write the filenames to provide more info):
- Havoc OS-v3.2-20200215-ARM64AB-GSI.img
- Resurrection Remix ARM64_AB_20191205.img (this is the only custom ROM that will do ANYTHING at all: It will show the Red RessurectionMix Bootlogo, but sadly it won't boot past that point)
- Treble AOSP losq-v224-201017-arm64-bvN.img
With the above 3, installing GAPPS is not possible because "not enough free space in system partition"
- Every possible lineage build for that phone
As stated before, I'm struggling with the phone for 3 days now, so I followed a whole bunch of threads and advices, flashed multiple firmware files using different methods and tried like 7 different TWRP versions. With other words: I did a lot of things, which yould possibly mess up the phone and maybe I did something wrong at some point.
Maybe, I flashed a wrong Firmware while trying to unbrick or something like that. Can you guys help me understand what I'm doing wrong?
I don't like it if people post questions in a forum and then don't share what they figured out, so I'll post 's a little update after 6 days:
Here's a serious advice, if you're considering to buy this phone because there are lineage builds available: forget it.
I mean in most cases it seems to work somehow (from what I read), but from my experience I can say now, that there are phones where it apparently just doesn't work.
I've wasted over one week of my holiday working nonstop on that phone, I've downloaded about 50GB of different firmware files, recoveries, patches and custom Roms and flashed my firmware like 40 times. Best thing I could archieve is an indefinitely looping bootlogo in AOSP, lineage won't even get to that point.
I've tried every lineage build available, i've tried EMUI versions from 9.1.0.0X up to 9.1.0.200 (it is stated multiple times that the .200 will definitely work), no chance. I even tried a rollback to EMUI 8 via Hisuite and using old lineag builds in the end.
The fact that I didn't get any advice in this forum leads me to the conclusion, that no one has an Idea on what the problem is here either.
As I don't feel good with using a phone that still has original google stuff and huawei spy/bloatware installed, the only option that is left to me is just throwing it away and using some old phone. That's sad and a real waste of material and time, as the phone is brand new, but using the stockrom is no option to me. I really don't know what went wrong, I've already successully installed lineage (and cyanogenmod before) on more than 8 other devices, always without any problems.
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
user_name_duplicate said:
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
Click to expand...
Click to collapse
P20 lite is not so bad, maybe you are doing something wrong...
I've installed without problems Havoc, LOS 16.0, LOS 17.1unofficial, AOSP 10, losq-v224-201017 etc. etc...
P.S.: If you "hate" Google and Google's bloatware (like me ) only, you can simply rebrand your phone to chinese Nova 3e.
Or, choose Custom ROM based on Stock with KangVip settings , stable enough to be used as your daily driver." ( e.g. https://forum.xda-developers.com/hu...m-emui-8-0-kangvip-p20-lite-catuva21-t3813564
https://forum.xda-developers.com/hu...-emui-8-0-0-huawei-p20-lite-dual-sim-t3813604) . Using KangVip settings you can disable completely GAPPs .
(My primary phone is at the moment Mate 10 lite rebranded to chinese Maimang 6 (to get away from GAPPS ) . Among other things, better battery life, lower data consumption (using FUT) etc.)
Hi -Alf-, thank you for replying.
-Alf- said:
P20 lite is not so bad, maybe you are doing something wrong...
Click to expand...
Click to collapse
You're right, it's not the phone, it's me. I guess I am doing something wrong, but I don't have the slightest clue what that is.
Any suggestions?
I've already invested a lot of time and have more or less resignated, but thanks to covid lockdown I'm basically trapped inside the house and might aswell give it another try.
Rebranding is an option, you're right. I already have downloaded a nova 3e Firmware, if nothing else works, I might try that.
Also, I'll have a look at the KangVip Roms, haven't heard of them before.
But to be honest, I think I wouldn't be satisfied with those options, at least not for a long time.
Getting lineage running on that phone is a task, the problem solver inside me is really commited to accomplish, because that was the intention I bought the phone with. Also, not being able to accomplish something that hundreds of other people already have done and that is proven to work is driving me nuts. I wouldn't have bothered trying to get it working for 10 days otherwise.
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Try Havoc 2.9 (requires EMUI 8)
Havoc 2.9
Hi -Alf-,
-Alf- said:
Try Havoc 2.9 (requires EMUI 8)
Click to expand...
Click to collapse
Tried that now, after downgrading to EMUI 8 via HiSuite, I did exactly what you wrote in that thread. The outcome is the same as with every other ROM I've tried: I see the "your device has been unlocked and can't be trusted" screen, then after a while it tells me that "my device is booting now" and just does nothing except rebooting every 10 or so minutes.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled, so I'll give it some more tries.
-Alf- said:
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Click to expand...
Click to collapse
I bought the phone because I thought it was officially supported:
LineageOS Downloads
download.lineageos.org
Was that assumption wrong, is there some hint or exception, that I'm not seeing?
The phone was delivered some weeks late because the seller was out of stock. I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
user_name_duplicate said:
I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
Click to expand...
Click to collapse
It may be a fake, try to verify the authenticity on linked website
imei24
user_name_duplicate said:
I guess it came directly from china
Click to expand...
Click to collapse
Exactly, I saw for example Huawei P20 Pro with MediaTek proc.
Btw., I have installed this Havoc 2.9 three times without problem, so it's really very strange...
In fastboot mode run commands :
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem get-product-model
fastboot getvar rescue_version
and post the results please.
Some might fail, so don't worry about it.
You can also download "Device Info HW" apk and check your SoC (Kirin 659) Vendor (HiSilicon), ABI (arm64-v8a) etc.
On imei24, the device is listed as "Huawei P20 Lite" for both imeis, blacklist status is "clean". Recognized Serial is the same for both Imei numbers.
Only thing that's not clear to me is the warranty status:
Warranty start: 2018/7/23
Warranty end: 2018/8/6
So it can't be that new, at least not factory new, right?
I bought it on real.de, so I have no further information where it comes from. China was just my assumption because they where out of stock and delivered 2 or 3 weeks late. I can't really imagine that real is selling fake phones (on purpose). That really wouldn't help their image if people found out.
I ran the commands you provided:
fastboot oem oeminforead-CUSTOM_VERSION: FAILED
fastboot oem oeminforead-SYSTEM_VERSION : ANE-LX1 8.0.0.180(C432)
fastboot oem get-build-number : ANE-LX1 8.0.0.180(C432)
fastboot getvar vendorcountry: hw/eu
fastboot oem get-product-model: ANE-LX1
fastboot getvar rescue_version: rescue0.6
I will download the Device Info apk as soon as my device boots again (I will reflash the stock image once again).
Edit: Device Info HW is telling me I'm using a Kirin 659 SOC.
Okay, most of custom ROMs require lower build number, that's why I wrote that I tested Havoc 2.9 on .126. If you are running latest build number, it may cause your problems.
IMO it is time to clean your phone, extract from Oreo firmware (it doesn't matter which build number) ramdisk.img , kernel.img, recovery_ramdisk.img and erecovery_ramdisk.img and transfer to the SD card.
Download .126 Service ROM
8.0.126
unpack it and transfer dload file to the SD Card (without unpacking it)
Install
TWRP
over eRecovery, boot into TWRP, select Flash image and flash 4 files. Go back to main TWRP's panel > Reboot > Power Off.
Use three button combo to flash the ROM. This process will erase all your data and lock the bootloader again!!!
Unlock BL and try Havoc 2.9 . It must work!
Good luck.
Edit: I found on my MEGA :
https://mega.nz/#!o8FUVR6T!-1fl6TviRtgGbssuG9LgyssCJg4dwxa84luJmrnvSCg
https://mega.nz/#!gkdgnLBa!O8LVZF4J0NiEB78c9z4_FxASN0vWx3rOAIQdmhApAOQ
https://mega.nz/#!xpViTTSC!Q_5ieeEL0gpKROj35cvjc_TRddmkFTMsIxvOT6lS23Y
https://mega.nz/#!EhM2lZqK!yphxvKNUQueIryop44DmPflp7Iwi9c8ExeaCRqA-iY4
Hello Alf, thanks for your last reply!
Downgrading worked, that was the last thing I've tried before christmas.
I wanted to continue today, but found this thread you've posted in.
I thought I'd give it a try and now I'm running on lineage (which is what I initially wanted), sadly only the 15.1 version, but I don't need the newest version.
WiFi is working and, until now, it's running stable. I've installed 8.1. nano gapps (might try pico in the future) and magisk v21.
Maybe I'm lucky and in the next few weeks or months I'll find a working build of an android pie lineage.
I think with installed TWRP it should now be possible, to do a complete backup, mess around with the system (i.e. upgrade Android/Flash ROMs) and then restore it to my now working state, is that correct?
If that's the case, I'll try some other ROMs, including the havok ROM I've already downloaded.
Which partitions must be included in my backup to perform such operations?
For anyone else encountering my problem, here is what finally did the trick:
Code:
- downgrade to .126, following alfs procedure
- Flash TWRP by pretoriano80 (on recovery_ramdisk partition)
- do a wipe (format data to get rid of encryption, then via advanced wipe format cache partitions and system)
- install lineage 15 (link), last build is from 2020-10-27, so it's not an abandoned build
- install GAPPS 8.1
- install magisk v21
- wipe cache/Dalvik
- boot to system
Booting for the first time took a few minutes, but since then, it's running smooth and without any problems.
The only thing that's still an enigma to me is, why the LOS builds I initially tried (with EMUI 9.0.0.200) didn't work, even though other people don't seem to have a problem with ANE-LX1 and LOS16. If anyone is reading this and has an answer to that question, please post!
For now, I'm happy with LOS 15. Thank you many many times, Alf! Greetings to Melmac!
user_name_duplicate said:
Thank you many many times, Alf!
Click to expand...
Click to collapse
No problem...
user_name_duplicate said:
Greetings to Melmac!
Click to expand...
Click to collapse
I'm currently struggling with the same issue. Tried every combination of TWRP with lineage 16 and gapps. Some roms I can get to boot but then not enough space for h gapps. I have tried to wipe system, data and cache to resize system partition which ends up in phone booting directly to TWRP. Other times I get to warning screen and end up with boot - loop. So I'm well a are off your frustration. However I have decided that I'm not gonna settle for version 15. I'm trying for 17 but much have to settle with lineage is 16..
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.
I see that XDA is filled with threads that leave a lot of loose ends. I did not see anyone post this yet, but there is an MSM unbrick tool for this model, hidden in plain sight (I will be testing it some time tonight):
Index of /list/Unbrick_Tools
You'll also need the Quantum drivers, duh...
https://drive.google.com/uc?id=1zKPFtcc2X_Nf70mcvn9TBu60bHl6Q3cP&export=download
I miss the good ol' days when we could flash a K20 Plus without having to do backflips. These new devices are awful. Anyway, once I unbrick this piece of junk I may get adventurous enough to try and install Lineage, again. I suspect that trying to install it when 12 was already on had something to do with it. Will try to use MSM to put 11 back on (it is softbricked in a loop but I can at least get into fastboot, so we'll see).
I'm soft bricked but got into fastboot by pressing all three buttons simultaneously to turn the phone on.
I would LOVE to have a vintage android version on here, back when things were fast and simple. I'm not yet talented enough to make that happen. My only real experience is with Mr. Travis Holt's K20 roms back in the day. They worked so well that I'm considering just buying an old K20 again and being done with all this new stuff. It's quite a disappointment.
Gonna get back to unbricking, flashing and ripping my hair out. Wish me luck.
averyboringusername said:
I suspect that trying to install it when 12 was already on had something to do with it.
Click to expand...
Click to collapse
Yes absolutely. The lineage install page warns that you must be on android 11 https://wiki.lineageos.org/devices/dre/install
Warning: Before following these instructions please ensure that the device is currently using Android 11 firmware.
Click to expand...
Click to collapse
They even make you click a button to acknowledge that you've read the warnings before they show the install instructions.
There is also a thread in this forum warning people
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
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...
forum.xda-developers.com
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
Click to expand...
Click to collapse
I'm sorry, but how many more warnings do you want?
Search the forum on how to recover the softbrick.
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks