Database Users

Root problems with newer ROMs

Curse these programs that won't use newer su/busybox combinations.
After installing one of the latest blur ROMs, I wasn't able to get webtop2sd to run (a very common problem), nor Cisco's Anyconnect VPN client. webtop2sd did the usual FC, while Anyconnect would complain that it couldn't start a "critical component". Going back to the one I was running before the upgrade didn't help either.
These problems are not unique to the beta, nor this ROM, but here's what I had to do:
Follow the steps in this thread starting in step 6:
http://forum.xda-developers.com/showpost.php?p=21155110&postcount=852.
Total props to dicksteele for the original post. Thought it might be better to put out here since this seems to be a recurring issue on most ROMs now.
Specifically,
6. Install Busybox installer from Market. Ran app installed busybox into /system/bin.
7. Open Root explorer Go to /system/etc mount r/w create webtop2sd directory
8. Go to /system/bin copy busybox over to /system/etc/webtop2sd
9. Still in root explorer, go to /system/bin and /system/xbin and delete su
10. Can't use quick reboot to reboot into recovery because su has been deleted. Wherever your adb is located, run adb reboot recovery.
11. Install the superuser app from the zip I have attached. Reboot.
12. Open some other app besides webtop2sd that needs root. Verify root is working.
13. Install webtop2sd.
14. Open webtop2sd, hopefully no FC's. Do the webtop2sd partitioning and copy webtop over to new partition on sdcard.
Click to expand...
Click to collapse
Yes, webtop2sd was very picky to the point of needing busybox from the installer, not the identical one installed by the ROM. Once I got webtop2sd running, I tried Anyconnect again and it started right up.
I can understand webtop2SD not working since it hasn't been updated for a long time, but a company like Cisco should be sure their tool, available on the Market, works with the latest superuser/busybox combinations.
I would go so far as to say that if you are having trouble with any programs requiring root access, try the steps above used to get webtop2SD working. Hope this helps others stuck on similar issues with these newer ROMs.

Nexus 7 has root, but

When apps that ask for root permissions are launched, it doesnt work, example: TI backup says that the device isnt rooted and i might have to check the SU binaries. My N7 was rooted before a update for Superuser was available, now something happen after i updated it. But i dont know what...

That's weird. After you updated your SU, did you go to SU to update its binaries?

i did that twice, and it did say to update binaries...so...

you might need SuperSu instead
What Android version are you running?
Droid_Boi86 said:
i did that twice, and it did say to update binaries...so...
Click to expand...
Click to collapse

I had similar problems with "lightly rooted" stock (4.2.1/JOP40D) using a slightly older version of Superuser. Some apps could get root and others could not. But things have been in flux recently; read on...
I poked around a little bit and it appeared that the 4.2 multi-user stuff was interfering with the way that older versions of (ChainsDD's) Superuser worked, and at that time (only a couple weeks ago) ChainsDD had not released a newer update - things were still in flux.
I switched over to SuperSU, and no problems since... but....
...for me, installation of SuperSU didn't go swimmingly. As I recall the SuperSU install instructions say something like "you need to already have root to install the SuperSU `su' binary". Makes sense as it needs to write it's 'su' binary into /system, which in turn means it needs to get root privilege from a pre-existing su/Superuser installation.
So it poses a chicken-and-egg problem if you have lost root completely which I somehow managed to do... wait, I remember now! I had left the old 'su' binary in place, but had manually uninstalled "Superuser" from /system before I attempted the SuperSU install. Doh!
If you have lost root... you can manually install SuperSU offline inside the recovery via adb & the command line, which means getting both the SuperSU.apk and the 'su' binary ahead of time.
You can get the .apk from the market. You can attempt an install - it will download the 'su' binary and (no kidding) place a copy of it in /data/data/eu.chainfire.supersu/files/superuser.png
If you haven't lost root completely inside the booted OS, I suggest mounting /system in "rw" mode prior to running the SuperSU install and startup.
It looks like I am back a version or two - I have superSU v 0.99
4d7abc0eb5898cdb81bc233dcd16e052 /system/app/SuperSU.apk
0034ec008416b1c3fa7010deb8a3a758 /system/xbin/su
-rwsr-sr-x 1 root root 91992 Jan 10 16:40 /system/xbin/su
note the setuid,setgid bits on /system/xbin/su. Also - no symlink from /system/bin/su to xbin/su.
OK, sorry for the long post. There have been new releases from both chainfire (SuperSU) and chainsDD (Superuser) quite recently. Since I haven't had any troubles since 10 January, I haven't been following it closely - YMMV.
cheers

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)

