Develop Bugs

Xposed and January update

Hello
I flashed on my N5X stock images of January upadte and tried to root and install xposed. So i flashed franco.kernel r2, rooted systemlessly with no proble, no FCs. And then when I flashed xposed got I FCs on Calc, Downloads and Bluetooth. It'đ normal (I hope no ) Had anyone problem like me?

domicq said:
Hello
I flashed on my N5X stock images of January upadte and tried to root and install xposed. So i flashed franco.kernel r2, rooted systemlessly with no proble, no FCs. And then when I flashed xposed got I FCs on Calc, Downloads and Bluetooth. It'đ normal (I hope no ) Had anyone problem like me?
Click to expand...
Click to collapse
For me xposed is a hit and miss. But I blame the modules more then xposed itself. It always boot up fine by itself. I guess it is just the modules that needs to be made working better with 6.0.1
Clearing cashe fixes the boot loop i get stuck in some times. Other times I need to disable the xposed conf file. and it boots up again with no active modules.
No FC.

frewys said:
For me xposed is a hit and miss. But I blame the modules more then xposed itself. It always boot up fine by itself. I guess it is just the modules that needs to be made working better with 6.0.1
Clearing cashe fixes the boot loop i get stuck in some times. Other times I need to disable the xposed conf file. and it boots up again with no active modules.
No FC.
Click to expand...
Click to collapse
I just installed Xposed, without any module active and i have those FCs.

domicq said:
I just installed Xposed, without any module active and i have those FCs.
Click to expand...
Click to collapse
I am running stock with no FC.
Make a clean redo.
Preferably flash the clean install straight from google with all the right updated radio and vendor etc and try again.

frewys said:
I am running stock with no FC.
Make a clean redo.
Preferably flash the clean install straight from google with all the right updated radio and vendor etc and try again.
Click to expand...
Click to collapse
I do clean install two times have you encrytped data?

domicq said:
I do clean install two times have you encrytped data?
Click to expand...
Click to collapse
Not encrypted. But I think it should work anyway.
Try without.
Are you flashing through ADB or through recovery?

frewys said:
Not encrypted. But I think it should work anyway.
Try without.
Are you flashing through ADB or through recovery?
Click to expand...
Click to collapse
Rom through fastboot, anything else through recovery.
Gesendet von meinem Nexus 5X mit Tapatalk

N5X encrypted running the latest image + xposed v79. No issues at all. I would advise clearing cache/dalvik via recovery to force recompiling of the apps.

Calculator was crashing for me, so I believe I finally just deleted it from /system/app, reinstalled it, and it's been fine ever since.

C3C076 said:
N5X encrypted running the latest image + xposed v79. No issues at all. I would advise clearing cache/dalvik via recovery to force recompiling of the apps.
Click to expand...
Click to collapse
Omg man! i was clearing cache and dalvik but before installing xposed, i was stupid. nvm. thank you:good:

On CM13, I just flashed supersu via TWRP, please help

I'm new to CM13 and I noticed I didn't have root so I went into TWRP and flashed superSU.
The phone booted up fine, I just noticed I wasn't supposed to do this!!
I DON'T have a backup of my current build.
Can anyone suggest what I should do here before something bad happens?

oshax said:
I'm new to CM13 and I noticed I didn't have root so I went into TWRP and flashed superSU.
The phone booted up fine, I just noticed I wasn't supposed to do this!!
I DON'T have a backup of my current build.
Can anyone suggest what I should do here before something bad happens?
Click to expand...
Click to collapse
Hi, I think you could simply reflash your ROM and GAPPS.
That should do it I believe.

oshax said:
I'm new to CM13 and I noticed I didn't have root so I went into TWRP and flashed superSU.
The phone booted up fine, I just noticed I wasn't supposed to do this!!
I DON'T have a backup of my current build.
Can anyone suggest what I should do here before something bad happens?
Click to expand...
Click to collapse
What's the issue? You can flash SuperSU if you'd like root access through the SuperSU app. Doesn't make a difference if root is already built into the ROM, if that's what you're worried about.

kipue said:
Hi, I think you could simply reflash your ROM and GAPPS.
That should do it I believe.
Click to expand...
Click to collapse
Yeah I was thinking the same thing. Just dirty flash ROM and GAPPS, just like if I was upgrading and should retain data but not supersu root. Thanks for the response.
dpryor88 said:
What's the issue? You can flash SuperSU if you'd like root access through the SuperSU app. Doesn't make a difference if root is already built into the ROM, if that's what you're worried about.
Click to expand...
Click to collapse
I'm worried because of these instructions from CM Forums:
http://www.cyanogenmods.org/forums/topic/root-android-using-twrp-recovery-install-supersu/
ROOT ACCESS FOR CYANOGENMOD ROM USERS AND ROMS BASED ON CYANOGENMOD:
If you install SuperSU on a CyanogenMod ROM or any other ROM built on top of CyanogenMod such as Resurrection Remix ROM or any other ROM then then there is a high probability that you will end up with bootloop. CyanogenMod has built-in “su” binary which is just hidden and needs to be accessible by a simple guide.
Click to expand...
Click to collapse

