Develop Bugs

Help me CM13 problem

Hello guys, i have a big problem: i can't install pure CM13 roms, i' ve installed the rom always in the correct mode, but they go only in bootloop at start! CM13 roms work on my phone only when i install agnikernel on them. Why? i want to use original kernel roms! I tried in every way (change recovery, all wipes, change gapps etc)but don' t work:crying: I' m desperate:crying:
Thanks to all can help me. (and sorry for bad english)

Wipe
Hello and thank you for using Q/A,
you need to wipe all partitions, expect internal storage. Then flash GApps and ROM. First ROM then GApps. But flash the GApps right after ROM and don't boot into the system before.

Trafalgar I resolved I understood that the TWRP doesn't wipe all in note 2 partitions . So I used the Old Philz recovery for wipe all (wipe for install new ROM) and everything work.
Thanks for help

No Wifi & Sim, Random reboots (Really need help)

My Issue:
No Simcard is found and the Wifi setting wont even show up any Wifi, only the loading bar. When i wait a few minutes my OP3 reboots and the rest works untill in reboots again after a few minutes.
My Story:
Yesterday i updated to 3.2.6 with magisk, phh systemless root and systemless xposed and everything went fine.
Today i did a backup (all partitions) and did a full wipe (except storage) and then flashed Resurrection Remix. I cant tell if the issue was already occuring at this time but i did a full wipe (except the internal storage partition, everything) again and recovered my backup. Definitely since then i am nolonger able to use my phone. I tried wiping everything (now even with storage) and flashing pure stock OOS (3.2.6) but nothing changed.
I am very desperate and dont know whats going on and how to fix it. Thanks to everyone who can help.

when you say you did a backup, exactly which partitions did you backup?
when you say full wipe, exactly which partitions did you wipe?
when you say then flashed OOS, exactly which version did you flash? And have you ever flashed the OOS CB 3.5.2?

Thanks for your fast answere i hope you can save my ass.
I went to Advanced wipe and selected everything except internal storage at the first time and the second time when i tried to clean flash oxygen os i wiped everything you can find there to be sure.
My Backup and the Clean Oxygen OS zip are both 3.2.6
In my Backup every partition is backed up except Cache.
No i never installed any CB.
Additional info: it was the unofficial [OxygenCam] Ressurection Remix and i did not flash Gapps over RR.

regardless of what you did, a clean flash should work if you're wiping /system + /data and then flashing a TWRP flashable version of OOS (since it includes gapps)
regarding RR, it probably requires gapps, but i could be wrong as i haven't used it (i know gapps were needed for sultan's CM which I used, for example)

2x4 said:
regardless of what you did, a clean flash should work if you're wiping /system + /data and then flashing a TWRP flashable version of OOS (since it includes gapps)
regarding RR, it probably requires gapps, but i could be wrong as i haven't used it (i know gapps were needed for sultan's CM which I used, for example)
Click to expand...
Click to collapse
Yes but my problem is that i wiped data and system a second time and tried flashing the clean 3.2.6 and after that in the first boot setup guide kinda thing it begins with my issue of no sim wifand random reboot, i my try with 3.2.4 now (sounds more stable)
Is there a downloadlink for full rom 3.2.4 at the op homepage?

I clean flashed oos 3.2.4 like you said but still the same error...
It seems like my efs is broken, i have no imei number anymore

Unwanted OS factory reset during *any* flashing and dirty updates on an Oneplus 3

Hello everyone,
I have flashed and dirty flashed, installed twrp and others for years for my different phones. But this Oneplus 3 seems different.
I flashed TWRP 3.1.1-0 to it and then LineageOS official 2017-05-something, after that the Magisk 13.0 and then OpenGapps aroma. This was done with a full phone wipe (system, data, dalvik cache, internal storage, cache).
But, afterwards I noticed that whenever I installed an updated build of LineageOS, or ANY other zip, the system would act as if a full factory reset was performed! This never happened before with Cyanogenmod or any of my previous phones.
This makes updating LineageOS super tedious - as after EVERY nightly I update I have to log into my Google account, install Titanium backup and restore all apps and their settings.
Could anyone give me a hint on whether I have missed something in moving my flashing habits from Cyanogenmod to LineageOS era?

There were reports, that the official TWRP has some problems and wipes data, when installing a zip.
I think this is the issue with TWRP.
Install the unofficial build from here: https://forum.xda-developers.com/on.../recovery-official-twrp-oneplus-3-3t-t3543391
or use TWRP from blu_spark here:
https://forum.xda-developers.com/devdb/project/?id=15934#downloads

Well - this explains everything! Thank you so much cl0g for this hint!

Bootloop on every Magisk installation

Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:

I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)

Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.

Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.

I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.

TWRP restore and Lineage 17.1

I have TWRP 3.4.0.1 and I have recently installed Lineage 17.1
Before the Lineage instalaton I made a backup of my Stock Android 6.0.
My installation Lineage 17.1 + gapps pico 10.0 was straightforward but I seem to be havinga problem in using Restore in TWRP.
I can restore the stock installation... though I need to keep the screen "alive" otherwise it fails and restarts.
Restoring Lineage is a problem and seems to boot loop (not sure how long I should wait ?)
Would somebody please advice what I should Wipe when going from "Stock" to a restore of Lineage backup and should I take any particular options on either the Backup or Restore.
If I go from a Lineage installation to Lineage restore (I'm experimenting with different gapps versions) do I need to handle this in a different way ?
Will what I backup and/or choose to restore guide what I should wipe ?
If I'm doing a Restore should I be wiping anything ?

CRJ343 said:
I have TWRP 3.4.0.1 and I have recently installed Lineage 17.1
Before the Lineage instalaton I made a backup of my Stock Android 6.0.
My installation Lineage 17.1 + gapps pico 10.0 was straightforward but I seem to be havinga problem in using Restore in TWRP.
I can restore the stock installation... though I need to keep the screen "alive" otherwise it fails and restarts.
Restoring Lineage is a problem and seems to boot loop (not sure how long I should wait ?)
Would somebody please advice what I should Wipe when going from "Stock" to a restore of Lineage backup and should I take any particular options on either the Backup or Restore.
If I go from a Lineage installation to Lineage restore (I'm experimenting with different gapps versions) do I need to handle this in a different way ?
Will what I backup and/or choose to restore guide what I should wipe ?
If I'm doing a Restore should I be wiping anything ?
Click to expand...
Click to collapse
Flash this immediately after restoring the Lineage 17.1 backup and you will be happy http://www.mediafire.com/file/a454nnpp8l7afbr/fix_rootfs_label.zip/file

Fixed !
Thanks for your advice ....solved all the problems.
Maybe this should be added to the standard installation instructions or is this problem unique to 17.1 ?