"Busybox" didn't load successfully in system/xbin then what or how? (2012 7 wifi)
I used Wug's all in one root. All went well. It also included the busybox app. I did the installation using the default choice of system/xbin, which appeared in a "how-to" video as well. In the video it showed that it loaded successfully. Mine did not load successfully. It specifically said that there was a conflict with the location. I tried system/bin and it basically said the same.
My main question is. 1. What does busybox do that I will need on this device, and 2. How then do I load it, as in, what options should I choose for location? Or delete altogether and reload it? and that question is asked because I want to make sure that deleting the app will not mess up my root/rom/twrp or anything else.
Thank you in advance.

busybox provides a set of linux commands needes especially when you want to run scripts e.g. in init.d
What version of Android do you have installed? Most likely there is no space left on /system and so installation of busybox failed. If you are on a custom rom, you can try to flash micro / pico gapps instead of the normal ones to leave some space left on /system for busybox, or you need to root your device "systemless" and you can install busybox on the partition provided by SuperSU ...

Flashing Kindle with 5.1.2 using KingRoot and SuperTool

At first it tried to follow this guide (especially the video linked from there) to flash, but with the update to 5.1.2 much of the bootloader functionality needed for rooting/flashing seems to be locked by amazon so that the root process of the SuperTool (Version from March 12th 2016, the MD5 of the AmazonFire5thGenSuperTool.zip was 8d813f3eacef9e932af5c366769b505e, not the one given on the download page where the file came from) failed.
So following the recommendation from here I tried to use KingRoot for rooting.
Rooting
I downloaded and installed KingRoot 4.8.2 from here. (file name "NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk", md5 11d61bfa1ab79ad3bb55cbaa1ebd6fc7).
Running
Code:
adb install NewKingrootV4.82_C138_B250_xda_release_2016_03_09_105243.apk
worked flawlessly.
Now I started KingRoot on my Kindle. KingRoot said that root is (currently) not available on this device, but that it can try rooting.
I connected to WiFi and let KingRoot download its instructions. At probably about 20% into the rooting process, the device rebooted.
Afterwards I had to restart KingRoot and after some further thinking and reaching ~27% it said that the rooting process failed.
But I didn't give up, rebooted the device, restarted the KingRoot rooting process and voilà - this time it ran through without rebooting and I got root.
Installing SuperSu and FlashFire
Now on getting SuperSu to work for using FlashFire, which won't work with KingRoot.
I extracted the Superuser.apk from the official .zip distribution obtained from here ("UPDATE-SuperSU-v2.65-20151226141550.zip"), but you can probably also get it from the playstore if you got that installed. The md5 of the Superuser.apk was b4a76bb94927431f0d5b617836fb3f9c.
After installing SuperSu via adb install it complained that another su app was installed and its binaries needed an updated. Neither the automated removal of KingRoot nor the update of the binaries worked.
So following this guide I downloaded the mrw.zip that was attached to the third post (md5 1c769fe61e1fe5952b81fb80965c4d6b) and then unzipped and pushed the contained "mrw" folder to /sdcard/ on my kindle using
Code:
adb push mrw /sdcard/mrw
As the script reported some failures (which is supposedly normal) and the SuperSu didn't come any further, I checked the mrw/root.sh script.
After replacing ´cat sdcard/mrw/busybox > /system/bin/busybox´ with ´cat /sdcard/mrw/busybox > /system/bin/busybox´ in line 17 (see the missing root slash?) I got the script to work (at least when not being started from the root dir).
The important part from the skript (see below) now ran without errors.
The two
Code:
>/dev/null 2>&1
files, /system/xbin/kugote and /system/xbin/pidof did realy not exist, so that didn't matter.
Thanks beingtejas for the skript (again, see the mrw.zip from the link above for the full, working version of the script):
Code:
cat /sdcard/mrw/busybox > /system/bin/busybox #this was line 17 with the missing slash
chown 0.1000 /system/bin/busybox
chmod 0755 /system/bin/busybox
busybox chattr -ia /system/xbin/ku.sud
rm /system/xbin/ku.sud
busybox chattr -ia /system/xbin/kugote >/dev/null 2>&1
rm /system/xbin/kugote >/dev/null 2>&1
busybox chattr -ia /system/xbin/su
rm /system/xbin/su
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/supolicy
busybox chattr -ia /system/xbin/pidof >/dev/null 2>&1
rm /system/xbin/pidof >/dev/null 2>&1
cat /sdcard/mrw/su > /system/xbin/su
cat /sdcard/mrw/su > /system/xbin/daemonsu
cat /sdcard/mrw/su > /system/xbin/sugote
cat /system/bin/sh > /system/xbin/sugote-mksh
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chown 0.0 /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chown 0.0 /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chown 0.0 /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d
Now KingRoot was uninstalled, the SuperSu update ran through and I rebooted the device as recommended.
Flashing
Afterwards the FlashFire installation ran fine with the SuperTool as described in the beginning and I could continue the normal installation.
After a very long AOSP boot sequence I now got the Fire Nexus ROM running nicely ob my kindle.
I mainly wrote this as documentation for myself but wanted to share it for other users facing the same problems with the updated bootloader.
If this post actually belongs elsewhere, please tell me to move it, as it is my first one and I couldn't find a better place to put it.

