Hello there,
I have some sort of a problem (although my phone is still working.. yet)
I recently flashed my OnePlus 6 with LineageOS 19.1 (coming from OxygenOS 11.1.2.2).
I flashed "copy_partitions.zip" first and then the official LineageOS 19.1 ROM without GApps,
but because I wanted to use some features, which needed at least the presence of Google Services, I flashed the "LineageOS for microG" (19.1) ROM.
Which worked like a charm.. besides I was very unhappy because of the lack of customization regarding color-theming and the changes made to the QuickSettings of Android 12 in general..
So I thought I could clean flash LineageOS 18.1 / ("Lineage for microG") to get the old theming back..
So what I did was installing the official custom LineageOS recovery from 18.1 (because microG had none for 18.1),
hit "Factory Reset" and afterwards applied the Lineage 18.1 zip over adb.
A message "Update package is older than the current build, expected a build newer than timestamp [...] but package has timestamp [...] and downgrade not allowed" along with the Question to install anyway appeared right after sideloading it to the phone.
I decided to hit "Yes" because I don't needed to backup any data from the phone and wanted to wipe clean anyways... (which I thought I did with "Factory Reset)
So I installed and afterwards rebooted to recovery to flash Magisk aswell..
After rebooting to system then, the phone entered the fastboot loop.
No matter what I do, it still doesn't boot to system after installing 18.1 from LineageOS recovery (also tried with the newest microG recovery from 19.1).
I also known you would wipe system, cache and data (and maybe vendor aswell) prior to a clean custom ROM flash (via TWRP)..
So flashed TWRP 3.6.2 (latest) for enchilada and tried to wipe my system, vendor and cache, but didn't manage to find "system" or "cache" on the advanced wipe menu, so I formatted and wiped data and wiped vendor.
Then installed LOS 18.1 via TWRP also..
But same problem - fastboot only.
also after my TWRP journey, sometimes when flashing the LOS recovery and booting it, a message appears on screen:
Failed to bind mount /mnt/staging/emulated/media/0 [...]
The thing is, I can install LOS 19.1 (microG) without any problems and it would boot,
but I just want to downgrade and I found no guide for my device (or any with ramdisk and A/B slots)..
And there is also no link to MSMDownloadTools for Android 10 (because onepluscommunityserver.com is offline)..
The links from this post and some other posts I found aren't working anymore..
- Is there a way to go back to LineageOS 18.1? What would be the intended way (not doing a downgrade but flashing clean)?
- Is my phone softbricked somehow? (partitions broken or corrupt?)
- Is it a firmware problem?
(I am on security patch from November 2021)
But I don't know what exactly happened to my firmware when flashing Lineage 19.1 over OOS 11.1.2.2
This is my first post as it is my first Android phone/flashing experience in general.. so I hope I got everything right from all I found out until now..
I really appreciate any help / even if it is just saying I messed up and need to go EDL mode... (if it truly is the case)
Thanks in advance.
You people are great!
o/
Related
I've tried installing PixelExperience 10 on my phone (which is unlocked and with a custom recovery) and first it throw me Error 7, but that was because I hadn't flash the firmware and vendor .zips before PixelExperience, but even flashing that, the device bootloops until a certain point and then it boot back to recovery.
I've tried with dotOS, LineageOS, even MIUI, multiple versions of it, and non of it are working. The device just bootloops with everything.
Fastboot is accesible, recovery is accesible. I'm using OrangeFox Version R10.0_2, but I originally installed TWRP and I had the same problem.
Have you tried flashing TWRP, then using TWRP recovery environment to wipe EVERTHING, then use adb to push lineageOS (since you will have wiped internal data and lost your rom file)
RunNgun42 said:
Have you tried flashing TWRP, then using TWRP recovery environment to wipe EVERTHING, then use adb to push lineageOS (since you will have wiped internal data and lost your rom file)
Click to expand...
Click to collapse
OrangeFox lets me wipe the same partitions (even Vendor, which TWRP doesn't let me).
I'm not sure if I can install Lineage OS thru adb because it asks for MIUI firmware to be installed. If I wipe everything, I loose the firmware.
Althought, I haven't wiped the internal storage in I while, since I have all the roms and zips, there. I'll try with that.
Make "Format Data" - Yes after that wipe data, system, cache and vendor. Copy zips to storage and dont sideload.
Flash fw 9.6.27, los17 and opengapps. Must work.
The way these roms work you basically have to have previously installed a corresponding version of MIUI first. For instance, if you want to install los16 then you must have previously been running MIUI 10. If you want to install los17 then you need to install MIUI 11 first. I guess Xiaomi does some weird stuff to the internal storage between flashes. If you're stuck in a bootloop the easiest thing to do is use the official MiFlash tool to flash the ROM version of your choice. MiFlash uses fastboot rom files. This site has the best catalog of roms
https://xiaomifirmwareupdater.com/miui/
MAKE SURE YOU UNTICK "Clean and lock" at the bottom or else you will relock your bootloader!
I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom
Hello, I'm not usually a poster to any forum as my questions can be found with enough digging but I can't find my answer, so here goes.
BACKGROUND:
Stock: Motorola 5G Ace (kiev). Android 10. I think it was Snapdragon 690.
Unlocked bootloader
Installed to TWRP 3.5.2 for the 5g ace to both partions _a, _b
Used TWRP to flash lineage-18.1-20210701-UNOFFICIAL-kiev
All commands sent through BASH
DISCUSSION:
Tried to install Gapps after LineageOS, recieved errors that said something like no room or storage and went through each line with a fail. Verified cache was wiped, tried again. Failed again then moved to reboot with just OS.
Lineage OS installed with success.
Boot back to recovery, TWRP is gone and now it's LineageOS recovery. Could not figure out how to flash Gapps to with LineageOS, but learned that if reducing Gapps size it should work in TWRP, so re flashed TWRP, no problems.
PROBLEM:
TWRP will not load. At load screen it shows the TEAMWIN logo and lasts for a min or so then times out, reboots and loads OS.
Will adb to bootloader.
Will adb to fastboot, BUT enters TWRP, no screen touch will accept commands then lock screen initates at about 30-60s and hard reset to get out.
Can fastboot to recovery. but enters orginal TWRP boot time out.
-----------------------------------
REQUEST:
Please assist in troubleshooting why recovery will not boot so I can get Gapps flashed.
-----------------------------------
ADDITIONAL NOTES:
If plugged into charger/power it wont stay turned off and boots. Will only turn off from LineageOS.
Can not boot into fastbootd but I'm guessing that was something related to the original recovery that I wiped.
Comments:
Would this have something to do with LineageOS at Android 11 and my original TWRP was set for android 10?
All I was trying to do was get Gapps to load, super bummed that I was so close. At least my phone is still a phone.
Your TWRP is old. You can flash gapps from the linage recovery. If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps. Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.
Your TWRP is old.
That's what I figured, what version would be better? Reading the TWRP pages make me believe I can't just pick anything that has a newer release date.
You can flash gapps from the linage recovery.
Lineage recovery appears gone. Do you know how to get it back, or if i'm wrong and then how do I get back into it?
If it was me, I would reflash the ROM and use the lineage recovery to flash the gapps.
Once you know that the system is working, worry about the TWRP. The best place to look is the Telegram channel.
I agree this would be a good path, but I have no access to any recovery SW. From what I understand I can't do this from inside the LineageOS either. Silver lining; Lineage is working fine.
Are you rooted with Magisk?
I am using TWRP 3.6.0_11.0 RC1.4. There is an installer that you can use Magisk to flash. It downloaded it from the Telegram channel. There is also a .img file in the Telegram channel.
https://t.me/MotoG5GOfficial is the correct channel.
That was it. Old TWRP. Thank you very much.
You are welcome.
Hello Forum,
Yesterday I was building lineage-18.1-20220427-UNOFFICIAL-guacamole.zip for my OP7Pro and I usually include the 19.1 branch as well, to have an idea that there is something ready to build; usually, it would complain and drop out when it gets to that point, however yesterday it built lineage-19.1-20220427-UNOFFICIAL-guacamole.zip.
I have seen a Lineage 19.1 build under the development forum and the LineageOS Github defaults to 19.1 when I checked. I build my images from the lineageos4microg/docker-lineage-cicd and it includes the kernel and whatnot.
Would the lineage-19.1-20220427-UNOFFICIAL-guacamole.zip actually work or would it break something?
So I went ahead and flashed lineage-19.1-20220427-UNOFFICIAL-guacamole.zip over lineage-18.1-20220427-UNOFFICIAL-guacamole.zip.
I flashed the recovery first lineage-19.1-20220427-UNOFFICIAL-guacamole-recovery.img
So fastboot flash boot lineage-19.1-20220427-UNOFFICIAL-guacamole-recovery.img
Then I powered off and went back into the recovery with VOL_Down + PWR.
Ran adb sideload copy-partitions-20210323_1922.zip (I didn't think I had to since I updated the base to 11.0.7.1 GM21AA for both A/B but did anyway so that the recovery would at least apply to both sides)
Advanced - Reboot to recovery.
Ran adb sideload lineage-19.1-20220427-UNOFFICIAL-guacamole.zip
Reboot system now.
And it worked; a dirty flash from 18.1 to 19.1, built on the same day.
I went back into the recovery and installed Magisk-v24-1.zip, rebooted and no complaints.
MicroG still has all ticks applied and no crashing of apps as far as I can see.
I had lineage os 17 installed on it. I wanted to access the recovery and I got into lineage s recovery even if I have twrp recovery. So I wanted to reboot back to the system and it always boots right into lineage os recovery. How can I fix this?
Hey! No need to worry, I just upgraded my LOS to 18.1 via TWRP and rooted it with magisk. You must have accidentally swiped to reboot to system with the install twrp option checked when you should've tapped the do not install option. You have two options.
1. Now you can try to "dirty flash" LOS via TWRP, download LOS 18.1 to a pen drive and go to "Wipe" and delete cache and dalvik cache and keep all your data in the process.
2. Or you can just try to get it to boot to system and backup your data and upgrade.
Some questions, do you have potentially boot loop causing magisk modules installed? or is your device even rooted in the first place? That is all for now.