I'm not responsible of
bootloops
dead sdcard
overheating
success
device suicide
anything else
Click to expand...
Click to collapse
everything in here became obsolete, you still can use but now there's an better way to do it
here's the link for flashfire thanks to @Chainfire
here's the link for xposed for lollipop thanks to @rovo89
download the sdk 21 arm version
just download the xposed zip and the flashfire
and use flashfire to flash the zip
it takes around 8 minutes to flash on our device but works
the old way to do it is here:
I found some files on google from a guy called "Nodis" that promised to install xposed on lollipop
yay
they worked?
No.
:crying:
but I followed the script manually and then...
yes xposed on lollipop working
Let's start
You'll need:
Code:
d690n (but mine is using d693n rom)
Root
busybox
Some app to unninstall system apps
Working adb
SeLinuxModeChanger
usb debugging enabled
the files from here
Luck
Let's begin
uninstall lg quick view app (it'll be force closing continuously)
download the CantRecoverv4 file attached in here
extract to desktop or the place you want
open cmd (or bash for linux) in the xposed folder that you extracted
a good way for do this is open the folder, hold shift, right mouse click and click open command window here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
type the following commands and then press enter to execute
Code:
adb push system /data/local/tmp/system
Code:
adb push installer /data/local/tmp
Code:
adb shell
in the adb shell type
Code:
su
in the su shell
Code:
chmod 755 /data/local/tmp/installer
and
Code:
/data/local/tmp/installer
it's really important to follow the order.
then install XposedInstaller_3.0-alpha4.apk
just open the xposedapp.bat and it will (should) install xposed app.
I've noticed that if you install SeLinuxModeChanger from @MrBIMC some blocked mods start working
So download the app here, install and set it to permissive.
reboot your device.
now xposed is probably working (worked for me)
MAYBE it'll work for other lollipop device without recovery
thanks if i helped.
If you have any questions ask in here and if I can help I'll do.
if the real author of this isn't the guy Mentioned contact me and I'll add your credits
thanks to @MrBIMC for SeLinuxModeChanger
Screenshots:
Reported working list:
D690
D693n
Xperia ZR
Can you Help me ?
gkillershots said:
Let's begin
uninstall lg quick view app (it'll be force closing continuously)
download the files attached in here
extract to desktop or the place you want
open cmd (or bash for linux) in the xposed folder that you extracted
type the following commands and then press enter to execute
Code:
push system /data/local/tmp/system
Code:
push installer /data/local/tmp
Code:
adb shell
in the adb shell type
Code:
su
in the su shell
Code:
chmod 755 /data/local/tmp/installer
and
Code:
/data/local/tmp/installer
it's really important to follow the order.
then install XposedInstaller_3.0-alpha2.apk
reboot your device.
now xposed is probably working (worked for me)
MAYBE it'll work for other lollipop device without recovery
thanks if i helped.
If you have any questions ask in here and if I can help I'll do.
if the real author of this isn't the guy Mentioned contact me and I'll add your credits
Click to expand...
Click to collapse
where I have to put the files ? here it seems "not found" im using "terminal emulator for android" and my g3 stylus is d690n with lollipop 5.0.2
V2power said:
where I have to put the files ? here it seems "not found" im using "terminal emulator for android" and my g3 stylus is d690n with lollipop 5.0.2
Click to expand...
Click to collapse
don't use terminal emulator, use adb. do you want me the tuto to setup adb?
gkillershots said:
don't use terminal emulator, use adb. do you want me the tuto to setup adb?
Click to expand...
Click to collapse
ohh thanks bro, i never used adb, but now i know how to use and i never heard of it i go try.
OW NICE !! Thanks man i finally got i,now i have xposed,thx
Sorry for my bad english
V2power said:
OW NICE !! Thanks man i finally got i,now i have xposed,thx
Sorry for my bad english
Click to expand...
Click to collapse
no problem, I'm brazilian too and please hit thanks if I helped
Hi OP,
I followed all you instructions and at the end my Xposed Installer shows.....
"Installation is only possible manually via recovery for now"
Please help.
Sunil Jagtap said:
Hi OP,
I followed all you instructions and at the end my Xposed Installer shows.....
"Installation is only possible manually via recovery for now"
Please help.
Click to expand...
Click to collapse
even if xposed is working he shows this message, just look if there are green numbers under active.
if it has, try some module because it may be working
in one of my screenshots you can see what i'm saying.
gkillershots said:
even if xposed is working he shows this message, just look if there are green numbers under active.
if it has, try some module because it may be working
in one of my screenshots you can see what i'm saying.
Click to expand...
Click to collapse
Thanks Gkillershots,
The xposed is now active, but it dont looks like other mobile. sorry OP, i dont know first.
I check modules G3 tweak but its not fully supportive do you know any modules like X Blast or Wannam for Our D690 only rooted.
Thanks in advance.
Sunil Jagtap said:
Thanks Gkillershots,
The xposed is now active, but it dont looks like other mobile. sorry OP, i dont know first.
I check modules G3 tweak but its not fully supportive do you know any modules like X Blast or Wannam for Our D690 only rooted.
Thanks in advance.
Click to expand...
Click to collapse
many modules aren't working, check if you are using the new g3 tweaksbox and use the new gravitybox lp too, because they complements each other.
and the selinux mode changer can make some things work too.
gkillershots said:
many modules aren't working, check if you are using the new g3 tweaksbox and use the new gravitybox lp too, because they complements each other.
and the selinux mode changer can make some things work too.
Click to expand...
Click to collapse
Thanks for your reply,
I have tried all kind of modules but non of theme support fully,
g3 tweaksbox only make some changes in ui but no satisfactory result
Gravitybox dont support our D690
is there any fully supportive module in your knowledge which gives me satisfactory result
Hxnter said:
Wow dude, I can't believe you made Xposed wihout recovery
I'm gonna try this out soon as I get my phone back
Click to expand...
Click to collapse
Thanks Pal!!! Work for my Xperia ZR Lollipop!!!
Sunil Jagtap said:
Thanks for your reply,
I have tried all kind of modules but non of theme support fully,
g3 tweaksbox only make some changes in ui but no satisfactory result
Gravitybox dont support our D690
is there any fully supportive module in your knowledge which gives me satisfactory result
Click to expand...
Click to collapse
i know but some tweaks works.
search for layers manager on google play store or in here. it's a new lollipop theme engine and it works on my g3
but it's not xposed
shenlong85 said:
Thanks Pal!!! Work for my Xperia ZR Lollipop!!!
Click to expand...
Click to collapse
thanks for the report
Al ejecutar el primer codigo me aparece
Error: device not found no me explico por que soy root. La depuracion usb esta activa que falla?
How do I uninstall it if I installed framework with this method?
Dereklop said:
Al ejecutar el primer codigo me aparece
Error: device not found no me explico por que soy root. La depuracion usb esta activa que falla?
Click to expand...
Click to collapse
Try Installing the drivers
irsal226dunkz said:
How do I uninstall it if I installed framework with this method?
Click to expand...
Click to collapse
I recommend you re-flashing the stock rom because it's a lot easier
Do I have to uninstall the quick view app with the new method? If so, can I install it again later? Or should I totally ignore the old method?
the-careta said:
Do I have to uninstall the quick view app with the new method? If so, can I install it again later? Or should I totally ignore the old method?
Click to expand...
Click to collapse
totally ignore the old method, just download the newest xposed zip for our phone (sdk21 armv7) then flash it via flashfire
no need to uninstall quickview
Related
Hi all,
In few days i will get s4 dual sim I9502 from china,i've asked friend to buy it for me .
Please i need to be prepared in advance ,
need the root and cooked rom with google apps if possile.
Thanks
copysat said:
Hi all,
In few days i will get s4 dual sim I9502 from china,i've asked friend to buy it for me .
Please i need to be prepared in advance ,
need the root and cooked rom with google apps if possile.
Thanks
Click to expand...
Click to collapse
I don't think it'll be easy to find roms for that model, since it's far from being common worldwide, and the roms for the i9500 probably won't work on it (who knows though).
I hope I'm wrong though.
Your best bet will probably be to check chinese forums for roms working on that device, I guess you can set them in english too.
EDIT : I did find this thread, but I think it's a stock rom : http://forum.xda-developers.com/showthread.php?t=2251357 .
The problem seems to be that you can't root it yet, and you can't install any Google apps (including Google Play).
Root is here: http://bbs.25pp.com/thread-129613-1-1.html
Mindbeats said:
Root is here: http://bbs.25pp.com/thread-129613-1-1.html
Click to expand...
Click to collapse
You're the man. Really looking forward to use this method when my SGS4 I9502 arrives.
rooted my i9502 and installed play store and when i opened the play store it closed it right away!!!!!
is there a mothed to install the play store?!!!!
by the way theres no error's when closing the play store its like theres a program that shut it down.
This is because China doesn't have an agreement with google to allow google apps. You will have to make the device think it is something else. You may lose dual sim in doing so.
Wayne Tech Nexus
r_theboss said:
rooted my i9502 and installed play store and when i opened the play store it closed it right away!!!!!
is there a mothed to install the play store?!!!!
by the way theres no error's when closing the play store its like theres a program that shut it down.
Click to expand...
Click to collapse
I had the seame problem, in a nutshell :
Google for GoogleLoginService.apk and GoogleServicesFramework.apk
With adb you can install the 2 files if your device is rooted
adb root
adb shell mount -o rw,remount /system
adb push GoogleLoginService.apk /system/app
adb shell chmod 644 /system/app/GoogleLoginService.apk
adb push GoogleServicesFramework.apk /system/app
adb shell chmod 644 /system/app/ GoogleServicesFramework.apk
Now the play store should work
jo139 said:
I had the seame problem, in a nutshell :
Google for GoogleLoginService.apk and GoogleServicesFramework.apk
With adb you can install the 2 files if your device is rooted
adb root
adb shell mount -o rw,remount /system
adb push GoogleLoginService.apk /system/app
adb shell chmod 644 /system/app/GoogleLoginService.apk
adb push GoogleServicesFramework.apk /system/app
adb shell chmod 644 /system/app/ GoogleServicesFramework.apk
Now the play store should work
Click to expand...
Click to collapse
Thanks for the fast reply
but is it possable to explane a bit more.
is there a program for the adb?
r_theboss said:
Thanks for the fast reply
but is it possable to explane a bit more.
is there a program for the adb?
Click to expand...
Click to collapse
adb comes with the android sdk, is a bit much to explain, but there are many howto's written already
One of them : http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Or a shorter way, your chinese phone is probably a clone with mtk chipset, you can install mtkdroidtools, adb is included. Don't forget the mtk 65XX (probably mtk6577) drivers
jo139 said:
adb comes with the android sdk, is a bit much to explain, but there are many howto's written already
One of them : http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Or a shorter way, your chinese phone is probably a clone with mtk chipset, you can install mtkdroidtools, adb is included. Don't forget the mtk 65XX (probably mtk6577) drivers
Click to expand...
Click to collapse
Thanks for your help, i'll try to do it and keep you posted.
tried this after the root by mistake and it worked loooool
http://forum.xda-developers.com/showthread.php?t=1997547
r_theboss said:
tried this after the root by mistake and it worked loooool
http://forum.xda-developers.com/showthread.php?t=1997547
Click to expand...
Click to collapse
Hi r_theboss
You really succeeded ?
Could you do me and the forum a favour?
Can you discripe First how you rooted (step by step ala cookingbook) ? The Chinese page through the Translationen is me too insecure.
And the Second step you made via adb is easy doing or do i have to be professional ? Some hints would be helpfull too !
Thanks and hoping that you reply,
Goes like hell
Still there's some force close but i'm going to put the steps right here so we could all work on it
first you must do root for your device and these are the steps from the same http://bbs.25pp.com/thread-129613-1-1.html website and you do it on your own responsibility!
Samsung Orion eight-core CPU ROOT tutorial is
suitable for i9500, i9502/i959 Asia-Pacific, Europe and other models
, download Odin: Odin3_v3.04.zip (456.59 KB Downloads: 1)
ROOT file I959 I9502 i9500 root file the ROOT file attachments Download:
Click here
2 Download driver installation : : http://pan.baidu.com/share/link?shareid=430360&uk=3439566523
phone volume down + home + power button, and then click on the volume up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do as shown in the picture,
Click start to start rooting phone and it will automatically restart, now you got ROOT access
This is for the root part
Now download this file and put it in you device
http://www.mediafire.com/?enbo8wix7114i36
******** You will get some force close for this part i think because these files for Nexus and there's some duplicate in some app's like Gallery and Camera and Email and if you restarted you device it keep on upgrading the App's don't know why but it work just fine ********
After that get in the recovery mode: shut down your device and press phone volume up + home + power button for 5 sec and then let go
you will enter the recovery mode
Go to "install zip from sdcard"
then "choose zip from sdcard" now choose the file that you have downloaded it in your device
go back and reboot your device
and thats what i have done.
"do it on your own responsibility!" Thats for sure !!!
But let me first say thanks for your doing !! :fingers-crossed:
I am longing for my 9502 but it will come earliest at the end of june.
Maybe we can before that discuss whats the Reading for the "Force close". Here are a lot of specialists on the run.
Somebody else an idea for r_theboss and me ?
"i think because these files for Nexus and......", but are the gapps Not belonging to jellybean-Versions instead of hardware(Nexus,Samsung,etc ?
Thanks for the Forum, thanks for r_theboss
Goes like hell
Root
Please help, I want to root but how? Thanks
Horeb7 said:
Please help, I want to root but how? Thanks
Click to expand...
Click to collapse
???
One post before !
the issue is when we use this method supersu complains "SuperSU is not installed and cannot be installed. There is a problem." We can boot into CMW... but after rooting this method we cannot install or run apks...
r_theboss
can you run supersu?
Dear all,
I would suggest not to try the above method as I beleive it is either a fake or a half baked method. I went to the Chinese forums and there are others with the same problem with no solution. I would say this is a broken method. I tried to use the CMW recovery to flash the latest SuperSUv1.25 and SuperSU does not install and the apk also is deleted.
I would wait for a method from xda developers...
Horeb7 said:
Please help, I want to root but how? Thanks
Click to expand...
Click to collapse
goes_like_hell said:
???
One post before !
Click to expand...
Click to collapse
:laugh::laugh:
Hok said:
the issue is when we use this method supersu complains "SuperSU is not installed and cannot be installed. There is a problem." We can boot into CMW... but after rooting this method we cannot install or run apks...
r_theboss
can you run supersu?
Click to expand...
Click to collapse
Hok said:
Dear all,
I would suggest not to try the above method as I beleive it is either a fake or a half baked method. I went to the Chinese forums and there are others with the same problem with no solution. I would say this is a broken method. I tried to use the CMW recovery to flash the latest SuperSUv1.25 and SuperSU does not install and the apk also is deleted.
I would wait for a method from xda developers...
Click to expand...
Click to collapse
what i have done isn't fake and you could try it for your self, and the Play Store, Gmail, Gallery, Camera, Email for the Nexus all work just fine.
now i'm having problem with the storage its all most full don't know why but still working on it, and i have tried the root explorer to delete some apps but no luck for it to work.
and about the SuperSU it didn't work even after the root and i have tried many method's but none work, i think the rooting files are not complete or some thing is missing because the CWM is working just fine but the SuperSU is not.
Hi r_theboss,
I'm not saying your method is fake, I am saying the Chinese page one maybe. I have also followed that method and installed GAPPs and it crashes and freezes consistently and is virtually not usable as a phone. I just don't want others to think this is a viable method at the moment. Alsoo everytime on reboot it says android is optimizing X apps
Also I have downloaded a root checker for my phone and the results are just freezing and constant crashing when I run it. I don't think it is rooted.
Guide: Getting Xposed RunningThis morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
What you'll need:
A paid copy of Mofo (obviously)
Either a modified system image containing Xposed already, or if you like, you can modify one yourself as described in this tutorial. I've already created a modified system image to include Xposed as well as Wifi Tethering and a modified hosts file for ad blocking.
The Xposed Installer apk
Xposed Installer needs to be installed on your phone
Terminal Emulator and ES File Explorer from the play store need to be installed on your phone
A rooted image flashed to your phone
Before flashing anything, this is what you need to do:
On your computer, find your de.robv.android.xposed.installer_v33_36570c.apk and rename it to be a .zip file.
Open this .zip file and extract /assets/XposedBridge.jar and, if you're modifying your own system image, extract /assets/arm/app_process_xposed_sdk16 as well.
Put XposedBridge.jar somewhere on your phone, I like to use the Downloads folder so I don't lose track of it later.
In ES File Explorer, navigate to /data (NOT SDCARD/DATA)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure it doesn't say sdcard > data!
Create a folder called "xposed"
Long press the folder, select properties, and set permissions to 755
Set the owner of the folder to root and the group to shell
Move XposedBridge.jar into the xposed folder we just created.
Make the permissions of XposedBridge.jar 644
As before, make the owner root and the group shell.
Open the Xposed Installer app on your phone.
Open terminal emulator and type
Code:
ps | grep xposed
This will return a pattern like the following. Make a note of the first seven characters, as shown (the first is a lowercase u)
Return to /data/xposed
Create two new files: modules.list and modules.whitelist
Make the permissions on both files 644 as above
Set the owner to the seven characters we noted down earlier and the group to shell on both files
If you're flashing a pre-compiled image with Xposed, you're done here! Go ahead and flash, and enjoy!
If you're modifying your own system image, you've got some more work to do. Take app_process_xposed_sdk16 from the Xposed apk and rename it to app_process.
In your turbo system image, navigate to /bin/ and replace app_process with the one from Xposed Framework. Make sure its permissions are set to 755:
Code:
sudo chmod 755 /path/to/img/bin/app_process
Linux does not allow setting the group of a file to a nonexistent group, so on your pc you'll have to make a shell group:
Code:
sudo groupadd shell
Change the group of app_process to shell:
Code:
sudo chgrp shell /path/to/img/bin/app_process
You're ready to flash!
NOTE: If XposedBridge.jar reports problems, try setting installation mode in the Xposed installer app to recovery (flash manually) and hitting install, then reboot.
You're done! Xposed should show up as installed! Don't use any modules that require system write access, such as replacing system icons, but most modules (ie GravityBox) work fine without it.
Ekkoria said:
This morning, I finally managed to get Xposed up and running on my Turbo. So I thought I'd write up a guide as to how!
Click to expand...
Click to collapse
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
ntxct said:
Gahhh I was working all day on getting Xposed baked in
Thanks for the write up! I'm finding modifying the image file and flashing it to be just as addictive if not more than flashing someones prebuilt roms on other devices. I never got into compiling android so this feels like a way to tinker on my own without jumping into the deep end of code.
Click to expand...
Click to collapse
Same here! When I finally opened Xposed Installer and saw it read the framework as installed, I've almost never been so excited about something Android.
i dont need it but its a great guide, easy, short and with pictures!
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Thanks so much man, about to flash. Will let you know how it goes.
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
It did not work for xposedbridge.jar
aven1357 said:
Does the phone need to be flashed with a rooted image, like that in the tutorial of how to modify system images? I can't write to /data, presumably because I don't have the rooted image flashed yet. Also my /data directory is empty.
I have a copy of mofo, and copies of the rooted system image and your already compiled system image. Is there something I am missing? Thank you in advance.
Click to expand...
Click to collapse
Yes, you will need to be rooted first to perform these actions. Apologies for not originally including this. OP updated
savagebunny said:
Ah damn, I actually just did a bit different process of installing Xposed on a image for myself, (which involved baking it into the rom that didn't have it) totally got it working and I've rebooted 3 times so far and everything sticks. Loving having battery percentage now! I can write a quick tutorial writing xposed files into a fresh rooted image via Virtualbox and such... Took me a few hours
Click to expand...
Click to collapse
Yes please do so. I'd be very interested.
Sent from my XT1254 using XDA Free mobile app
I am having trouble with es file explr it tells me the operation failed when trying to do anything I have root and I enabled root for ES it seemed to work on root browser fine (I reset my device and just installed es so far)
edit checked and the root enhancement options are greyed out?
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
I am having same problem as u smokie
smokie75 said:
After following directions for all files and then subsequent flashing of your pre-built image xposed installer still reports framework problem. I've gone back and double checked the user:group and perm masks and everything looks good. Any ideas what else I should check?
Click to expand...
Click to collapse
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
Thanks! That worked!
Thanks for this , works great , now we just need one with busybox preinstalled
Stuck at this point any help?[/ATTACH]
Ekkoria said:
What's reporting a problem? Is it XposedBridge.jar?
If so, try setting the installation mode to recovery (flash manually) and hitting install, then reboot.
Click to expand...
Click to collapse
so will doing this enable gravitybox to work on the turbo?
hmltnjrmy7 said:
Stuck at this point any help?[/ATTACH]
Click to expand...
Click to collapse
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
rayjr13 said:
You should be able to foloow the instruction you quoted from that point. You should go back and check your permissions, ownership and group for the 4 files. first
Do the change in install mode to manual. Hit install and go to recovery
recovery should give you the dead droid an then reboot
Also don't worry if the group "shell" shows up as something else in app_proces
Click to expand...
Click to collapse
Lol the dead droid freaked me out at first, but I'm so happy xposed finally works!!!
Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.
Excellent work friend @ondrejvaroscak. Congrats! Awesome
Was waiting a long time for this! Thanks man! working perfectly.
Working perfectly on D6603, thanks
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Thanks Bro , Very Nice !!
Perfect Work !!
Z1, C6903
Thank you for this great solution, works on Z1.
NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app
norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..
Working on fully setup 5.02 on Z2 thanks.
ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).
Ok fine... for verify all you said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?
hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Great thanks
ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line
hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
I noticed that old init.d enabling methodes aren't working anymore with latest firmwares on the Xperia Z5
I tried many of available traditional methodes (that relies on init.qcom.post_boot.sh, install-recovery.sh ... I believe they stopped working because a lot of them used SuperSU ), also tried many magisk init.d emulators but none of them worked as well. My mod uses simpler and modern method I thought I'd share it with you to help those who still have troubles activating init.d especially newbies
What is init.d ?
Init.d plays an important role in the world of Android development and customization It allows users to install scripts and mods to be run at boot—everything from battery tweaks to performance tweaks..
Click to expand...
Click to collapse
Compability
Code:
- Any device
- Tested with Magisk v14 but should work on all V12+
Bugs
Code:
- You tell me
Downloads
Second post
Credits
@topjohnwu for making this possible
RXSMB Team
Version Information
Status: Stable
Current Stable Version: 2.2
Stable Release Date: 2017-09-27
Created 2017-09-23
Last Updated 2017-07-29
[MOD][Magisk][Universal] A simple init.d enabler (system-less) [Fixed*]
Downloads
Please use remover before updating to new versions
Make sure you read the notes above carefully before downloading !
Magisk 14+
https://www.androidfilehost.com/?fid=962021903579480972
Magisk 15+
https://drive.google.com/open?id=1bzT5Uu2jIZDJpcaBvSMYqF11M-YYz5SJ
Remover UPDATED 27.09.2017
https://www.androidfilehost.com/?fid=889964283620753913
How to make sure it's working ?
Code:
- Go to [B]/data/[/B] if you find the file [B]"initd_test.log" then congrats it's working [/B]
Changelog
Code:
2.2 | 29/09/2017
- Bug fixes for some devices
2.1 | 27/09/2017
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
2.0 | 24/09/2017
- Changed permissions from 777 to 755 (standard)
- Added writing permissions to init.d folder too
1.0 | 23/09/2017
- First release
DO NOT STEAL MY WORK!!
FEEL FREE TO USE MY MOD IN YOUR ROM, JUST GIVE PROPER CREDITS !
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
whalesplaho said:
Flashed buh phone stuck at bootlogo, had to flash uninstaller zip before phone boots up.....
Click to expand...
Click to collapse
colorado48 said:
Flashed the mod in Magisk and rebooted, the mod made the fingerprint option unavailable in Settings. (stock 7.1.1 140)
Disabled the mod Magisk and rebooted, fingerprint appeared again.
Can you look into it?
P/s: flash the mod directly in TWRP will get you stuck at boot logo.
Click to expand...
Click to collapse
Please update to new fixed version I updated the link now for second time nothing hardcoded it's working perfectly for me on 32.4.A.0.160 should do same for all roms/devices
Do not forget to use remover before updating .. enjoy
New version works now ?
Fingerprint works now too.
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
colorado48 said:
New version works now
Fingerprint works now too.
Click to expand...
Click to collapse
good bro enjoy
whalesplaho said:
I still dnt have tha log file.... But test file inside init.d folder!!
Woooooooppppppssss......
Click to expand...
Click to collapse
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
korom42 said:
good bro enjoy
how is that, what kernel/rom you are using.. working fine on stock here
Also note that you might need to wait 30sec at least after boot before init.d takes effect
So try to refresh in your file manager and check the result in /data/
Click to expand...
Click to collapse
Im on crdroid lineage os and using stock kernel too brov.. 30secs? Okay will try again.
New version is up ! .. minor changes but better update
2.1 | 27/09/2017
Code:
- Removed sleep for 30 sec post boot (to avoid conflicts with some scripts)
Bro @korom42 there is no initd_test.log in the data folder on my XZ
Verstuurd vanaf mijn F8331 met Tapatalk
This works but breaks both safetynet checks for me on a Z3C LOS 14.1 with Universal safetynet fix 10.1.
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Adil Tariq said:
[MENTION=5033594]
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Click to expand...
Click to collapse
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Adil Tariq said:
@korom42, first of all, thanks for this awesome work. I can confirm that this mod is working on Xperia Z5 Premium E6833, 7.1.1 stock rom with magisk 14.2 beta.
BUGS:
1) the test file present in the /system/etc/init.d namely "00test" is undeleteable. I tried remounting the system as R/W but still get the message "Device or Resource Busy".
2) When I create my own scripts (which is just another test script or any other) in the /system/etc/init.d folder, it gets saved successfully with permissions rwx-r-x-r-x. But when i restart the device, my created scripts get deleted automatically without execution.
Is their something I'm doing wrong???
P.S: I have attached the script I'm using for your consideration....
Regards
Adil
Click to expand...
Click to collapse
Adil Tariq said:
@korom42, i figured out the problem.
EVERYONE FACING PROBLEMS WITH THIS MODULE SHOULD PLACE THIER SCRIPTS IN THE FOLLOWING PATH:
/magisk/simple_initd/system/etc/init.d
DON'T PLACE THE SCRIPTS IN:
/system/etc/init.d
This is a systemless module, placing files in the latter mentioned path you modify the system which kind of ruins the systemless purpose....
Thanks alot for this extremely awesome module @korom42
Regards
Adil
Click to expand...
Click to collapse
Alright, if you managed to use the mod while keeping SafetyNet bypass working than that's great
but I won't change anything since it's not a reliable way because the user will have to move his files each time adding new scripts
- for deleting the 00test file did you try a different file manager .. root browser works fine here
Infy_AsiX said:
However the module breaks safetynet immediately after installing. Is it because of the test output file created in /data or otherwise?
I'm using this init.d link module instead now with a small mod and workaround. I've written my experiences in that thread. It's not straightforward but it's the only semi-working safetynet init.d for me.
Click to expand...
Click to collapse
- Just disable the module from Magisk Manager whenever you need SafetyNet bypass back .. will try to make it SafetyNet compatible in next versions if possible
@korom42 i just want to report that safety is now also broken on my Xperia Z5 Premium E6833 Stock Rom (LOL) after just 2 reboots. Uninstalling this module fixes the issue. Hope you will find a way to make this module work with safetynet....
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
As for safety net, there is the very easy way to fix it. Just reinstall busybox version 27.2 after each reboot that will return safetynet back to pass state. I use meefik and that helps.
Click to expand...
Click to collapse
Download the app here
Altenative by Stephen (Stericson)
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
Great! it's working!
Thanks!
korom42 said:
@Infy_AsiX @Adil Tariq @crisout
This is a quick temporary fix for SafetyNet untill I release I new version .. thanks to @Mondor1979
Download the app here
Altenative by Stephen (Stericson)
Click to expand...
Click to collapse
crisout said:
Great! it's working!
Thanks!
Click to expand...
Click to collapse
Did you find out another fix to safetynet? It's not working anymore
Hey guys, recently a member from Discord channel (ikkun) showed me steps on how to root Phoenix OS by just placing the su binary in the system folder. This method is so much easier and convenient than replacing the system.img, that it should be the main way to root your Phoenix OS installation.
Advantages:
No need to wait to download and extract a 500MB system.img. Instead, download a 5MB .zip file
No need to do a fresh install. You can root an existing installation without removing all your data.
Play store and Google Calendar sync work
Tested and works with:
v2.2.0 64-bit
v2.2.1 64-bit
v2.5.0 64-bit
v2.5.3.64 64-bit
v2.5.7.348 64-bit (Tested myself)
(Probably works on your system too. Why not test it and post your results below?)
Instructions:
Download and extract the .zip file. For the purposes of the tutorial, I'm going to assume that you extract it in the Download folder and rename the SuperSU folder to su. Inside su, you should see META-INF, x64, x86, etc folders.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open the terminal by pressing Alt+F1
If you have Phoenix OS 32-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x86/[B]su.pie[/B] su
chmod 4751 su
su --install
su --daemon
If you have Phoenix OS 64-bit, type in these commands:
Code:
cd /system/xbin
mv su su.orig
cp /sdcard/Download/su/x64/[B]su[/B] [B].[/B]
chmod 4751 su
su --install
su --daemon
This screenshot is for 64-bit:
Note 1:
If after typing in the mv su su.orig command, you get an error saying:
mv: rename su to su.orig: No such file or directory
Click to expand...
Click to collapse
That means your Phoenix OS installation does not come with the su binary. Skip the mv command and proceed to the next step since there is nothing to make a backup of.
I usually install my Phoenix OS using the .exe installer and always see the su file in that folder during the rooting process so I never see this error. It was never clear to me why people are missing the su binary, but my observations tell me it could be because people are installing it using the ISO file or using 32-bit. I never had the opportunity to test this out, but if you have this error, please post your Phoenix OS version, architecture, and installation method.
Click to expand...
Click to collapse
Note 2:
Make sure you type in the commands exactly as provided. I saw other people were having trouble because they typed in the command incorrectly; they were missing a period after a space. It should be with a period and a space after the command (if you're rooting x64):
Code:
cp /sdcard/Download/su/x64/su [B].[/B]
and not:
Code:
cp /sdcard/Download/su/x64/su
The dot simply tells the cp command to place the file in the working directory (which was set earlier by the cd /system/xbin command). Alternatively, you can replace the dot with the current directory, the new command being:
Code:
cp /sdcard/Download/su/x64/su /system/xbin
It's just easier to type a dot then type out the whole directory, especially considering the fact that you can't copy-paste in the terminal (as far as I know, could be wrong)
Click to expand...
Click to collapse
Close the console by pressing Alt+F7. (If you have trouble exiting the console, post below with your Phoenix OS version and architecture. Then, try pressing Ctrl+Alt+F7)
Phoenix OS might crash and restart. Using the File Manager, go to the Download folder. Navigate to su>common> and install Superuser.apk
Launch SuperSU app from the app drawer. Press Continue, then select Normal to update the binary normally. Exit out of the app after the update is successful.
Launch Security app from the app drawer. Click AutoRun.
Toggle SuperSU to enable it so that it can automatically run when other apps request Superuser access. Exit out of the app.
History:
Added notes for common errors people were having
Added another keystroke to exit console (Ctrl+Alt+F7)
Added screenshots. Removed unnecessary steps. Fixed grammar mistakes.
These instructions were posted in the Phoenix OS Discord Server by ikkun. Thanks to Chainfire for SuperSU.
Instructions ported from tutorial Installing SuperSU on Remix OS 2.0
Attached zip file in case their website is down.
Thanks, it works
jamarita said:
Thanks, it works
Click to expand...
Click to collapse
Thank you for the confirmation! What device do you have and what GPU does it come with?
Does not work on hp 655 32 bit
lomax84 said:
Does not work on hp 655 32 bit
Click to expand...
Click to collapse
First of all, what kind of a computer is an "hp 655"? Second, can you provide more details to what exactly doesn't work? What step are you failing at?
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
ariadnejro said:
Working fine for me on PhoenixOS 2.2.1. My computer is a HP Spectre x360.
Click to expand...
Click to collapse
Awesome, thanks for letting us know!
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
mic1000s said:
The method here is which I use to make a partition of demarage for another os, the method is simple and it erases nothing in the PC videos Show a complete installation has 2m30 you can see the procedure. On the second video we little to see how installing Android 7.1 Phoenixos 2.2 new version the whole in two-tier and triple boot.
Phoenixos 1.1
Partition at 2mn30
https://youtu.be/NUCsSkbooqw
https://youtu.be/LWYU3eIp-Zk
Phoenixos 2.2
https://youtu.be/fYpLOBjnYxM
https://youtu.be/W0kz9LUXdiA
Here is I hope to have taken forward l.
Click to expand...
Click to collapse
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
jbardi said:
This method still causing the Play Services sync problems with Gmail, etc. Any fix?
Click to expand...
Click to collapse
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
mic1000s said:
It is exactly it, forgiveness if my English is not very clear. It is a method to install a dual boot or a triple boot in this particular case on a tablet Teclast x98 or on a mini PC Pipo X7 that have the same characteristics it does not solve at all the problems of synchronization of Google moreover I have no problem of synchronization on Phoenix os 2.2
Click to expand...
Click to collapse
Oh okay, thank you for the guide, I hope others find it useful. The other reply was to another user, not to you. Phoenix OS has a Gmail sync issue. So if you try to install and sign into the Gmail app, you will not be able to synchronize your mail. You actually do have a synchronization issue, it's just that you haven't experienced it yet because you haven't tried using the Gmail app.
meanhacker said:
I'm sorry, it's kind of hard to understand what you're trying to say, but I'm assuming this is a guide on how to set up a triple-boot system.
This method only roots the system, it's not supposed to fix the sync problems with Gmail. The problem exists even before you root, so we need to search around for a solution. I would recommend asking in the Discord channel and someone might shed you some light on this issue.
Click to expand...
Click to collapse
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Seanie280672 said:
when I type the 2nd command, mv su su.orig it says no such file, what am i doing wrong ?
Im single OS booting and the files are as you laid out, but in the Download folder from within Phoenix OS
Click to expand...
Click to collapse
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
meanhacker said:
It sounds like you're not in the right folder. What Phoenix OS version do you have and what processor architecture? (32/64-bit) are you sure you're running the first command correctly (cd /system/xbin)? In the terminal, type in pwd and press enter. Post the output here. It should say /system/xbin. If not, use the command cd /system/xbin. If that doesn't work, type in ls -a and post the output here. Can you find su in that list of files? If so, all we're trying to do is make a backup of it before replacing it with the one we downloaded from Chainfire
Click to expand...
Click to collapse
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Seanie280672 said:
Im running the latest version x86-64bit ver: 2.21.247
Ive manually had a look in the system xbin folder and can see all of the above mentioned files and commands etc, mv, su.orig etc etc thats why I dont understand why its not working, so ill try your other commands now and let you know.
EDIT: running it on a packard bell easynote TE, Intel celeron N2820 CPU, 4gb DDR3l with a samsung evo 120gb ssd
EDIT 2: when im in system/bin and type pwd it gives the result /system/xbin, posted a couple of pictures below.
Click to expand...
Click to collapse
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
meanhacker said:
Great, thanks for the pictures. So it looks like you already made a backup of the su, which is now named su.orig. Proceed with the rest of the steps
Click to expand...
Click to collapse
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Seanie280672 said:
Thanks for all of your help, all the commands went in ok this time, however a little problem, ALT+F7 isnt working to close down terminal, so I have to force restart, then once its back up and running, continuing with the instructions to install super SU says not root found.
Click to expand...
Click to collapse
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
meanhacker said:
I don't remember off the top of my head, but try Ctrl+Alt+F7. Also, try other numbers for the F (Function) keys. If superuser doesn't work for you, go into the Security app and enable SuperUser for AutoRun.
Click to expand...
Click to collapse
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Seanie280672 said:
Thank youu very much, strangest thing happened, just reinstalled the whole OS and all the commands went in this time perfectly fine, the keys to get out of Terminal are indeed Ctrl+Alt+F7.
Managed to have a bit of a play and sort of get the latest version of showbox running, also installed it through Kodi where it appears to be working perfectly fine, going to stick with this OS for a while now, does everything that I need it for, without the crap sluggishness of Windows, looking out for any future updates.
Click to expand...
Click to collapse
I'm glad you got it to work! I will update the OP with the new information. What made it work? Was it the fact that you could now escape the terminal or letting Superuser in AutoRun?