Dude... :fingers-crossed:
I love you. In a non sexual way.

Deleted

I managed to get it done also. Thanks for posting those steps. It took about 20 trys with kingroot, but it finally went all the way, lol. I had the same problems SuperSU also but following your compilation of forum guides, I got the Fire Nexus ROM and I'm loving the absence of Amazon!

Deleted

Hello. Just posting to let people know that this also worked for me as well.
Once you get Kingroot to work, it's all smooth sailing. Not sure if this helped the process but keeping the screen on while Kingroot to do its thing might help. I had several failed attempts and on all of those instances, my display expired and I had to unlock my device. The successful attempt, I just held my device and prevented it from locking... went to 30% and rebooted. Then I had root.
I have Fire Nexus installed.

Very nice!
Posting to say thank you! I did not know any of the roms could be flashed with FlashFire! I attached the most recent version of FlashFire.

feefeeboomboom said:
Posting to say thank you! I did not know any of the roms could be flashed with FlashFire! I attached the most recent version of FlashFire.
Click to expand...
Click to collapse
Flashfire v.30 appears to be a beta version according to Chainfires site

kgirlx said:
Flashfire v.30 appears to be a beta version according to Chainfires site
Click to expand...
Click to collapse
All versions released to date are betas (evidenced by '0.' prefix)

Davey126 said:
All versions released to date are betas (evidenced by '0.' prefix)
Click to expand...
Click to collapse
Ok, boy am I dumb. Thanks

kgirlx said:
Ok, boy am I dumb. Thanks
Click to expand...
Click to collapse
Not 'dumb'...learning

Just used your method, am now running 5.1.2 rooted, may have screwed up with KingRoot, but otherwise good, gonna try removing the KingRoot crap now

I really appreciate your post. It helped me get SuperSU working great! For some reason FlashFire 0.27 was closing on launch so I had to try the 0.30 version that someone posted using adb install -r
Thanks all!

Thank you a million times!! Fire OS was making me insane
Now to block the OTA updates. I haven't seen the definitive word on that as yet (if anyone could guide me, I'd be very appreciative!)

I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)

