[solved] Reboot to twrp when installing latest lineage16 - ONE Q&A, Help & Troubleshooting

Hello
Strange think for me, maybe not for you
I switch from carbon 8 and came back to lineage 16.
I'm not able to achieved installation with latest lineage 16, lineage microG or lineage17. Flashing the new rom works well, but after lineage home screen, the phone reboot to recovery.
With an lineage16 old version from 03/2019,install is ok and phone boot well.
I've suspected an old twrp version, but I'm on 3.3.1.0.
Any idea ?
thank you

it's the same with an old twrp version 3.2.

Ok, solved. You shouldn't install twrp as an app before rebooting to new os version.

Related

problem installation lineageos

Hi all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
LucasJahier said:
Hi all, i have a problem whan i install lineage os, i don't have any system on my oneplus one and i want install lineage but when the installation has finished, my phone restart and freeze on logo one plus one android powered.
if you have a solution ;D
good night
Click to expand...
Click to collapse
Which firmware were you on? Which recovery you used?
Did you tried previous lineage os nightly's?
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
LucasJahier said:
I don't know what firmware i m and i have try with the latest nighly release. And i use the latest version of twrp
Click to expand...
Click to collapse
Go to setting > about phone and see Baseband version.
If you're coming from CM13.1 make sure to wipe everything except internal storage.
Download the ROM again if possible (the version you have downloaded may be corrupted) from the Lineage os official site and gapps(micro or pico).
Flash the ROM first and then gapps.
Reboot your device.
If you want the Root access download the Su add-on from the Lineage website also.
Hope it will work.
Let us know.
Thanks.
Re
Re,
Sorry... but i don't have any os in my oneplus one... he is empty exept zip the lastest version of official website and zip of gapps.
Thank you

[SOLVED] Bootloop when trying to downgrade from Android 8.1 (LineageOS 15.1) to 7.1.

I have the following installed:
[url]https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670[/URL]
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
-Snowrider- said:
I have the following installed:
https://forum.xda-developers.com/oneplus-one/development/8-0-0r3-lineageos-15-0-t3670670
Android: LineageOS 15.1 (8.1.0_r4) with latest magisk installed (15.3) with unofficial opengapps 8.1 mini package
When I try to downgrade to either Lineage 14.1 official or carbonrom 5.1 I am getting a boot loop at the oneplus logo. Restoring from backup to 8.1 resolves the issue.
1. factory reset
2. wipe system
3. Install Lineage 14.1 or carbonrom 5.1
4. Install recent opengapps mini package for 7.1.2
4. Reboot
The phone boot loops at the oneplus logo and I end up restoring from backup.
I have looked online and was struggling to find anything relevant. Some people report a new battery solved the issue but since It works when I restore from the backup It doesn't seem to be that. I do have a new battery on hand that I am eventually going to install though so I can do that.
Apologies if I am missing something obvious.
Click to expand...
Click to collapse
Try the following :
-uninstall magisk using uninstaller(available in magisk forum)
-clear system,data,cache,dalvik
-install only the rom with out gapps
if it boots properly then you can install the gapps later or else if u find flashing gapps is causing the bootloop then use an older version and double check the compatibility.
if still not just try out another nougat rom
Thanks for the suggestion.
I tried your steps with the latest stable slimrom 7.1.2, lineage 14.1 and carbonrom 5.1 and I am still seeing the same issue. I was able to clean install the lineage 15.1 beta I linked to though in addition to restoring my backup as I have done before. I might try to clean install a different 8.1 (AOSP for example) and see if that one works. This will help narrow down if the issue is caused by 8.1 in general or specifically something that the lineage 15.1 beta has done.
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
CedArctic said:
I had a similar problem when I flashed Sultan's LOS14.1. I fixed it by flashing down to stock using wugfresh's bacon root toolkit. Keep in mind though that this will wipe EVERYTHING on your phone. Hope it doesn't come to that. Best of luck!
Click to expand...
Click to collapse
This is what I ended up doing and it did the trick. Thank you for the suggestion.

Constant Reboot

I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup
Mmodi said:
I had the official Lineage 15.1 installed with gapps pico, it was upgraded from 14.1 lineage with gapps pico + magisk 16 . Today I wanted to downgrade back to 14.1 so I flashed the latest 14.1 lineage with gapps 7.1
After booting it shows com.android.phone has stopped working and it restarts again to show the same thing.
I am able to get into TWRP recovery , can anyone please suggest me what should I do?
I dont have previous backup
Click to expand...
Click to collapse
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now
Mmodi said:
I did a factory reset using TWRP . Lost all the data but the phone started, able to use it now
Click to expand...
Click to collapse
Always do a clean wipe (wipe everything except internal/external storage). Always back up your previous system just in case. Sometimes it is better to flash Gapps right after flashing the ROM, sometimes it's better to flash the ROM, boot and then flash the Gapps.

From OOS 10.0.1 trying to install LOS 16.0 as a beginner and failing completely

I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?

Been gone for a while, help confirming a few things to upgrade to Android 10

Hi, hoping a kind soul out there will help to confirm a few things about moving to Android 10 from Android 9
I haven't bothered keeping my phone up to date for around a year, and I'm just looking into updating to stock OOS 10 for now.
I'm currently rooted with TWRP & Magisk running an old Android 9 custom ROM, and there seems to be a bit of confusion around TWRP and updating to android 10. I'm looking to completely format the phone, not worried about loss of data as I'll just restore titanium backups, so my plan is this to get a clean install with TWRP + Magisk+Gapps:
1) Reboot to current bluspark TWRP, Flash OOS 10.3.0, Flash twrp-3.3.1-16 mauronofrio installer.zip, Reboot to recovery
2) Flash OOS 10.3.0, Flash twrp-3.3.1-16 mauronofrio installer, flash Magisk 20.3, flash GApps arm64 10.0 nano, reboot to system & enjoy.
This was always my normal update process so i'm pretty comfortable with this way if it will work.
Can anyone confirm if this will cause issues due to TWRP not working properly with android 10 when i preform my first reboot to recovery? My thinking is that if I flash it after installing android 10 then any issues caused by android 10 should be fixed, is this correct?
Thanks!
There is no confusion at all.
Everything is clear since months ago that 10.3 was released.
Upgrade firstly to the latest 9.x Rom, then flash the latest TWRP and then u are ready for flashing 10.3 and latest magisk.
Sent from my ONEPLUS A6003 using Tapatalk
ok, so I have to go to OOS 9.09 with twrp-3.3.1-16-enchilada-Pie-mauronofrio, before upgrading to 10..3.0 & twrp-3.3.1-16-enchilada-Q-mauronofrio, even if I want to just do a full wipe and start fresh on 10.3.0?
Paratax said:
ok, so I have to go to OOS 9.09 with twrp-3.3.1-16-enchilada-Pie-mauronofrio, before upgrading to 10..3.0 & twrp-3.3.1-16-enchilada-Q-mauronofrio, even if I want to just do a full wipe and start fresh on 10.3.0?
Click to expand...
Click to collapse
This is the latest TWRP: twrp-3.3.1-x_blu_spark_v9.108_op6
The rest has already been discussed.
Sent from my ONEPLUS A6003 using Tapatalk

Categories

Resources