I have my bootloader unlocked.
I've downloaded the AOSP 13 Borneo Monthly Build.
I used
Code:
fastboot -w update .\aosp_borneo-img-Feb-Week4.zip
to install it. I don't have GApps now (as expected).
I've tried NUMEROUS things, but I always end up back to having to reinstall AOSP 13. And all the posts are almost 1-2 years old so outdated information. I tried to use the TWRP Android 11 based, but I of course got an error of "Cannot mount /data" despite no matter what I've done.
Is there any way to get GApps on the ASOP 13 build? I don't care about a custom rom and my phone has been wiped numerous times multiple different ways over the last our, so losing data (not that I did) isn't a problem.
EDIT: I don't mind if it's A11 or A12, A13 would be nice if possible. But I'd just like ASOP with GApps. Though I couldn't even find where the ASOP A11 and A12 builds for this phone would be (if there is any).
Try flashing BitGapps through TWRP and see if it works
traman124 said:
Try flashing BitGapps through TWRP and see if it works
Click to expand...
Click to collapse
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
traman124 said:
You didn't say that you wanted a PE GSI in the original post.
Also that was confusing for me the first time too (and moreso with the TCL Revvl 4)
Click to expand...
Click to collapse
Well I attempted PE GSI because there's no TWRP for AOSP 13 for this phone, the latest is A11 and that won't mount /data/
As well as the TWRP you listed doesn't work with my touchscreen and the other one avail doesn't do decryption.
There’s an SHRP build with decryption support for your phone… Would that work?
traman124 said:
There’s an SHRP build with decryption support for your phone… Would that work?
Click to expand...
Click to collapse
I've tried that myself, and decryption doesn't seem to be any better than twrp. That and it doesnt read AOSP 13 /data anyway. I've had the same problem trying to get gapps, even MagiskGapps doesn't seem to work. Is there a gapps package that can be flashed via fastboot maybe?
Not as far as I know... I’m sorry I can‘t help much further
ErraticFox said:
I actually just install AOSP 13 and then flashed the Pixel Experience system image.
I've been doing this for like 8 hours of trial and error. I think what was confusing me most of the time was I didn't realize that you use fastboot in Bootloader and in fastboot. But you can only run certain fastboot commands in bootloader and only some in Fastboot mode. Which took me quite a bit to realize. Which means I would run a fastboot command in something like bootloader and it was meant for fastboot mode so it'd give me random errors that no one else got because they apparently knew the difference.
But that was confusing lol
EDIT: WELL ****E, NOW THE KEYBOARD DOESN'T WORK.
Click to expand...
Click to collapse
Mind if I ask what you mean by "pixel experience system image"? Are you talking about the PE GSI?
Yes he means the GSI.
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
graewulf1 said:
So. This works and you end with aosp 13 and gapps? For those of us with zero adb experience, is there a step by step on how to do this?
Click to expand...
Click to collapse
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
LethalGamer2121 said:
I'm not sure how to get gapps, but you can flash aosp with fastboot update aosp.zip (replace aosp with the aosp file name). Just power off your phone, then power on while holding the volume down key to boot into the bootloader and perform this command.
Click to expand...
Click to collapse
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
graewulf1 said:
right, i get that. i need to load gapps as well, i have too many paid apps there to not use it. since there is no TWRP for android 13, I need to figure out how to flash AOSP, then Gapps before the first boot.
Click to expand...
Click to collapse
Well, let me know if you figure it out, cause i'm just as clueless about it as you are. I'm kind of suprised nobody's made a fastboot flashable gapps package yet.
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..
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
I asked about on one Telegram, I think that TWRP is out-of-date for newest Android version (main dev is on hiatus)
Newrooter22 said:
Hi Everyone,
Just wondering if there has been any update about custom recoveries for pixel 6. I've been checking the TWRP website and what not but there no info on the subject that I can see.
Just curious to know if anyone else has heard anything about custom recoveries yet
Click to expand...
Click to collapse
TWRP for Android 11 only came out in late 2021. It should come soon for 12. No ETAs obviously but they have a chat here: https://rebrand.ly/teamwin-recovery-zulip-community and make announcements here: https://twrp.me/
Thanks guys, it's good to know that it might still be a while away hopefully not too long. It does have some good features so fingers crossed it's sooner rather than later.
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
adamf663b said:
Got any recomendations for getting shell access on a phone that doesn't boot normally? That's about the only use I have for twrp, its ability to be fastboot booted without an install.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
bobbarker2 said:
adb reboot bootloader
fastboot boot boot.img (I think that's the syntax but if not then fastboot help will show you)
Click to expand...
Click to collapse
That won't help on a system that has boot issues.
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
nutzfreelance said:
there was a custom recovery ( lineage recovery i think) that came with a custom rom. i was reading about the rom a few weeks back(forget where), but the developer would not release the recovery separately.
so really there is no reason why TWRP or some other custom recovery could not be developed.
but with the lack of roms on XDA and limited custom roms elsewhere, i feel that the pixel 6 will have very very little support.
Click to expand...
Click to collapse
Statixos or staticos , something like that.
nutzcase said:
TWRP has been dead for the Pixels for over two years.
You need to learn adb and fastboot if want to mod the Pixels.
If you are lazy, you can use this program to do what TWRP can do,
📳🔥PixelFlasher for Google Pixel 6 Support Thread.
This is the support thread of PixelFlasher (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features). Note: This thread is meant for issues and problems faced in...
forum.xda-developers.com
Click to expand...
Click to collapse
Only thing I ever really used it for was a nandroid
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
alarmdude9 said:
I have a question that is probably really stupid. Twrp and other custom recoveries allow installing custom roms, staticos and the like are out. How do they do it without a custom recovery?
Click to expand...
Click to collapse
You push it as a zip file on fastboot. They're is dotos, deep, statixos, grapheneos, protons, crdroid etc for device
So basically bypassing the recovery altogether.
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
The feature I miss most is adb and having access to the decrypted file system. Decryption was always a problem for twrp; I used to unset my phone unlock method to get around that.
nutzfreelance said:
twrp lets you flash your device without needing a pc.
not to mention backup , on device formatting. amoung very many other useful tools
Click to expand...
Click to collapse
I miss having the ability to do a complegte image of your phone. Comes in handy when you get stuck in a boot loop and have to do a factory reset. Is there any other program that can do a full backup like TWRP?
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
vandyman said:
I really do not see the need for a backup of andoid on the Pixel 6.
Backup your data.
There are several ways now days to restore the Pixel 6 with Android 12 and above.
adb and fastboot are your friends.
Kernel manager apps have a flash tool built into them.
Click to expand...
Click to collapse
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
nutzfreelance said:
none of the ways you mention are possible with only a pixel6 and nothing else.
i cant tell you how many time when i was away for vacation or on a trip where i have flashed a rom on my S7. even a few times when some new software borked my phone and i could boot to recovery and RECOVER my device.
you can go to the custom kernel posts here and look at how many people have soft bricked their phone in April with a bad kernel. with a TWRP recovery they could have flashed a backup and never left their chair.
how can anyone say that more tools to fix things is in anyway a bad thing.
Click to expand...
Click to collapse
Why would you attempt to mod your cell while on vacation?
I was referring to the general user.
I have been through hell and high water today with this Nord N200 5G today. Soft Brick after Soft Brick. iI only flashed TWRP and try to boot into OS after exiting TWRP but i get No OS you sure you want to reboot?. I also can't figure out how to get my internal storage viewed in TWRP. I've read multiple guides and still can't figure it out. I"m pretty new to this so . and they try to flash Magisk for root as well as super su during on adventure fiasco after fiasco today. The Bootloader and OEM unlock was simple straight forward. Most Guides though are not in LAMENS terms and have abbreviations that new people do not understand. i have had to reflash my phone 20+ today with factory due to the NO OS problem with TWRP and can't get it so i can view my internal data from twrp even though i've followed several guides and the ones that says to do the wipe thing i always get the error about it can't mount the data or it has encountered and error 255 and by got try looking things up for those and you you get sent all over the place. So If there is Anyone Out There That would like to help an old geezer out to be able to get a stable TWRP and a Stable root going on please Respond. Sorry Had to Vent......
Oh yea and not to mention Unable to install 3.6.2
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
weirdfate said:
TWRP is not officially launched for this phone. In my opinion lineage is the best option for this phone as of now. It has a custom recovery and is easily rooted as well. https://forum.xda-developers.com/t/rom-official-dre-12l-lineageos-19.4473129/
Click to expand...
Click to collapse
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
jova33 said:
A couple of questions before I jump into that.
How are updates handled? Does the OS do auto-updates?
How is the camera?
I don't know a lot about this phone, but previous phones I've owned had proprietary camera/software, and any custom ROM not based on the stock OS lost camera quality because it couldn't use the proprietary software..
Click to expand...
Click to collapse
Obviously not who you were asking but I just updated to Lineage and it was fairly straightforward following the directions, just make sure you're on Android 11. Updates can be done through settings menu, I just actually applied an update and it worked fine. It can check for updates every day, week, month if you choose I don't know if it will automatically update it though. Camera I have not tried as I don't use it as an everyday phone but generally from what I've seen it's common to have quality go down using software other than stock but I could be wrong.
I can't speak on the difference in camera quality because I dont use it much. There is some loss of function between the stock camera app and the aftermarket rom camera app
This phone has no official twrp so it has tons of decrypting issues which explains almost all of your problems.
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
swee08315 said:
What worked for me is to avoid touching the phone if at all possible while in TWRP. It's very unstable and if you click something it will try to mount partitions and somehow brick you in the process. While booted into TWRP I did almost everything via ADB command from my computer instead of through the TWRP menus, including reboot.
I Pushed my magisk package to /tmp instead which worked. I'm just going to go the lineage route later though. I don't think it's worth messing with TWRP on this device.
Click to expand...
Click to collapse
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
MiniNinja2024 said:
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
swee08315 said:
I believe it was just "adb push boot.img /tmp/boot.img"
And then in TWRP when selecting a file to flash you have to click on the top level option to go up a directory and find /tmp while not clicking anything else. I pushed to tmp to avoid mounting any partitions since the phone bricked everytime that happened.
Click to expand...
Click to collapse
how do i get the phone completely unbricked cause it's saying something like The Image[boot,recovery] has been destroyed please flash correct image or contact customer service to fix it
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Will be trying again in a week when i get my new unlock token. just took the phone to the store, said that the bricking of the phone happend during an update. They didn't have any Nord N200's in stock so they ordered one and said they would have it in the store in a day or two. onto the next phone til then. any ideas on a TCL A509DL Trac Phone?
MiniNinja2024 said:
I forgot to mention that I can no long get into recovery it won't even flash a recovery anymore. it will say it completed successfully but i got to boot recovery and it just boot right back into bootloadre/fastboot mode. i even tried to do fastboot --set-active=a and fastboot --set-active=b tried booting into each of them and nothing. when i do fastboot getvar all it says that boot_a and boot_b are unbootable. any idea how to fix this?
Click to expand...
Click to collapse
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
MiniNinja2024 said:
Having problems getting msm running on deb linux. Have the firmware and files needed but can't get msm to run on MX linux And can't get VMware to run either to try it through that on windows 10
Click to expand...
Click to collapse
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
i don't have another machine only the one i'm using running MX linux. and with all the Distro's of linux i have installed and used there is no need to install drivers for phones for every phone, 3 that i have connected to my computer it' has recognized all 3 phones and runs adb and fastboot commands fine on them. Lol, Took me a minute to read your name but Love the Name.
Haha, don't flash it. Boot it. I ended up stop using it and am now using the Lineage OS Recovery. SUPER stable. I am in the works making a new TWRP as well... This unofficial variant just isn't working for me either. So, I figured since im making it doe myself, might as well release it
justauserthatusesaphone said:
i'm not sure if you can even get the devices to connect to the unbrick tools in a virtual machine. to save some time, use a physical computer running windows 10+ and use a virtual machine as a last resort or if you don't have another computer.
by the way, make sure you have the drivers.
Click to expand...
Click to collapse
You can. Use virtualbox. I wouldn't bother with qemu.
swee08315 said:
You need to use MSM tools to unbrick. It'll restore your device to stock and relock your bootloader.
Click to expand...
Click to collapse
There is a command line alternative for Linux. It is originally made for flashing android boards, but works with phones as well.
Springles2 said:
You can. Use virtualbox. I wouldn't bother with qemu.
Click to expand...
Click to collapse
Interesting, that's actually useful to know. Thanks.
MiniNinja2024 said:
Update: Phone Complete Bricked. Says something like The Image(boot/recovery) has been destroyed please flash the correct image or call customer service to fix it. on top of this....Unable to flash anything. everything no matter what it is, i even tried to follow a guide to get back to factory and it say that no such partition or volume full. Oh and it's an A/B partition phone
how do you push? ive tried the adb push and to no avail... it just keeps saying it's unable to. oh and when i did have twrp installed it wouldn't boot into the os unless i fastboot boot twrp.img then it would reset and finally boot into regular os
Click to expand...
Click to collapse
I do adb push (File) partition
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
So,
This may seem mundane to some of you, and I apologize. But I'm hitting a wall with this Pixel. I cannot use Fastboot normally because I can't get access to any of the internal partitions. I have a list of them that I looked up, but fastboot will not allow me to use any fastboot flash or flashing commands that I need to flash a new ROM.
I've unlocked bootloader - Duh - (been doing this a little while)
Rebooted
Reenabled ADB - #adb reboot bootloader (works fine)
Sending files --> ADB and fastboot both will serve the image or file to the phone, but the phone fails on "partition does not exist" on every time.
I have tried re-flashing this device with the android flashing tool through Google (works fine and I'm currently running the 13 Beta T3B3). Would straight flashing from a zip file help?
I want to be running LoS but I cannot get even the vendor_boot or boot image to flash. Everything seems to be software/firmware locked and I've tried the fastboot commands to unlock certain partitions and things like that from what I can tell in the changes to fastboot. So my question is:
What am I missing? I have even got it to boot into LoS and things worked, but you could tell something was very wrong with the flash and major app/gapp issues. This was accomplished with the flash tool flashing the partitions "boot" and "vendor_boot" and "dtbo" for me to get me into the LoS recovery. From there I reset and installed via sideload like normal, flashed the rest of the partitions listed with LoS and I cannot get a working build without major app issues and major stability issues. CLI will also not give me any info on why these can't be flashed, of course, but that's not how this should work. I know it should be more stable than it is just because it's a Pixel (one would think - has been in the past) It's a Global model GB7N6 and I don't understand what the hold up is.
Any help or suggestions would be greatly appreciated! Thanks!
You need to flash the regular factory image first, not the beta!!
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
See instructions
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
XGX5309 said:
To be fair, I just flashed the beta as a last ditch. Every try I've done was with production software.
I will absolutely try this though. Anything to straighten this mess out.
Click to expand...
Click to collapse
Hi friend
If prior attempts to fix the problem in GetSimple CMS failed, it could be worthwhile to try the beta version as a last resort. A alternative strategy can occasionally assist in solving the issue Free Fire