drmattyg said:
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
Click to expand...
Click to collapse
Any rollback attempt will yield an unrecoverable brick...as you discovered.
Multiple reports of installing CM 12.1 and Fire Nexus on a device that previously hosted FireOS 5.1.2. FlashFire v0.31. Latest ROM builds.

drmattyg said:
I was able to root and get SuperSU and Flashfire onto 5.1.2, but it died when I tried to flash it with SlimLP. I tried restoring it to stock 5.1.1 (probably a bad idea) and it's fully bricked, won't turn on at all. Are there any ways to recover from a full blank-screen no-turn-on with a 5.1.2 device? Has anyone had success flashing CM12 or SlimLP onto a 5.1.2? If so, what versions of the ROMS and what versions of flashfire did you use? Thanks!
(BTW, I'm testing a few options, so I have a few of these used cheap tablets, so bricking one of them isn't a tragedy, just want to get this to a working state.)
Click to expand...
Click to collapse
HOW TO ROOT FIRE 7 THAT HAS FIRMWARE 5.1.2 AND THEN INSTALL NEXUS ROM USING FLASHFIRE.
I have three Fire 7's with 5.1.2 firmware. I rooted them with RootJunky's SuperTool. After they were rooted, I installed FlashFire v.031 and then used that to load the Nexus rom (the latest one from early April). All of those are mentioned in threads here on xda.
Run RootJunky's SuperTool and root the Fire 7.
With the SuperTool, you can also load FlashFire. But it loads v.030. I believe you can get v.031 through a special link here on xda to the Google Play store.
If not, you can find FlashFire v.031 on a european server. Download v.031 apk and install it manually.
The FlashFire program icon will appear with the other installed apps on the Fire 7 apps screen, even on the Amazon Fire OS menu system.
Copy the Nexus rom (a zip file "lp-fire-nexus-rom-ford-20160405.zip" ) to your Fire 7's sd card root folder.
Make sure your Fire 7 is fully charged.
I started FlashFire v.031 and made the following menu selections:
In the FlashFire program do the following:
- Click the Red + and choose 'Wipe'.
- Ensure System data, 3rd party apps and Dalvik cache are CHECKED.
- Click the Red + button and choose 'Flash ZIP/OTA'.
- Navigate to and choose the latest Fire Nexus ROM Zip (I used "lp-fire-nexus-rom-ford-20160405.zip" that I had previously loaded on the root folder of the SD Card.).
- Ensure Auto-mount and Mount /system read/write are UNCHECKED.
- Move (drag) "Wipe" to the Top of the order (just above the ROM flashing).
- Press the big FLASH button.
- Ignore any warnings that appear.
The Fire 7 screen will go black for a few seconds.
-Then it will say, "Loading" and lines of text will go by rapidly for a few seconds.
-A red bar will then appear at the top of the screen titled "FlashFire".
-The rest of the screen is black. Don't touch the tablet. Just let the program run. It takes 5 or 10 minutes. It looks like nothing is happening, but it is.
-Finally the tablet will reboot. The Amazon logo will appear for a little while, then a pulsing color dots animation will appear. This dot animation will run for 5 or 10 minutes more as the tablet boots for the first time. Don't touch the tablet until a Setup screen appears.
You can now set up the tablet, registering it with Google and loading your desired apps.
The Nexus rom gives you a generic Android 5 Lollipop interface. After loading the Nexus rom, I installed the Nova launcher, it gives you a lot of options for menu control.
Nexus is a nice ROM. Much better and faster than the stock Amazon Store ROM.