oshax said:
Yeah I was thinking the same thing. Just dirty flash ROM and GAPPS, just like if I was upgrading and should retain data but not supersu root. Thanks for the response.
I'm worried because of these instructions from CM Forums:
http://www.cyanogenmods.org/forums/topic/root-android-using-twrp-recovery-install-supersu/
Click to expand...
Click to collapse
Never happened to me on any phone using a cm based ROM. Seems like this info is outdated.
Anyway, yeah just flash the cm ROM and then Gapps. It'll get rid of su root

oshax said:
Yeah I was thinking the same thing. Just dirty flash ROM and GAPPS, just mods.org/forums/topic/root-android-using-twrp-recovery-install-supersu/[/URL]
Click to expand...
Click to collapse
Well I think if you had no bootloader yet, you'd be safe

Nightly 14.1 lineageOS Rom For Crackling

https://download.lineageos.org/crackling
The First One!

Do we need su for arm or su for arm64?

Obscurax said:
Do we need su for arm or su for arm64?
Click to expand...
Click to collapse
Arm64

What's the build name of the Swift 2X?
Sent from my Moto G4 using XDA Labs

kartotar said:
What's the build name of the Swift 2X?
Click to expand...
Click to collapse
marmite

M.A.K said:
marmite
Click to expand...
Click to collapse
Thanks. Do you have any idea if LineageOS will be supported on Marmite?
Sent from my Moto G4 using XDA Labs

AFAIK, Swift 2 ks not officially supported by Lineage OS, so no. You may be able to find an unofficial version though.

Cannot dirty flash
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?

Got no problems installing it via TWRP. Works great, stable so far.
crdroid was fine too, lots of special settings (little too much for me), but I prefer a ROM with regular OTA updates. Thank you beroid anyway.
P.S. My grammar help changes "beroid" to "heroic"

Can this be installed over the top of cm13.0 nightly?

Mithodin said:
I currently have thomson.aa's unofficial lineage os build installed. This update shows up in the updater app, but after I download it, it says the zip is corrupt or unsigned and it does not let me install it. If I manually download it and try to install via TWRP, it fails saying "can't install this package on top of incompatible data. Please try another package or run a factory reset". I would hate to have to reinstall all my stuff, though. Is there some way around this? Or is there something wrong with the update?
Click to expand...
Click to collapse
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
I dirty flashed from stock -> cm13 -> crDroid -> thomson.aa's LOS14 without issue. I tried with the official release and got the same as you. So after editing the installer script to force it to install, it did. But once it booted, everything kept force closing. It just wasn't happening.
So I wiped data and chose to restore my backup from google. I just installs most of your apps but it saves a bit of time. Still need to set things up properly though.

M.A.K said:
You basically asked the same question in 2 threads??? So as this isn't really thomson.aa's problem, I'll answer you here.
Click to expand...
Click to collapse
I figured this might be due to either
- Something being wrong with the currently installed build
- Something being wrong with the one I'm trying to install
That's why I posted in both places. Sorry if that is not the thing to do.
Thanks for your reply. I guess I'll have to do another reinstall then.

Wifi
Installed tonite smoothly however no wifi - anyone else with this?

Same here, just reported a bug to the bugtracker.

Make a clean install three days ago, all works fine

pahesis said:
Same here, just reported a bug to the bugtracker.
Click to expand...
Click to collapse
I have no wifi, too (after trying a dirty install over an old CM13 that resulted in an error). Here's the issue in their bugtracker, I think, in case anyone else experiences this.
Got the same issue when trying to go back to CM13 now -___-

Seems strange that I've had no wifi issues. I've tried turning it on and off with no problems.
A few (maybe patronising) thoughts:
Did you guys check the md5 hash?
Which recovery did you use? I used TWRP 3.0.2.5
Were you previously on COS13.1.2? I was.
I downloaded fresh open-gapps for the install - ARM64, 7.1, nano.
I wiped system, dalvik, cache. Installed LOS14.1, su, gapps in that order.
The dirty boot left me with lots of force closures so I wiped data, dalvik and cache, completed the wizard after booting and all was fine.

