Xposed framework
Hi guys, was wondering if anybody got xposed up and running on the z4t? I know the tablet has been rooted, but I haven't heard much in the way of a custom recovery.
I stumbled on this thread: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
Apparently the LG G4 guys got xposed to work without a custom recovery. Does anybody think this will work for the z4t?
mickifree said:
Hi guys, was wondering if anybody got xposed up and running on the z4t? I know the tablet has been rooted, but I haven't heard much in the way of a custom recovery.
I stumbled on this thread: http://forum.xda-developers.com/g4/themes-apps/guide-installing-xposed-locked-t3181593
Apparently the LG G4 guys got xposed to work without a custom recovery. Does anybody think this will work for the z4t?
Click to expand...
Click to collapse
I have a G4 and used that method to get xposed on it successfully but when I tried it for the Z4 Tablet it didn't work. Got FC's after flashing and the apk refused to install.
Also, I only flashed the official framework since romracer's version is only for 5.1.
Charsher47 said:
I have a G4 and used that method to get xposed on it successfully but when I tried it for the Z4 Tablet it didn't work. Got FC's after flashing and the apk refused to install.
Also, I only flashed the official framework since romracer's version is only for 5.1.
Click to expand...
Click to collapse
xposed-v71-sdk21-arm64.zip
Is the correct zip.
Also IIRC it's possible to "flash" though adb too...
Today we are on Android 5.02 and have a 64bit processor
I have not tried it myself.
The referenced zip:
You must be on Android 5.1. It will NOT work on Android 5.0 (too many changes to ART)
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
The master of it all:
No, this ZIP doesn't support arm64/x86 processors yet.
Click to expand...
Click to collapse
I find an elf file for 32bit arm in rovo89's installer.
http://forum.xda-developers.com/showpost.php?p=60368383&postcount=8
Flashfire works on my Tablet Z4. I tried it with SuperSU. It will not magically get you a recovery partition though ...
EDIT Steve is right! Flash with Flashfire could work. via adb: not available for our xperia
Stevethegreat said:
xposed-v71-sdk21-arm64.zip
Is the correct zip.
Also IIRC it's possible to "flash" though adb too...
Click to expand...
Click to collapse
That's the zip I flashed, it didn't work. Had to wipe back to stock afterwards.
I actually got this to work. After you flash it you have to clear your dalvik-cache.
I did this through adb:
Code:
adb root
adb shell rm -r /data/dalvik-cache
So far I've tested Gravitybox, YouTube AdAway, and OBB on SD and they all work
Charsher47 said:
I actually got this to work. After you flash it you have to clear your dalvik-cache.
I did this through adb:
Code:
adb root
adb shell rm -r /data/dalvik-cache
So far I've tested Gravitybox, YouTube AdAway, and OBB on SD and they all work
Click to expand...
Click to collapse
It works. Just tried it. Used flashfire to flash xposed-v73-sdk21-arm64.zip. After it rebooted, just cleared the dalvik cache and everything seems fine. Xposed modules all seem to be working.
mickifree said:
It works. Just tried it. Used flashfire to flash xposed-v73-sdk21-arm64.zip. After it rebooted, just cleared the dalvik cache and everything seems fine. Xposed modules all seem to be working.
Click to expand...
Click to collapse
Assuming you're rooted to do this yeah?
Sent from my C6603 using Tapatalk
zippy01 said:
Assuming you're rooted to do this yeah?
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Yes. I followed this guide:
https://androplus.org/Entry/626/
After you obtain root, follow this guide:
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Make sure you flash the zip for Android 5.0
Then after you flash the zip, clear the dalvik cache and you should be good to go.
Thank you but my bootloader is locked thanks anyway
Sent from my SGP771 using Tapatalk
Related
I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
gerstavros said:
I am trying to root the stock Lollipop rom of DG280 (can be find in doogee.cc)
i created custom system.img, custom recoveries, unsecured boot.img but even if i root it, it doesn't boot again.
I unpack system.img and put the su binary in xbin, then i pack it and flash , but bootloops.
Unsecured boot.img boots but when i connect phone to pc, it doesn't get recognized. I created a custom recovery based on kitkat and worked, but after installing various rooting packages, like supersu v2.46, phone boots rooted at first time, but after reboot it doesn't boot again!
Please any help appreciated.
Click to expand...
Click to collapse
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
frooby said:
Not sure if you have it sorted but just thought I would mention what works 100% for me. Just picked up a leo dg280 while waiting for a replacement screen for my main phone.
Anyway use kingroot to root, then google for the mrw script and follow those instructions to replace kingroot with SuperSU. So far has worked everytime for me ( have reflashed lillipop numerous times for different reasons)
Sent from my LEO_DG280 using Tapatalk
Click to expand...
Click to collapse
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
gerstavros said:
I had tried that but never worked (vroot, root genius, kingroot etc). I finally flashed a custom made cwm recovery and installed a kinguser su package.
Click to expand...
Click to collapse
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
frooby said:
What recovery did you use? I can't find any that work! Any chance you can pm me a link?
Click to expand...
Click to collapse
Ι had made a custom cwm based on kitkat rom i think. It doesn't work properly in lollipop rom, it cannot read internal or external file storage partition although i was sure i had configured correctly the files, you can install a package only via adb sideload. Also it is bigger than the stock recovery and i ' m not sure if that occures any problem.
I m not sure now which file it is, if i make one for lollipop rom i ll upload it
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
kibmikey1 said:
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
Click to expand...
Click to collapse
So you just used the system less boot.img in place of the new one in the factory image?
elreydenj said:
So you just used the system less boot.img in place of the new one in the factory image?
Click to expand...
Click to collapse
Correct.
I did mine on the 08K and I get an update. From what I am reading, I need to flash the stock bootloader and stock recovery then do theupdate. Then reflash the TWRP recovery and systemless boot again. I guess I need to keep back up systemless recovery and boot folder and stock ones.
I am also reading that I can just flash the new system image. Downloaded the new rom, extracted it and now commands
fastboot flash radio (radioname).img
fastboot flash system (systemname).img
??????
Is xposed killing android pay for anyone on systemless root? I assume it would because it touches system files.
durag5 said:
Is xposed killing android pay for anyone on systemless root? I assume it would because it touches system files.
Click to expand...
Click to collapse
It stopped working for me once I installed exposed, even with no modules active. I could live with needing stock DPI, but I just decided android pay isn't worth staying so close to stock. I'd rather be free to mod my phone and just use a credit card.
kibmikey1 said:
For those wondering, the 08M update works fine with Chainfire's systemless boot image. I completely wiped the device, and manually installed each image via fastboot, then sideloaded the 2.56 supersu, and everything worked normally.
Click to expand...
Click to collapse
Will this allow you to have root (and xposed) on stock rom without touching system partition?
Can you provide the steps to go from completely stock to this?
This info is in the pinned thread already, section 6.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
There is also a boot.img for M in there.
skrowl said:
Will this allow you to have root (and xposed) on stock rom without touching system partition?
Can you provide the steps to go from completely stock to this?
Click to expand...
Click to collapse
If you are trying to keep android pay you will not be able to use Xposed. Best you can do right now is have root + android pay, but nothing more it seems. I am going to test out flashing a custom kernel (for double tap to wake) and see if I lose it again.
durag5 said:
If you are trying to keep android pay you will not be able to use Xposed. Best you can do right now is have root + android pay, but nothing more it seems. I am going to test out flashing a custom kernel (for double tap to wake) and see if I lose it again.
Click to expand...
Click to collapse
Like most people who have used NFC payments more than twice, I'm bored of it. I'm OK with losing Android Pay to get Xposed + Gravity Box.
Can you provide steps to do it from stock?
Hi,
I was thinking about trying to get TWRP and CM11 on my 2014 Fire HD 6, as I went to do it I couldn't for the life of me get the device into recovery or the bootloader. ADB commands do absolutely nothing and nor do any button combinations. I've even tried adb shell, su, reboot recovery to no avail.
Software I'm running atm is OS 5.1.1.
Any help would be appreciated!
jakestevens96 said:
Hi,
I was thinking about trying to get TWRP and CM11 on my 2014 Fire HD 6, as I went to do it I couldn't for the life of me get the device into recovery or the bootloader. ADB commands do absolutely nothing and nor do any button combinations. I've even tried adb shell, su, reboot recovery to no avail.
Software I'm running atm is OS 5.1.1.
Any help would be appreciated!
Click to expand...
Click to collapse
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
bibikalka said:
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Thank you for that, I did have a look around for some stuff but obviously missed that. Thanks again for finding that
Sent from my SM-N910F using XDA-Developers mobile app
I'm running 4.5.5, can I still use that same script to install TWRP?
bibikalka said:
Easy. Get root (have root already ?). Then, the script in post #2 for TWRP, and
do whatever you want from TWRP:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Click to expand...
Click to collapse
Emerald9 said:
I'm running 4.5.5, can I still use that same script to install TWRP?
Click to expand...
Click to collapse
You need to get root. But with root, the TWRP script will work just fine!
Thanks, bibikalka. I have root and TWRP (thanks to you and doLooper), but no Google store yet. Can I use your guide here to go from 4.5.5 to 5.3.1?
bibikalka said:
You need to get root. But with root, the TWRP script will work just fine!
Click to expand...
Click to collapse
Just flash the zip in the attachment, and then flash SuperSU. No more messing with Terminal Emulator!
Note: if you installed SuperSU first, and got a bootloop, install the fixer then SuperSU again. All will be good.
Please don't redistribute this, just link to the thread.
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
mx597turbo said:
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
Click to expand...
Click to collapse
I'll add your note to the op
Life saver
Yay! I was in that bootloop, and then I couldn't find an ADB driver that worked, to load this fix. The obvious solution was to put the fix on a Micro-SD card but it didn't come to me for a bit - my other current phone has no external card slot - but once I did this, the fix worked perfectly. Many thanks to whomever came up with this!!!
No need to flash SuperSu for root, phh's SuperUser works perfect
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
BigNaes said:
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
Click to expand...
Click to collapse
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
fireball0093 said:
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
Click to expand...
Click to collapse
Thank you for your reply. I understand. I prefer to use SuperSu as opposed to the LineageOS SU package.
When I installed LineageOS I flashed this zip first and then SuperSU after and it works perfectly, I am just not sure if I needed this zip first when using Lineage OS.
Also one last question is I believe I found a post which explains what this fix does, can anyone confirm this is the fix being performed? https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592
Thanks again for all the help, always learning on XDA :good:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Ashutosh Sundresh said:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Click to expand...
Click to collapse
What's that for??
Sanjay parsi said:
What's that for??
Click to expand...
Click to collapse
SuperSU, if you don't type this, your device WILL bootloop
download link isn't working for me.
Edit: everything is fine my brain is the one not working
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?