hello
Today was the first time I joined.
DisasterROM_v8 bugs will tell.
Was a supersu DisasterROM_v7 DisasterROM_v8 do not have su and superuser privileges error appears.
Rom developers solve problems related supersu by Please
8.0 7.0 original rom the xbin su was not xbin busybox and su-related files.Re-upload please.
Xbin 7.0 and 8.0 below screen syaseun comparison photos.
I'm sorry, but I've used Google translate.
Can write well by the developers who made Erom!
Installed su binary and supersu can not be installed.
Problems.!
Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270
jl10101 said:
Reflash any other compatible kernel. Something like Philz kernel : http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
I have a solution.
1. Download http://downloadandroidrom.com/file/tools/SuperSU/CWM-SuperSU-v0.99.zip and put on sd card
2. Reboot into recovery
3. flash this zip
4. In recovery go to advanced, and Fix permissions
5. Reboot and enjoy your rom with working superuser
6. Run Google play and let the supersu app to update
Hello guys. I need your help please. I have LG L9 II with 4.4.2 build 20g.
I have found this root method and it works, i get root access. Then i decided to remove kinguser and install SuperSU. So i installed supersu from google play, it asked for su binary update. I let it update, but it always ended with error "su binary update failed".
I tried Google and found tutorial on YouTube how to replace kinguser with supersu. I used that script, it worked - after end it opened supersu, and su binary update worked without error, great. But then i restarted device and i lost root access, supersu was telling su binary missing and cant install it. So i must root again with kinguser.
Then I tried to install SuperSU from recovery, so i downloaded supersu flashable zip, entered command 'reboot recovery', it opened stock 3e recovery. There are options apply update from external sdcard and from cache (+ ADB and wipe options). But when I select 'apply update form external sdcard' it shows error "E: failed to mount /sdcard (No CSI structure available)". Only 'apply update from cache' doesnt show error, so i put supersu to /cache partition, but flash failed with error 255 and installation aborted.
So please, can someone help, how i can fix 'no csi structure available'? And how i can have supersu permanently?
Big thanks for all helpers.
Hi,
what started as an Idea seems to be working now. For once i wanted a phone that has warranty for more than two weeks (or at least a chance for warranty).
DISCLAIMER:
Do all of this at your own risk. Even though we will not be flashing a custom recovery, technically the warranty is lost the moment you root your phone.
None of the Tools is actually written by me, i just tinkered a bit and came up with this tutorial.
1. You will need
- Galaxy A3 (mine was an A300FU but i guess every one that can be rooted without flashing should do) on Lollipop (5.0.2).
- Minimal ADB or some other software that brings debugging drivers and adb.
- KingRoot 4.60+
- SuperSu-ME (from play Store or an older version is also fine) or any other way to go from the Kinguser Root Management to SuperSU
- Deodexed apks matching you phone model
- Flashfire Beta
- Xposed Installer, I used 3.0alpha4
- Xposed bridge for Samsung lollipop I used xposed-v75-sdk21-arm-arter97-snapdragon_requestConcurrentGC
2. If something goes wrong:
- Odin and a stock LOLLIPOP ROM for your device!
This is Important: Since we dont have a custom recovery, whenever something goes wrong the only rescue is going back to a stock rom and thereby wiping. If everything works in the first go there will be no wipe.
3. Rooting
First we need to root. Thanks to KingRoot thats very easy and just a matter of waiting. Install KingRoot (has to be 4.60+ for Lollipop), Click try to Root, wait for it, done. Know we need to get rid of the KingRoot stuff again and install SuperSU (FlashFire does not support KingUser but SuperSU) thats what we need SuperSU-ME for. There Will be some Left overs since KingRoot converts itself to a system app, you can remove this with Titanium Backup or a ROM Toolbox of you choice.
4. Deodexing
Next step is gonna be Deodexing. This one is a little Tricky without a Custom Recovery. Flashing the Deodex using FlashFire will leave you stuck at the Boot Logo.
Unpack the Flashable Deodex zip. you#ll find a META-INF and a system folder. Copy the system folder (or rename it, doesnt matter) to your SDcard or the phone memory using USB. At this point you can also copy the two Xposed files (zip+apk). Next we need USB Debugging. Install the minimal ADB, browse to the install location and start "adb devices" once (this will start the daemon). Now take your phone, browse to settings / phone info and tap the build number like 10 times (this gives you developers options) now go to settings / developers options and enable USB debugging.
Connect you phone via USB. This hould bring up a dialog granting your PC permission to connect. Click Yes.
Connect to the phone and request root using
Code:
adb shell
su
Now turn on the phones screen there should be a root request, allow it.
Next is the following commands, assuming the location of the extracted system folder is /storage/extSdCard/deodex_system
Code:
mount -o rw,remount /system
rm -Rf /system/app
rm -Rf /system/priv-app
rm -Rf /system/framework
cp -R /storage/extSdCard/deodex_system/* /system
chown -R root:root /system/app
chown -R root:root /system/priv-app
chown -R root:root /system/framework
chmod -R 755 /system/app
chmod -R 755 /system/priv-app
chmod -R 755 /system/framework
rm -Rf /data/dalvik-cache/*
reboot
This will replace all system apks with the deodexed ones, sets the right owner and permissions, clears the dalvik cache and reboots. Booting is gonna take a while and then you're enjoying you're rooted, deodexed stock ROM without flashing anything so far. So now about installing Xposed.
Don't be to slow with thus step. Deleting the three folders will make the phone go crazy and at some point reboot, you should be done by then.
Edit: I did this on a second device now, for some reason the remount did not work. In this case try disabling SElinux (http://forum.xda-developers.com/devdb/project/dl/?id=12178) and then remount.
5. Xposed
Install the XposedInstaller apk file like any other app, no need to start it yet. Next install FlashFire and launch it (granting root access) now select the Option "OTA or ZIP" in Flashfire and select the flashable Xposed zip you downloaded earlier. No further settings needed just hit Flash! The next reboot is again gonna take a while, but after that you can launch the Xposed Installer and start Installing Modules. We're done.
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Once more, I did not develop any of the tools mentioned, all credits to their respective authors.
Cheers,
prometh
Edit: I did not try too many modules yet but Wanam for lollipop works just fine and that useless S Whatever bar is a thing of the past
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Squall88uk said:
Hi.
I already have a rooted Galaxy A3 (A300FU) and I have TWRP as my recovery so my warranty is already gone and I'm not too worried about that. However I have had no success at trying to deodex my rom to be able to install xposed.
Would it be possible to just flash the deodexed and the xposed zip from TWRP? And with regards to the deodexed zip would it matter if I flash it over the top of my current rom when I'm using a carrier rom rather than the BTU unlocked rom?
Click to expand...
Click to collapse
I think this would be a question for the deodex thread I linked but heres my 5 cents: The procedure in your case should be Flashing Deodex (eventually also gapps_replacement from that thread if you get Google Apps FCs) flashing Xposed, booting, installing the xposed installer. The Deodexed zip is meant to be flashed on top of your system. What I described is basically doing manually what the deodex zip file would do (deleting copying...). Since you have twrp already, I guess a system backup wouldn't hurt.
Many thanks for the help. I'll make a nandroid backup of system first just in case and then give it a go.
Thanks again.
Impossible with my SG A3 A300FU
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
darwin345 said:
Hello, I already have the root and TWRP installed, but if I try to type the command line with ADB it doesn't work and if I flash the zip, it doesn't work too. Any Idee ? With the first or the second method boot loop with the samsung logo !!
Click to expand...
Click to collapse
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Great work prometh696 !!! I managed to get xposed on my A5 with knox 0x0 !!!
Some other steps I followed to get it for my A500FU; first I extracted my own system folders system/app/, system/framework/ & system/priv-app/ with root explorer to my ext SD card and then copied it to my computer.
On the computer I batch deodexed those folders with joeldroid's batch deodexer:
http://forum.xda-developers.com/and.../script-app-joeldroid-lollipop-batch-t2980857
Had some issues there as not every Java version seems to deliver the deodexed folders without errors; more details in that topic.
Then I followed your adb commands and installed xposed, and as you said, knox didn't change and is still 0x0 !!!
Thanks again !!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:06 PM ----------
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
The command lines are for copying the deodexed apks (so not in a zip). The zip is for xposed and is flashed by flashfire.
But as he already got TWRP (and thus knox 0x1) I see no use for him to use your method anyway
prometh696 said:
If you try the adb commands whats the exact error? Permission Problems? Anyway the Command line should do nothing else than flashing the zip file (I dont know what the zip file wipes after flashing but I assume its dalvik and cache).
Click to expand...
Click to collapse
When I type the first command line after this one "rm -Rf /system/priv-app" or this one "rm -Rf /system/framework" I don't know when exactly my phone reboot and bootloop on samsung logo (dynamic one) ???
My mobile restart before end of commands line
Hi,
your solution seems really good but my mobile (A300FU) is retarting before I typed all commands line.
Do you know a solution ?
Maybe cause I've no ExtSDcard and use the internal card ?
Thank you for your help !!
Regards
Virtua
update : I tried with trwp and made the necessary but the mobile does not boot.
This phone is a mess
It's the first time I can't do what I want with a phone. All posts seems to be a hoax. ;( ;(
Whenever you do a factory reset (from the recovery), You need to root again using Kingroot, replace it with SuperSU and install Xposed again.
Click to expand...
Click to collapse
This is actually incorrect unless root is systemless.
Root remains in system, and so does xposed. A factory reset does not touch the system partition.
You lose root after a reset because you need to reinstall superuser. If you make it a system app you won't lose root even after a reset.
The same with xposed just reinstall the apk.
I was new for rooting and choose the easiest way to root(kingoroot not kingroot) my samsung galaxy j1 ace...
and now i want to switch to supersu from kingo superuser...
as kingroot being more famous... i didnt found any tutorials too... some are using supersu me...
i have no idea what to do... i want to clear the remainants of kingo too...
help me...
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
pascal.malaise said:
A procedure is here:
https://forum.xda-developers.com/an...g/replace-kingoroot-supersu-manually-t3573361
My device stores applications in directories in /data/app, ex:
com.kingoapp.apk-1, com.kingouser.com-2, eu.chainfire.supersu-1,
with subdirectories, lib and oat...
Any help to transpose the procedure above into this environment?
Click to expand...
Click to collapse
can u suggest me something easy???... like with terminal....
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
rolland.arriza said:
Revert to stock rom and try the manual rooting using SuperSU. You'll need a compatible custom recovery to install supersu.
Click to expand...
Click to collapse
terminal or supersu me will work?
http://www.ccnworldtech.com/2017/03/how-to-replace-kinguserkingo-superuser.html?m=1
will it work???
yashasvi.malik said:
can u suggest me something easy???... like with terminal....
Click to expand...
Click to collapse
plss help....
yashasvi.malik said:
terminal or supersu me will work?
Click to expand...
Click to collapse
Have you reverted to stock rom? You can just do a factory reset (root access should be removed too). Install the necessary drivers. Download a custom recovery for your device (TWRP maybe, search it here in the forum). Download the supersu flashable zip (this is an older version, just update after install). Also download the latest ADB drivers (awesome app). Then you root:
(1) Copy the supersu zip to your device storage. Copy/move the custom recovery to the root folder of your ADB.
(2) Open ADB:
Code:
adb reboot bootloader
wait for the device to go into fastboot, then:
Code:
fastboot boot "recovery.img"
(3) Navigate the new custom recovery and select "Install" and select the supersu zip file, then reboot.
(4) Check root access.
Goodluck
Hi.
After i updated my phone to 7.10.19 i cant run su command in terminal and i cant install viper arise. it installed but it doesnt appear.
bu i can install xposed and it work!!!
@x23are Did you reflash supersu/magisk (or whatever root your using) after applying the update?
xposed doesn't need root but some modules do.