With the Nexus rom installed, I then added the Link2sd app from the Google Play store to recover 3.5gb of internal storage, linking apps to the sd card.
Link2sd is an app that links and moves most or all of an app to your sd card, but someway links it to the Fire 7 internal storage for the android system to run. Some custom roms allow you to just move and run the apps from the sd card. But with the Nexus rom, the app file is moved to the sd card, but run, maybe virtually from internal storage.
I have 150 apps installed on the Fire 7 with a Nexus rom. Before I loaded Link2sd, the Fire 7 had about 500mb internal storage free. After loading Link2sd and linking apps to my sd card, there is 3.5gb for free internal storage on the Fire 7.
In order for Link2sd to use the sd card you have to partition the sd card into Fat32 and ext4 partitions. The ext4 partition is used by Link2sd for app linking. The Fat32 partition is used in a normal manner for MP3, picture, video, e-book, etc storage.
I am using Linux Mint on my pc, so I used the linux program Gparted to partition a 32gb micro sd card for Link2sd to use. There are also free Windows programs that will allow you to do the same functions on your Windows 7 or 10 pc..
Link2sd uses a linux ext4 partition on the sd card to place and link apps to. The other half of the sd card is partitioned as a Fat32 format, for MP3, video, ebook, pictures storage.
Here is how to partition a 32gb micro sd card using the linux program Gparted. Use some type of micro sd adapter to connect the micro sd card to your linux pc. My Dell laptop has a built in sd slot, so it only needed and sd to micro sd adapter.
First delete the existing partition on the micro sd card. Then create a Fat32,. Primary partition, that takes 1/2 of the space on the micro sd card. Format the Fat32 partition as Fat32.
Next create a linux ext4, Primary partition, using the other 1/2 of the space on the micro sd card. Format the ext4 partition as ext4. The micro sd card is now ready for use by the Link2sd app.
Insert the micro SD card into the Fire 7 with a Nexus rom and Link2sd installed.
Start Link2sd and point it at the ext4 partition on the sd card when it asks and you are set to link apps to the sd card.
You can probably partition 64gb and 128gb sd cards in the same way, although I haven't tried. The Fire 7 is suppose to be able to accept up to a 128gb micro SD card.
Fire 7 boot times with the Nova rom are about 45 seconds to a minute. After installing Link2sd, the first boot after linking about 100 apps took 3 minutes. Later boots took about 90 seconds. So linking apps to the sd card does increase boot time on the tablet. Those times are for a cold start, from pushing the power button to being able to open the lock screen.
ADDENDUM: Well, after a couple of days of use, boot times are back to 60 seconds from a cold boot. Link2sd must have sorted things out. Wow.

Deleted

Thanks for the info, I managed to stumble through most and got root, updated the root.sh as per your instructions above and pushed the MRW folder to SD, installed Superuser, installed FlashFire. However, I am stumped at how to run the root.sh script!
Sorry for the noob question, but I just couldn't find a noob-friendly instructions ...
Do I install a Terminal Emulator on the Fire tablet, and run the script? I tried that (installed "Terminal Emulator") but just couldn't get any prompt to run.
If you don't mind giving me a more detailed instruction of how to run the script ... Mainly how to remove Kingroot ... Most appreciated!
Thanks!
---------- Post added at 09:07 PM ---------- Previous post was at 08:30 PM ----------
vn33 said:
Thanks for the info, I managed to stumble through most and got root, updated the root.sh as per your instructions above and pushed the MRW folder to SD, installed Superuser, installed FlashFire. However, I am stumped at how to run the root.sh script!
Sorry for the noob question, but I just couldn't find a noob-friendly instructions ...
Do I install a Terminal Emulator on the Fire tablet, and run the script? I tried that (installed "Terminal Emulator") but just couldn't get any prompt to run.
If you don't mind giving me a more detailed instruction of how to run the script ... Mainly how to remove Kingroot ... Most appreciated!
Thanks!
Click to expand...
Click to collapse
Duh! I managed to run the script through Terminal Emulator. It updated the, and rename the Kinguser to com.kingroot.kinguser
Now just trying to figure how to delete that file.
Thanks OP for this thread!

Xposed for Fire HD 8 (6th) 2016

Edit: confirmed method from post #4 worked
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?

2ig2ag said:
Now we have root, time for xposed.
I tried flash xposed framework zip with FireFlash, it stuck at blank screen.
I tried xposed installer, it said wrong platform.
Any other ideas?
Click to expand...
Click to collapse
I'm new to android, can't help
sit and wait

