Related
Clean install of a ftf is better than Flashing a Pre-Rooted zip. I flashed a Lp Pre-Rooted zip and face some problem... Specially battery drainage issue. So I cleaned installed the LP ftf. And rooted it afterwards... My battery is a beast now
Requirements
1: King Root http://https://userscloud.com/ke35zvpes88k
2: XZDualRecovery 2.8.15-RELEASE.installer.zip http://nut.xperia-files.com/
3: BETA-SuperSU-v2.49.zip http://https://userscloud.com/7hs0w0d9l46h
(SuperSU-v2.46 will give you binary update error) (place this zip in your internal memory/Sdcard
Steps
1: Flash your latest ftf of LP 5.0.2 via flashtool to start a clean install. IF You are already on LP, ignore step 1.
2: Install King Root Apk and Run it. Click on root. Wait until it says 100%. It should be 100%. U rooted your mobile successfully. Don't restart your mobile.
3: Place XZDualRecovery 2.8.15intsaller.zip in any folder of your PC and extract it.
4: Connect your mobile to your computer with Debugging mode enabled.
5: Open XZDualRecovery folder and Click on Install.bat. A command window will be opend. Choose/Type 2 (root with SuperUser) and pres enter. Follow the instructions... Done... XZDualRecovery is installed
6: Boot in to recovery and Install BETA-SuperSU-v2.49.zip. Restart your mobile... You have a working SuperSu without any binary update problem.
7: Delete KingUser App Manualy by Going into /system/app/kinguser.apk. Or u can delete it by some system app remover application. It is necessary to delete King User App because It may be cause conflict with SuperSu.
All Done.....
Moderater: kindly delete it... Posted in wrong section by mistake
xuhaib said:
Clean install of a ftf is better than Flashing a Pre-Rooted zip. I flashed a Lp Pre-Rooted zip and face some problem... Specially battery drainage issue. So I cleaned installed the LP ftf. And rooted it afterwards... My battery is a beast now
Requirements
1: King Root http://https://userscloud.com/ke35zvpes88k
2: XZDualRecovery 2.8.15-RELEASE.installer.zip http://nut.xperia-files.com/
3: BETA-SuperSU-v2.49.zip http://https://userscloud.com/7hs0w0d9l46h
(SuperSU-v2.46 will give you binary update error) (place this zip in your internal memory/Sdcard
Steps
1: Flash your latest ftf of LP 5.0.2 via flashtool to start a clean install. IF You are already on LP, ignore step 1.
2: Install King Root Apk and Run it. Click on root. Wait until it says 100%. It should be 100%. U rooted your mobile successfully. Don't restart your mobile.
3: Place XZDualRecovery 2.8.15intsaller.zip in any folder of your PC and extract it.
4: Connect your mobile to your computer with Debugging mode enabled.
5: Open XZDualRecovery folder and Click on Install.bat. A command window will be opend. Choose/Type 2 (root with SuperUser) and pres enter. Follow the instructions... Done... XZDualRecovery is installed
6: Boot in to recovery and Install BETA-SuperSU-v2.49.zip. Restart your mobile... You have a working SuperSu without any binary update problem.
7: Delete KingUser App Manualy by Going into /system/app/kinguser.apk. Or u can delete it by some system app remover application. It is necessary to delete King User App because It may be cause conflict with SuperSu.
All Done.....
Click to expand...
Click to collapse
Hi there, I got the problem while rooting my xperia zr and stuck at step 3. I can't recovery me device, could you help me please.
HTML:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?2
* server not running *
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
xuhaib said:
Clean install of a ftf is better than Flashing a Pre-Rooted zip. I flashed a Lp Pre-Rooted zip and face some problem... Specially battery drainage issue. So I cleaned installed the LP ftf. And rooted it afterwards... My battery is a beast now
Requirements
1: King Root http://https://userscloud.com/ke35zvpes88k
2: XZDualRecovery 2.8.15-RELEASE.installer.zip http://nut.xperia-files.com/
3: BETA-SuperSU-v2.49.zip http://https://userscloud.com/7hs0w0d9l46h
(SuperSU-v2.46 will give you binary update error) (place this zip in your internal memory/Sdcard
Steps
1: Flash your latest ftf of LP 5.0.2 via flashtool to start a clean install. IF You are already on LP, ignore step 1.
2: Install King Root Apk and Run it. Click on root. Wait until it says 100%. It should be 100%. U rooted your mobile successfully. Don't restart your mobile.
3: Place XZDualRecovery 2.8.15intsaller.zip in any folder of your PC and extract it.
4: Connect your mobile to your computer with Debugging mode enabled.
5: Open XZDualRecovery folder and Click on Install.bat. A command window will be opend. Choose/Type 2 (root with SuperUser) and pres enter. Follow the instructions... Done... XZDualRecovery is installed
6: Boot in to recovery and Install BETA-SuperSU-v2.49.zip. Restart your mobile... You have a working SuperSu without any binary update problem.
7: Delete KingUser App Manualy by Going into /system/app/kinguser.apk. Or u can delete it by some system app remover application. It is necessary to delete King User App because It may be cause conflict with SuperSu.
All Done.....
Click to expand...
Click to collapse
Dude dual recovery doesn't install if rooted via kingroot...if m not mistaken...
Here it is. Full T-mobile With root, wifi calling, bluetooth and volte all working - since this is t-mobile based all bands should work as well
Updated to use API4 System Image and API4 Modem - MyMods has also been updated for the API4 System - Whatever you do DO NOT FLASH the API4 BL file. you will be Stuck on the new firmware without root if you do this as you cannot go back
To Avoid Repeat Questons. READ! READ IT AGAIN! and then READ it once more! if you do not Understand any part of this. Do Not Continue!!!
This Guide assumes you have some basic knowledge and is for advanced users!!!!!!!!
This Guide also Assumes you have an sdcard inserted in your phone(however some of you may not and this will not work.)
i will post an update to this guide when we have a method working for those of you with no extsdcard
Read this entire post before doing anything to avoid issues and FOLLOW Directions - if you don't things will not work right.
Note! if at anytime during the following steps you see the samsung boot animation before step 11. start over cause you screwed up!
Step 1. download the following files
https://www.androidfilehost.com/?fid=24651430732237653 bbx.rar
https://www.androidfilehost.com/?fid=457084094631641263 API4 system.rar
https://www.androidfilehost.com/?fid=24686680535467223 T-mobile APGC Bootloader
https://www.androidfilehost.com/?fid=529152257862665245 T-mobile API4 Modem
Step 2. extract system.rar and bbx.rar and then copy system.img and bbx to your extsdcard(the sdcard you inserted into your phone)
Step 3. odin sprint userdebug firmware available here. http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
Step 4. Directly after odin is done with the sprint file you will immidiatly be presented with an update screen
Step 4a when this process of erasing your phone is finished it will reboot(this is the point you want to do the next step)
Step 4b. press and hold power, home and vol up to enter recovery
Step 4c If you see the samsung boot animation. you did NOT do this right and i would suggest you start over
Step 5. open a command prompt in your adb folder and do the following steps 1 at a time(these are case sensative)
Step 5a. adb shell
Step 5b. su
Step 5c. setenforce 0
Step 5d. export PATH=$PATH:/sbin
Step 5e. mount -o remount,rw /
Step 5f. on your phone, go to apply update from sdcard(this will mount your extsdcard as /sdcard and you should see the system.img file and the bbx file) do not select anything, go back to adb and continue(it is not a big deal if those files don't show. we just needed the extsdcard mounted as sdcard - the files exist, just continue to the next step)
Step 5g. cp /sdcard/bbx /sbin/bbx
Step 5h. chmod 777 /sbin/bbx
Step 5i. cd /sbin
Step 5j. ./bbx --install /sbin
Step 5k. umount -l /system
Step 5l. /sbin/dd if=/sdcard/system.img of=/dev/block/platform/soc/624000.ufshc/by-name/system
Note. you will see a blinking cursor. just be patient
Step 7. when it is done you will see something similar to this
11161600+0 records in
11161600+0 records out
5714739200 bytes (5.3GB) copied, 268.668086 seconds, 20.3MB/s
Step 8. if all went well you should be at your prompt and not in adb anymore
Step 9. from your command prompt simply type
Step 9a. adb reboot bootloader
Note! - if you still have odin open and the sprint file in the ap box make sure you uncheck it so it doesn't reodin the sprint firmware
Step 10. open odin and click the bl button and select this file - BL_N930TUVU1APGC_CL8706614_QB10376889_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10b. now click the cp button and select this file - CP_N930TUVU2API4_CL9115549_QB10937257_REV00_user_low_ship_MULTI_CERT.tar.md5
Step 10c. now click start. it will reboot when done let it fully boot this time.
Step 11. once booted and you have setup your phone, we need to add the root files or supersu as most of you know it
Note! pertaining to Step 12. these instructions were taken Explicitly from @freeza thread which is listed in step 3
Step 12. Now we need to add supersu and the needed files for it to work
Step 12a. download this file - https://www.androidfilehost.com/?fid=24651430732236679
Step 12b. Extract the sun7 file to your adb folder making sure the files are in a folder called sun7(mine looks like this - c:/adb/sun7 and contains 4 files)
Step 12c. Open a command prompt where your ADB executable and sun7 folder are.
Step 12d. adb shell
Step 12e. su - Note! if your adb prompot changes from a $ to #(you are good and have root access)
Step 12f. type exit twice to get back to the command prompt. - Your Phone should be fully booted when you do this
Step 12g. adb push sun7 /data/local/tmp/su
Step 12h. adb shell chmod 0777 /data/local/tmp/su/*
Step 12i. adb shell
Step 12j. cd data/local/tmp/su
Step 12k. su
Step 12l. ./root.sh - Note. this command begins with a . do not leave it out
Step 12m. Your Phone will now reboot
Step 13. when booted back up go to playstore and install busybox on rails or a similar app and install busybox to /system/xbin(if your given an option of where to install it)
Step 14. Thats Pretty Much it. install any additions i have included if you like. most of all enjoy it
Additional Notes!
If for any reason you do a factory reset. you will break root and need to redo this method to get it back
If you use shealth do not update it or allow playstore or galaxy appstore to auto update it or it will break it
If you plan on running the debloat/deknox file you will need to disable auto updates in google playstore as soon as you finish the setup wizard or you will be uninstalling the apps that managed to update
Note! Keep in mind that i remove alot of things(ie. allshare, knox, gear manager, game manager, tmo apps, google apps, facebook and alot of other things) if you need any of what i remove, you can simply open the zip and go to META-INF/com/google/android and open the following file "updater-script" in notepad++(do not open it with windows notepad as it will screw up the formatting on the entrys) you will see a whole bunch of lines that begin with delete_recursive, remove the lines with names of the apps you do not want removed. most of this stuff is self explanatory by it's name as to what it is and should be very easy to figure out. when done editing the file, save it. and flash the updated zip in flashfire. it's as simple as that.
Additional Files for those that want them(these are all flashed via flashfire)
https://www.androidfilehost.com/?fid=385035244224381428 my modifications zip API4 Version(very minor mods to statusbar and a few other added features)
https://www.androidfilehost.com/?fid=24686680535467932 debloat/deknox zip - Updated with remaining t-mo apps i missed initially
https://www.androidfilehost.com/?fid=24651430732237106 beats audio installer(this is a blue themed version done by me)
https://www.androidfilehost.com/?fid=24651430732237109 Dolby Atmos Installer
https://www.androidfilehost.com/?fid=24651430732237107 Viper4Android Installer
https://www.androidfilehost.com/?fid=24651430732237108 selinuxmodechanger.apk so you can set kernel to permissive for viper(this is an apk. just install it from your sdcard)
My Mods Contains the Following Modifications
3minit battery
battery bar - option is in rom control
potato clock
loud volume warning - toggle to disable or enable this via rom control
network speed on statusbar - option in rom control
aokp rambar in recents
added some additional toggles
ability to move the wifi and signal bar indicator to the left or right side via a toggle in rom control
a few csc tweaks
Applock Added - Thanks @TEKHD
FOLLOW Directions - if you don't things will not work right.
thank you to the following:
@freeza - for posting the original userdebug file
@ted77usa - for testing
@bajasur - for the initial idea which ultimately led to this
@Surge1223 - for the busybox installer and the adb help and android commands that make this work
@galaxyuser88 - for testing this and pointing out some flaws
@Hashcode - for inspiration
and anyone i missed
this was a complete collaboration and is only available because of those mentioned so be sure to give them thanks
Big Thanks to @galaxyuser88 for testing the mods for me as i can't
for those that don't like PI4 update. heres the original PGC files
https://www.androidfilehost.com/?fid=24686680535467933 - PGC mods
https://www.androidfilehost.com/?fid=24651430732237809 - PGC system.img
https://www.androidfilehost.com/?fid=24686680535467224 - PGC CP File(modem)
method is the same, just use these files instead of the updated pi4 files
reserved 2
reserved 3
Ok here it is: Xposed still works with this new root method, Only one catch, you have to install this before you install any of @OvrDriVE Mods.
If you plan on using Xposed then do not install @OvrDriVE my modifications zip as this will crash your systemui.apk.
As with any custom rom's, root, add-on's, you assume all risks with modding your phone. You have been warned.
Make sure you read all of my directions below, before you start posting errors with the install. Worst case you just have to start over with @OvrDriVE s installation.
Here is the way you can install xposed on your phone after you have root. I in no way have made any files or apks, I am just posting ways you get this loaded on your phone.
Please Thank the devolopers and others that have made all these files and apks possible..
The way to install Xposed framework via FlashFire:
1. Download FlashFire, You can get it from the app store: https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Download the Xposed Installer Apk: Xposed installer Apk
3. Download the Xposed Framework zip.<<< this is the file that you will be flashing via FlashFire: Xposed Framework.zip
4. Once you have all the files downloaded onto you computer/phone: you are ready to start. If you have'nt all ready copied all the files to your phone storage, do so now. If you did then you can move on to the #5.
5. Open FlashFire on your phone. Once it is loaded and open, click on circle with + button on the bottom right of the screen.
Then Click on Flash ZIP or OTA button.
Now select the xposed framework zip that you downloaded from #3.
Next you click the check mark on the top right of
the screen( do not change any of boxes on the left of the screen.<<< You Have Been Warned!!!!! .
Next scroll to the bottom of the screen and click the left button (flash button w the lighting bolt)
Sit back and watch FlashFire do its magic..
6. After #5 completes, you can now install the xposed installer apk from #2. Once installed open and check framework in the app and you should have this : Xposed framework version 86.1 (custom build by wanam / 2016709 is active.
7. Now go to Download in the xposed installer and download: XTouchWiz 1.1.2 or Wanam Xposed 1.3.0 Made for Samsung Android 5 and 6 Roms by Wanam. You can also download Firefds kit 1.0.5.1 by firefds <<<<< this is just a modified version of XTouchWiz with more stuff added to it.. This works as well on samsung note 7 root method.
8. Once you downloaded it, installed it, then go into the Xposed installer app- modules- you select the the app in #7 by placing a checkmark in the box on the right to activiate the modules.
9. Reboot your phone to activate the module.
10. Enjoy your efforts and customizing your phone:
If you some reason you want to uninstall xposed : flash this:xposed-uninstaller-20160211.zip
Awesome.....finally[emoji106]
Video tutorial could be found in here http://forum.xda-developers.com/showthread.php?p=68831392..... make sure to download correct modified system.rar for your specific carrier.
https://youtu.be/Oi-tuA_EIxA
*TwisT3DroiD_N930T*
Thank you!!!!
Sent from my SM-N930T using Tapatalk
OvrDriVE said:
Ok all here it is. root, with wifi calling and volte along with a few modifications
1. Follow the guide here skipping the root method for now- http://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202
2. go through setup. add your google account but do not setup samsung account(you'll do this later)
3. once at the homescreen, open google playstore and go to settings and set it to not auto update apps(you can change this back later)(this is to prevent apps from auto updateing as i will be removing most of them)
4. now do the supersu install as instructed in the sprint post
5. once booted back up, open playstore and install flashfire
6. once flashfire is installed flash this zip
7. https://www.androidfilehost.com/?fid=24651430732237438 - note7update.zip
8. once booted back up. open themes and add your samsung account info.
9. exit themes and open galaxy apps and update all available apps(they should install without errors)
10. you can skip this if you want - install supersu2.77 apk
11. https://www.androidfilehost.com/?fid=24686680535467222 - superuser 2.77
12. when done. open shealth. and go through it's setup. when done flash this file - if you don't setup shealth it will not work once we remove knox.
13. https://www.androidfilehost.com/?fid=24686680535467219 - knox remover
14. when booted back up. go to your apn settings and reset it to default and then select the t-mo apn
15. boot download mode
16. and odin t-mo cp file only - This will flash the t-mo Modem
17. https://www.androidfilehost.com/?fid=24686680535467224 - t-mo cp odin file
18. once booted up, enable airplane mode, then enable wifi and wifi calling should turn itself on.
19. everything should work fine
20. if by chance you get a wifi calling error 0082 just enable airplane mode then enable wifi and it will fix itself
heres a few Extra Files for those that may want them
here is a beats audio installer
https://www.androidfilehost.com/?fid=24651430732237106 - beats
here is dolby atmos installer
https://www.androidfilehost.com/?fid=24651430732237109 - dolby atmos
and here is viper4android installer
https://www.androidfilehost.com/?fid=24651430732237107 - viper4android
and here is selinuxmodechanger to set kernel to permissive
https://www.androidfilehost.com/?fid=24651430732237108 - selinux mode changer
all 3 audio mods fully work together. make sure you have permissive set or they won't work
enjoy
the mods included are battery bar, 3minit battery, potato clock, network speed statusbar mod, 5 way reboot, ability to toggle wifi/data on the left or right, and a few other mods. it debloats the rom as well.
FOLLOW Directions - if you don't things will not work right.
thank you to @jovy23 for the wifi calling files. and a great big thanks to all those who tested this. and a great big ty to @freeza for posting the original userdebug file
also ty to anyone i missed
i know this isn't a proper post and i will fix it later
View attachment 3865172View attachment 3865173
Click to expand...
Click to collapse
Wow nice job man!
FTW
Sent from my SM-N930T using XDA-Developers mobile app
Nice job man! :good:
Thanks!
Samsung Pay
Does this still make Samsung pay not work or any other NFC payment types?
freeza said:
Wow nice job man!
Click to expand...
Click to collapse
nah. thats all you guys man. you guys deserve the credit. i just did a few mods and wrote out the install instructions.
batsup606 said:
Does this still make Samsung pay not work or any other NFC payment types?
Click to expand...
Click to collapse
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or
!!!!!!!!
If you guys want Samsung pay....u need to stay stock and use disabler package pro to debloat and like @OvrDriVE said we can't have it all ....either or we gotta give up something. .... but with this breakthrough with root from @freeza.... now WiFi calling and volte work.... we are moving in good direction .... until we all get new note 7 replacement phone in couple week..... happy Labor days guys for people in US.
Sent from my SM-N920T using Tapatalk
OvrDriVE said:
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or
Click to expand...
Click to collapse
Ah okay thanks! and do you know if the Bluetooth issues still occur?
I am going to watxh this topic. I know alot of work is going on however i want to see how stable it is before i do anything. I can wait no problem. i know we have been hitting roadblocks and until we have an official root method I am perfectly fine without for now... To all the Devs great job now we wait and see if penetration testing and users can do this method of root. Thank you all for your time and hard work!
Ice.
Sent from my SM-N930T using XDA-Developers mobile app
OvrDriVE said:
keep in mind that once you root no payment method will work. however as this does not trip the knox counter. you can odin stock t-mo firmware and samsung pay and android pay will work just fine. you can't have it both ways unfortunately. it's either or
Click to expand...
Click to collapse
Great job on this and all the other developers who finally got android development this far for us!
Also has anyone tried chainfire's suhide app to see if samsung pay or android pay will work even while being rooted?
batsup606 said:
Ah okay thanks! and do you know if the Bluetooth issues still occur?
Click to expand...
Click to collapse
i do believe the issue still exist. i havn't tryed replacing the etc folder yet to see if it fixs it or not
you can connect but once disconnected you have to unpair the device and repair it for it to work.
I'm struggling with installing Viper4Android on my device.
I tried installing using either the apk from the original thread (http://forum.xda-developers.com/showthread.php?t=2191223). It install successfully but I keep getting a driver install prompt, after installing the driver and rebooting.
Things I already tried without success:
- Installed BusyBox with BusyBox app (https://play.google.com/store/apps/details?id=ru.meefik.busybox)
- Setting the SELinux mode to permissive using SELinuxModeChanger app (http://forum.xda-developers.com/showthread.php?t=2524485)
- Setting the SELinux mode to permissive using flashable permissive.zip
- Installing the apk from the Material design Viper4Android thread (http://forum.xda-developers.com/android/software/app-material-viper4android-2-3-4-0u-t3190352)
- Flashing the .zip from the same thread.
I'm currently running Android 6.0 GPE, flashable version (http://forum.xda-developers.com/showthread.php?t=2708589)
Root access is granted through SuperSU, so no problem on that matter I suppose.
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Duccibreeezy said:
2. With a File Manager(Solid Explorer Recommended) locate " /system/etc/htc_audio_effects.conf" and rename "htc_audio_effects.conf" to "htc_audio_effects.bak" (Renaming this file will make it inactive but while keeping it backed up just in case this doesn't work for you, however it appears this file is not needed as no negative effects occur, and this should fix V4A.)
3. Reboot Device.
And if this doesn't work I thin you should grant storage permission for V4A under settings. I hope I can help you!
Click to expand...
Click to collapse
Thanks mate!! This worked for me.
Thanks for ur help
SYSTEMLESS DevBase has been developed and physically tested on S7 Edge (G935F), so main thread containing the most detailed description you can find here:
>> [SAMSUNG][6.0+] SYSTEMLESS DevBase | Encryption support | Stock OTA updates <<
However, it should work on ALL SAMSUNG DEVICES running Android 6.0+, so if you are Galaxy S7 flat (G930xx) owner - please place your feedback & discussion here to let me know about device-specific issues or to let me know that everything works perfect
---------------------------------------------------------------------------
Are you tired with traditional custom ROMs?
Do you miss custom ROMs but do not want to decrypt your device (for privacy/security reasons)?
You are in the right place! I present you SYSTEMLESS DevBase - an SYSTEMLESS equivalent of my previous work (for older devices)
Prerequisites:
- Samsung device running stock or stock-based Android 6.0+ (mandatory!)
- Rooted device - SuperSU v2.76+ installed in SYSTEMLESS mode (mandatory!) (*) (!)
- Stock, untouched /system partition (not mandatory, but recommended for working OTA)
(*) NOTE: The latest CF-Auto-Root image for G930F contains SuperSU v2.74 which does not support SYSTEMLESS solutions (su.d is not triggered early enough). It is NOT enough to update it via PlayStore to the newest version and update su binaries! You need to update it using TWRP / FlashFire installable ZIP from THIS STABLE or THIS BETA thread. Alternatively you can use "EverRoot" -> "Inject SuperSU" option in FlashFire even if you are rooted already by CF-Auto-Root (it will update SuperSU in the same way as flashing ZIP).
(!) WARNING (related to installing TWRP @ Nougat - e.g. ZPLN, DPLT): There are confirmed reports that entering TWRP on encrypted phones running Nougat causes bootloop (even if you just enter TWRP, tap "Keep read only", do nothing else and then tap reboot!). You will need to restore both - stock recovery and stock kernel (if you e.g. tried to flash SuperSU or other ZIP which might modify the kernel) to make your device bootable. In case of encrypted devices we need to wait for a solution..
SYSTEMLESS DevBase:
1. Benefits / main features:
- Works with encypted /data partition
- Working official OTA updates! (see Tips & Tricks)
- Does NOT perform any phisical modifications in /system
- Does NOT perform any additional changes/patches to the kernel
- Removed KNOX warnings (systemlessly removed SecurityLogAgent)
- It contains SYSTEMLESS BusyBox (bionic, the most stable and respected release)
- It allows you to easily modify most of files & apps in your /system - SYSTEMLESSLY (see Tips & Tricks)
- It does not interfere with Magisk! You can use Magisk in paralell with SYSTEMLESS DevBase if you need it for your favorite module.
2. Systemless Safe De-Bloat (more info below):
What does it mean and why is it called "safe"?
- ONLY apps available in stores will be systemlessly removed from the ROM, so you can easily (re)install any of these app if you like
- ONLY pre-installed system apps are will be systemlessly removed, DevBase installer never touch any updated app nor app installed manually from store
Thus, the following conclusions can be drawn:
1. If you install my SYSTEMLESS DevBase directly over working stock ROM - in most cases almost all these apps will remain untouched, because almost all apps have been updated already (stored on /data). But then you will be able to remove any useless app using the "Application manager" -> [Name_Of_App_To_Remove] -> MORE -> Uninstall updates. NOTE: App will disappear arter reboot and will be visible even in Titanium Backup!
2. If you perform "Wipe data" directly before installing SuperSU and my SYSTEMLESS DevBase (before you let to install app's updates) - then all apps listed below will be removed. If you would like to use any of these apps - just install it manually from appropriate store. Installed manually app will not be removed during the next DevBase update or re-install.
Removed apps list (depends on the device, should cover all devices starting from Galaxy S5):
ChatON
Chrome
Drive
Dropbox
EditorsDocs
Evernote
Excel
Facebook
FB Messenger
FB Pages Manager
Flipboard
Google+ / Photos
Group Play
Hangouts
Instagram
OneDrive
OneNote
PEN.UP
Play Books
Play Games
Play Movies
Play Music
Play Newsstand
PowerPoint
Skype
Smart Remote
WhatsApp
Word
NEW! Safe De-Bloat feature automatically detects and systemlessly removes apps not listed above, but present in your CSC package
3. Systemless CscFeature MOD (enabled some built-in, hidden features):
- Added shutter sound menu in Camera app
- Sending/receiving MMS without data on
- Show SMS/MMS sending time instead of receiving
- Added "Exit Internet" option to stock browser
- Added call button in Phone Logs (**)
- Added "Call/Message block" option in Settings
- Added symbols as secondary keys in Samsung keyboard (**)
- Call Recording (added "Record" button, auto record calls - starting from Nougat)
(**) may not work starting from Android 7.0 Nougat
Installation:
1. FlashFire app (recommended ***):
- Open file using "Flash ZIP or OTA" option
- UNTICK "Mount /system read/write" [extremely important for working OTA!]
- Enable "EverRoot" -> "Inject SuperSU" option if necessary (see NOTE above (*))
- Tap "FLASH"
2. TWRP recovery:
- Tap "Keep Read Only" on the Welcome screen [extremely important for working OTA!]
- Open file using "Install" option (use extSdCard or OTG storage in case of encrypted /data)
- Confirm flash by swiping right
- Tap "Reboot System"
NOTE1: One additional auto-reboot may be performed at first boot. It is not a bug (may be required for systemless build.prop support - see Tips & Tricks for more explanations)
NOTE2: Do not worry about red "mount /data failed..." messages displayed in TWRP in case of encrypted /data (installer will do the work anyway!)
(***) As far as I know - FlashFire is the only flashing tool with full access to /data during flash in case of encrypted devices. It is also the only tool which allows you to perform full backup/restore of partitions, including encrypted /data. It does NOT require custom recovery to work!
Credits: @Chainfire for systemless SuperSU and a lot of inspiration
Hit Thanks button if you like my work. If you really appreciate my work - feel free to buy me a beer
Download
>> Recent SYSTEMLESS DevBase <<
Note:
Check MD5 sum BEFORE flash (useful TOOL), because flashing damaged or incomplete ZIP files can lead to issues! Correct MD5 sum is shown on the AndroidFileHost website while downloading.
Changelog
Please visit MAIN THREAD - post #3
Tips & Tricks
1. OTA updates:
- Basically, the only thing you need to take OTA update is to perform "Full unroot" in the SuperSU app. However, a better way is to use "unroot2ota" terminal command, because this will not remove DevBase boot script from /su/su.d and the only thing you will need to re-activate SYSTEMLESS DevBase (and all your systemless MODs) after performing OTA update is just re-root your device with CF-Auto-Root.
- If you flashed custom recovery like TWRP - it is mandatory to restore your stock recovery (otherwise OTA will not work). You can do it using FlashFire app (the easiest way) - just open recovery.img file (extracted from your original FW) using "Flash firmware package" option, disable "Preserve recovery" option and then tap "FLASH". EDIT: Starting from version v1.2 there is a new "unroot2ota" feature which allow you to restore stock recovery using /system/recovery-fromm-boot.p file. There is no guarantee to perform it successfully (even if there is no error message) but in most cases it works well (tested on Nougat beta). Please go to recovery before you try to get OTA to check if you have stock recovery already after performing "unroot2ota" (if not - you need to use PC Odin to flash recovery.img packed in tar file).
- It is recommended to temporarily disable "Auto-update apps" in Play Store settings before you unroot your device. It will prevent updating applications covered by Safe De-Bloat list, as there apps will temporarily appear until you re-root the phone after performing OTA update.
Note (devices which use dm-verity): You should never allow /system modifications in TWRP, never allow to remount /system r/w in any app (e.g. Root Explorer, FlashFire, etc.) and never flash a ZIP file which could modify your /system or remount it r/w. Failure to follow these recommendations will break dm-verity verification and will cause, that your device may not be able to boot with the stock kernel (you will need to re-flash your original FW using PC Odin to make your device bootable).
2. Making your own modifications:
- You can systemlessly replace any existing system app by modded one. Just put modified app to /data/devbase/system/app or /data/devbase/system/priv-app and then reboot your device
- You can systemlessly replace jar or apk in /system/framework. Just put modified one to /data/devbase/system/framework and then reboot your device (NOTE: framework support has been added for advanced users -> there is high risk of bootloop if you do something wrong!)
- You can systemlessly add or override any line in /system/build.prop. Just put (only new or changed) line to /data/devbase/system/build.prop and then reboot your device (NOTE: one additional auto-reboot will be performed if /data/devbase/system/build.prop file has been added, modified or removed. It is not a bug - it is required for the changes in /data/devbase/system/build.prop to take effect!)
- You can systemlessly replace any existing file in /system/csc and /system/etc (but NOT in subdirectories). Just put modified copy of a file to /data/devbase/system/csc or /data/devbase/system/etc and then reboot device
Limitations: original app or file MUST physically exist with the same name in /system, you can NOT add a new app or file this way!
Example 1 (Ad-Blocking): Download the latest Ad-Blocking ZIP installer from THIS thread. Extract "hosts" file (placed in /system/etc inside ZIP file), then copy it to /data/devbase/system/etc, set rw-r--r-- (644) permissions and then reboot device
Example 2 (modded SystemUI): Create "SystemUI" directory in /data/devbase/system/priv-app and then put modified "SystemUI.apk" file into it. Set rwxr-xr-x (755) permissions to "SystemUI" directory, rw-r--r-- (644) permissions to "SystemUI.apk" and then reboot device
Example 3 (De-Bloating a bit more): You can just create empty directories in /data/devbase/system/app (or priv-app) corresponding to applications in /system/app (or priv-app). Alternatively (more advanced method), you can add an app to modded enforceskippingpackages.txt file (you can find it in /data/devbase/system/etc or /data/devbase/system/csc_contents, depending on the original location in /system) and increase number in the 1st line. Second method should not be used by beginners (without a basic knowledge related to UNIX text format)
3. How to manually maintain the newest ROM version:
If you do not care about OTA - you can manually update your device to the newest ROM available @ Sammobile, keeping your original CSC (you need multi-file original FW, I mean separate files for BL/AP/CP/CSC). You need to download 2 ROMs: ROM with the newest changelist and the latest ROM containing your original CSC. Extract both and open in PC Odin BL/AP/CP files from the ROM with highest changelist but open CSC file from the ROM containing your CSC (I recommend to use HOME_CSC_* file to avoid auto-wipe-data). Flash such "mix", re-root and enjoy
Optional MODs
I put some of my favorite MOD's. These modifications I have done personally using (bak)smali tools - these are NOT "borrowed" from other custom rom, nor from someone else's thread (thanks to @majdinj & @tdunham for their excellent modding guides). All files are FlashFire / TWRP flashable ZIPs.
These MODs are compatible with SYSTEMLESS DevBase - installer will try to detect if your /system has been moddified (or not) already. If the installer will not detect any popular /system modifications like SuperSU / busybox / Xposed (installed to /system) then will try to install app systemlessly to /data/devbase/system/(priv-)app
1. Modified Camera app:
- Full functionality of the Camera app in low battery
2. Modified Messages app:
- Disabled SMS delivery notifications (*)
(*) If you long press a message you can still check if the message has been delivered or not, we do not need to see and hear notifications for every sms. It's annoying to me!
>> MODs for G93xF (Marshmallow) << (**)
>> MODs for G93xF (Nougat) << (**)
(**) Original apps come from stock ROM for G935F, but these MODs should work on all S7 flat & edge variants (Exynos based)
In case of MODs installed to /system - you can restore original apk using backup stored in /data/alexndr/backup
sorry i just want to make sure i understand what this is... I can install magisk root and xposed while also being able to encrypt my phone?
I was a big fan of your work on the S5, good to see than you're now working on S7
First question, can i play PoGo with root using this rom ?
I will try this soon, thanks for your work !
GbizzleMcGrizzle said:
sorry i just want to make sure i understand what this is... I can install magisk root and xposed while also being able to encrypt my phone?
Click to expand...
Click to collapse
You can use Magisk but only with SuperSU. I'm not sure if you can encrypt already decrypted device (just not tested it as my S7 was always encrypted)
Tamos42 said:
I was a big fan of your work on the S5, good to see than you're now working on S7
First question, can i play PoGo with root using this rom ?
I will try this soon, thanks for your work !
Click to expand...
Click to collapse
This work is not for bypass root detection - try magisk hide or suhide (but AFAIK it does not work anymore with the latest FWs)
BTW. There is new version available
Changelog
v1.1:
- Added SYSTEMLESS support for /system/framework
- Added SYSTEMLESS support for /system/build.prop (overrides & additions)
- Added major Android update detection (auto-remove mods for older API to prevent bootloops & FCs)
- Added BusyBox bionic (the most stable and respected release)
- Added logging to /data/devbase/last_boot.log (API & errors)
- Added SuperSU boot patcher version checker (exits su.d boot script if < 2.76)
- Added "Please DO NOT wipe /cache" warning in case of encrypted devices and TWRP recovery
- Minor changes & optimizations in the shell code
- Added SYSTEMLESS DevBase uninstaller
Download link:
>> SYSTEMLESS_DevBase_v1.1.zip <<
Since new version has many more features -> there are more possibilities of bootloop (especially if you are playing with framework mods). I have created DevBase remover to let you get out from bootloop. Of course uninstaller does NOT "know" which mod caused the problem, so it will not remove any file from /data/devbase directory, it will remove only /su/su.d/0000000devbase boot script to make your device bootable (again) so you can manually delete problematic mod:
>> SYSTEMLESS_DevBase_remover.zip <<
MODs section (#5) has been updated
>> MODs for G93xF (Nougat) << (**)
(**) Original apps come from stock ROM for G935F, but these MODs should work on all S7 flat & edge variants (Exynos based)
Another update
v1.2:
- Added info in Settings/About device/Software info/Build number (can be overrided by editing /data/devbase/system/build.prop)
- unroot2ota: added ability to restore stock recovery using /system/recovery-from-boot.p file (no guarantee)
- unroot2ota: check /system partition for common modifications before unroot
- Minor changes & improvements in the shell code
Thread update:
- added screenshots (see original S7 edge thread)
- updated description (e.g. auto record calls - starting from Nougat)
- removed "Stock recovery" requirement from "Prerequisites" (due to new unroot2ota ability)
Another update:
v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)
>> SYSTEMLESS_DevBase_v1.3.zip <<
Thanks a lot for this ! I will test it once android 7 is out for the s7.
how to convert asus rog phone 6 pro chinese version to global rom?
root the phone then flash it, but i dont think there is anyway to root it
concorduser said:
root the phone then flash it, but i dont think there is anyway to root it
Click to expand...
Click to collapse
until now still dont have 1 proper guide to root for 6 pro
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
tuannghia1985 said:
I can not found any Official guide for How to convert. Old method worked for Rog 2 is not work anymore on Rog 6.
Found COUNTRY code file and already modified it into WW but fingerprint appeared on phone still remain at CN (with re-flash the whole system package (holos - dallas/texas.raw).
But you can still do following step to gain Device is certified on Play Store and eat FOTA update.
1. Flash WW rom (full rom not OTA), finish all set up.
2. Root your phone, by using Magisk.
(unlock bootloader via official apk from Asus, install Magisk Manager.apk, copy and place original boot.img on your phone and use Magisk Manager on phone to patch it, using CMD and fastboot command on PC to flash boot magisk patched.img, now you have rooted phone with magisk.)
3. With root explorer, navigate to /vendor/factory/COUNTRY open and edit CN to WW.
4. Re-flash WW if you want to make sure if there is any change on your phone. (My vendor fingerprint still not changed into WW).
5. Now you have WW rom on tencent hardware but Play store remain "Device is not certified".
6. Install termux and some modules on Magisk as: MagiskHide Props Config (must have), SElinux permissive (optional), Systemless Hosts, Universal SafetyNet Fix (must have), zygisk - SUI (optional).
7. After reboot your phone, come back to Magisk to make sure MagiskHide Props Config is properly installed. Then open Termux and typing:
su
props
- A short list is appeared on Termux, and you typing 1 to choose option "1 - Edit device fingerprint." then enter
- Choose "f" next to pick option "f - pick a certified fingerprint". then enter
- Choose next "1" to pick up "Asus". then enter
- Choose next "2" to pick up "ROG phone 5" then enter
- Choose next "Yes" to confirm and reboot phone.
Your phone is going to reboot and do a normal clear cache/data with Play Store to force Play Store recognize new status of your phone. Even download and install safetyNet test/check to make sure every thing is green.
Now your phone could eat up FOTA update, not OTA update. But please re-do the patched boot.img with Magisk Manager everytime you do an update by FOTA.
PS: difference between FOTA and OTA is:
FOTA - download update file from Asus HomePage, place it on root of your /SDcard folder, reboot phone and an update notification will show, do an update and it will success.
OTA - download directly via system/system update.
I will add credit later. All that works above is not belong to me.
Click to expand...
Click to collapse
thanks