Related
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.
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
Main thread + Features + Dev support
http://forum.xda-developers.com/showthread.php?t=2201860
CWM 6.0.4.8 Advanced Edition / PhilZ Touch Recovery 6.40.1
PhilZ Recovery is a CWM Advanced Edition that adds all the features you could ever miss in CWM.
It is a well proven recovery for many phones.
Please give your feedback, what works, and any bug you could encounter.
Read the features at the Main thread, and check if you are missing something.
To take a screen shot, just slide left!
And don't forget to read about powerful aroma file manager integration and double-tap shortcut (in FAQs).
How to install recovery?
From download link below, you'll get a 'recovery.img' file. Put that recovery.img file at root directory of your
sdcard. (means not in any folder)
Now, go to terminal emulator.
Give command:
Code:
su
You'll be asked to grant superuser permissions, grant it.
Now, give the following command:
Code:
flash_image recoveryonly /sdcard/recovery.img
Wait until it executes the command (4-5 seconds), it is installing the recovery.
Now, normally reboot to recovery and enjoy new recovery!
Download links
Latest version can be found here:
recovery.img (v6.40.1)
https://docs.google.com/uc?id=0B5c3gpyMBJusXzRfRWg4TXhZdVE&export=download
aromafm_cooper.zip (v1.91)
http://www.upload.ee/files/3959191/aromafm_cooper.zip
Click to expand...
Click to collapse
Special thanks to:
@Phil3759 : For this awesome open source recovery.
@chraso: For hosting and compatible flags.
AndroidARMv6 Team: For keeping this device alive.
Cyanogenmod Team: For making all these possible.
XDA:DevDB Information
PhilZ Touch Recovery for Galaxy Ace, Tool/Utility for the Samsung Galaxy Ace S5830
Contributors
Bhargav97, chraso, Phil3759
Version Information
Status: Stable
Current Stable Version: 6.40.1
Stable Release Date: 2014-05-04
Created 2014-05-07
Last Updated 2014-05-07
:FAQs:
Q: Wanna know about Aroma File manager?
Visit the aroma file manager main thread for more info---> Aroma file manager main thread
Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,
change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any
file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI
is fully customizable.
Q: How to start this File manager in Recovery?
Rename the downloaded file to 'aromafm.zip'.
Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.
Now, move that 'aromafm.zip' file to the 'aromafm' folder.
We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select
"Aroma File Manager" and it will start up.
If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.
Q: Problems with Aroma file manager startup?
After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip
not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe
busy mounting sdcard.
If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.
Q: Does your phone every time reboots to recovery?
This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do
is:
-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.
OR
-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot
to system. Booting process will take time.
NEW: Now you can enjoy the full version of the recovery! Thanks to @Phil3759 for uploading necessary
commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.
SCREENSHOTS:
Main menu and PhilZ Settings
{
"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"
}
GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...
27 color settings + 5 alpha transparency levels for every GUI element
Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original
cwm image
User configurable touch gestures (feel free to request for new actions)
Setup your time-zone + 30mn offset, super wipe option to install a new ROM
Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)
Custom backups can also be restored by original CWM Advanced Restore Menu
TWRP Backup and Restore Support + md5 + single/multivolume format
Support multi-cpu compression, md5 check toggle and custom .android_secure path
Choose ors backup volume target
Flash multiple zip files in a raw
Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)
Full Wipe to Install a new ROM (sdcard is preserved)
Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
Very nice... will try it soon... :good:
Wow this should be great
I tried the recovery and it works. Installation is quick and simple and works just as described. Installing, wiping, backups, touch (up and down) and everything else works just as said. Kudos to you OP!
The last thing I wanna know:
After installing/restoring anything, can you successfully reboot to system?
You should also try Aroma File manager, it's the best part of this recovery.
Gonna Try...
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and then boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
nizar.nasani said:
@Bhargav97 i tested it , everything is working but there is one big problem , the recovery cannot reboot to system , it only reboot to recovery ,even if i shut down the device and the boot it , still stuck on recovery
hope you fix it
thanks for your hard work
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
Expect a fix soon!
I was understanding the problem for last few days (because same happens to other two devices also) and finally got the solution and I'll be re-compiling recovery as soon as I get some time.
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Am I dreaming? Thanks for revive my old Ace
Sent from my Nexus 5 using XDA Premium 4 mobile app
Bhargav97 said:
UPDATE:
-Updated philz recovery sources to 6.23.9 (26.03.2014)
-cm-ota compatibility fixes.
-reboot to system bug is now fixed.
Download link updated in first post.
Click to expand...
Click to collapse
swipe left and right dont work for me ????
Rhievaldo said:
swipe left and right dont work for me ????
Click to expand...
Click to collapse
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Bhargav97 said:
Always Read OPs of a thread.
See my post #3, I've already stated that Right/Left swipe won't work yet. We're lucky to at least have a basic touch code implemented in our androidarmv6 sources. It is improving...someday if androidarmv6 developers plan to furnish the recovery touch code, right/left swipe will also be fixed. I can't fix that.
Click to expand...
Click to collapse
always read it,, but forgot about that. Sorry... cause read it at 23 march, and try at 30 march..
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
everything seems to be working for me
---------- Post added at 06:43 PM ---------- Previous post was at 06:34 PM ----------
actually, all features work butkeeps rebooting into recovery,, not sure if its a problem restoring a back up ill try installing a new rom
edit,, yes it reboots into recovery no matter what,, damn,, nearly close to perfect
Bhargav97 said:
MAJOR UPDATE:
PhilZ Recovery updated to 6.27.9.
PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).
CWM updated to 6.0.4.8.
Ready for official support!
I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.
Download link:
https://drive.google.com/file/d/0B5c3gpyMBJusUkVLRWJ2OVBXak0/edit?usp=sharing
Click to expand...
Click to collapse
yes right when i reboot to system it reboot to recovery, the same as the previous time.
There was a little bug which caused issue for rebooting to system. I just fixed it and asked @chraso to compile. So, now finally it's done! Updated first, second and third posts.
Report back for the download link put up on first post.
i've test almost everything and i can say this is the best recovery ever made for ace ✌
thanks for bring it to our ace
sent from my kitkat ACE
HOW TO ROOT AND MOD YOUR AUSTRALIAN TELSTRA G900I
WITHOUT TRIPPING KNOX
Firmware 4.4.2 G900IDVU1ANE1 ONLY !!
WANAM XPOSED THEMES CAN BE FOUND IN THIS POST
{
"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"
}
Hi fellow Australian Telstra S5 users.
About a week ago I finally got my hands on my Galaxy S5 G900I model.
This has been my 5th Samsung device (GT-I9000, GT-I9100, GT-I9305T, GT-P5100, and SM-G900I), and the first I've encountered the deadly KNOX security.
This is a small guide on how to install SuperSU, Busybox, Xposed Framework, and Wanam Xposed without tripping your KNOX counter.
STARTING OFF
WARNING: MAKE SURE THAT THE KERNEL VERSION AND BUILD NUMBER MATCH YOUR PHONE.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE, DO THIS AT YOUR OWN RISK !!
First of all, download the G900IDVU1ANE1_Mods-djb77 file attached to this post, this contains all the files and resources you need.
The original files can be found in the G900IDVU1ANE1_Original zip file.
This Mods zip file contains the following:
ROOTING TOOLS: Towelroot - SuperSU - Busybox (Stericson)
APPS: AdAway - Phone INFO - Titanium Backup - Total Commander
XPOSED APPS: Xposed Installer - Wanam Xposed - XSecureStorage
OTHER FILES: Modded others.xml - Original Samsung Bootanimation - Wanam Xposed Presert
The modded others.xml file is the same as the original others.xml except for the following changes:
- Show proper SMS / MMS timestamp (when the item was sent, not recieved)
- Disable the Software Update Menu
- Enable Call Button in Contact List
PREPARING FOR ROOT
- Go to Settings -> General -> About Device -> Software Updates, uncheck Auto-update and Wi-Fi only.
- Go to Settings -> General -> Security, check Unknown Sources, and uncheck Verify apps.
- Go to Settings -> General -> Security -> Security Policy Updates, disable Automatic Updates.
- Copy downloaded files to your SD Card.
INSTALLING ROOT / BUSYBOX
- Install Towelroot and launch. Press the "Make it Ra1n" button and wait, the app will prompt you when its finished.
- Install SuperSU and launch. Install SU Binary via Nomral option, and don't disable KNOX.
- Restart Phone.
- Install Busybox and launch. Wait for Small Install to finish loading, then press the Install button. Restart Phone.
RESTORE SAMSUNG BOOTANIMATION (Optional)
This removes the Telstra branded bootaniatmion / shutdown with the stock Samsung bootanimation / shutdown
- Install Total Commander
- Launch Total Commander and delete the following files
/system/media/bootsamsung.qmg
/system/media/video/shutdown/shutdown.qmg
/system/media/audio/ui/PowerOn.ogg
- Copy the files from the Bootanimation folder over to these locations, with chmod 644 on the new files.
FIX MICROSD CARD WRITE PERMISSIONS (Optional)
- Install Total Commander (if you haven't already)
- Launch Total Commander and delete the following file
/system/etc/permissions/platform.xml
- Copy the files from the MicroSD folder over to that location, with chmod 644 on the new file.
ADD EXTRA CSC FEATURES (Optional)
- Install Total Commander (if you haven't already)
- Launch Total Commander and delete the following file
/system/csc/others.xml
- Copy the files from the CSC folder over to that location, with chmod 644 on the new file.
INSTALL XPOSED FRAMEWORK / WANAM XPOSED (Optional)
- Go to Settings -> Applications -> Application manager, uninstall any updates for S Health and HealthService.
- Install Xposed framework + apps, but don't open them just yet.
- Launch Xposed Framework installer with all modules ticked. Restart Phone.
- Copy Standard Settings.wx to .WanamXposed folder.
- Launch Wanam Xposed and load the Standard Settings. Restart Phone.
Hope this little guide helps some of you out
Enjoy your modded G900I with genuine KNOX
and for OS above NE1, refer here:
http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044
Just a shame we can't use Mobile ODIN, otherwise I'd look at deodexing the ROM and doing some further modifications.
I hear that it trips KNOX, and if that's the case I'm staying well clear of it.
djb77 said:
Just a shame we can't use Mobile ODIN, otherwise I'd look at deodexing the ROM and doing some further modifications.
I hear that it trips KNOX, and if that's the case I'm staying well clear of it.
Click to expand...
Click to collapse
Mobile ODIN (Pro version) does not trip knox only the simple version does
wajiman said:
Mobile ODIN (Pro version) does not trip knox only the simple version does
Click to expand...
Click to collapse
So you've tried it and can confirm it's all good? Sorry to be extra-cautious lol
This is what scares me, that bottom warning... Did you get the same warning screen?
I'm using the Pro version too...
djb77 said:
This is what scares me, that bottom warning... Did you get the same warning screen?
I'm using the Pro version too...
Click to expand...
Click to collapse
yes i did, but it does not trip knox, and you can also flash zip files through mobile odin (OTA/Update option) but it requires some additional things for the zip to work perfectly. @_alexndr know about it, i flashed his rom that way.
but in my thread, i havent mentioned anything about Mobile Odin, only PC Odin
wajiman said:
yes i did, but it does not trip knox, and you can also flash zip files through mobile odin (OTA/Update option) but it requires some additional things for the zip to work perfectly. @_alexndr know about it, i flashed his rom that way.
but in my thread, i havent mentioned anything about Mobile Odin, only PC Odin
Click to expand...
Click to collapse
What additional things are you talking about? Is it something in the updater-script, does the zip need to be signed?
I just made a deodexed version of this ROM with ArchiKitchen so I'm keen to flash the deodexed system files and framework.
djb77 said:
What additional things are you talking about? Is it something in the updater-script, does the zip need to be signed?
I just made a deodexed version of this ROM with ArchiKitchen so I'm keen to flash the deodexed system files and framework.
Click to expand...
Click to collapse
i have no idea, this is what he told me when i asked him:
_alexndr said:
Yes, you can. Most of CWM flashable zip files should work. Unfortunatelly, some devs in their zip files do not care about compatibility with MOP and use mount points specific for CWM/TWRP. Here is an example of not working zip using Mobile Odin Pro (reported in my thread @ Polish forum):
[THEME] All Backs Black S5 ••●The Blackness Realm●••
Above zip file can't be succesfully flashed using MOP because it contains /sdcard mount point for internal emulated SD card (in updater-script AND in sh scripts). Unfortunatelly - such mount point does not exists in case of MOP... If the dev/themer would change the point on the other (/sdcard -> /data/media/0) then such zip file will be compatible with all custom recoveries AND with Mobile Odin Pro
BTW
Note that if you flash using MOP zip file containing custom recovery or custom kernel - then your KNOX will be tripped !!!
Click to expand...
Click to collapse
OK that seems pretty straight forward to understand. Make sure the partition mounts are compatible with Mobile ODIN Pro (which my updater-scripts usually are) and don't flash kernel, recovery, or modem. Too easy
THEMES FOR WANAM XPOSED
To install these themes, extract the zip file and copy the .wx file to your .WanamXposed folder on your Internal SD Card.
This is what the standard quicksettings screen and device settings screen look like:
The first thing that is changed in all the themes is that terrible blue colour that is used for the backgrounds, as shown below.
Please note that not all apps are supported by this function, however it does work on a few (even 3rd party market apps)
BLACK AND BLUE
BLACK AND GREEN
Guide updated to v2, to include a fix for the MicroSD Card. I noticed the issue when trying to use Titanium Backup
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!!!
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