Related
Hey there,
a few days ago I received my new OP3T.
Cause I don't really like to stock OxygenOS I installed TWRP, wiped system, dalvik cache and cache and flashed the Ressurection Remix (RR) v5.8.0 and the Open GApps mini Pack for Android 7.1 (ZIP over TWRP).
The installations wen't without any problem, but now when I'm trying to reboot into RR it always just sends me into TWRP again.
I also tried to reinstall the stock OxygenOS (again without any errors while installing) but still, RR or OxygenOS won't boot and I'm always just going back into TWRP.
After a bit of googling I also found this post https://forum.xda-developers.com/showthread.php?t=2451696 (although my problem didn't occur because of an OTA update) and tried to execute the commands on the TWRP Terminal and the ADB Terminal,
but the commands always return "dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/fota': No such file or directory" and "dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc': No such file or directory".
I don't really now what else I could try, therefore I hope anybody here is able to help me.
Thanks in advance!
Ok, fixed it by using this recovery tool https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
It restores everything to stock. Afterwards I've been able to just flash RR again and it worked like a charm.
did you had to use the dm-verity and forced encryption disabler ?
jackgreyhat said:
did you had to use the dm-verity and forced encryption disabler ?
Click to expand...
Click to collapse
No, the dm-verity disabler is only needed if you wan't to disable the forced device encryption of OxygenOS (RR has no forced encryption therefore I didn't need to use the disabler). After resetting everything to stock with the mentioned tool I just flashed RR with TWRP again and it worked.
I have no idea what caused the problem in the first place.
Update: A working solution is listed below for reference.
A detailed tutorial for encrypted and rooted Nougat OOS users on how to flash Oreo OxygenOS without running into the infamous boot loop issue.
Step 1: Remove all fingerprint & pin from the device
Step 2: Backup everything on your PC/Laptop
Step 3: Reboot the device to TWRP bootloader
Step 4: Using a PC/Laptop, flash Blu_Spark TWRP via ADB command
Step 5: Reboot device to TWRP
Step 6: Wipe dalvik, cache, system & internal partition
Step 7: Format device
Step 8: Copy Oreo Rom & no_verity_mod file onto your device
Step 9: Flash Oreo under TWRP
Step 10: Flash TWRP again
Step 11: Reboot to recovery again
Step 12: Flash Magisk Beta for root (I used Magisk beta 14.5)
Step 13: Flash no_verity_mod file
Step 14: Reboot into Oreo Oxygen OS
Your device is now decrypted, rooted and running the latest stable Oreo OxygenOS build.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Seeing as a couple of forum members have messaged me regarding the official update of Android Oreo, I would like to make a proper discussion thread for it.
I just want to make it clear that HatRiGt has made an outstanding effort by making a tutorial thread. -> ([OFFICIAL] [Stable Oreo 8 ] Oxygen OS 5.0 Update [Tutorial-Root] [Mirror] by HatRiGt)
With that said, I believe the title is somewhat misleading. Since a lot of members are under the impression that this Oreo update will be a simple and straightforward process like all previous Nougat updates, except for it's not.
Stock OxygenOS
Rooted with Magisk v14
TWRP Recovery
Device already encrypted
Almost everyone with the device configuration listed above has run into some sort of serious issues, such as boot loop, file system decrypted/corrupted, or a complete data loss.
So far, it seems like the few groups of members that have managed to update their device without any data loss are either users that have flashed the Oreo Beta rom, or users with a non-rooted & stock recovery device. Almost everyone else is facing some form of issues.
I understand that some people have suggested that rooted users should first format the internal storage, before proceeding with the Oreo update. I personally feel that it is an inconvenient method of OS update, since many of us have a huge collection of photos, media files and app settings etc... to worry about.
The purpose of this thread is to address the aforementioned problem for rooted OOS users and to come up with a solution, so that everyone can enjoy this latest stable release of Android Oreo.
Any comments or thoughts are welcomed.
Maybe a stupid idea, but I am a bit noobish in this. Running stock 4.5.15, rooted, K2 TWRP and Magisk.
Is it not an option to just flash stock recovery (via ADB or Root Toolcase), then remove/deinstall Magisk and use the OTA update? After that flash Blue Spark via ADB, reflash Magisk and be good to go?
Unfortunately this is my daily driver company phone so I haven't the time to experiment with it at the moment.
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Malcol13 said:
I had some issues trying to dirty flash mine. Didn't know about others' troubles until after the fact.
I ended up with the black screen and blue notification LED. Everything encrypted and unable to go anywhere in recovery mode. Had to do a full wipe and image load; I also am not sure if I had been running my backups for a while, so this could be a lesson learned.
Click to expand...
Click to collapse
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
DionysosD said:
Still experiencing the exact same problem.
The problem is, I can't transfer the zip to my phone to flash.
Under TWRP, any computer recognizes it as a mass storage, but even with adb push/sideload it doesn't work.
Does a full wipe help with that problem?
Click to expand...
Click to collapse
I saw the same thing. Unable to copy the zip file until I did the full wipe, which means no chance of recovering what was on it, but I'm cutting my losses.
I'm now stuck on the configuration stage, it's just sitting on "Just a sec..." for forever it would seem. Trying to update on Christmas day was a bad decision.
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
fards said:
Root *shouldn't* cause issues. But that really depends on what has been changed by root
Twrp will though.
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I had the same idea, encrypted, rooted (no system modifications) and running twrp, I flashed stock OP5 recovery, and updated through the ota and ended up in a bootloop.
I did a nandroid to a usb before updating, but I still lost all internal storage files
so...the no verity is only for decrypted users right?
fards said:
Flashing stock recovery should allow the ota to work without issues.
Having said that it's a major update so factory reset isn't a bad idea anyway.
Click to expand...
Click to collapse
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
igoorsoouza said:
The way I installed the beta 2, was removing the pin and fingerprint before installing magisk through Twrp, at first I got stuck with bootloop, but made it come back to life after installing the ota through Twrp and booting back, removing my pin and then installing magisk.
Click to expand...
Click to collapse
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Are you sure flashing Open beta2 won't compromise the internal storage? I bet no one affords to loose previous photos, apps, settings, etc without full backup.
I've triyed this. All good till i flash 5.0 & Magisk & no verity....
Hello there and Merry Christmas.
I faced to this issue too, fortunately before to update to Oreo. I made a full backup of my data.
My OP5 was running under Oxygen OS 4.5.15 Nougat 7.1.1
Rooted with Magisk V14.5
TWRP Blue_Spark 3.1.1
First I have updated my TWRP to Blue_Spark 3.2
And then I've installed Oreo Oxygen OS 5.0 from TWRP with the full zip.
After the update, my op5 has been bricked and locked on blank black screen with a blue led.
To unbrick my phone I used a tiers softwate to install Hydrogen OS first.
After that I could installed TWRP Blue_Spark 3.2 and then flash to the full zip Oreo Oxygen OS 5.0
My OP5 works as well but...
Right now I'm blocked, Google who usually sends an SMS, does not offer me. Only the authentificatorator or the security code. : /
Be careful, print a Google code to access your account when you go to install Oreo.
I'm waiting for Google to do the right thing.
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
1) What is that "no-verity" file?
2) Isn't the regular TWRP 3.2.0 good with Oreo?
MadCow809 said:
Okay, so I've been thinking that maybe it's possible for us rooted Nougat OOS users to update to Oreo stable release without any form of data loss.
I've listed the steps to avoid any potential confusions.
You start with stock Nougat OxygenOS (Encrypted) with Magisk v14 (root) and non-Oreo compatible TWRP (e.g TWRP 3.1.1.1)
Flash an Oreo compatible TWRP (e.g Blu_Spark TWRP)
Boot up the new Oreo compatible TWRP
Flash OreoBeta 2
The phone should boot up OreoBeta 2 without any data loss
Dirty flash the official Oreo stable release via the new Oreo compatible TWRP
Flash Oreo compatible TWRP again
Flash Magisk beta for root access
Flash No-verity file
So the basic order of flashing should be Nougat OOS -> OreoBeta -> Oreo Stable
Any thoughts on this?
Click to expand...
Click to collapse
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
BenSow said:
Isn't a full wipe required even for Oreo Beta builds? Also thanks for starting this thread I'm really eager to jump into Oreo but would love it if no wipe happened.
Click to expand...
Click to collapse
I think it's possible to flash the Oreo Beta without a full wipe. And yeah, I've got way too much stuff on my device, so I can't afford to wipe my storage.
MadCow809 said:
I appreciated the suggestion, but there are a lot of users with loads of files stored on the device, along with various other app settings, having to wipe the storage or perform a factory reset can be really troublesome. I believe that OnePlus pushed through this stable OTA update with the intention of a seamless update. Endless boot loops and data loss wouldn't be an ideal method of an OS update.
Click to expand...
Click to collapse
I never suggested either.
Oneplus don't test using twrp or using root.
Their prescribed ota route, as pretty much every other OEM, is unmodified system partition using stock bootloader.
Twrp or root will affect those and can cause bootloops.
Obviously there's a chance with so much diversity in installs that there can be an issue arises.
raboliot said:
Hi,
I have a boot loop on my OP5.
I ddirty flashed Oreo and had twrp/magisk.
Any ideas to recover my data partition ? (I had fingerprint/pin)
Best regards,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-5/how-to/guide-restore-data-stuck-bootloop-n-o-t3724515
Read it all.
I have a Encrypted phone and I was able to recover all.
Actually I was able to restore my Nandroid backup.
Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??
Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.
I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!
Hi,
maybe someone here can help me or point me in the right direction for a guide. That would be much appreciated!
I have a Oneplus 3T (A3003) that I flashed to LineageOS 14.1 with Magisk-Root a while ago.
I have been stuck on 14.1-20171005-NIGHTLY-oneplus3 for a while now, because since then, whenever I tried to do a nandroid backup from within TWRP, the backup failed because of some kind of error on the data partition (I believe). I haven't flashed a new version since then and haven't come around to it until now, because everything ran very smoothly. :silly:
Since I would like to switch to a more modern ROM (I was thinking of going back to Oxygen OS (5.08)) I started playing around with it yesterday and noticed that TWRP (I think 3.2.0) would not start anymore. It will always get stuck on the logo screen.
I then tried to flash a new version (3.2.3.1) through the Official TWRP app. It still got stuck on the logo screen and I tried flashing 3.2.3.0 after reading about problems with 3.2.3.1 but the results were the same.
Can you please tell me how to get TWRP working again and how to flash OxygenOS 5.08 on my 3T or point me to the neccessary guides?
Thank you.
Data about the phone:
ONEPLUS A3003
Android Verson 7.1.2
LineageOS Version 14.1-20171005-NIGHTLY-oneplus3
Security Oct. 5th 2017
Baseband MPSS.TH.2.0.c1.9-00102-M8996FAAANAZM-1.89286.1.99649.1
Kernel 3.18.31-lineageos-g0036392...
As OOS implies enforced encryption of data partition, going to an from it can be a bit tricky. Simplest way is by wiping using Qualcomm factory restore tool and then just OTA upgrade or flash latest OOS zip.
Skickat från min ONEPLUS A3003 via Tapatalk
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
@r_wraith, I'm thinking that your data may be formatted f2fs and be encrypted but no on-boot password, and have a lot of data in your user data. This could cause a long start time in TWRP.
So try waiingt for about 5 minutes when you boot into TWRP. It may end up getting past the logo screen.
Click to expand...
Click to collapse
That worked, thank you. Yes, my data partition is/was encrypted.
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
r_wraith said:
Since TWRP seems to be working again, do I need to flash some kindof firmware upgrade before I flash Oxygen OS or is this included in the OxygenOS-Image and only needed for flashing ANdroid 8 Custom ROMS?
Click to expand...
Click to collapse
The OOS zip includes the firmware. Custom ROMs don't because they use the OOS firmware. The firmware is stored in separate partitions so it isn't affected by wiping the system and data positions.
Since you're coming from Los 14.1 you'll need to do the following in TWRP:
- take a backup of your current system
- do a factory reset to clear the data partition without losing the files stored on internal storage
- flash the OOS zip file
- flash Magisk 18.0 which will root the phone as well as prevent TWRP from being replaced by the stock OOS recovery
Sent from my OnePlus3T using XDA Labs
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
a.f.x. said:
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
Click to expand...
Click to collapse
Please clarify - did you do the following steps from the installation instructions using the latest official TWRP?
4. Go back to return to main menu, then tap Wipe.
5. Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Sent from my OnePlus 3T using XDA Labs
Dupe
Dupe
BillGoss said:
Please clarify - did you do the following steps from the installation instructions using the latest official TWRP?
4. Go back to return to main menu, then tap Wipe.
5. Now tap Format Data and continue with the formatting process. This will remove encryption as well as delete all files stored on the internal storage.
Click to expand...
Click to collapse
Yes, as this is also part of the Lineage install instructions.
cheers
afx
a.f.x. said:
Yes, as this is also part of the Lineage install instructions.
cheers
afx
Click to expand...
Click to collapse
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
The official version of TWRP has a bug: if you decrypt the phone, you end up with a broken encryption header.
(Lots of discussion about this in https://forum.xda-developers.com/on...covery-official-twrp-touch-recovery-t3742894)
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS.
Sent from my OnePlus 3T using XDA Labs
There's a problem with this build, just read the official thread on the forum...
Next build will fix it, you're not alone
BillGoss said:
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
Click to expand...
Click to collapse
This is the one I have installed. I already went on a Google tour before asking here.
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS
Click to expand...
Click to collapse
I got OOS installed that way.
But only after I ignored the "No OS Installed" message in TWRP.
This killed TWRP, so flashed that again, then (after the wipe sequence) LOS 16, Gapps and Magisk and I am back to the "No OS installed" message and a reboot ends at the fastboot menu.
thx
afx
fra9090 said:
There's a problem with this build, just read the official thread on the forum...
Next build will fix it, you're not alone
Click to expand...
Click to collapse
Thanks!
So what is the best course of action now.
Stick with OOS until the next build or flash LOS 15.1 and then upgrade (or is this again a complete reflash)?
thx
afx
a.f.x. said:
Thanks!
So what is the best course of action now.
Stick with OOS until the next build or flash LOS 15.1 and then upgrade (or is this again a complete reflash)?
thx
afx
Click to expand...
Click to collapse
It's a major release, so you should do a full wipe anyway while you're installing lineage 16.0, stick with 15.1, or OOS.
Don't waste too much reinstalling everything, wait for lineage release.
Edit: They just release it
fra9090 said:
Edit: They just release it
Click to expand...
Click to collapse
Yup, flashing it already.
Still the TWRP message about no OS installed,
But Lineage boots!!!!
THX!!
afx
Another useful post for Titanium users:
https://forum.xda-developers.com/showpost.php?p=78599004&postcount=4
cheers
afx
a.f.x. said:
Yup, flashing it already.
Still the TWRP message about no OS installed,
But Lineage boots!!!!
THX!!
afx
Click to expand...
Click to collapse
Glad to here you're up and running again.
It's odd that you get the no OS message in TWRP, yet the phone boots.
See if deleting both the .twrps file and the theme folder (if it exists) in the TWRP directory helps .
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
It's odd that you get the no OS message in TWRP, yet the phone boots.
See if deleting both the .twrps file and the theme folder (if it exists) in the TWRP directory helps .
Click to expand...
Click to collapse
A regular reboot in TWRP works fine, it was just after the Install step where I had seen that message.
cheers
afx
BillGoss said:
In that case, I strongly suggest that you use this version of TWRP https://androidfilehost.com/?fid=11410963190603866112
The official version of TWRP has a bug: if you decrypt the phone, you end up with a broken encryption header.
(Lots of discussion about this in https://forum.xda-developers.com/on...covery-official-twrp-touch-recovery-t3742894)
After installing TWRP, tap the Format Data button in the Wipe menu. This will reformat and fix the encryption header. You can then reinstall OOS.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your hint regarding the TWRP version.
I was stuck with "E1001: Failed to update system image" and "Error 7" on every custom or stock ROM I tried to install with TWRP 3.3.1-0 after my encrypted data partition got corrupted on latest update.
Formating data with TWRP 3.2.1 fixed the issue and I was finally able to reinstall the stock ROM.
a.f.x. said:
Hi,
tried going from stock OxygenOS (rooted) to LineageOs 16 according to the LineageOS Instructions.
No dice.
After flashing successfully, including nano gapps, TWRP (3.2.3-1) tells me that there is no OS.
Reboot ends in the bootloader.
Tried flashing stock OxygenOS and it only shows me the OxygenOS boot animation.
Any Ideas on how to clean that up?
thx
afx
Click to expand...
Click to collapse
Download os karnel + os ( you can find that in xda forum)
Then flash karnel and os
It will work
You should use usb otg
Hi all,
I have got another problem with the nightly updates since modem firmware changed to 9.0.4 in July . This is just the date, don't know if it is related to that.
Since then I get the common hints about "new nightly available".
-> download -> install.
"Preparing update" -> Reboot.
Getting into TWRP 3.3.1.0 -> Patching all fine. -> Reboot
Enter PIN to start Android -> starting Android
Lineage running circles but longer than normal -> Back to reboot and TWRP Main Menu
That's it. This happens at every update since then.
What I do then is
Wiping cache and system, install lineage-os from the lineage update directory, install gapps reboot.
Data and all programs are still there with all of there setting except permissions. So I have got to start more or less every app to grant their permissions and the system is more or less back to normal.
Any idea how to fix that or where to get some more information what is happening during startup that the system cannot settle?
Greez2all
Tweety