Database Develop

[Q] Dynamic Kat 1.4 Lost root

Since I'm mostly a lurker and I rarely run into issues that someone hasn't already run into, I don't have the post count to post on the actual Dynamic 1.4 thread. But I'm a little stumped. I seem to have lost root, and when I run anything in SS I get multiple I/O errors referencing data/data/chainfire su files.
I came from knoxraid. Installed new safestrap. wiped. Installed 1.0 from SS then 1.4 from SS. Set up the phone. Restored apps. Set up my favorite xposed modules. All was good for a few hours then I noticed I didn't get a full screen call ID on a call. I went in to check xposed and all the modules were unchecked. I tried to install/update but it said xposed wasn't compatible with my version. So I uninstalled xposed and tried reinstalling. Now it errors on install with "Can't install, free up space and try again" I have plenty of space, but I noticed the last I/O error I get in SS refers to data/data/xposed something or other. So I did the whole wipe and start with 1.0 process over, but nothing changed. No root. And I don't know if the I/O errors are keeping SS from wiping system when it installs, so I'm wary about installing another rom just to see if it works. But I can still boot into SS.
So I'm not sure which direction to go from here.
The errors are:
E:error: I/O error
E:error opening '/data/data/eu.chainfire.supersu/logs'
E:error opening '/data/data/de.robv.android.xposed.installer'
" " " /data/data/eu.chainfire.supersu/requests
fix permissions didn't work. An extra error was "unable to chmod data/data/eu.chainfire.supersu/requests"
I can't access those files using file explorer in SS.

Well if anyone runs into a similar issue- I wasn't able to install any applications after that as well.
A wipe from stock recovery fixed it. Although it wiped a lot more than I had anticipated

Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!

bri315317 said:
Was the installation on the stock slot? That is where it needs to be. Get your post count up so you can join us!
Click to expand...
Click to collapse
Yeah I made sure to use stock slot. And everything was fine for a few hours. I really don't think it had anything to do with the rom. I'm leaning towards and install/enable/unistall/disable process that I was burning through on xposed, since the locked up files were su and xposed. And I had other apps downloading and installing in the background. I just gotta learn to slow down. Got everything set up today and it's running beautifully. I was on your Dynamic GPE for JB and it was my favorite. I gave the KK version of knoxraid a shot but got super excited when I saw SS had updated and I could go back to dynamic without odin.
It was fun now that it's fixed. I hadn't been into stock recovery since the old DX days. I didn't realize a data wipe from there took out just about everything on internal storage. Good thing I had the important stuff backed up.
I've been following your work for a while. And you sir, are fantastic. :good:

SM-T710 rooted, but can't install Xposed

So I used Autoroot and got my tablet rooted. Root is working. I downloaded Flashfire. Downloaded the most recent Arm32 Xposed zip for the device. The Wanam one.
Short version: Leaving everything at default in Flashfire it fails out saying system can't be mounted (after turning black, then listing files) I think. It reboots so quick... It's hard to read.
First am I using the right one? ARM32?
Secondly... What is going wrong!
Edit: Another attempt I was able to read it was unable to find system in proc mounts if that helps.

Spadowski said:
So I used Autoroot and got my tablet rooted. Root is working. I downloaded Flashfire. Downloaded the most recent Arm32 Xposed zip for the device. The Wanam one.
Short version: Leaving everything at default in Flashfire it fails out saying system can't be mounted (after turning black, then listing files) I think. It reboots so quick... It's hard to read.
First am I using the right one? ARM32?
Secondly... What is going wrong!
Edit: Another attempt I was able to read it was unable to find system in proc mounts if that helps.
Click to expand...
Click to collapse
Never used Flashfire before. But TWRP works perfectly and installs Xposed without any issue.
http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686

Thanks. That's what I wound up doing. Working fine. Thanks!

Xposed for RK3288 Devices

Hi, im new here and this is my first post, so i appreciate all the help and feedback you can give me.
im interested in using xposed in android TV Box's and Dongles, i've been reading and learning all about it for more than a month now. i've got it to work on most TV Box's and dongles that i have "RK based devices with android V 4.4 or less",but i still have a problem with one device which is an RK3288 based with android 5.1 that is already rooted.
i used twrp to flash xposed-v86-sdk22-arm.zip which was successful, than i wiped Dalvik/cache and rebooted, but the boot stuck on bootanimation, i disabled xposed by installing the uninstaller.zip and everything went back to normal. i tried it many times but with no use. i noticed that twrp doesnt mount internal SD, i installed an older version of bootloader which gave me the ability to mount the internal Sdcard, and i tried to install xposed again and this time it pass the animation and goes to a black screen where i can use the mouse but nothing else. with some research i found that UT3+ is based on firefly board and their original ROM is available for download and it has the same bootloader version that came installed with the device, after flashing the new ROM i was able to mount the internal Sdcard and i tried to install xposed again, and this time it gives me optimizing apps but after it finish the device reboot and get stuck again on bootanimation.
my question is, if there is a log for errors to know why the system/boot get stuck , where can i find them??
and if there is no logs how can i monitor the booting process to find the info i need??
also i know or read what bootloader is but i dont understand how it is effecting xposed installation.
Sorry for the long post, and thank you for your help in advanced
EDIT: i finally got adb connection with the device and used logcat to get the logs, but im not sure how to attach the files. if anyone can help i will gladly send the logs. thanks