M.A.K said:
Did you guys check the md5 hash?
Click to expand...
Click to collapse
Yes
M.A.K said:
Which recovery did you use?
Click to expand...
Click to collapse
TWRP-3.0.3-0
M.A.K said:
Were you previously on COS13.1.2?
Click to expand...
Click to collapse
I was on the latest CyanogenMod snapshot.
I wiped data, dalik and cache, then installed lineage, gapps and su. Restoring a nandroid backup of CM13 did bring the wifi back again.
I then wanted to restore my backup of lineage, because I already transferred most apps and settings and don’t care to much for the wifi (hoping it will be solved in not too far future), but TWRP failed to recover, getting stuck while restoring data, only restoring the system partition. Strangely, after this, the wifi worked, however I experienced many FCs. After wiping data again, the wifi was broken again, the MAC adress showing as 02:00:00:00:00:00.
Wiping system, I tried to reinstall lineage without any extras, but TWRP just got stuck again with no progress being made after detection of the partitions. Strangely, restoration of the lineage backup worked now, including data The original problem persists, of course.

I mentioned COS13.1.2 specifically because it flashes partitions other than system that may affect your situation. CM doesn't. If you've had COS13.1.2 installed previously then these other partitions should be up to date.
If you're having inconsistent results using TWRP3.0.3 it may be worth trying 3.0.2.5.

ES File Explorer
Hello guys! I have a small problem. I installed the LOS 14.1 and now I have error in ES File Explorer, "Sorry test failed. This feature cannot run on your phone".
The su binary I already threw, and all files bin already threw. Help solve the problem!
p.s. sorry for my English

How to recover a formatted phone stuck on lineageos bootscreen? with anti rollback

Hi
I unlocked the bootloader of my redmi note (whyred), and installed TWRP (booted it from fastboot and flashed from there, as it would not allow direct flashing due to anti rollback)
Then I formatted and wiped everything as described on the lineagos install docs.
It seems that this lost encryption and now the phone is stuck on the lineage os bootscreen.
How can I recover to a working lineag os?
I read about installing MUI ROM, and making sure to encrypt and not to format.
But I am afraid that this will trigger the anti rollback and brick my phone.
What is the best way to proceed?
(twrp recovery and fastboot works, normal boot is stuck probably because of missing encryption)
Please give me some advice - thanx!

OK ... fixed it.
Flashed miui_HMNote5HMNote5ProGlobal_V9.6.3.0.OEIMIFD_7fe1fc0813_8.1.zip from recovery.
Reinstalled Lineage OS without formatting.
Works now.
LOS should really delete the format from their installation guide!

Ricsi999 said:
OK ... fixed it.
Flashed miui_HMNote5HMNote5ProGlobal_V9.6.3.0.OEIMIFD_7fe1fc0813_8.1.zip from recovery.
Reinstalled Lineage OS without formatting.
Works now.
LOS should really delete the format from their installation guide!
Click to expand...
Click to collapse
I really don't get what encryption has to do with LOS not booting up, it's so weird.
So, if you format your data, to remove encryption, LOS doesn't boot? You mean, you're forced to use encryption?

