Related
I used sultan's version of CM13 for 2 month and last week end i flashed OOS beta 7 and now i have several problems :
- My booting animation is neither the oneplus animation nor the one i flashed (the marvel/dc one, yes i reflashed it after flashing OOS), it is the word android. how can i change that?
- I can't flash Xposed : he tells me there is no space on the system partition and then the phone bootloop : i have a runing superSU 3.0.2-22 (the phone is rooted, ever app that uses root works)
- I have a zooper widget who doesn't load at startup (i have to opent the zooper app) and i checked, i allowe it to start at the start of the phone
Any idea on what i can do? i thought that maybe the kernel of sultan didn't get witched back to the original kernel when i flashed OOS and that causes problems
Friend, I will advice you tu flash Freedom OS 1.11 which is build on top of beta 7. Why I am saying this.
1. It allows to change the boot animation at the time of installation.
2. It will allow you to de boat the Google/oneplus pre-installed apps at the time of installation. That you can even do on stock beta 7 using titanium Backup app. That will resolve the problem you got while flashing xposed.
3. On beta 7 xposed wont work it will stuck on boot logo. So go to official xposed link and download the latest build, that will work.
4. Before installing freedom os I will highly recommend your too go through few last pages on its thread.
Sent from my ONEPLUS A3003 using Tapatalk
manishsoni7689 said:
Friend, I will advice you tu flash Freedom OS 1.11 which is build on top of beta 7. Why I am saying this.
1. It allows to change the boot animation at the time of installation.
2. It will allow you to de boat the Google/oneplus pre-installed apps at the time of installation. That you can even do on stock beta 7 using titanium Backup app. That will resolve the problem you got while flashing xposed.
3. On beta 7 xposed wont work it will stuck on boot logo. So go to official xposed link and download the latest build, that will work.
4. Before installing freedom os I will highly recommend your too go through few last pages on its thread.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
how is the camera on freedomOS?
will freedomOS update there build at the same rate as the betas or is it exeptionaly on the same base?
for the xposed, i did use the last build and it didn't work. but i am not against
using a different OS if can solve my problems
bigben14 said:
how is the camera on freedomOS?
will freedomOS update there build at the same rate as the betas or is it exeptionaly on the same base?
for the xposed, i did use the last build and it didn't work. but i am not against
using a different OS if can solve my problems
Click to expand...
Click to collapse
1. Camera is the same that you have on beta 7. Actually Freedom os is deboated stock oxygen with some extra tweaks like custom kernel, audio mods etc. Every thing is customizable there.
2. And yes they provide update as soon as newer build comes from oneplus.
3. This can solve all the issues you mentioned with the same taste of beta 7.
Sent from my ONEPLUS A3003 using Tapatalk
manishsoni7689 said:
1. Camera is the same that you have on beta 7. Actually Freedom os is deboated stock oxygen with some extra tweaks like custom kernel, audio mods etc. Every thing is customizable there.
2. And yes they provide update as soon as newer build comes from oneplus.
3. This can solve all the issues you mentioned with the same taste of beta 7.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
thank you very much, i'll try it then. hope it fixes evrything
I installed 3 custom roms previously and all of them worked perfectly. These are the ROMS I installed:
Cosmic OS (build-2017/01/10, vendor-nmf26f, opengapps nano 2016/12/11)
SASOP-N (build-2017/01/09, vendor n4f26i, dynamic gapps full 2017/01/07)
Pure Nexus (build-2017/01/13, vendor n4f26i, dynamic gapps full 2017/01/07)
All these roms got the same bug. Camera works fine if I restart the phone when it is crashed. Please let me know if someone know the reason.
jkvithanage said:
I installed 3 custom roms previously and all of them worked perfectly. These are the ROMS I installed:
Cosmic OS (build-2017/01/10, vendor-nmf26f, opengapps nano 2016/12/11)
SASOP-N (build-2017/01/09, vendor n4f26i, dynamic gapps full 2017/01/07)
Pure Nexus (build-2017/01/13, vendor n4f26i, dynamic gapps full 2017/01/07)
All these roms got the same bug. Camera works fine if I restart the phone when it is crashed. Please let me know if someone know the reason.
Click to expand...
Click to collapse
Copy important user data to a computer. Then completely wipe your entire device by install the latest 7.1.1 factory image via fastboot. Now, test your camera.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Copy important user data to a computer. Then completely wipe your entire device by install the latest 7.1.1 factory image via fastboot. Now, test your camera.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you for the suggestion. Can I use Substratum theme engine on stock ROMs? I install custom ROMs to get full substratum compatibility on my device.
jkvithanage said:
Thank you for the suggestion. Can I use Substratum theme engine on stock ROMs? I install custom ROMs to get full substratum compatibility on my device.
Click to expand...
Click to collapse
I have no idea, however I don't think so.
Sent from my Nexus 5X using Tapatalk
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
kvothe26 said:
So, I'm very eager to upgrade to a 7.1.1 custom ROM from 6.0.1 (currently using Dirty Unicorns 6.0.1), but I seem to have an issue with any android 7.1.1 version of a custom ROM I install where the sensors for auto rotate and auto brightness stop working. I've tried complete wipes and resets and installed crDroid, resurrection remix dirty unicorns and lineage OS. All of them have the same result. When downloading any apps that can be used to test and calibrate sensors, they all will read for that the sensor is unavailable for all hardware in the phone except for Wifi and GPS. Is this a general issue with android 7.0.1 on nexus 5x or is this just me? I've yet to find any other forums or pages with anyone experiencing this.
Any suggestions at all on this? I don't want to be stuck using Android 6 forever.
Any advice that can be offered would be greatly appreciated!
Ryan
Click to expand...
Click to collapse
I have a similar problem with every 7.1.1 custom ROM. Lift to check phone is not working (and yes, ambient display is enabled, vendor is correct). Every stock-based 7.1.2 ROM does work. Try flashing Stock+ 7.1.2 and see if your sensors work.
indian84 said:
Make sure you read the OP of the ROM you are installing.
Clean flash everything with correct vendor image.
Click to expand...
Click to collapse
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
kvothe26 said:
I am always clean flashing. What do you mean by correct vendor image? It's always a bullhead version of the ROM. Maybe I misunderstand what you mean.
Click to expand...
Click to collapse
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
indian84 said:
There is something called vendor image that you have to flash along with the ROM. It's generally linked to the build number.
Read the OP of the ROM you are using, it should have the correct vendor image you should use. If THE OP does not mention anything about the Vendor image, just search the thread or politely ask what vendor image to use.
Hopefully someone should link the download link for you. If not, you can easily Google it.
Click to expand...
Click to collapse
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
kvothe26 said:
Ohh. I was never aware of having to do something like this. I've always just downloaded the ROM and flashed it. Really appreciate this! Thanks! I'll have to give this a try.
Click to expand...
Click to collapse
I have a strong feeling flashing correct vendor image will solve your problems.
indian84 said:
I have a strong feeling flashing correct vendor image will solve your problems.
Click to expand...
Click to collapse
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
kvothe26 said:
You were right!
I downloaded the latest image from google and used the flash-all.bat script through fastboot, reflashed twrp, flashed crDroid 7.1.1, got a vendor image mismatch error on boot, then flashed the recommended vendor image version and now I'm booting without error and all sensors are working! I noticed Wifi detection and connection were working a but slow before, now everything is working perfectly. I was completely unaware that this needed to be done. It never came up as an issue for me when I was on Nexus 5.
I love the XDA community! Thanks a million for your help!
Click to expand...
Click to collapse
Separate Vendor partition was introduced with 5X and 6P. It was not needed on earlier devices.
LineageOS 18.1, see this link
Installation instructions :
- Download the zip(s).
- Install latest TWRP for clover
- Perform a backup of your current ROM (optional)
- Wipe dalvik/cache (upgrade from lineageos 18.1) and wipe system/data if upgrade from other rom.
- Flash ROM.
- Flash GApps (NikGApps is recommended) is a must.
- Optional: Flash latest Magisk for root.
Everything should work.
Source :
sdm660
Hello !
No SD card.
Clean installation.
NikGapps-core-arm64
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Awesome! Thanks!
rchoi999 said:
Thank you for the LOS R. Very good rom.
Clean install with Nikgapps omni, found download in Chrome to sd card showing "download pending" and chrome will force close.
Click to expand...
Click to collapse
I didn't use sdcard...it would be help if log is available...
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
addro said:
-----> Have New Update 2020/10/19 I didn't install it, don't know the difference
Click to expand...
Click to collapse
Some update in lineageos qcom repo....
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
@sabar_op, @sb56637, @amityg
Please keep in mind that there are many reports of bootloops etc using TWRP with Android 11.
TWRP officially supports all devices running Android up to 10, except devices LAUNCHED with 10 or later (having dynamic/logical partitions). There are no versions officially supporting devices running Android 11 to date:
TWRP 3.4.0 does not yet bring support for dynamic/logical partitions, which is required to support devices that launch with Android 10. It does, however, fix support for legacy devices that upgraded to Android 10, but retain the old partition scheme.
Click to expand...
Click to collapse
https://www.xda-developers.com/twrp...s-support-legacy-devices-upgraded-android-10/
Latest TWRP 3.4.0 arrived in June 2020 w/ support for devices upgraded to Android 10 (only). There's been no further versions. See here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post83725859
The solution for most using custom Android 11 based ROMs has been to KEEP STOCK Recovery and use ADB fastboot boot TWRP (NOT flash) command from PC when needing custom recovery functions to flash ROMs etc. This seems to work for most despite having no TWRP fully supporting Android 11.
Nb. To achieve root with MagiskSU, this method is probably even more critical as users are reporting bootloops with TWRP custom recovery (flashed) and Android 11 when flashing Magisk pretty much accross the board.
Nb2. Achieving root with MagiskSU can alternatively be done without custom recovery by flashing Magisk Manager patched boot.img (extracted from ROM) using ADB fastboot flash image command from PC. This may be a less fraught method.
I'm still on LOS 17.1, but the above outlines the approach I intend to take / try soon.
Hope it helps, PW
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.[/QUOTE]
View attachment 5123311
idcom said:
Running well on mi pad 4 plus. Really good apart from no sd card. Trying to upload logs.
Click to expand...
Click to collapse
View attachment 5123311[/QUOTE]
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?
Enry44 said:
I tried your room on my mi pad 4 wifi with twrp 3.4.0 no installation problem.
Click to expand...
Click to collapse
Thanks for confirmation...it means no problem with mipad 4 wifi only... :good::good::good:
sabar_op Sure, where can I find the log?
Can't open the attachment...send me a pm for the log link.
A quick question : is sdcard not showing in setting/storage?[/QUOTE]
Have PMed you. Settings-≥Storage shows Portable but corrupted. When I format nothing changes.
sb56637 said:
Thanks a lot for working on this. I tried the following versions, but they all bootloop (bootsplash, lockscreen visible for a few seconds, then reboots):
lineage-18.0-20201017-UNOFFICIAL-clover_rev0.zip
lineage-18.0-20201018-UNOFFICIAL-clover.zip
lineage-18.0-20201019-UNOFFICIAL-clover.zip
This is with a WiFI-only miPad 4, latest TWRP, complete wipe of everything first.
Click to expand...
Click to collapse
This is probably because didn't install a *Gapps package.
sabar_op said:
Can you take the log?
Never try for mipad 4 wifi only, I use mipad 4 wifi-lte, twrp 3.4.0 with previous los17.1 installed and no issue so far...
Click to expand...
Click to collapse
Alex Kane said:
This is probably because didn't install a *Gapps package.
Click to expand...
Click to collapse
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
sb56637 said:
Hmm, not sure, LineageOS 17.1 works fine on this tablet without Gapps.
Click to expand...
Click to collapse
Yeah, but apparently LOS 18.0 beta doesn't.
I tried LOS 18.0 (beta) without gapps first and it would bootloop after reaching the home-screen. Flashing gapps would solve the issue (for me) but I don't use gapps so ... I went back to LOS 17.1.
I also experienced the issue with the sdcard not being properly detected.
Removed by XDA Staff
Pictures ?
Enviado desde mi Pixel XL mediante Tapatalk
I've been using this rom for a few days, it's amazing, stock rom pixel 5, even i use adb mod installer for pixel 5 it works fine, thanks @Lunarixus
a_khusairi said:
I've been using this rom for a few days, it's amazing, stock rom pixel 5, even i use adb mod installer for pixel 5 it works fine, thanks @Lunarixus
Click to expand...
Click to collapse
Can you please give us a hint how to find "adb mod installer for Pixel 5"?
Thanks in advance
MartinN6 said:
Can you please give us a hint how to find "adb mod installer for Pixel 5"?
Thanks in advance
Click to expand...
Click to collapse
This https://forum.xda-developers.com/pixel-5/themes/custom-adb-magisk-module-mod-maker-t4186841
Downloaded and flashing now to test
Dont be dissapointed if i revert back to 10, i had issues with the 1st build of stock 11 (i havent tried the 2nd build), and ive seen others have them too
So dont take it personally if it doesnt pan out
Heres how i installed (much like most ROMS)
With the following in platform tools folder (unless you have your adb and fastboot in path) and at command prompt:
1) rom.zip (renamed from its longer name to make flashing easier)
2) twrp.img (renamed from its longer name to make flashing easier)
3) magisk.zip (renamed from its longer name to make flashing easier)
adb reboot bootloader
fastboot boot twrp.img
On device: wipe usual partitions &/ delete /sdcard/Android folder
push rom.zip /tmp
adb shell twrp install /tmp/rom.zip
adb reboot bootloader
fastboot boot twrp.img
push magisk.zip /tmp
adb shell twrp install /tmp/magisk.zip
adb reboot system
Setup ROM.....all good so far
Install full Magisk Manager (only stub appears from flashing zip) and reboot for full Magisk
Only gripes so far:
1) As with all ROMs ive ever seen with inbuilt G-Apps: Wheres Gmail? Annoying....
2) Be preprared for pretty much every app to need an update out of the box....needs more recent G-Apps cooked in if possible
73sydney said:
Downloaded and flashing now to test
Dont be dissapointed if i revert back to 10, i had issues with the 1st build of stock 11 (i havent tried the 2nd build), and ive seen others have them too
So dont take it personally if it doesnt pan out
Click to expand...
Click to collapse
Please let us know your thoughts and experience whether you continue to run this build out revert to 10 - thank you!
Great ROM definitely will stay here ??.... Maybe you should add more features in next builds like the possibility to hide the navbar without having to root (I only root because of this)
Just one question (I'm curious) why the name is Pixel 5a? @Lunarixus
images ? What a mania to present a product to us and not leave images of them
Enviado desde mi Pixel XL mediante Tapatalk
stifmaster81 said:
images ? What a mania to present a product to us and not leave images of them
Enviado desde mi Pixel XL mediante Tapatalk
Click to expand...
Click to collapse
In this case it's Pixel experience, so what you get is the same visually as a Pixel with Android 11.
@Lunarixus
I suspect youre using the device name Pixel 5a to pass SafetyNet out of the box?
I would personally rather it was left at original values (Pixel 2/XL) and then use MagiskHide Props Config to change the fringerprint to Pixel 2/XL Android 11 to pass SafetyNet (as with every other custom Pixel 2/XL ROM 10 ive tested with post-October security patches (Pixekl 2 XL - Android 10), that way its still recognised as a Pixel 2/XL, but maybe thats just me
I mean, i get it, less faffing about for users, but well, its not for me personally - ive just used MagiskHide Props Config to change it back to Pixel 2XL - Android 11
73sydney said:
@Lunarixus
I suspect youre using the device name Pixel 5a to pass SafetyNet out of the box?
I would personally rather it was left at original values (Pixel 2/XL) and then use MagiskHide Props Config to change the fringerprint to Pixel 2/XL Android 11 to pass SafetyNet (as with every other custom Pixel 2/XL ROM 10 ive tested with post-October security patches (Pixekl 2 XL - Android 10), that way its still recognised as a Pixel 2/XL, but maybe thats just me
I mean, i get it, less faffing about for users, but well, its not for me personally - ive just used MagiskHide Props Config to change it back to Pixel 2XL - Android 11
Click to expand...
Click to collapse
The stock Pixel 2 XL fingerprint has an older platform security patch level so it won't pass on a newer ROM (in this case the stock FP is October and my ROM is November)
So I use Pixel 5a as the device name to keep Safetynet in BASIC mode and I user the Pixel 5 fingerprint to have a newer security patch fingerprint.
So no, using Pixel 2 XL as stock is not an option anymore.
excellent, I would prefer the rom like this, I had a problem with my jabra helmets, for a moment it is heard with jumps, but then well, another thing, for my curious, I have seen that in google photos, the unlimited storage in original photos It does not have an expiration date, it will always be like this, like the first pixels?
supergenio2 said:
excellent, I would prefer the rom like this, I had a problem with my jabra helmets, for a moment it is heard with jumps, but then well, another thing, for my curious, I have seen that in google photos, the unlimited storage in original photos It does not have an expiration date, it will always be like this, like the first pixels?
Click to expand...
Click to collapse
Yes, it uses the first Pixels permission to make that happen so it will be indefinitely unlimited.
Lunarixus said:
The stock Pixel 2 XL fingerprint has an older platform security patch level so it won't pass on a newer ROM (in this case the stock FP is October and my ROM is November)
So I use Pixel 5a as the device name to keep Safetynet in BASIC mode and I user the Pixel 5 fingerprint to have a newer security patch fingerprint.
So no, using Pixel 2 XL as stock is not an option anymore.
Click to expand...
Click to collapse
All custom ROM's ive tested on the post-October security patch will pass SafetyNet with MagiskHid eProps Config, setting it to Pixel 2/XL and choosing Android 10 fingerprint. It passes in basic mode, without forcing basic mode....
Anyways this is a moot point for me as im heading back to Android 10 as this seems to have the same as yet unfixed issue with battery usage, it dropped dramatically on idle after i went to sleep last night, chewing through through battery. Your mileage may vary.
73sydney said:
All custom ROM's ive tested on the post-October security patch will pass SafetyNet with MagiskHid eProps Config, setting it to Pixel 2/XL and choosing Android 10 fingerprint. It passes in basic mode, without forcing basic mode....
Anyways this is a moot point for me as im heading back to Android 10 as this seems to have the same as yet unfixed issue with battery usage, it dropped dramatically on idle after i went to sleep last night, chewing through through battery. Your mileage may vary.
Click to expand...
Click to collapse
I'm not forcing people to root to have a device name changed.
Lunarixus said:
I'm not forcing people to root to have a device name changed.
Click to expand...
Click to collapse
Not arguing, just pointing out, its a custom ROM, 99.9% of people are gonna root it, otherwise they'd be on stock...
Changing the device name has potential issues....
Hello!! Been using for couple of days, everything is great! Battery isn't still stable yet but that's normal in initial setups.
I'm just missing one thing (for now): Add cards to power menu is not possible... Can you please add it to next build? Thanks! @Lunarixus
EDIT: The option is there, didn't see it till today!
Lunarixus said:
I'm not forcing people to root to have a device name changed.
Click to expand...
Click to collapse
good luck with this one, been there, done that, not again, certain users like to make things more complicated than they need to be but fail to read the "whys" things are the way they are (like in this instance of taimen no longer supported) then argue back. thanks for the awesome ROM and all the work you do for us throughout the years! I appreciate it!
Thread closed .
The "owners" of ROM were previously warned against posting HentaiOS ROMs on XDA.
Guess they forgot to intimate their maintainers
- XDA Staff