Update 1
i was looking at the logs "didnt know what to search for im not a developer" and i noticed that everything is crashing and "Not granting permission" ,"Unknown permission " are everywhere .
sample of logs:
Code:
"com.google.android.partnersetup.permission.WRITE_APP_PROVIDER in
package com.android.vendingW/PackageManager( 4712): Not granting
permission android.permission.BIND_WALLPAPER to package
com.android.camera2 (protectionLevel=18
flags=0x58bc45)W/PackageManager( 4712): Not granting permission
android.permission.BIND_APPWIDGET to package com.android.launcher3
(protectionLevel=18 flags=0x583e45)W/PackageManager( 4712): Unknown
permission android.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission
com.android.launcher.permission.READ_SETTINGS in package
com.android.launcher3W/PackageManager( 4712): Unknown permission "
so i decided to root again with KingRoot, and i tried installing xposed again, and it kinda worked. the system boot and the launcher opens but crashing messages keeps showing "Stresstest for 5.0 has stopped running" , "The process com.android.phone has stopped running", and others.
now im not sure about what im doing but i'll test two methods:
1- i will unpake ROM.img put xposed in the root and update the updater script to install xposed when i flash the ROM.
2- the device can run Linux version from SD card so i might run it and manually install xposed files.
if anyone have any tips or info please let me know. thanks

SOLUTION
For those who are having problems with their RK based android TV Box with android 5.1, if you get stuck on Boot animation or the system boots with black screen and you can use your mouse only, or if you getting errors when you boot the main problem would be your firmware is modified and up to Xposed V.86 is not supported because of the error "No implementation found for void dalvik.system.VMRuntime.clam" you can read more about it in this post https://github.com/rovo89/Xposed/issues/167.
and luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325

viVaPale said:
luckily dsa8310 made a modefied version of xposed, i tested it and it works you can find the download link here http://forum.xda-developers.com/showpost.php?p=67787484&postcount=325
Click to expand...
Click to collapse
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.

Anyone that can compile Xposed v87 to fix this problem for RK3288 Lollipop devices?
https://github.com/rovo89/Xposed/issues/167
https://android.googlesource.com/platform/art/+/379d09fe3c3feb7c2a2fb5a3623689b5ace7e79b
Are there instructions somewhere so we can compile it ourselves?
The code above looks like it needs to be applied to Android source code, what must be changed in Xposed Github code to fix it and compile our own new Xposed only for our devices?
Thanks

humptydumpty said:
I can't get to the page with the link. (I get a noob alert) We want to try this xposed on a ugoos ut3s (android 5.1 with a rk3288)
Would someone please be so kind to post it here or tell me where I can download it.
Click to expand...
Click to collapse
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend

viVaPale said:
Please try this link https://mega.nz/#!300ggYoJ!1vdLP0OyU2D1ky6pWv-Y3VJFH5paHSAqV3Y8A64bvkk
i recommend you download the xposed uninstaller in case something wrong happend
Click to expand...
Click to collapse
Wow ! Work nice on my haier pad971 (ifive air clone) rk3288 5.1.1 !!
Thanks so much

does anyone know if there's an RK3288 enabled xposed v89 built to avoid the issues described by viVaPale? Tried the one from 3.1.5 installer, but after boot it doesn't load the launcher, only mouse can be moved around like viVaPale describes.

XPosed with Lollipop

I have seen a couple of posts scattered around about xposed and if it can be used on lollipop. Yes it can, provided you are rooted of course. There are several different variants of the xposed framework, to my knowledge, only 1 works decently and the others...not so much. This is what I have set up to run xposed on my S5. Since this phone uses Touchwiz, there will probably be some limitations on what modules you can install or what modules even work.
Disclaimer: actual results may vary, you assume all liability for anything you do to your phone as well as inadvertently activating Skynet.
To avoid plagiarism, all of this information is taken from the link below. However, I put the links that are one this post in one easy to find location instead of post jumping to find what you need.
https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-5-0-x-t3455992
1. Make sure you are running a rooted, stock Lollipop 5.0 rom with FlashFire installed. This works with both Odex and Deodex roms!
2. Make a backup of your device with whatever app or method you choose. I would recommend FlashFire.
3. Install the Xposed Installer app to your phone. Do not run/open it after installation, it will not work as it still needs the framework installed.
>> https://forum.xda-developers.com/attachment.php?attachmentid=3921508&d=1477916609
4. Save the following file to your phone, either internal or external SD. I would recommend external SD card.
>> https://forum.xda-developers.com/attachment.php?attachmentid=3955895&d=1480698503
The OP says to install the zip file via recovery, we can not have a custom recovery installed due to locked bootloader. Use FlashFire to install the zip file for the Xposed framework. Once that has completed, reboot your phone and open the Xposed Installer app on the phone.
From there you can enable Xposed, download modules, etc. Keep in mind, I did not create any of this...therefore, I can not offer much help on how to use Xposed or if you are having issues installing/configuring. If you are having issues, please reply and ask but you may get referred to the OP of the software.
On the Xposed Installer app, there is (see the attached screenshot) that says something about there seems to be an issue with your rom blah, blah, blah. Xposed and Touchwiz have had issues working together. Please remember that not all modules may install properly or even work...might even jack your phone up, hard telling! Please research any and all modules before installing them first, better safe than sorry.

