I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the attached .zip file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary
Apache14 said:
I have just edited the AnyKernel updater script by koush to work with eMMC devices :-D
hope ppl can make use of this
its very simple
1) grab the .tar.gz file
2) extract
3) add the zImage to the /kernel/ directory
4) add .ko modules to /system/lib/modules/ directory
5) **optional** change the boot partition location in the updater-script (not normaly needed)
6) zip up the file
7) its ready to flash in CWM
Credits
Koush for the original boot unpack / repack bin's and scripts
IEF for the stand alone dd binary
Click to expand...
Click to collapse
When you say grab the .tar.gz file, your referring to the file attached correct?
Just making sure I have everything clear before I use this.
Thanks! Great work!!
BAh yep thats a typo lol the .zip file
Apache14 said:
BAh yep thats a typo lol the .zip file
Click to expand...
Click to collapse
Thanks! I figured it was.
Here are some flashable zips that I created oringinally for myself and my sister, but I decided to share this so that people that want an easy way to root can have their wish fulfilled.
NOTE: This zip isn't compatible with all devices due to update-binary being quite device-specific! Should definitely work on Galaxy Ace or Wildfire S though!
These zips contain the latest busybox and SuperSU as of 01.08.2013, so if it gets updated, these zips WILL be outdated.
Just flash these zips from any custom recovery and you will be rooted. It has been whole-signed, so it should be able to pass any custom recoveries' zip file signature verification.
I would try my best to update these zips if possible, so please don't be annoyed if the zips get outdated!
Credits:
[email protected] for his busybox installer & busybox binary
[email protected] for his Superuser apps and su binaries
All testers and suggestion-ers
I sincerely apologize if I left any of you out in the credits section. I am truely sorry.
Arrangement of attachments:
1st: Root_SuperSU.1.44-Busybox.1.21.1_in_xbin-signed.zip
This flashable zip installs busybox in /system/xbin
2nd: Root_with_SuperSU_&_Busybox_in_bin-signed.zip
This flashable zip installs busybox in /system/bin
@haoyangw Update to the latest version pls.
My z3 is D6653, I have root, backed up TA partiition, unlocked bootloader and installed TWRP v2.4.8.0. I downloaded CM12 nightly on Feb 17th on download.cyanogenmod.org and copied it along with Google App to my SD card. When I came to recovery mode, after whippìg data, cache, things went wrong. I tried to install cm12 nightly on zip file multiple times but all failed. The error message said "this ROM is for D6603, D6633, your device is leo" and "error executing updater binary". My D6653 Z3 is recognized as "leo" which means that it is different from "z3" listed on cyanogenmod home page. What can I do now to have Cm12 on my z3?
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Omario-242 said:
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Click to expand...
Click to collapse
Which files do I need to edit? Do I just replace "z3" with "leo"?
Ariana Grande said:
Which files do I need to edit? Do I just replace "z3" with "leo"?
Click to expand...
Click to collapse
Only the updater binary which is located in the ROM zip.
Yes just replace the " z3".
Omario-242 said:
Only the updater binary which is located in the ROM zip.
Yes just replace the " z3".
Click to expand...
Click to collapse
Omario-242 said:
This updater error is caused by the updater binary. Just open the zip on your PC, open the updater binary script and change the line where it says "z3" to leo". Cyanogen should be aware of that, but I think they are not changing it, as there is another device called "leo" from another manufacturer.
You could also get another ROM zip and copy the updater binary script from it to the CM12 one and repack it.
Click to expand...
Click to collapse
this would be so much easy if there is a way to open this updater binary with notepad++ without an error .. any help there?
It should work just well with Notepad++. What error do you get when trying to open it?
There seems to be a lot of issues regarding the systemless root method. Here is some help/basic info.
Prerequisite:
1. Bootloader must be unlocked
2. Must have TWRP recovery installed
How to systemless root:
1. Download SuperSU v2.61 or SuperSU v2.62-3. Both work, I use the v2.62-3.
2. Flash either in TWRP recovery. Reboot to system. You now have systemless root.
Problems/Fixes:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
2. One of your favorite root apps doesn't see that your rooted? Do THIS.
I update super su from the playstore without issues.
kadopt said:
I update super su from the playstore without issues.
Click to expand...
Click to collapse
Could you explain your process? I tried updating from the 2.61 and had issues.
gokart2 said:
Could you explain your process? I tried updating from the 2.61 and had issues.
Click to expand...
Click to collapse
Well, to get root (systemless) you flash super su 2.62-3 with twrp, then go to playstore and update super su app, open Super su and a pop up will indicate that your binaries need updating, press OK and wait until it's complete, then just reboot your device.
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
gokart2 said:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
Click to expand...
Click to collapse
Where can one find this magical "How to systemless root" list of safe-to-flash systemless SuperSU?
And I assume only the BETA versions are systemless? I have tried flashing the latest STABLE v2.76 and it just stuck on boot.
The SuperSU v2.62-3 that you mentioned does work but just want to find the latest version to flash.
jason2678 said:
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
Click to expand...
Click to collapse
Adding the single line text file to /data worked for me to root stock 1575 18-4 with the latest Supersu 2.76 stable.
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
The systemless file contains the following:
SYSTEMLESS=true
BINDSYSTEMXBIN=false
Click to expand...
Click to collapse
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
Click to expand...
Click to collapse
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
csrow said:
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
Click to expand...
Click to collapse
Yeah I'm hoping this will make it easier for those who are flashing SuperSU and ending up with an un-bootable phone due to the installer defaulting to system root in newer versions.
I've removed the permission script since I had no idea 2.76 now applies it. Thanks for the heads up!
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
Click to expand...
Click to collapse
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Edvin73 said:
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Click to expand...
Click to collapse
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Spasticdroid said:
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Click to expand...
Click to collapse
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Ijspegel said:
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have updated the zip to fix this and it will now find and flash it.
Spasticdroid said:
Yes, I have updated the zip to fix this and it will now find and flash it.
Click to expand...
Click to collapse
Thank you for your work on this one, it is very helpfull!?
Sent from my XT1572 using XDA-Developers mobile app
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
Thanks man, your script was the only thing that worked for me, but now wifi isn't working. what can I do?
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
OMG THANK YOU
I had accidentally installed the wrong SU and i thought I would have to wipe my entire device after hours of trying different methods. Yours was the only one that worked and my phone booted back on. Thank you so much.
Taking a risk of sounding stupid, will your SystemLess Root work for Android 7.0 Nougat?
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
phillyguy /northeast said:
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
Click to expand...
Click to collapse
Didn't we fix this in another thread?!?!
Hi, I have an android device with a custom recovery, I also have the ROM package and I can flash the system directory using the recovery, and I can modify the contents of the ROM package and then flash it, I want to add to this ROM GApps, I've downloaded the GApps package,
It has the folder /system and META-INF that includes the installation script updater-script.sh, The ROM package also have updater-script.sh.
1. Is if it possible to install GApps on to this ROM by copying the contents of updater-script.sh of GApps into the updater-script.sh of the ROM package and copying the contents of /system of GApps to /system of the ROM package?
2. Should I be worried about ROM's META-INT signature files? (CERT.RSA,CERT.SF,MANIFEST.MF)
Thanks.
Hi, I have a device with custom recovery that can update ROM using update files, I got a working update file (zip contains system/ and META-INT/), When I'm unzipping it, add files to it and zip it again then flashing it, I get update failed, I even get update failed when I'm just unzipping and zipping without adding files or touching the content in the zip. Does anyone know why it might happen?
Thanks.