@attitude12 ...exactly. This is what happened to me. I arrived here searching for info.
@Ricsi999 so installing a stock MIUI actually worked? I was a bit skeptical at first, reading this info also on Reddit.
If I remember well, I was on MIUI 9.5.19, so already with anti-roll-back v4 (I didn't upgrade to 10.x because I wanted LOS. I was waiting for that stupid unlock countdown...)
EDIT: So, will be OK to re-install a stock MIUI via TWRP? Or do I need to use some official Xiaomi tool?
Thanks.

Ricsi999 said:
OK ... fixed it.
Flashed miui_HMNote5HMNote5ProGlobal_V9.6.3.0.OEIMIFD_7fe1fc0813_8.1.zip from recovery.
Reinstalled Lineage OS without formatting.
Works now.
LOS should really delete the format from their installation guide!
Click to expand...
Click to collapse
U can even flash lazy flasher ?

Kireto00 said:
U can even flash lazy flasher ?
Click to expand...
Click to collapse
From my understanding this tool will disable the check for encryption by the lineageOs ROM, right?
If yes, will be possible to happily update the LOS with nigtlies and all?

xda_dentex said:
@attitude12 ...exactly. This is what happened to me. I arrived here searching for info.
@Ricsi999 so installing a stock MIUI actually worked? I was a bit skeptical at first, reading this info also on Reddit.
If I remember well, I was on MIUI 9.5.19, so already with anti-roll-back v4 (I didn't upgrade to 10.x because I wanted LOS. I was waiting for that stupid unlock countdown...)
EDIT: So, will be OK to re-install a stock MIUI via TWRP? Or do I need to use some official Xiaomi tool?
Thanks.
Click to expand...
Click to collapse
Yes it's ok to install stock MIUI with TWRP, especially to re-encrypt.
I used the latest non arb V4 version from TWRP (miui_HMNote5HMNote5ProGlobal_V9.5.17.0.OEIMIFA_35b0cda8a7_8.1.zip).
But if you want to "come back to MIUI" I think you need to flash the full rom usign MIUI tool (not sure about that).
To re-encrypt the rom you can also use the Pixel Experience rom, boot into system, and encrypt.
I was able to re-encrypt from a LOS in another device too, but I had to run manual commands to ensure /data was properly sized.
---------- Post added at 12:34 PM ---------- Previous post was at 12:33 PM ----------
xda_dentex said:
From my understanding this tool will disable the check for encryption by the lineageOs ROM, right?
If yes, will be possible to happily update the LOS with nigtlies and all?
Click to expand...
Click to collapse
yes, its one of the feature, to disable the force encryption checks.
See page:
https://forum.xda-developers.com/android/software-hacking/zip-lazyflasher-tool-flashing-custom-t3549210

What I did in the end, has been to install the AOSP-Extended ROM, forgetting about the encryption and all that fuss. It worked out of the box, installing via TWRP.
I didn't want to go back to MIUI, that I hated, I just wanted LineageOS (in this case another AOSP ROM I think will do the job fairly good. It seems promising. Not to mention that whyred seems unmaintained at LOS).
Inviato dal mio Redmi Note 5 utilizzando Tapatalk

xda_dentex said:
What I did in the end, has been to install the AOSP-Extended ROM, forgetting about the encryption and all that fuss. It worked out of the box, installing via TWRP.
I didn't want to go back to MIUI, that I hated, I just wanted LineageOS (in this case another AOSP ROM I think will do the job fairly good. It seems promising. Not to mention that whyred seems unmaintained at LOS).
Inviato dal mio Redmi Note 5 utilizzando Tapatalk
Click to expand...
Click to collapse
It's very simple to redo the encryption, really!
Then you can reflash LOS easily.
Up to you.

[UNOFFICIAL][ROM] crDroid 5.12 for Galaxy Tab E [SM-T560NU][Pie]

I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.

I tried to install the ROM to my SM-T560NU, it boots with no issues. It's very laggy to use, so I mess around with crDroid settings and I changed the scrolling cache setting (Settings->crDroid Settings->User Interface->Animations->Scrolling Cache) from Default enable to Default disable, it fixed the laggy issue.
I also tried to flash Vince2678's overclock kernel and it boots with no issues.

This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.

This rom is for Android 7?

zeovani said:
This rom is for Android 7?
Click to expand...
Click to collapse
>Android Pie
Sorry bud this an android 9 rom lol

edwardnizz said:
This is the Bomb. I have a Tab E TM-560NU. I failed miserably trying to install other roms. But yours went in 1st shot. Nice work!
Click to expand...
Click to collapse
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
edwardnizz said:
Question is I'm thinking about putting Magisk, But do I really need it? Is that like SU? Probably a very dumb question.
Click to expand...
Click to collapse
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.

Tickbaby said:
I am not responsible for any bricked devices. Install at your own risk!
This is experimental so please post any bugs you find.
SCREENSHOTS
What doesn't work:
I haven't found anything so far that seems to be broken. Doesn't mean it's bug-free though.
How to install:
1. Factory Reset
2. Format Data
3. Flash rom <-- Download
4. Flash GAPPS
5. Flash Magisk [optional]
6. Reboot to system
Enjoy.
Click to expand...
Click to collapse
download link for the rom is broken :/

Fruse said:
I've experience of flashing my tablet so I can flash my tablet without issues. Since it's too laggy to use, so I switched to LightningFastROM 17.1, for now.
If you had issues of flashing the ROM, I recommend to use this version of TWRP:
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
It's your choice whenever you want to use Magisk or not. If you want Busybox, ViPER4Android FX,etc... or other apps that requires root then you'll need to flash Magisk in order to use it.
Click to expand...
Click to collapse
I just installed liightningfast. It turns out, I forgot to wipe data the first time i tried. Thanks a bunch. Now i have a few choices! Dude your the BOMB!!

One Questions Dev's and Fellow members Can this rom be flashed on SM T561 too ?

running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys

malfuncion said:
running on the sm-t560nu well. no lag issues, doesn't pass safety net though. not that big of deal, was just hoping magisk hide worked. Did you by chance add in the patch (or is this even applicable) found here: https://github.com/kdrag0n/safetynet-fix/tree/master/patches/9/sys
Click to expand...
Click to collapse
i used super su to root

I have found a bug. When using stock screen recorder with puting only record internal audio, if u have headphones connected it freaks out. Plz don't mind the video, I clicked on it for representation of the issue.