I feel that it is necessary to add instructions about the process of flashing with Flash Fire. For anyone who does this in the future, select install from .zip and select the file you downloaded. You don't need to mount /system read/write or any other options. This was unclear to me, so hopefully no one does it in the future.

Lineage OS 17 getting "Magisk is not installed"

I'm at my wits end trying to get Magisk back!
(The backstory is that I had been running a DirtyUnicorns OS for a year just fine, but then Pokemon Go started failing to login. So it was time to update.)
Using a Samsung Tab 4 (SM-T330NU)
Formatted and installed stock OS/boot
Used Odin to flash "twrp-3.0.0-3"
Used TWRP recovery to update to "twrp-3.3.1-0"
Installed "Lineage OS 17" (and added Gapps) - made sure it booted and all was well
Booted into TWRP recovery and installed the latest "Magisk-v20.4"
Wiped cache and rebooted
Installed the latest "MagiskManager-v7.5.1" and got "Magisk is not installed"
After a great deal of searching I learned how this is supposed to be corrected:
Took the boot.img from the Lineage OS 17 zip,
Used Magisk to patch it, creating "magisk_patched.img"
Used TWRP recovery to install "magisk_patched.img" to the boot section
Wiped cache and rebooted
Still getting "Magisk is not installed"
Booted into TWRP recovery and installed the latest "Magisk-v20.4" just in case
Still getting "Magisk is not installed"
This is all after roadblocks for hours a day for a week trying to pass safetynet using Magisk on Lineage OS 16 for about a week, so I thought this fresh start would be easier and now I'm pulling my hair out.
Any suggestions would be helpful. I just want to be able pass safetynet and my ctsProfile match fails. Which I can't even begin to work on without Magisk core.
Thanks in advance.

First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed

Didgeridoohan said:
First thing I would check is if the Manager is installed to external/adoptable storage. The Manager can't work properly like that...
https://www.didgeridoohan.com/magisk/Magisk#hn_Magisk_not_installed
Click to expand...
Click to collapse
Thanks for the quick reply!
How do I check to see where it's installed and/or reinstall it to the proper storage? Because that could be it.
There's no SD card or USB device plugged in and I couldn't find more information online (I even scoured didgeridoohan.com before posting here).

Also, and this may be helpful, it appears the device is not rooted. Fx file explorer and root checker apps confirm this. So it's possible even with the steps I followed that Magisk core really isn't installed and the apk is telling the truth (I'm just at a loss to know how that's possible after flashing the zip and flashing the patched boot file, both in twrp).

If you have no SD card installed adoptable storage won't be an issue.
You can easily verify through TWRP if the core Magisk files have been installed. Check in /data/adb/magisk. It should contain busybox, magisk, magiskboot and magiskinit binaries, together with addon.d, boot_patch and util_functions scripts.
Seeing the recovery log from when you attempt to install the Magisk zip in TWRP might show us something. Also try the could also be a good idea trying the Canary release to see if there's any difference from stable v20.4.

(This thread can be locked/(closed?)/answered)
I tried my damnedest and nothing worked. So I wiped/formatted lineage-17.1-20200512 and installed lineage-17.1-20200419. THIS was the ease with which I was accustomed to installing Magisk (Recovery install and immediately working on boot). Sadly, other problems abound and they are outside the scope of this subforum.
Just in case anyone reads this and cares:
- GPS Joystick was a no-go because apparently Lineage has a not-so-nifty feature that blocks the "draw over apps" android feature if your RAM is below some secret threashhold, which prevents the entire app from functioning.
- Fake GPS can take getting used to, and I'm used to it and love it, but the location and routing keeps crashing in the background, which means pogo closes when I tab back to start it back up again.
- Regardless of which I use I am rubberbanding back to my house... despite using all the tricks I can find or think of (yes, including 'smali patcher', specific app settings, systemizing the GPS app, setting off/on mock locations, etc)... but I think it's because this OS has no unique setting for the GPS data to be "device only".
Problems one and two are due to the ****ty ram on this Samsung tablet, which I've always known was an issue, so I suppose it might just be time to buy a phone specifically for this purpose. From what I read, the best cost effective option is an iPhone SE, and I'm truly not an Apple fan (I certainly would not risk my own phone being bricked or even merely wiped).
Not sure how I used it for the last year without this many issues, but it seems like that's over now unless I want to deal with DirtyUnicorn OS again, and that was it's own nightmare sometimes.
Thanks all for reading, but especially Didgeridoohan for replying and for all the resources on your pages and threads.