Since this information was buried in the other thread I am posting it here for visibility:
This will work only on CWM flashable zip stock (because you need CWM to flash the zip, obviously):
- Flash this first:
http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
- Then flash this:
http://d-h.st/X1A
Click to expand...
Click to collapse
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Is there any way I can root the phone if i already upgraded to KitKat, but I don't have CWM ?
I'm guessing that RootKeeper does not work?
help
dSERiES said:
I'm guessing that RootKeeper does not work?
Click to expand...
Click to collapse
:cyclops:
whether we should try this guide with other sd card
[GUIDE] [ROOT] Root your LG Mini L40/L70/L90/G2
"update.zip"
looks positive
or try a Varcain "kk_root.zip"
consider and report
or for us, and there are many of us, the OTA upgrade, no root and CWM
pozz
I want to know if this method will work to me( I am using 4.4.2 OpenEu v20b.)
Изпратено от моят LG-D605 използвайки XDA-FORUM, благодарение на appyet.com
hepy
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
skakavac65 said:
or loss from the root 4.4.2.sa ota update
working with this method, at least for me
I just installed TowelRoot V 2
and without a reboot got root
Then I installed the Super 1.9.4 (any little problems)
and got root .....
very happy
http://forum.xda-developers.com/showthread.php?t=2784416
[ROOT][EXPLOIT][APK]Root Your Phone[LG and other supported]
Originally Posted by giperborey View Post
So. I got it Thanks to all!
1) Download and install TowelRoot.
2) Varcain's patch
Add string "/system/etc/install-recovery.sh &" to the end of /system/etc/init.engdo.post_boot.sh
or just simply replace it by Varcain edited version
this file.
It's neccessary to get root after each boot.
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rw-, r--, r--)
3) Delete last string "/system/etc/install-recovery-2.sh" from the /system/etc/install-recovery.sh
NOTE!!! YOU MUST SAVE ORIGINAL PERMISSIONS TO THAT FILE (rwx, r-x, r-x)
Congratulation! You get rooted phone
IMPORTANT NOTE:
When I did it the first time, I tried to install SuperSU 2.0 from the Market. He did not want to upgrade properly. Finally I got a soft-broken phone and repaired it by kdz firmware flasher. I'm not sure that the reason of soft-brick was SuperSU, but without it root works fine.
since I'm not a programmer, I would ask Varcain and opportunity that we end up CWM,
so that we enjoy the OTA UPDATE CM11, PA Rom 4.4.3 .......
Get the conversation
Click to expand...
Click to collapse
But this is only temporary root. After restart of phone you must run this root again
help
Varcain said:
Since this information was buried in the other thread I am posting it here for visibility:
Now, people are wondering if it's possible to root from OTA/kdz update (like we originally rooted stock JB). In theory it should be. Basically what I did with this root fix is I've added one line to one of init scripts (which all run with root permissions). This line is starting the install-recovery.sh script (which is provided with SuperSU zip package). With KK it's not enough to just drop su binary to /system/xbin - you also have to start daemon (as root). Whatever rooting method you are trying to use has to add a line to one of startup scripts which starts the SuperSU script. If one such method is found please post here, I will also update the OP.
Click to expand...
Click to collapse
Hello.Thanks for the tutorial.I cant put the recovery mode as i dont know how to do it exactly.I know that i have to press the power button and volume up.If you help me i will be grateful.Thanks
Hi Varcain
Please could you update "varcain_rootfix.zip" for SuperSU v 2.01?
With the current "rootfix" does not work, and still wants to install SU binary.
Thanks for your work.
Sorry bad English.
Root Stock Recovery 4.4.2
Hello people,
After many attempts,
it seems that these instructions
definitely the easiest to root lg d 605, the OTA upgrade to 4.4.2.
A big thank you lioko27
Android.com.pl
Root Stock Recovery 4.4.2
Welcome.
Modification is used to zrotowania v20 firmware preloaded or OTA update for the PC (KDZ, Software LG)
This method does not allow upload custom recowery Cwm-fault is either with the powers or the installation file Cwm-work in progress
needs
* soft v20
* stock recovery
installation
charge applications:
- Towelroot (gives you temporary root)
https://towelroot.com/
Rom Toolbox Lite (or other manager with root privileges)
https://play.google.com/store/apps/d....toolbox&hl=pl
w / the apps you install on your phone, run Towelroot and click on the banner "make it ra 1 n"
charge pack zip
https://drive.google.com/file/d/0B1t...it?usp=sharing
move it through the USB cable or a memory card reader
run rom toolbox, click the root browser and copy the root file location v2.zip dp "cache" on your phone,
we leave the rot browser to the main menu click "scripter"-reboot recovery-run script-do
the phone will start in recovery, select apply update from the cache and select the copied package,
after the installation is completed, restart the phone and look forward to root.
The procedure is simple and Root after restart everything is OK
Now is already high time for CWM ....
Help Varcain....
and other developers ....
When I see what kind of support are second LG devices,
I was angry a lot.
Just look at what support has LG 9 and all will be clear.
The other devices that do not speak ....: (
Sorry for my english, going over translater,
greeting
I hope CWM soon ...: Kiklop:
hey I updated to v2.01 supersu
link
http://forum.android.com.pl/f1211/root-stock-recovery-4-4-2-a-439890/
I have seen a way for cwm to kitkat in a polish forum.
Instructions:
You must have adb.
1 Extract the zip on PC
2 Connect your phone to a PC with USB debugging enabled
3 Open the folder and press "shift" and the right mouse button
4 Select "Open command window here"
Follow the commands now:1 adb push aboot.img / data / local / tmp
2 adb shell
3 su
4 dd if = / data / local / tmp / aboot.img of = / dev / block / platform / msm_sdcc.1 / by-name / aboot
5 exit
6 exit
7 adb push loki_flash / data / local / tmp
8 adb push recovery.img / data / local / tmp
9 adb shell
10 su
11 cd / data / local / tmp
12 chmod 777 loki_flash
13 ./loki_flash recovery recovery.img
14 reboot recovery
After your phone will reboot in cwm mode.When i did it rebooted automatically with an error:HW reset was detected.Dont worry just press the turn on button for 20 sec and the phone will reboot without giving that error again.
Big thanks to szymel00 a user of a polish android forum.
The link for the zip: (http://d-h.st/2kk)
Tested without any virus.
I didn't have to flash anything
I used the app KingRoot(not in appstore). It just rooted and it was just done. Later that day it rooted jelly bean version as well.
PS! You have to allow unknown sources when running apk-s from outside play store.
Related
I succesfully updated my Samsung Galaxy S3 from Android 4.2.2. to 4.3 after rooting my Phone.
However, SuperSU doesn't work anymore, giving the message "If you upgraded to Android 4.3 you need to manually re-root".
I cannot find an answer in the forums here on XDA developmers.
Can anyone help me?
Thanks in advance,
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Rooted 4.3 and installed SuperSU
morwit99 said:
I already tried that on my own. Didn't work. SU still tells me that I need to update the SU binary. Manual re root. And I AM rooted! I even wiped EVERYTHING and started over. no go. So, I'm guessing that I need to manual re root. I'll search for that binary where ever that is Oh, I went to the latest SlimBean build #2 for 4.3.1 after CM 10.1.3 and CM 10.2 refused to install on my d2usc. Now CM's Rom Manager won't work, SU doesn't work, anything that needs root access no work mahn! On the good side, everything else works fantastic, except PIE control. But I bet that has something to do with root access, so no great surprise there. I am enjoying every minute of these problems!
Click to expand...
Click to collapse
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Same problem here
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
otto68 said:
After updating to 4.3 my SU does not work, I have tried all I have internatinal model if any info please post
Click to expand...
Click to collapse
if you have supersu or super user already than just download update-supersu from http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip and flash it through the recovery mode( custom recovery preferred).
xprivacy / reboot to recovery
In my case I was getting false alerts as xprivacy has blocked system access. (eg was with AdAway) Cleared those apps in XPrivacy and all worked find then.
Also you can try to go into recovery and the try to reboot. You may get message to reinstate/fix SU.
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
You rock, I had re-rooted my updated Android 4.3 but my SuperSU was not usable anymore. Redownloaded it, allowed it to update SU Binary, disabling Knox, and viola! Root galore
suyash1629 said:
if you have supersu or super user already than just download update-supersu from ...LINK REDACTED.. and flash it through the recovery mode( custom recovery preferred).
Click to expand...
Click to collapse
that fixed it for me..thanks :good:
Tried all these steps on the new 4.3 MK6 ROM. Does not work for me. I cant find the Root access option itself in developer options. I already tried flashing CF-Autoroot multiple times after factory reset, using odin. I CWM still says binaries outdated and SuperSU doesn't work work even after updating from play store. Later i tried flashing supersu via the recovery mode. Still no success. Any suggestions?
Edit:
Another factory reset and flash did it. I don't know how. But it is fixed now.
By following your step, my superuser icon is gone...
Stuck in ODIN
Everytime I try to root S3 LTE via ODIN with CF auto root, it gets stuck there, need some help please, have had to use kies's recovery tool 3 times today because of that
i dont have this function
tallman43 said:
Been answered loads of times known issue go to settings/Developer options/root access tick Apps and ADB reboot
Click to expand...
Click to collapse
Hi, I dont have this function in my phone, nowhere, please help me?
fragiepacino said:
Hi, I dont have this function in my phone, nowhere, please help me?
Click to expand...
Click to collapse
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
no
tallman43 said:
Tapping on Build number till it says Developer Options Activated/Enabled, press back and you will see Developer Options in the list.
Click to expand...
Click to collapse
the root function in the developers section, nowhere i can tick it
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Sorry I thought you wanted to know how to get into developer settings....This thread is from 2013 i don't have S3 anymore if your trying to get root to work just follow some of the other suggestions posted.:good:
fragiepacino said:
the root function in the developers section, nowhere i can tick it
Click to expand...
Click to collapse
Here you don't have the "root access" setting ?
Sent from my GT-I9300 using XDA Free mobile app
s3 i9305 supersu binary problem
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
—------------------------------------------------------
I know this is an old problem and has been answered many times, i have read all thepossible ways to fix it and i have tried, over and over but I'm missing something.
Please help.
I rooted with Supersu, it worked for 2days then stopped. Now all the root apps can't work and i have tried everything to make it work, to no avail. Here is a copy of my Root hecker:
Root access not properly configured or granted.
Superuser Application Status
Installed: SuperSU by Chainfire - version 2.46
System Files Status
Standard Location
Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 66916 2015-04-17 00:03 su
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard Location
Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
User Account Status
Error: stderr: [-] connect ui: Timer expired, stdout: null, exit_value: 1
Optional: ADB Shell User Status
Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional: System Environment PATH Status
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
_----------------------
So my device is rooted, but i don't have permission. Tried to copy .su file from xbin to bin, not possible.
Uninstalled reinstalled, unrooted rerooted, reinstalled SuperSu from playstore.
Made sure no double superuser programs running.
Got rid of Knox.
Tried to custom install Supersu update, says invalid certificate.
I believe if i can copy the .su file in \xbin to \bin the permissions wil be there. Bought Rootbrowser but error when copying. Or give permission on file SetUID.
Can't run Bootbox cause didn't install before root stopped working. Also Titanium backup stopped working now.
Any ideas how to fix? Don't want to factory reset. Can't be to difficult to fix.
PS. If this post is i wrong place please advise where itshould be.
Thanks
S :good:
cbmk said:
I had similar problem. Here is what I did -
1. Download CF-Auto-Root-d2att-d2uc-samsungsghi747 from autoroot.chainfire.eu.
2. Unzip
3. Use ODIN in the package to root.
4. Install ROM Manager.
5. Install SuperSU(Chainfire) from Play Store.
6. Open SuperSU and update SU binary. I saw a message to disable KNOX. I did it:highfive:
7. Install CWM Touch.
Then I installed other apps that need SU - Triangle Away, Titanium Backup. These apps worked fine for me. I went ahead and froze bloatware.
** Credit goes to all those hardworking folks who stay ahead in the game **
Click to expand...
Click to collapse
I can't find my phone as one of the packages. I have an Alcatel phone.
root my mobile but didn't get access
rooted my phone micromax a116, all proccess done wel as shown in tutorials. But root checker says that "root access is not properly installed on this device". Please tell me what to do?
DISCLAIMER : You attempt the following at your own risk !
I'm not responsible if your phone blows up, bricks, you travel back in time or go bald or something!
Background :
I have the MT2-L05 Mate 2 from China.
When I received my Mate 2 last Thursday, the phone was on 4.2.2
After much hunting and downloading and flashing of ROMS, I managed to finally update to 4.4.2 KitKat.
Great ! I was happy. But I didn't have root access.
After trying and failing to use the various bootloader unlock tools on these forums, I Emailed Huawei, and politely asked them if I could have the 16 digit code for my Mate 2. An hour later an Email arrived with my bootloader unlock code, so I fastbooted, used the code and unlocked the Bootloader.....Cool ! Thanks Huawei, great customer service.
I then went to root my phone, and here the problems started. I tried at least 20 different Root tools, both via phone and over the pc, but no joy.
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine and all was good with the world. I tried wakelock detector first ( Yeah, I know, I REALLY need more battery life from the Mate 2 ! ), and Supersu asked for permission and it worked no problem.
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
Root Genius 2.0.1.3 :
http://www.shuame.com/root/
The Problem :
The 4.4.2 update adds a file to your System folder called :
set_immutable.list
this file contains :
Code:
/system/bin
/system/build.prop
/system/etc
/system/fonts
/system/framework
/system/isp.bin
/system/lib
/system/ons.bin
/system/usr
/system/vendor
/system/xbin
/system/app/HwLauncher6.apk
/system/app/HwLauncher6.odex
/system/app/systemUI.apk
/system/app/systemUI.odex
Any location listed above is IMPOSSIBE to mount as rw. Every file explorer or emulator you try will tell you it is rw, but it's not.
It's locked down completely...................and it's REALLY annoying.
This is why I could never edit my build.prop or Install Adaway etc..................
But I found a solution...... ( I think ! )..........
The Solution :
I spent the afternoon at work using google translate to find a fix for my problem and found a post from a guy called :
**** wire His Royal Highness Prince czx ( I cannot post the first 4 letters as it will probably be banned....It must be a Google translate error but it made me laugh ! )
His guide never worked for me until I made a few edits and added STEP 4. Then I got it to work.
The Solution :
1, First Root your Phone ( I suggest trying Root Genius 2.0.1.3 from my first post )
2, install busybox (I suggest BusyBox ( Stericson ) as I couldn't get this to work with the Jrummy BusyBox installer )
3, Install Rom Toolbox Pro ( I know it's payware and I tried other programs, but this is the only one that worked for me. I had already purchased ages ago. The free version may contain the following tools too, but I genuinely don't know )
4, open Scripter from Rom Toolbox pro and click " Mount System R/W "
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
6, Leave Terminal Emulator open, Hit your Home Button
7, then delete the file :system / set_immutable.list with Root Explorer. Other File managers with root access may work, I haven't tried
If you can not delete it, the above steps haven't worked, I can only suggest you try from step 4 after rebooting your phone.
If you are successful and manage to delete the set_immutable.list file then reboot your phone.
Job Done !
You now have full Root Access.
This has been tested by myself on my MT2-L05, it should work on ALL China Variants and presumably on the US MT2-L03 if this file is included in a 4.4.2 update, but I obviously cannot guarantee this.
I'm also curious as to whether anyone thinks this has left my phone open to exploits by the deleting this file....? Remember, if I have done something stupid by doing this, then so will you if you follow the above!
All I know is Xposed has installed perfectly after finally being able to edit my build.prop file and Adaway is running like a charm.
Feedback very welcome.
4L0M said:
The Solution :
Snip
5, open Terminal Emulator from Rom Toolbox Pro
Type: su then press enter
Type: mount -o rw, remount / system then press enter
Type: cd system then press enter
Type: chattr -R -i * then press enter
(On step 5 there is a space between remount forward slash and system and also between i and *)
Snip
Click to expand...
Click to collapse
I followed your guide, the part I bolded didn't seem to work for me, but after a few attempts I just kept going with the rest of the guide and I was still able to delete the file at the end of the day Thank you so much! I always felt like the root I had with 4.2 was kind of a pseudo root since I was limited by my root access, this is exactly what I needed!
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
4L0M said:
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
I haven't tried too many xposed apps yet, but wanam works if you want circle battery etc
Experimental features of Greenify work too.
Gravity box Kitkat will not run properly for me.. I suggest you do not attempt to install it at the moment.
Let me know if you find anymore cool xposed modules to try!
Click to expand...
Click to collapse
Thanks dude. Btw does your device support Google search by swiping up from home?
scpion said:
I manage to get root and delete that file. Hooray and thanks! But after editing the build.prop, I still can't get xposed to install. I keep getting this error on the install screen.
Click to expand...
Click to collapse
Same issue for me
janrck said:
Same issue for me
Click to expand...
Click to collapse
Install xposed 2.5.1, it's the safest option for now and you will not get this error message.
Cool xposed apps for 2.5.1 :
wanam kit : adds circle battery, expanded notifications, 4-way reboot menu etc etc
Android L Navbar : adds Android L navbar and Android L shapes Navbar
Both work flawlessly for me and have NEVER crashed once.
Hi, I followed your steps but in the step 5, when i type this : mount -o rw, remount / system it doesnt work.
4L0M said:
DISCLAIMER : You attempt the following at your own risk !
Nothing worked ! Vroot, Kingoroot, Towelroot, srs root, root genius 1.8.7, etc they all failed.
I was at the point of giving up, when I found a Chinese version of rootgenius 2.0.1.3......I ran it via pc........and Success ! I was finally rooted.
Supersu was installed, the binaries updated fine
I then tried to install adaway, and then I ran into problems, I was unable to edit my hosts file....ummm...odd. OK, then I tried to install xposed......Impossible to install.
Click to expand...
Click to collapse
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
magicpromise said:
I then read on these forums to edit build.prop and change a simple setting to get xposed running.......ok, no problem, yet when I edited my build.prop file, it would NEVER EVER save the edits. Weird? what's going on?.......after much searching and much reading I finally found the problem.................
/QUOTE]
How was SU installed if you had no rw privs?
vroot, kingroot, kingoroot, kinguser, srs root and rootgenius were created for a select few... it was a side effect of massive social engineering via the internet that they'd leak to so many others who weren't the target.
Click to expand...
Click to collapse
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
4L0M said:
I'm guessing because I could write rw to system folder. Set-immutable-list blocks folders inside system folder, not the basic system folder itself. ie/ system/xbin or system/etc they are blocked. /system on its own isn't.
Click to expand...
Click to collapse
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
magicpromise said:
yes, and the instructions worked great.
i made a script with it in totalrom and set it to load on boot along with total rom itself to keep a strangle hold on the permissions.
Click to expand...
Click to collapse
Can you please upload the script you made?
You'll make things easy for me, 'cause commands in terminal don't seem to work in my case.
Thank's !
After searching a guide about this on internet for weeks (without any result), i decided to post my own guide about Permanently Rooting a L9 II mounting KitKat (it also include two little scripts made by me, to simplify the process to newbies) :good:
Code:
[COLOR="DarkRed"]DISCLAIMER: I DONT TAKE ANY RESPONSABILITY FOR ANY DAMAGE DONE TO YOUR PHONE[/COLOR]
P.S: You need ADB to be installed on your Computer.
1)Install TowelRoot (go to TowelRoot website with the L9 II and press the red Lamba, it will start the tr.apk download)
2)Open the "TowelRoot" application and press "make it Ra1n"
3)Install "Super User" and "Total Commander" from PlayStore
4)Enable "USB DEBUG" in "Developement" setting's
7)Download "init.engdo.post_boot1.sh" and place it in C:
6)Download and open Permanent_D605_KK_Root_Part1.bat
7)Open "Total Commander" , go into /system/etc/ , delete the original "init.engdo.post_boot.sh" and rename "init.engdo.post_boot1.sh" to "init.engdo.post_boot.sh"
8)Download and open Permanent_D605_KK_Root_Part2.bat
9)Enjoy
If anybody will ask for it, i'll upload a standalone .exe to do all this
P.S: I'm kinda new to XDA and English is not my motherlanguage, sorry about any mistake i could've made
Erorr
CursedCake said:
After searching a guide about this on internet for weeks (without any result), i decided to post my own guide about Permanently Rooting a L9 II mounting KitKat (it also include two little scripts made by me, to simplify the process to newbies) :good:
Code:
[COLOR="DarkRed"]DISCLAIMER: I DONT TAKE ANY RESPONSABILITY FOR ANY DAMAGE DONE TO YOUR PHONE[/COLOR]
P.S: You need ADB to be installed on your Computer.
1)Install TowelRoot (go to TowelRoot website with the L9 II and press the red Lamba, it will start the tr.apk download)
2)Open the "TowelRoot" application and press "make it Ra1n"
3)Install "Super User" and "Total Commander" from PlayStore
4)Enable "USB DEBUG" in "Developement" setting's
7)Download "init.engdo.post_boot1.sh" and place it in C:
6)Download and open Permanent_D605_KK_Root_Part1.bat
7)Open "Total Commander" , go into /system/etc/ , delete the original "init.engdo.post_boot.sh" and rename "init.engdo.post_boot1.sh" to "init.engdo.post_boot.sh"
8)Download and open Permanent_D605_KK_Root_Part2.bat
9)Enjoy
If anybody will ask for it, i'll upload a standalone .exe to do all this
P.S: I'm kinda new to XDA and English is not my motherlanguage, sorry about any mistake i could've made
Click to expand...
Click to collapse
When i try to push file init.engdo.post_boot1.sh with root_part1.bat CMD says: remount failed: Permission denied or failed to copy C:/init.engdo.post.boot1.sh to /system/etc//init.engdo.post_boot1.sh : read-only file system
Much easier instruction.
Most of the instruction in the first post is unnecessary.
1) you do NOT need any computer at all
2) no USB debug needed (because you do not need a computer)
3) two .bat files are also unnecessary to download
All you have to do is to replace init.engdo.post_boot.sh file, which resides in /system/etc
You DO need:
1) towelroot installed
2) a file manager with root capability (I used Root Explorer for example)
Instruction:
1) download the init.engdo.post_boot1.sh, using the link in the first post- download it to your phone SD
2) open the file manager with root permissions enabled, /system/etc must be accsessible for read/write
3) copy init.engdo.post_boot1.sh to /system/etc (using the file manager running on your phone)
4) delete init.engdo.post_boot.sh in /system/etc
5) rename init.engdo.post_boot1.sh that you copied to /system/etc to init.engdo.post_boot.sh
6) reboot
All this is great! But, you forgot one important thing:
TOWELROOT does not work on version 20D (which is increasingly represented)
But here you have an explanation for v20D so who wants to try:
http://forum.xda-developers.com/opt...4-4-2-v20a-t2964723/post57308650#post57308650
forgetting...
I did not know the 20D issue so I also could not have forgotten it.
Thanks for info. I just checked, indeed, I have 20A. Towelroot and the permanent root trick work in my case.
Thanks for the feedbacks
I know it can be done more easily using a file manager on the phone, but i tried to make the process easier for newbies (I'm still a newbie too, i did it for myself because i was lazy, but i decided to post it , hoping to help someone )
All this is great! But, you forgot one important thing:
TOWELROOT does not work on version 20D (which is increasingly represented)
But here you have an explanation for v20D so who wants to try:
http://forum.xda-developers.com/opti...0#post57308650
Click to expand...
Click to collapse
Thanks koxyman88, i didn't know about that
When i try to push file init.engdo.post_boot1.sh with root_part1.bat CMD says: remount failed: Permission denied or failed to copy C:/init.engdo.post.boot1.sh to /system/etc//init.engdo.post_boot1.sh : read-only file system
Click to expand...
Click to collapse
Mmmm strange, are you sure you have SuperSU installed, and TowelRoot started before restarting? (TowelRoot's Root disappear after reboot, and so SuperSu binaries)
the question is ... WHY?
I want to point out that I did permanently root my D605 with KitKat. Took a bit of effort but actually it was wasted time.
I did finally go back to 4.1.2 software, rooted it, installed TWRP and then Varcain's modified Cyanogen 11. It is so much nicer than rooted stock 4.4.2. All the efforts of rooting Kitkat and keeping the root were unnecessary exercise.
Because the Varcain's image does not have any bloatware I could even switch from Dalvik to ART and still have enough free space on phone.
Hello,
I have been searching forum for the information, but most of it looks to be outdated.
Is there any way to to root my LG L9 II (D605) with 4.4.2 Android version? How can I install CWM afterwards?
deiivis said:
Hello,
I have been searching forum for the information, but most of it looks to be outdated.
Is there any way to to root my LG L9 II (D605) with 4.4.2 Android version? How can I install CWM afterwards?
Click to expand...
Click to collapse
works on v20a and v20b
on phone enter in towelroot . com
click on lambda
download and install apk
download rom toolbox lite from google play
run towelroot and click "make it rain"
copy attached files (root v2a) to sdcard
run toolbox, click "root browser" and copy attached files do cache (/cache)
quit from root browser to basic toolbox menu and click "rebooter" then "reboot recovery"
click "apply update from cache" and pick root v2a
if ur phone will fail binaries update install v2b by the same methode
~~~~CWM~~~~
d-h . st/2kk
download
extract and put files in sdcard
open toolbox and click root browser
copy files (aboot.img, loki_flash, recovey.img) to /data/local/tmp
exit to toolbox menu and click terminal emulator
Code:
su
dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
cd /data/local/tmp
chmod 777 loki_flash
./loki_flash recovery recovery.img
reboot recovery
Mine is 20d, towelroot displays error message that my phone is not supported. I don't know what to do, all .kdz links are not working to downgrade it.
deiivis said:
Mine is 20d, towelroot displays error message that my phone is not supported. I don't know what to do, all .kdz links are not working to downgrade it.
Click to expand...
Click to collapse
Well towelroot (the futex.c) exploit got patched at most kernels and systems built after 3rd of June or July ( I can't remember the date exactly). Go on: http://lg-phone-firmware.com/
If they are not working from there send me your IMEI (on private of course; will remain private and will not be used in any bad scoper ofc) and then version you would like. Peace out.
Neutron
http://forum.xda-developers.com/opt...ot-l9-d605-stock-recovery-4-4-2-v20a-t2964723
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.