Related
Hi community! I'm having a problem with my OP2, I currently have cyanogenmod installed on my OP2, and the version is from may-june? Not sure, but I want to upgrade to this rom here: https://forum.xda-developers.com/oneplus-2/development/6-0-x-cyanogenmod-13-oneplus-2-t3292436
How would I go about doing that without messing anything up on my phone? I'm still very new to this stuff, any info will help.
Well, all you gotta do is follow installation instructions for any ROM. That means:
Boot into recovery
Wipe everything except internal memory.
Install ROM .Zip
Install Gapps .Zip
Install any other customizations/patch/SU-addon/etc.
Boot system. You may experience some bootloop the first time, it takes a few minutes to set up the entire ROM.
Also check from what OOS version are you coming. In this particular case, you may need to upgrade OOS atleast to 3.1 or 3.5.6. That can be done the same way.
And take a Nandroid and a Titanium (or whatever else) backup for your apps (or anything you want to survive wipes, except internal sdcard), because when you erase data, you will be losing them.
Best of luck.
fabrquila said:
Well, all you gotta do is follow installation instructions for any ROM. That means:
Boot into recovery
Wipe everything except internal memory.
Install ROM .Zip
Install Gapps .Zip
Install any other customizations/patch/SU-addon/etc.
Boot system. You may experience some bootloop the first time, it takes a few minutes to set up the entire ROM.
Also check from what OOS version are you coming. In this particular case, you may need to upgrade OOS atleast to 3.1 or 3.5.6. That can be done the same way.
And take a Nandroid and a Titanium (or whatever else) backup for your apps (or anything you want to survive wipes, except internal sdcard), because when you erase data, you will be losing them.
Best of luck.
Click to expand...
Click to collapse
This guy is correct. How ever if you make sure your on twrp 3.0.2.2 or what ever latest is. You can go in advanced wipe and clear system too. The quite frankly in. My experience I've never had to worry about what my preview OS was. Upgraded to nought with an empty system juts don't wipe internal lol
Although I believe new twrp has given us the usbC support now! Huzzah
Archtects said:
This guy is correct. How ever if you make sure your on twrp 3.0.2.2 or what ever latest is. You can go in advanced wipe and clear system too. The quite frankly in. My experience I've never had to worry about what my preview OS was. Upgraded to nought with an empty system juts don't wipe internal lol
Although I believe new twrp has given us the usbC support now! Huzzah
Click to expand...
Click to collapse
Forgot about that. It's TWRP 3.0.2-2, which made this phone compatible with most marshmallow roms (and then wasn't needed an upgrade for nougat)
I mentioned the thing about previous OS because I don't remember when did OP release OTA to update phone to marshmallow, so I can't be sure.
fabrquila said:
Forgot about that. It's TWRP 3.0.2-2, which made this phone compatible with most marshmallow roms (and then wasn't needed an upgrade for nougat)
I mentioned the thing about previous OS because I don't remember when did OP release OTA to update phone to marshmallow, so I can't be sure.
Click to expand...
Click to collapse
Valid point sir.
Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
possi.rodrigo said:
Hi all,
I'm with problems in Lineage OS.
I'm trying install Unofficial version under Official, but when I try usying TWRP, they show me this error:
" Can't install this package on top of incompatible data. Please try another package or run a factory reset"
I delete the "assert" section but the error persist.
Can any people help with this?
Thanks in advanced!
Rodrigo Possi
Click to expand...
Click to collapse
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
echo92 said:
Did you wipe cache/data/system/Dalvik prior to installation of the unofficial Lineage OS-OMS? The unofficial and official builds don't mix - if you wish to switch between the two, you must wipe your device (unless you're dualbooting). Of course, by doing this, all data and your official Lineage OS system apart from your internal storage/SD card will be erased, make backups before you proceed. Your TWRP backup will live on your internal storage btw.
Click to expand...
Click to collapse
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
possi.rodrigo said:
I didn't, only cache and dalvik. I would like install without lost my data and settings Have any way for I install changing the updater-script?
I would like try install only change this script first if I have any problem, there yes I'll do a clean install.
Thanks in advanced!
Click to expand...
Click to collapse
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
echo92 said:
I don't know of a way to modify the update script, and in any case, I still would suggest your data (this is your app data and settings, not your photos and other media stored on your internal storage) be wiped along with your system. As I mentioned above, the official and unofficial builds are quite different, and trying to flash one on top of the other without performing a wipe of your system, (app) data, Dalvik and cache (no need to wipe your internal storage for most cases) will give you problems. It's even mentioned in the instructions for installing Lineage OS OMS https://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274
If you don't wish to wipe your device, then staying on the official Lineage OS might be a wise option.
Click to expand...
Click to collapse
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
possi.rodrigo said:
Thank you so much, I'll do a nandroid backup and try install following this tutorial. Other doubt, Can I use in this unofficial version the kernel elemental x or is better keep the original?
Click to expand...
Click to collapse
I recall from what Silesh has mentioned is that the commits from ElementalX are present in his kernel, thus the benefits should be seen in the unofficial stock Lineage OS kernel and so you don't necessarily need the ElementalX kernel. If you wish to use the ElementalX kernel with the latest builds of Lineage OS-OMS, and there is nothing stopping you doing so, you need to flash the sensorhub firmware, else you'll lose sensors like your fingerprint sensor (if you have a G4 Plus, that is - I don't know if other sensors are affected on non-Plus models as well if you don't flash this). The firmware can be found here https://forum.xda-developers.com/showpost.php?p=71360979&postcount=2723
To install said firmware if you need it (credit to rahulsnair for the procedure https://forum.xda-developers.com/showpost.php?p=70716729&postcount=170):
Download the zip and extract, you should get a sensorhubfw.bin file. Copy this .bin file to your adb directory.
Connect your device to your computer and check adb can detect your device using 'adb devices'
Staying in adb, execute the command 'adb push sensorhubfw.bin /etc/firmware' (without the quotation marks). This will copy the sensorhub file to the /etc/firmware directory on your phone.
Reboot and hopefully you should have sensors back.
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
SysAdmNj said:
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
Click to expand...
Click to collapse
Just flash the full zips from TWRP and reflash Magisk to maintain root.
SysAdmNj said:
Seems, I need to lock bootloader to take official update. Is it worth the hassle of backing up all data, and upgrading to oreo?
Click to expand...
Click to collapse
I didn't need to lock the bootloader again to update to Oreo from rooted and encrypted Nougat. This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
pleomaxell said:
I didn't need to lock the bootloader again to update to Oreo from rooted and encrypted Nougat. This is what I did:
Downloaded OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5. zip, twrp-3.2.1-0-universal-codeworkx-cheeseburger.img and Magisk-v15.3.zip.
Rebooted to TWRP and installed the Codeworkx TWRP using the Install->Image option inside TWRP.
Rebooted to TWRP again to make sure that my TWRP was updated.
Entered WIPE from TWRP main menu and used the 'Format' option to Format the Data and typed 'Yes'
This deleted my Internal Storage so I had to backup everything beforehand.
Then used advanced wipe to wipe Cache and Dalvik.
Mounted the internal storage by using the Mount option from TWRP main menu.
I was having problem copying files to the internal storage so I rebooted TWRP and the problem was fixed.
Copied the OnePlus full update and Magisk zip file.
Installed the OnePlus full update and Wiped Cache and Dalvik and rebooted the device to make sure that the OS boots.
Then rebooted the device to fastboot to flash Codeworkx TWRP again because it was unavailable.
Booted into TWRP and flashed Magisk.
I am now on Oreo and I hate the way Ambient Display looks right now.
Click to expand...
Click to collapse
beningodfrey4 said:
Just flash the full zips from TWRP and reflash Magisk to maintain root.
Click to expand...
Click to collapse
Yes but is there a way to dirty flash so you don't have to wipe your data?
Yes, obviously a lot more steps to remain encrypted, but worth it if you want to keep your data intact. Do try it out and reply the outcome on that thread.
https://forum.xda-developers.com/oneplus-5/how-to/guide-upgrade-nougat-rooted-encrypted-t3734779
You guys don't understand. Any tutorial that includes "format data" means EVERYTHING gets wiped - even internal storage.
The OP is asking for a way to avoid it, and I think there isn't any. So you either bite the bullet or stay where you are.
Also, I had trouble flashing Magisk 15.3 with codeworkx recovery. Worked fine with bluspark.
Rhoban said:
You guys don't understand. Any tutorial that includes "format data" means EVERYTHING gets wiped - even internal storage.
The OP is asking for a way to avoid it, and I think there isn't any. So you either bite the bullet or stay where you are.
Also, I had trouble flashing Magisk 15.3 with codeworkx recovery. Worked fine with bluspark.
Click to expand...
Click to collapse
Do you think its worth the jump? Are you seeing better battery life or any other improvements?
SysAdmNj said:
Do you think its worth the jump? Are you seeing better battery life or any other improvements?
Click to expand...
Click to collapse
It feels a bit faster, but I used to run Boeffla Kernel with battery optimized interactive governor on Nougat. So that's probably why.
As for battery, I don't really see a big improvement.
The biggest benefit was a clean system and internal storage. Don't even have face unlock, so can't comment on that.
I am happy with oreo!
Magisk
xposed framework sdk26 v90beta1
greenify + boost
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps
i installed system ui tuner and substratum on oos pie ob 22, and my OP5 is bootlooping (i think because of it). I have tried uninstalling and reinstalling Magisk from recovery,flashing the rescue zip of substratum, and moving both apps from the data partition (in app and data folders) elsewhere (read somewhere that this is equivalent to deleting the apps).i have also cleared cache many times.
Is there a way to revert this? I haven't tried anything else to not make things worse. Can i just dirty flash the zip (without compatibility)? i would like to keep the apps and data as they are even if the fixing procedure is longer. I have only managed to install it 2 days ago with great suffering
Thanks
update: dirty flash did not help
yohouse2 said:
update: dirty flash did not help
Click to expand...
Click to collapse
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
Thanks. will try this out as soon as i get the chance.
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
is backing up the data partition any helpful after dirty flashing over the old ROM. i.e: will restoring it in the new clean ROM actually work, or will it end up corrupting it as well?
yohouse2 said:
is backing up the data partition any helpful after dirty flashing over the old ROM. i.e: will restoring it in the new clean ROM actually work, or will it end up corrupting it as well?
Click to expand...
Click to collapse
Every situation is unique. Bootloops are cause by system problems. So in theory it should work but there's only one way to find out.
try reinstalling rom through ADB
Download official stable firmware file from their official website and then flash ..i couldnt be able to understand ur exact issue but i solved my bricked phone through that
OOS recovery does support installation through ADB
Awkydee said:
Neither of those apps should cause bootloops. I used substratum on OB22 with no issues and again in OB23 with no issues. I don't see the use of UI tuner as the firmware on the OnePlus 5 had plenty of customizations. It sounds like you need to do a clean install. Maybe try backing up your phone, wiping your caches, system, and data partitions. Do a clean install and restore the data partition. Just an idea. Otherwise it's a clean install.
Click to expand...
Click to collapse
I am wanting to update to Pie but for the life of me I can not see anywhere that says it is safe to update the phone once it's rooted. Can you point me in the right direction to a thread that gives info? Or let me know what you have done. Please and thank you!
ADGill0926 said:
I am wanting to update to Pie but for the life of me I can not see anywhere that says it is safe to update the phone once it's rooted. Can you point me in the right direction to a thread that gives info? Or let me know what you have done. Please and thank you!
Click to expand...
Click to collapse
I simply download OB22 and removed the compatibility.zip and dirty flashed it in TWRP. Once it was finished I re-flashed magisk v18.0 and wiped both caches and rebooted. That's it then I was on pie. No data loss or issues.
Awkydee said:
I simply download OB22 and removed the compatibility.zip and dirty flashed it in TWRP. Once it was finished I re-flashed magisk v18.0 and wiped both caches and rebooted. That's it then I was on pie. No data loss or issues.
Click to expand...
Click to collapse
Did you have to update TWRP too?
No I did not. As long as your version has treble support then you're good.
yohouse2 said:
i installed system ui tuner and substratum on oos pie ob 22, and my OP5 is bootlooping (i think because of it). I have tried uninstalling and reinstalling Magisk from recovery,flashing the rescue zip of substratum, and moving both apps from the data partition (in app and data folders) elsewhere (read somewhere that this is equivalent to deleting the apps).i have also cleared cache many times.
Is there a way to revert this? I haven't tried anything else to not make things worse. Can i just dirty flash the zip (without compatibility)? i would like to keep the apps and data as they are even if the fixing procedure is longer. I have only managed to install it 2 days ago with great suffering
Thanks
Click to expand...
Click to collapse
Try dirty flashing your rom again. ?
I just clean flashed the rom again and it was good to go