Marshmallow root has been much more difficult than simply flash a zip in recovery, because it also requires a modified boot image to work.
I've done all the work for you, this root is achieved with SELinux enforced using Chainfire's method.
The original RUU/Stock rom is here.
In this post you can find the followings:
Aroma Stock Rom
Root Info
GPE Marshmallow on All Models
Disable S-ON System Write Protection
Sweep to sleep module
FAQ
Aroma Stock Rom (All models support with selectable root)
Simplest way to dive in GPE Marshmallow, the installer will guide you to the right direction.
If you want root, take a look at the next section for some info about root methods.
Choose your model in the installer, it also includes proper support for Sprint and Verizon device,
This will NOT convert your device into GPE!! It only flashes a rom.
Aroma Version Stock GPE
Mega Link
Important!! If you choose systemless root, please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in boot loop.
Root Info
In Marshmallow, Chainfire gave us with two rooting methods include:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
If you already downloaded the GPE Marshmallow stock rom and you want root, this is where you'd be interested with.
(Non-GSM device should now jump to next section)
Choose your preferred root method above, and follow the correspond instructions below.
Instructions:
Traditional:
Flash m8-mmgpe-su-boot.zip in attachment with TWRP
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the traditional one above), if you've rooted with other methods, please re-flash your system back to pure stock
Flash m8-mmgpe-su-boot-systemless.zip in attachment with TWRP
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in bootloop.
GPE Marshmallow on All Models
Not an International/GSM device and still want some Marshmallow love? This is where you'd be interested with.
Simplest way is flash the pre-packed rom above, but if you already downloaded the stock rom and don't want to re-download, then look below.
GPE MM on all models is possible because it uses the Sense all-model dtb image, thanks to sun_dream for his work!!
Choose your preferred root method above, and follow the correspond instructions below.
Instructions:
Traditional:
Flash m8_AIO-mmgpe-su-boot.zip in attachment with TWRP
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the traditional one above), if you've rooted with other methods, please re-flash your system back to pure stock
Flash m8_AIO-mmgpe-su-boot-systemless.zip in attachment with TWRP
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP, because TWRP isn't updated to detect this new method. If you choose to install SuperSU within TWRP you'll get stuck in bootloop.
Disable S-ON System Write Protection
After you rooted, you might find out that your system partition is locked up, this is because of HTC's system write protection on S-ON devices, and here is a handy mod for you to bypass it. Original mod by flar2, I modified it to work on MM GPE.
Instructions:
You have to use the traditional root method above to make this work!!
Flash m8-mmgpe-wp_mod.zip in attachment
Sweep to Sleep module
A handy mod to turn of the screen by swiping the bottom of the screen. Original mod by flar2, I modified it to work on MM GPE.
Instructions:
This will flash files to system, there is no point in using systemless method, it ot should be OK
Flash m8-mmgpe-s2s_mod.zip in attachment
FAQ
Q: After choosing full wipe, my contents in internal storage are all gone!!
A: No, it's not. It's a new behavior of Marshmallow. After each clean flash, it will move all previous files in /sdcard into /sdcard/0. You can just move them back to the proper locations.
Q: I cannot install Busybox in system / I cannot use adaway !!
A: Flash wp_mod.
Q: I used systemless root and wanted to keep my system partition intact, how do I install Busybox?
A: Download Busybox Pro, type /su/bin as the installation path for busybox. You cannot do it using the free version, unfortunately.
Q: **** app cannot access external SDcard!!
A: Look at this explanation:
Since Kitkat(2 years ago man), we don't have direct external storage write permission. Google consider it insecure, so they implemented this feature. The reason why you can access external SDcard easily before is because most roms on XDA already contains a hack in /system/etc/permissions/platform.xml. You should not rely on this hack forever, please take a look below.
In lollipop and after, Google provided a much secure and better way to grant external storage access to third party apps, first of all take a look at this article for details:
http://www.androidpolice.com/2014/1...s-automatic-mediastore-and-improves-security/
So instead of using the old platform.xml hack in the old Kitkat days, adopt yourself with this new behavior of Android!! If a certain app cannot access SDcard, ASK THE DEVELOPER to add support for this API!!
Many apps already have support for this API. I'll take Titanium Backup for example, as lots of you cannot find the way to use it on externals SD. In Menu>>Preferences>>Backup Location, you can choose Document Provider on top of the detect button.
In the provider, open the menu on the top right corner and select "Show SDcard", then you'll see External Storage in the left side. Select external SDcard in the document provider and press the button on the bottom, the app will then be granted access to the whole external storage. You can then create a new folder in TiBack and select it as your backup location.
Other apps also follows the instructions above, you just have to manually set up the folder where the app can access, in the case which most of us would love to give access to the whole SDcard, I set the location to the root of external storage. Each app has independent permission, so you have to manually grant each app you wish to access external storage.
Q: I want OTA, what should I do?
A: Look at the following info
To accept OTA updates, you need the following:
Your MID should be 0P6B17000
Your CID should be GOOGL001
You have to fully convert to GPE
You have to keep system partition untouched
You have to have GPE stock recovery
So before anything, if you want to accept OTA, you have to change MID, CID, and convert to GPE. The tricky part is the system partition and the recovery. The easiest way is when the OTA comes, flash the stock rom again without root, flash GPE stock recovery through fastboot, then apply OTA. But if you like to go the hardcore way, here comes a tutorial:
fastboot flash systemless_boot.img
fastboot boot TWRP.img(so that you can use TWRP but you didn't actually flash it)
Flash systemless SuperSU
By doing so you can accept OTA at anytime.
Q: Are there any mods around?
A: Because of the difficulty of file based flashing, modded GPE MM might take a while to appear.
You can use Xposed Framework, as it now officially support Marshmallow.
http://forum.xda-developers.com/showthread.php?t=3034811
Credits:
@Chainfire for the new root methods and SuperSU
@flar2 for wp_mod.ko and s2s_mod.ko
@enewman17 for original RUU
@sun_dream for the all models dtb image
@whaevr for porting to Verizon
@Captain_Throwback for porting to Sprint
{
"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"
}
Does this mean it will boot with a warning message?
Edit: My post was in response to the very first version of pre systemless Root for M8 GPE 6.0 .. But the Dev was fast in updating
Noonski said:
Does this mean it will boot with a warning message?
Click to expand...
Click to collapse
no message - just root like normal.
Requires s-off?
Updated thread with systemless root.
Noonski said:
Does this mean it will boot with a warning message?
Click to expand...
Click to collapse
No warning message.
popoyaya said:
Requires s-off?
Click to expand...
Click to collapse
S-ON is OK
Have you encounter any issue with systemless root?
Thanks
Could anyone check if they have HTC's motion launch working with this?
isx said:
Could anyone check if they have HTC's motion launch working with this?
Click to expand...
Click to collapse
I have all of them working... Swipe to unlock is disabled by default though.
nhoc_maruko9x said:
I have all of them working... Swipe to unlock is disabled by default though.
Click to expand...
Click to collapse
EDIT after a TWRP restore and re-flash its all working well.
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
tominozh said:
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Nope, mine still works. I think you've got to go to storage and configure your sd card as removable storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
tominozh said:
Anybody lost ex-sd card after using the traditional method?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
@topjohnwu the mod doesnt seem to be working.. v4a still keeps asking for drivers..
n1234d said:
Nope, mine still works. I think you've got to go to storage and configure your sd card as removable storage.
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
@topjohnwu the mod doesnt seem to be working.. v4a still keeps asking for drivers..
Click to expand...
Click to collapse
Try copy a random file to system (or remove an system app you don't like) using root explorer and reboot and see if it sticks. I haven't used v4a for years, and I'm not sure if it is something about selinux or other possible reasons.
Also I'm not sure if the su.d script is executing correctly(because stock rom lack init.d support I tried su.d), try this also:
First reboot the device, before doing any modifications to system open terminal on the phone and type:
su
insmod /system/lib/modules/wp_mod.ko
then do the system modification tests.
Thanks a lot!!
topjohnwu said:
Try copy a random file to system (or remove an system app you don't like) using root explorer and reboot and see if it sticks. I haven't used v4a for years, and I'm not sure if it is something about selinux or other possible reasons.
Also I'm not sure if the su.d script is executing correctly(because stock rom lack init.d support I tried su.d), try this also:
First reboot the device, before doing any modifications to system open terminal on the phone and type:
su
insmod /system/lib/modules/wp_mod.ko
then do the system modification tests.
Thanks a lot!!
Click to expand...
Click to collapse
My bad, it does indeed work!! Adaway works, and so does deleting system apps! Thanks a lot
n1234d said:
My bad, it does indeed work!! Adaway works, and so does deleting system apps! Thanks a lot
Click to expand...
Click to collapse
Thanks for the confirmation.
Doing thing blindly without testing is always a challenge
I am loosing htc gestures like double tap to wake after sometime
Have to disable and then re enable it to get it working
Just posting to say that the Systemless Root method worked great for me. Able to successfully modify /System files and folders (verified changes were still there after reboot), restored some apps, Messages, and Call Log using Titanium, and Android Pay is still working after rooting.
Thanks JW!
Is there any way to flash TWRP without PC if you don't have root...??
Well, whatever I try, V4A keeps asking for drivers. I have selinux permissive (selinux mode changer app) and flashed the wp_mod from here. Adaway and other changes to the system partition stick. Any ideas?
Updated post with pre-rooted with aroma installer rom.
gauravbhawsar said:
Is there any way to flash TWRP without PC if you don't have root...??
Click to expand...
Click to collapse
Flashify. Play store.
Or, I have one you can just put on SD card and rename 0p6bimg. It's 2.8.7.0
Related
[06 Sept 2012][ICS]Universal Rooting for most ICS phones, Any ROM, now with CWM6
See original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
For questions, feedback and support, please do not post here, but in original thread
Root your ICS phone S2 + Samsung + not Samsung phones - No more waiting for custom kernels
This topic provides universal root methods to bypass the use of custom kernels. I took the time to write it as I was tired from waiting for a Dev to publish a custom kernel for the last firmware released.
I will try here to reference most threads and ways to root your phone. Some methods will let you root as soon as you get the new ROM, no more waiting for some dev to release a kernel for you.
I will not list here custom kernels that come with root, you can find them in other threads.
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM
Method 1 - Recommended
Push superuser + Busybox (Now v1.20.2 from Linus Yang) in recovery
{
"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"
}
Now, on the i9100 and some other phones (N7000...), you can flash the attached signed zip files in stock recovery, no more need to CWM.
A BIG BIG THANK YOU TO Chainfire for his support that made it possible and to Entropy512 who pushed me to look for a fix
Attached is the CWM Recovery 4.x non touch version, confirmed safe for wiping. It will not superbrick your phone
>>>>>> Now it is even getting greater with attached Clockworkmod v6.0.1.2 !!!! <<<<<<
>>>>>> Also probably safe from brickbug <<<<<<
Pros
Universal and will probably work on any ICS phone, if you have a CWM image. No longer wait for a modded kernel
On the i9100 and some other phones (N7000...), you can now even root from the stock recovery, no need to the cwm image
No PC needed, only an android device and the zip files that you download to your sd card
Fully reversible unroot without PC needed
No Yellow Triangle (Only for phones with a zip CWM image)
No custom counter increased (Only for phones with a zip CWM image)
Only copies superuser +/- busybox, nothing else is touched, neither /data nor the kernel
No brick risk while flashing cwm even if things go wrong as it will be always overwritten by stock recovery after a reboot
Click to expand...
Click to collapse
Cons
None since I switched to the CWM4 and CWM6 recoveries (no more superbrick risks under 4.0.4 ICS kernels, only CWM5.x was affected)
Click to expand...
Click to collapse
Special notes about busybox
The zip files attached in this post install busybox only in /system/xbin. I do not put any symlink in /system/bin
If you previously installed other versions of busybox, I advise to run Busybox Uninstaller v1.0 zip in the thread dedicated to it here: http://forum.xda-developers.com/showthread.php?t=1853419
It will clean any orphan symlink that could be left from a previous install. After that, install busybox from any of the attached files in this post
The uninstaller in this post, only removes busybox package from /system/xbin. I do not delete any package put in bin, as it is assumed it was put there by another program, not my script. It will not remove any symlink either. So, run the Busybox Uninstaller v1.0 for that
Click to expand...
Click to collapse
This method was first inspired from Rachmat3 thread here and Chainfire script here (do not forget to thank them). I modified it to work in stock recovery, enhanced script, include Chainfire superSU last version + BusyBox last binary. I also keep a ChainsDD superuser version.
Instructions
For phones affected by the superbrick bug (i9100, N7000) and that has a stock recovery accepting update.zip files (most phones with a temporary cwm.zip file at Clockworkmod site:
You can flash the attached files directly in stock recovery 3e, no need to cwm:
Download the root file:
- Root_SuperSU.0.96.Only-signed.zip for Chainfire SuperSU (the one that comes with CF_Root) without busybox.- Root_SuperSU.0.96-FreeSpace.zip for Chainfire SuperSU without busybox (use only if you have issues with previous one, usually for phones having a /system partition with 0 free space).- Root_SuperSU.0.96-Busybox.1.20.2-S2-signed.zip to install superSU + busybox v1.20.2 from Linus Yang.- Root_Superuser_3.1.3_Busybox_1.20.2-Update1-signed.zip if you prefer the classic ChainsDD superuser + Busybox from Linus Yang.- Root_Busybox_1.20.2_Only_XXX.zip to install only Busybox from Linus Yang.
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
.
Copy the Root_XXX.zip file you downloaded to externalsd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the Root_XXX.zip file downloaded above and you are rooted
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
To get temporary cwm (to make nandroid backups...) or if stock recovery gives you a signature error, follow the next more universal steps.
Click to expand...
Click to collapse
.
.
For most (if not all?) ICS phones having a CWM image at Clockworkmod site:
Download attached cwm-touch-6.0.x.x-i9100.zip for the i9100 Galaxy S2. This is the touch version but it also works with volume up/down keys and power button to select menu.
CWM6 is now thought to be probably safe for wipe, no superbrick risks under ICS 4.0.4: read more here
I also attached the cwm6 non touch version and the recovery-clockwork-4.0.1.5-galaxys2.zip. CWM4 is also confirmed to be safe for wipe by Entropy512 Recognized Developer
For other phones, download the cwm image from here http://clockworkmod.com/rommanager
.
Put the previously downloaded cwm-touch-6.0.x.x-i9100.zip file on your external sd card
Download the attached root file you want as per instructions above
I advise Chainfire SuperSU for 2 reasons: it lets you unroot from within superSU application and it lets you migrate to ChainsDD superuser if you like later
Copy the Root_XXX.zip file you downloaded to internal or external sd card
Boot into stock recovery (volume up+home+power), and select "apply update from external storage". Now select the cwm-touch-6.x.x.x-i9100.zip file you copied in previous step (this step gives a temporary flash that will disappear after reboot)
You get CWM recovery interface (this custom recovery is temporary, not permanent)
Inside CWM, select "install zip from sdcard". Then, select "choose zip from sdcard". Now, scroll down to the "Root_XXX.zip" file and hit power button to install it.
It will add SuperSU or Superuser last version apk to system/app, last superuser binary (su) to system/xbin and busybox last version to system/xbin, all with correct file permissions.
Reboot and you get permanent root + busybox installed on your stock kernel.
To unroot, do the above steps and replace the file Root_XXX.zip by the attached Unroot_SuperUser-Busybox-Uninstaller-Update2-signed.zip. It will delete superuser, su and busybox packages.
For a complete removal of busybox, look here at my Busybox Uninstaller which will remove ALL busybox symlinks (over 600 files depending on installers used before):
http://forum.xda-developers.com/showthread.php?t=1853419
Click to expand...
Click to collapse
Fix common issues: You end with both ChainsDD and Chainfire superuser and SuperSU
Also another symptom is having constantly superuser asking for updates from market.
Some people are getting duplicates from previous root methods using ChainsDD superuser instead of Chainfire superSU or vice versa when they come from SuperSU and switch to superuser.
Also, this can happen when you updated let's say to a future Chainfire SuperSU v1.0 and later you use one of my outdated scripts (with version 0.94 for example).
The cause is that I do not delete anything from /data/app. I can add it, it is not an issue, but till these brick things are fixed, I chose not to do it.
The solution is very easy:
Just uninstall from stock application manager all superuser applications. The /system/app application will stay as system applications cannot be removed normally in application manager
After that, just update your superuser application from market. Updates are put in /data/app and original copy will stay in /system/app.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Important notice for people that downloaded previous non touch versions 6.0.1.3 and 6.0.1.4 from post 1
20 Sep 2012: Update non touch version to 6.0.1.4 ** Recommanded Update from previous 6.0.1.4 attached here **
Now, CWM6 is built from source to fix possible issues related to previous dynamically linked binary
Big big thanks to Tallustus from Team SkyFire for the support
Click to expand...
Click to collapse
People using my previous non touch versions 6.0.1.3 and 6.0.1.4 are strongly advised to move to this updated 6.0.1.4
Previous version was not a static binary and could behave unexpectedly under some circumstances
Actual 6.0.1.2 touch and non touch are fine to use
I removed previous 6.0.1.3 and 6.0.1.4 files to avoid confusion
Original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
THIS IS AN OLD OBSOLETE TOOL. CLICK HERE TO GET THE NEW IMPROVED ONE!
{
"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"
}
FEATURES
Rickys Rom Kitchen Features(BETA2):
Build updater-script
Set up working from backup imgs (doesnt always work)
Add my theming system
Check for boot.img
Check for theming system
Ability to add license for aroma
Push to device and flash with ORS
Split boot.img
Rebuild boot.img from kernel and ramdisk
Setup project from phone
Setup project from .zip
Ability to modify .zips
Saves project and project settings
Open working folder
Add busybox
Install curl and openssl
Deodex
Zipalign
Build.prop options
Install aroma
Configure aroma
Open most recent build
Remove current project and files
Add lines to build.prop
Automatically adds project name to build.prop
Automatically adds project name to aroma-config
Build PROJECTNAME
Configure preinstalled aroma
Sign PROJECTNAME
TOOL FEATURES FOR All Other Phones:
Deodex rom
Odex rom
Port rom(very early beta)
Get device information
Install Curl
Install OpenSSL
Install Busybox
Hot Reboot
Compress Backup
Integrated Lcd Density Changer
Fixes Permissions
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
Enable root permissions
Flash any .zip file
Flash a rom
Create a coloured logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Reboot options
Advanced wipe Options
Pulls Files From Server
Manual Adb And Fastboot
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Fix Low battery error
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
TOOL FEATURES FOR HTC Sensation XL:
Deodex rom
Odex rom
Port rom(very early beta)
Get device information
Install Curl
Install OpenSSL
Install Busybox
Hot Reboot
Compress Backup
Integrated Lcd Density Changer
Fixes Permissions
Show oem token code
Flash oem token
Flash recoveries
Flash recovery themes
My GraffStyleZ TWRP Theme Included
S-Off
Enable root permissions
Force Update
Flash any .zip file
Flash a rom
Create a logcat
Show CID
Write superCID
Backup device
Restore device
Relock bootloader
Flash custom radio
Fix sdcard errors
Reboot options
Fix low battery error
Advanced wipe Options
Pulls Files From Server
Manual Adb And Fastboot
Wipe Data
Wipe Cache
Wipe System
Wipe Dalvik Cache
Wipe Android Secure
Wipe Recovery
Wipe Boot img
Wipe Data,Cache
Wipe Data,Cache,System,Dalvik
Automatically Kills adb Upon Completion Of Task
Unlock bootloader guide
Install custom recovery guide
Install recovery theme guide
Enable root permissions guide
Install roms or .zip files guide
Restore device to defaults guide
DOWNLOAD
Download The .EXE (Installation Package) From D-h.st(Dev host)
Download The .ISO (Disk Image)From d-h.st(Dev host)
Click to expand...
Click to collapse
Installation For .EXE
1. download and install java and notepad++(optional but reccomended)
2. Open AETv7.5.exe
3. Follow Prompts
4. Enjoy
Installation For .ISO
1. download and install java and notepad++(optional but reccomended)
2. Right click on AETv7.5.iso
3. Click "burn disk image"
4. Burn it to a disk
5. Insert disk and it will run installation
-NOTE-
This tool is to be used at your own risk, i will not be held responsible for any damages even though none are expected!
This tool voids your warranty!
VERSION 10.0(BETA2)-
Added build updater-script
Set up working from backup imgs (doesnt always work)
Add my theming system
Checks for boot.img
Checks for theming system
Ability to add license for aroma
Push to device and flash with ORS
Split boot.img
Rebuild boot.img from kernel and ramdisk
Partially fixed deodex issue
VERSION 9.0(BETA)-
Made and added Rickys Rom Kitchen(like kitchen for windows)
--kitchen options
Setup project from phone
Setup project from .zip
Ability to modify .zips
Saves project and project settings
Open working folder
Add busybox
Install curl and openssl
Deodex
Zipalign
Build.prop options
Install aroma
Configure aroma
Open most recent build
Remove current project and files
Add lines to build.prop
Automatically adds project name to build.prop
Automatically adds project name to aroma-config
Build PROJECTNAME
Configure preinstalled aroma
Sign PROJECTNAME
--kitchen options
Added developer options
Added deodexing
Added odexing
Added decompile
Added better backup compression
Added port rom option
Fixed menu issue
Minor code fixes
New icon
Added skip backup in installation
CHANGELOGS FOR OLDER RELEASES
VERSION 7.5-
Program wont install unless device is connected
.iso Image (able to burn to disk)
More Lcd density Options
Fixed menu error
Added compress backup to save space
Hot Reboot option added
Ability to install 'BusyBox'
Ability to install 'cuRL' and 'openSSL'
Get Device Info
AET icon
Uninstall-able
VERSION 6.0-
Fixed All Knows Bugs
Integrated Lcd Density Changer
Fix Permissions
VERSION 5.0-
Manual Adb And Fastboot
Pulls files from server
better compression
Smaller file size
Fixed bugs
Updated sources
Semi-Final build
VERSION 4.5-
Added low battery fix
Fixed Big
Fixed 'Choose device' Menu
VERSION 4.0-
Title Change
Fixed sources
Updated adb
Updated AdbWinApi.dll
Updated AdbWinUsbApi.dll
Updated fastboot
Added backup
Added restore
Added super CID
Added colour logcat
Fixed bug
VERSION 3.0-
Fixed all bugs, added advanced wipe options,
automatically kills adb server upon completion of a task
VERSION 2.5-
Fixed allmost all bugs, Added 'GraffStyleZ' TWRP Theme By Me!
VERSION 2-
Support for all HTC Devices and minor bug fixes
VERSION 1-
Initial release[As Alpha], only support for HTC Sensation XL
If You Like This Tool And Want Me To Continue My Learning And Development, Hit The Thanks Or Donate To Me Providing Better Hardware For Better Tools, Roms and Mods!
Credits:
Special-TRoP0niCZ - Teaching me how to create roms, tools, and mods
RunnyCM Team (anders3408, Lexmazter and Zasuk)
Prof Peach
Cybervibin
ChainsDD
And Many Other For Allowing Me To Use There Creations But Unfortunately Were Not Used In My Tool!
XDAevDB Information
Rickys rom kitchen and android everything tool, a universal way to do everything in one package
Contributors
Ricky310711
Version Information
Status: Stable
Current Stable Version: RRK 2.0 AET 10.0
Stable Release Date: 16/10/2013
Created 12/02/2013
Last Updated 16/10/2013
Follow me on Twitter or Facebook to receive news about my developments first!
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Closed Source Project said:
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Click to expand...
Click to collapse
If You Can Link Me To The S-OFF Hboot I Will Modify This Tool For HTC One S! i heard there is facepalm s-off for your device, link me to the thread and ill see what i can do!
Closed Source Project said:
Any chance for S-Off for the HTC One S in here? Or just the Sensation?
Click to expand...
Click to collapse
This won't have S-Off or the better looking AIO Toolkit(sorry) would have it. The dev asked not to do such a thing.
ricky310711 said:
If You Can Link Me To The S-OFF Hboot I Will Modify This Tool For HTC One S! i heard there is facepalm s-off for your device, link me to the thread and ill see what i can do!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2155135 but then
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
Click to expand...
Click to collapse
Darknites said:
This won't have S-Off or the better looking AIO Toolkit(sorry) would have it. The dev asked not to do such a thing.
Click to expand...
Click to collapse
That Explains, i just already pm the facepalm dev to see if i could, i guess ill know the answer then
But if theres any suggestions someone would like me to add to v3 please pm me
cat2115 said:
http://forum.xda-developers.com/showthread.php?t=2155135
Click to expand...
Click to collapse
sorry cat2115: im afraid i cant publish a v3 without permisions to publish with facepalm unless i get permissions!
ricky310711 said:
That Explains, i just already pm the facepalm dev to see if i could, i guess ill know the answer then
But if theres any suggestions someone would like me to add to v3 please pm me
Click to expand...
Click to collapse
Ya I think its a bit lame but guess they just don't want to deal with it or what ever.
Be wary of this... I followed the instructions TO THE T yet I believe this flashed a recovery to my phone that was not from the HoS. I had to Ruu to stock to fix it. Suppose I could have done something wrong... but nonetheless. Also, when I tried doing the recovery it opened my docs... I put the .img in there and then it said I needed to put it in ETv2/prog/zo so I did so and that's when bootloader froze up on me.
Re: [TOOL] HTC Everything Tool!
Fastboot is programmed to execute 'fastboot flash recovery recovery.img' it flashes it the only way you can via pc, although I will look into the problem and see if its on the software side!
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Daiskei said:
Be wary of this... I followed the instructions TO THE T yet I believe this flashed a recovery to my phone that was not from the HoS. I had to Ruu to stock to fix it. Suppose I could have done something wrong... but nonetheless. Also, when I tried doing the recovery it opened my docs... I put the .img in there and then it said I needed to put it in ETv2/prog/zo so I did so and that's when bootloader froze up on me.
Click to expand...
Click to collapse
Uh i think u just got a bad flash. it happens once in a while. Happened to me a few months ago. Had to RUU back to stock before flashing anything cuz fastboot commands wouldn't work. and i do everything by hand. not a fan of tools.
blackhartct said:
Uh i think u just got a bad flash. it happens once in a while. Happened to me a few months ago. Had to RUU back to stock before flashing anything cuz fastboot commands wouldn't work. and i do everything by hand. not a fan of tools.
Click to expand...
Click to collapse
Ive checked over the batch file, there seems to be no problem, i also just flashed twrp on a friends phone and was successfull, maybe it was a bad flash!
ricky310711 said:
Ive checked over the batch file, there seems to be no problem, i also just flashed twrp on a friends phone and was successfull, maybe it was a bad flash!
Click to expand...
Click to collapse
Yeah, that must be it. No worries guys, like I said... I got it back. ^_~ I was just really scared thinking I screwed up the recovery partition or something because flashing the recoveries manually did nothing and when I tried to boot to recovery it would just go to a black screen. At that point I was unsure how to re-lock the phone without the recovery to flash my bootloader lock zip so I tried fastboot oem lock and though it gave me an error I saw that it was now "Relocked" and I was like.. "Oh crap, please RUU back to stock with stock recovery... PLEASE!" XD
Re: [TOOL] HTC Everything Tool!
Well glad it worked, I just flashed twrp recovery and everything went well, although I found minor hugs and fixed them, updating my tool to v2.5
Sent from my HTC Sensation XL with Beats Audio X315e using xda premium
Tool Updated to 3.0
Could you add S-Off support for the HTC ONE S?
lejohn said:
Could you add S-Off support for the HTC ONE S?
Click to expand...
Click to collapse
i am sorry, i wanted to but i do not have permission to publish tool with facepalm sorry
ricky310711 said:
i am sorry, i wanted to but i do not have permission to publish tool with facepalm sorry
Click to expand...
Click to collapse
Sorry to hear that. SuperCID looks a bit complicated. Pushing the files and rooting must be do-able.
Look like I'll have to wait a bit more then.
Thanks for the reply.
lejohn said:
Sorry to hear that. SuperCID looks a bit complicated. Pushing the files and rooting must be do-able.
Look like I'll have to wait a bit more then.
Thanks for the reply.
Click to expand...
Click to collapse
cant you 'fastboot oem writecid 11111111' in cmd or terminal?
ricky310711 said:
cant you 'fastboot oem writecid 11111111' in cmd or terminal?
Click to expand...
Click to collapse
also a write cid option in v3.5 or v4.0
If you are in a ROM slot on safestrap, this may be your lucky day. If you catch the update after it installs, immediately open SafeStrap & install the recovery. Before the reboot, the recovery partition is still writeable & so SafeStrap will install. Once it does, immediately install the 3.1.0 firmware zip & flash chainfire's SuperSU zip installable.
Then you can reinstall the Xposed framework & you are good to go.
If you already updated, but can still get into safestrap, even after a reinstall, then you too can still revert & reclaim root.
I have tried allowing the update with a modified build.prop, to reflect the current update version (tho higher is prob. better) the update fails & says the current firmware is up to date & newer than the installing version.
I don't have my PC, so this is from my phone. I'll try to edit it to be an easier read tomorrow.
For now, here's the proof.
{
"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"
}
Sent from my Nexus 5 using XDA Premium HD app
I'm not positive I understand. For clarification, after the update downloads and installs, but before it reboots to apply everything, go to safestrap and reinstall safestrap, allow the update to reboot, and then when it reboots go into safestrap and flash the supersu zip?
S_transform said:
I'm not positive I understand. For clarification, after the update downloads and installs, but before it reboots to apply everything, go to safestrap and reinstall safestrap, allow the update to reboot, and then when it reboots go into safestrap and flash the supersu zip?
Click to expand...
Click to collapse
close you have to install the firmware zip right after the update reboots then chainfires super user zip
1. After update installs, you immediately install/open SafeStrap. It will then install the openrecovery script because the recovery partition is still unlocked.
2. once in Safestrap, install the previous update-kindle-14.3.1.0_user_310079820 update. At this point, you can reboot, or do whatever you want, but I suggest imeddiately installing the SuperSU flashable, which restores root access.
3. Once you reboot, you may notice a few apps missing. Just reinstall safestrap again, but there is no need to re-install the recovery a third time, & add the HDX Xposed framework back in + the GAPPS you use & you should be good to go.
That's really it, aside from modding the build.prop to reflect the current version or higher. I suggest modding it to match the new version first, which will give you the "updated successfully" message again, & then raising the version/build number higher to protect against future updates.
I got my KIndle Fire HDX 8.9 Apollo today and the first hing it did was updating to 321093620. But i haven't it rebootet yet.
Of course it was not rooted before the update or safestrap installed (new device, as i told).
Is there alsp hope for me?
GSLEON3 said:
1. After update installs, you immediately install/open SafeStrap. It will then install the openrecovery script because the recovery partition is still unlocked.
2. once in Safestrap, install the previous update-kindle-14.3.1.0_user_310079820 update. At this point, you can reboot, or do whatever you want, but I suggest imeddiately installing the SuperSU flashable, which restores root access.
3. Once you reboot, you may notice a few apps missing. Just reinstall safestrap again, but there is no need to re-install the recovery a third time, & add the HDX Xposed framework back in + the GAPPS you use & you should be good to go.
That's really it, aside from modding the build.prop to reflect the current version or higher. I suggest modding it to match the new version first, which will give you the "updated successfully" message again, & then raising the version/build number higher to protect against future updates.
Click to expand...
Click to collapse
I'm new to the device and i think i need some help doing your steps:
1. I found this thread for installing Safestrap Recovery on Apollo.
It lists "Rooted w/ SuperSU installed" as a requirement. OK, so i search for a rooting how to and found the[Root] Kindle Fire HDX 8.9 14.3.1-thread. Will try if it still works for me. But how can i install SuperSU (which is a requirement for Safestrap) after rooting? I guess without Safestrap i cannot flash SuperSU.zip
2. If I have rooted and installed Safestrap, where can i get "update-kindle-14.3.1.0_user_310079820 update"?
Edit:
I just tried rooting, but i seems it no longer works
I get the following errors when I try the last step from the rooting tutorial (all other things worked):
Code:
adb shell /data/local/tmp/exploit -c "/data/local/tmp/rootme.sh"
Device detected: KFAPWI (JDQ39)
Attempt acdb exploit...
KFAPWI (JDQ39) is not supported.
Attempt fj_hdcp exploit...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt put_user exploit...
ioctl: Bad address
Attempt fb_mem exploit...
Detected kernel physical address at 0x00008000 form iomem
Attempt perf_swevent exploit...
KFAPWI (JDQ39) is not supported.
failed to open /dev/diag due to Permission denied.
mount: Operation not permitted
/data/local/tmp/rootme.sh[3]: can't create /system/xbin/su: Read-only file system
Unable to chown /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
GSLEON3 said:
1. After update installs, you immediately install/open SafeStrap. It will then install the openrecovery script because the recovery partition is still unlocked.
Click to expand...
Click to collapse
Question here…
If the recovery partition remains unlocked after this update, is there a way to force a RE-update? And wouldn't this leave the recovery partition unlocked again, thus allowing installation of SafeStrap/openrecovery?
-Pie
EatingPie said:
Question here…
If the recovery partition remains unlocked after this update, is there a way to force a RE-update? And wouldn't this leave the recovery partition unlocked again, thus allowing installation of SafeStrap/openrecovery?
-Pie
Click to expand...
Click to collapse
That is sort-of what I did & was looking at. I think you'd have to edit the 14.3.1.0 firmware to read as a newer version, since you would need to roll back the kernel for root, which you need BEFORE safestrap. However, it causes issues that I have not been able to iron out, including an occasional bootloop that is a real bitc# to get out of, which is why nothing has been updated yet. I also do not know what, if any, checks are being performed during kernel update. I think I noticed a few endif instructions, but I haven't looked at what they are referencing. Not too mention, I have no idea about the 7" model or how I was able to recover AVOD. I thought I figured out the AVOD part, but in recreating the issue, what I thought was the solution, doesn't seem to necessarily be the answer consistently on other devices. I need to find some time to sit down & go thru everything thoroughly. I should be able to soon, since I was able to hit R8 again in Ingress. Now that it won't take up so much time, I can start poking around more.
GSLEON3 said:
That is sort-of what I did & was looking at. I think you'd have to edit the 14.3.1.0 firmware to read as a newer version, since you would need to roll back the kernel for root, which you need BEFORE safestrap. However, it causes issues that I have not been able to iron out, including an occasional bootloop that is a real bitc# to get out of, which is why nothing has been updated yet. I also do not know what, if any, checks are being performed during kernel update. I think I noticed a few endif instructions, but I haven't looked at what they are referencing. Not too mention, I have no idea about the 7" model or how I was able to recover AVOD. I thought I figured out the AVOD part, but in recreating the issue, what I thought was the solution, doesn't seem to necessarily be the answer consistently on other devices. I need to find some time to sit down & go thru everything thoroughly. I should be able to soon, since I was able to hit R8 again in Ingress. Now that it won't take up so much time, I can start poking around more.
Click to expand...
Click to collapse
i have an 8.9 that i managed to keep from updating
do you think you could show me how to or write something up on editing the build.prop to keep from updating ?
jjrizzelcincy said:
i have an 8.9 that i managed to keep from updating
do you think you could show me how to or write something up on editing the build.prop to keep from updating ?
Click to expand...
Click to collapse
I will create a tar. That way, if extracted on the device it should keep the owner/group & permission settings. Without those set, you get a bootloop.
GSLEON3 said:
I will create a tar. That way, if extracted on the device it should keep the owner/group & permission settings. Without those set, you get a bootloop.
Click to expand...
Click to collapse
THANKS
maybe we can rebuild a cracked kernel from source for fire os 3.2？
Sent from my Galaxy Nexus using xda premium
oubeichen said:
maybe we can rebuild a cracked kernel from source for fire os 3.2？
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Breaks signature. All kernels HAVE to be signed by Amazon ATM.
best way to avoid update
hey guys. iv been outta the loop for about a month now due to life stuff. since then there was an update that ruins everything and seems to go around firewalls and hdxpose. so, for someone like me who hasnt turned their hdx on since the update what do you guys suggest is the best way to avoid updates? should i use gsleons suggestion in the OP as the best work around?
thank you
gutts10 said:
hey guys. iv been outta the loop for about a month now due to life stuff. since then there was an update that ruins everything and seems to go around firewalls and hdxpose. so, for someone like me who hasnt turned their hdx on since the update what do you guys suggest is the best way to avoid updates? should i use gsleons suggestion in the OP as the best work around?
thank you
Click to expand...
Click to collapse
The best solution for now is to CAREFULLY modify the build.prop to reflect a version equal to or greater than the latest updates version number.
I have attached a tarball of the build.prop I use. It reflects the 14.3.2.1 version. It is ONLY FOR THE KINDLE FIRE HDX 8.9. You can use it as a guide for changing the version in the HDX7, but DO NOT INSTALL IT ON THE HDX7.
Since it is a tar created in Linux, you should be able to extract it & it should keep it's permissions & user/owner groupings. However, extracting files to SDCARD first can sometime change the Owner group. I would recommend using an app like Root Explorer Pro (paid version which I use comfortably on every device) or whatever Root file browser you use that can change permissions & owner/user group.
If another update comes out, this will not stop it since it only is set to reflect the current 14.3.2.1 version.
If you choose to use another file explorer/browser, make certain that the user & owner groups are set to "Root", or immediately use ADB to chown to root.root or root:root depending on if you are using windows or linux.
If you use an explorer that extracts to the sdcard, you also will need to set the permissions to 644. Again, you can use ADB to chmod the file, or a file explorer/browser to set permissions to 644, or rw-r--r--. This means that owner is set to read & write, group is set to read only & others are set to read only as well.
Do not reboot until you are sure you have the permissions & owner/group set & also note that the changes to the build.prop will not be active until you reboot.
If you are using SafeStrap, make sure that if you change the wifi status off or turn on airplane mode, the you revert the changes before booting back to an active rom-slot. Having mismatched connectivity settings in stock & rom-slot will cause issues with connectivity & reboots until it is rectified.
GSLEON3 said:
The best solution for now is to CAREFULLY modify the build.prop to reflect a version equal to or greater than the latest updates version number.
I have attached a tarball of the build.prop I use. It reflects the 14.3.2.1 version. It is ONLY FOR THE KINDLE FIRE HDX 8.9. You can use it as a guide for changing the version in the HDX7, but DO NOT INSTALL IT ON THE HDX7.
Since it is a tar created in Linux, you should be able to extract it & it should keep it's permissions & user/owner groupings. However, extracting files to SDCARD first can sometime change the Owner group. I would recommend using an app like Root Explorer Pro (paid version which I use comfortably on every device) or whatever Root file browser you use that can change permissions & owner/user group.
If another update comes out, this will not stop it since it only is set to reflect the current 14.3.2.1 version.
If you choose to use another file explorer/browser, make certain that the user & owner groups are set to "Root", or immediately use ADB to chown to root.root or root:root depending on if you are using windows or linux.
If you use an explorer that extracts to the sdcard, you also will need to set the permissions to 644. Again, you can use ADB to chmod the file, or a file explorer/browser to set permissions to 644, or rw-r--r--. This means that owner is set to read & write, group is set to read only & others are set to read only as well.
Do not reboot until you are sure you have the permissions & owner/group set & also note that the changes to the build.prop will not be active until you reboot.
If you are using SafeStrap, make sure that if you change the wifi status off or turn on airplane mode, the you revert the changes before booting back to an active rom-slot. Having mismatched connectivity settings in stock & rom-slot will cause issues with connectivity & reboots until it is rectified.
Click to expand...
Click to collapse
I tried to change the build.prop on my thor fire os on a rom slot but it crashed on reboot. You may have seen the new utility I made for the hdx. I'm looking for a safe way to block ota. I know you told us how to do it but I'm still unsure.
Can you update the build.prop in general for Thor/Apollo with that version?
Can you completely stop all future updates before they're released by changing the build.prop version value to a high value?
To note, I read your post above but I still want your insight.
Any help is appreciated.
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?)?