I have been trying to get xposed working since I acquired root. I believe there is a mismatch between the processor and installed os. The CPU identifies itself as a 64-bit (aarch64) but there is no app_process64 in this OS. I tried touching the file and running the installer but that just soft bricked my tablet. Looking at the spec sheet it seems this CPU does not support 64-bit. The normal 32-bit Arm installer gave me the same results. May be time to ask @rovo89 for some advice.

I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.

can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送

How you guys rooted it ? on 5.3.2.1 - I yet to get the root. Please guide.

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios

phpbb88 said:
can someone tell what is xposed to me
從我的iPhone使用Tapatalk Pro 發送
Click to expand...
Click to collapse
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more

nbc12 said:
Its a framework that allows people to change their android rom to have features it normally wouldn't. Kinda like cydia on ios
Click to expand...
Click to collapse
smokejumper76 said:
It's when you walk up to a really cute girl and you flash/expose yourself to her and run away.
Exposed framework is like an underlying interface to tweak just about everything in the android UI. It's behavior. Things like the battery, or order in the status bar, etc etc.
* and a lot...LOT more
Click to expand...
Click to collapse
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!

phpbb88 said:
I understood immediately when @nbc12 said its like cydia on iOS. lol
Thanks!
Click to expand...
Click to collapse
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.

smokejumper76 said:
right on, yeah you should def. install it and play with it. I haven't yet on this device, but it is very very cool.
Click to expand...
Click to collapse
will try when I have time to play with my device
but I expect Custom ROMs on fire hd the most important

coltxL2717 said:
I have managed to get Xposed working on my Kindle. I will lay out the steps I followed. I used the installer from this thread: https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758. I installed the "exposed-v87-sdk22-arm64" framework. At this point I received an error about /system/bin/app_process64 being missing. This will be important later. I restarted the tablet and ended up at the Fire boot screen. I plugged the tablet into my computer and tried to adb. I was able to adb and su. I went into /system/bin/ to see what was amiss based on the previous error. I noticed Xposed created a couple files ending with "_xposed" in this directory. I also noticed I had a file named "app_process64_xposed" in this directory. This is when the previous error clicked. I never had a file named "app_process64" on my tablet. The installer should not have created this file.
I fixed this error by running these commands in adb:
1. 'su'
2. 'mount -w -o remount /system'
3. 'rm /system/bin/app_process64_xposed'
4. 'reboot'
Crossed my fingers and waited for tablet to reboot. Got the typical updating system partition screen and waited 10 mins. Xposed was activated and working. Success.
Hope this helps some of you get this working. I would suggest deleting the "app_process64_xposed" file after you run the Xposed installer but before you reboot.
Click to expand...
Click to collapse
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated

ahac85 said:
i have the same problem but when i try to mount system i get permission denied, system is read only, although im rooted cant mount system?? any help appreciated
Click to expand...
Click to collapse
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Code:
C:\adb>adb shell
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ #

phpbb88 said:
did the shell change from $ to # after you typed 'su'?
if not, have you grant access to adb shell?
Click to expand...
Click to collapse
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!

ahac85 said:
Hi i had to use kingoroot pc for root access again then the above commands worked. Even though i was fully rooted and had SuperSu installed.
Edit: I think I may have changed SuperSu permissions to "prompt" instead of "grant", which is why it was being denied?
Anyway its all working... Sucess!!
Click to expand...
Click to collapse
Glad you got it worked out.

@coltxL2717 which version of the xposed installer did you use?
I downloaded the dvdandroid_26_11_1 and fail to install

@phpbb88, that is the installer I used. The script will error but the framework is still being installed.

coltxL2717 said:
@phpbb88, that is the installer I used. The script will error but the framework is still being installed.
Click to expand...
Click to collapse
I cannot install that apk by using file explorer, keep telling me installation failed....
edit: its working now, thanks!

I had the same issue as @ahac85. The kingoroot method he mentioned worked for me as well. You guys find any good/cool xposed modules that worked?

I was wondering if I changed my supersu gettings from grant to prompt would mess anything up? So far I haven't touched it, but would like the normal pop-up prompt that happens when su is requested. And if it doesn't work, that is just weird.