***THIS GUIDE DOES NOT WORK. THIS SIMPLY ALLOWS CARDS TO BE ADDED TO ANDROID PAY. PAYMENTS WILL NOT PROCESS. THIS IS A WORK IN PROCESS.***
Unfortunately us rooted users are unable to use Samsung Pay. Samsung Pay is superior to Android Pay due to its MST feature which allows the use of any card reader to take payments from the phone. Samsung Pay as of this time doesn't support a lot of cards, So Android Pay is a great backup. Just as Samsung tries to stop rooted users from using Samsung Pay, Google tries to stop them as well by blocking Android Pay. This guide will show you how to get around that.
1.) You need a non rooted phone to start.
You can either flash your Note 5 completely back to stock, or use another phone to do it. Whichever phone you use MUST be able to be rooted or this will not work. This guide will assume you will use a second device to setup Android Pay, as I did, so that you don't have to wipe your Note. If you use your Note 5 to do this, just modify the guide as needed.
2.) Download the Android Pay app from the Playstore to your non-rooted phone
3.) Setup Android Pay application fully with all your bank cards and info
4.) Force close Android Pay app
5.) Root the device
6.) Install Titanium Backup
7.) Make a backup of the Android Pay app using Titanium Backup
8.) Move the Titanium Backup folder to either a computer or OTG drive
- If you only backed up Android Pay, there should be 3 files inside of the folder.
9.) Move your Titanium Backup folder to your rooted Note 5
10.) On the Note 5 download and install Titanium Backup
11.) Open Titanium Backup and select: menu - preferences - backup folder location
- Point the backup folder location to wherever you moved the Titanium backup folder to on the phone.
12.) Close and reopen Titanium Backup if it does not automatically do this when you exit settings
13.) Select menu again and then "batch actions"
14.) Select restore missing apps with data
- Android Pay should be the only app being restored
15.) After the app is restored, DO NOT OPEN IT.
16.) Open the superSU app and select: settings - "Enable Superuser" (uncheck the box) and let it finish
17.) Reboot
18.) When the phone boots up, open Android Pay and set it up as normal
19.) Open the superSU app and select: settings - "Enable Superuser" (check the box) and let it finish
20.) Reboot
21.) Done.
I do not think it'll work when making a purchase...
You can install "cigital safety net playground" from the play store to test if the state of your phone will allow it to pass Android Pay verification.
I my experience (I was using Android Pay on a rooted Moto X 2015), the only way to get Android pay to work with root, is to use Chainfire's systemless root and NOT to modify anything "major" in the system (host file and minor files edit are okay, replacing or adding a system app breaks it)
Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.
seh6183 said:
Hmm, the app says failed. I will test the pay function right now. I just need to run to the store.
Click to expand...
Click to collapse
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Remove the folder "/su/xbin_bind" and reboot for Android pay compatibility
- Try "Cigital safety net playground" it should pass.
timeToy said:
Yup... no surprises there.
Now try this:
- Back to stock, unlocked bootloader
- Install and setup your cards in Android pay
- Install TWRP or any custom recovery
- Try rooting with the latest systemless root (you may have to force a systemless install by typing "echo SYSTEMLESS=true>>/data/.supersu" on shell before install the zip in TWRP)
- Try "Cigital safety net playground" it should pass.
Click to expand...
Click to collapse
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.
seh6183 said:
Isn't systemless for android 6.0+ only and the kernel has to support it? I have it on my nexus but didn't think it was possible on the note.
Click to expand...
Click to collapse
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"
timeToy said:
From the man himself in the linked thread: "If on Android 6.0 or Samsung 5.1, the ZIP installer will install SuperSU in systemless mode and patch the boot image (...)"
Click to expand...
Click to collapse
This is amazing news and will be implementing this immediately.
Yup it failed at the card swiper.
{
"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"
}
Booted to CWM and flashed "unsu.zip" which removed all superuser from the phone. Then flashed beta 2.61 because they say it's the last working version for Android Pay. I rebooted from CWM and chose not to install root. When it Booted the phone was not rooted. I don't have a folder in /data. Supersu says this when I open it:
Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.
seh6183 said:
Wiped everything and reflashed my rom and still doesn't work. I am getting this error in CWM after flashing the superSU zip:
- Extracting ramdisk
--- Failure, aborting
I'm going to Odin back to stock and try again.
Click to expand...
Click to collapse
About the ramdisk issue, make sure you have the stock kernel and use the latest version v2.65, it fixed a lot of compatibility issues. To enable Android pay compatibility on v2.65 you need to delete the folder "/su/xbin_bind" and reboot.
I am not yet able to test this (waiting for my Samsung promos to go trough before messing up with KNOX), but Chainfire's himself is reporting it working:
Chainfire said:
(...)It's working great on my Note5 (G920T) on OJ5 and S6 on OI9(...)
Click to expand...
Click to collapse
I got systemless root installed.
My kernel (Arter) wasn't compatible with the systemless flash and that was causing the error. Had to switch back to ext4 and flash a modified stock kernel to get it to work.
Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again.
The only way I can get it to work is totally stock. That's boring. I need at least a custom rom. I was thinking that maybe I can flash my rom, flash unsu.zip, my kernel, and then somehow Odin my stock recovery back. Then setup android pay, then reboot and go back to a custom recovery to flash root.
Thoughts?
Flashed stock recovery and rebooted. Android pay still didn't work. Rebooted and flashed stock kernel and now it hangs on the first splash screen lol
Back to the drawing board. Going to ODIN back to stock and try different kernels I guess.
seh6183 said:
(...)Now here's the problem. You can't flash a custom rom without a custom recovery and you can't boot with a custom recovery unless you have a modified kernel. So that means you need a kernel and recovery at minimum if you want a custom rom. Once you install those 3 android pay fails to work again. (...)
Click to expand...
Click to collapse
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...
timeToy said:
Android pay will ONLY work with a 99.9% stock system partition. (no custom ROM that I know of)
Maybe this can work:
- Back to 100% Stock
- Install custom kernel and custom recovery
- Reboot into recovery, then install stock Kernel, no reboot, then flash systemless root, no reboot, then flash back stock recovery, then reboot.
That should get you systemless root with Android pay. No ability for full ROMs but the ability to run an Ad Block and disable the bloat...
Click to expand...
Click to collapse
My rom is a stock deodexed, debloated rom. I am trying something, well two things, that may get me working. Otherwise I am confident that I can get a stock rom, debloated myself, systemless root, custom kernel, xposed, and android pay all working. I can live with that. I will update my guide when I make it happen.
So far the things to remember is that systemless root needs a certain kernel format to be able to flash, and android pay needs certain things in the rom to be present or it wont work. I know the chroma rom for nexus devices has working android pay with systemless and its heavily modified. I doubt the dev will share how he did it though
Didn't work. Can't get any modified rom to work. I just booted two different roms with a stock kernel and stock recovery and it failed the safetynet check. Wiped all and am reflashing stock as I write this and will do it one step at a time to see what causes the safety check to fail.
Flashed a stock rom with ODIN and booted. It passed safety check. Flashed CWM recovery and it passed. As soon as I flashed a custom kernel it failed the check and I haven't even gotten to the rooting part yet. As of right now I don't want to give up a rom AND a kernel simply for android pay. I will be updating this guide to have the mods take it down.
Related
How to Root, Install TWRP (Custom recovery) & Install Xposed Framework on Samsung Galaxy J7 (SM-J700F))
Even though the tutorial is just for J7 Sm-J700F, it should work for for all the Exynos variants of J7, that is J700H and J700M !
Disclaimer
Your warranty is now void.
Flashing firmware void your device warranty. You alone are responsible for any consequences that might occur during the process. I am not responsible for any bricked devices.
Preparations
Enable USB Debugging on your phone:
This is very important thing to be done before you try flashing a firmware or recovery file. USB Debugging mode make Android devices receptive to download and send data over USB cable connection. If you do not know how to turn debugging mode ON, do this:
Go to Settings> About Device.
Scroll down to find Build number and tap it 7 times.
{
"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"
}
You will see a message that “Developer mode has been enabled” on your device.
Now go back to Settings panel and you will find a new item called Developer options there.
Tap it and go to USB debugging option and check the box to enable it.
Enable OEM Unlock: Go to Settings> Developer Options> and turn on OEM unlock.
Install Samsung Android USB Driver for Windows to your Laptop/PC
Steps to root your phone:
1) Download Odin, TWRP Recovery & SuperSU file to your Laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+home+power buttons at the same time for about 6-8 secs)
4)Press the Volume up button to continue.
5)Open the ODIN file you downloaded on your Laptop/PC. (By Double-clicking the Odin v3.10.7.exe file. This will open an Odin window.)
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the recovery file (twrp-2.8.7.0-j7elte_2.tar) you downloaded.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the recovery flashed successfully. It will boot into recovery.
11) Swipe to Allow Modifications. Click on Reboot then System.
12) Copy and place downloaded SuperSU file to your external SD card.
13) Turn off your phone.
14) Reboot to recovery (by pressing Volume up+home+power buttons).
15) The recovery will start. Select 'install zip'.
16) Click on Storage to change from Internal Storage to Micro SDcard.
17)Select SuperSU which you downloaded. Swipe to Confirm Flash. Flashing process will start. Once Completed. Wipe Cache/dalvik.
18) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy J7 !!!
Install Xposed Framework on J7
Most Android users mainly root their devices only to install Xposed Framework. Xposed Framework is a powerful tool that enables you to modify your ROM as you wish using some tweaks. Xposed Framework can be installed not only on Custom ROMS but also on the Stock ROMS. So using Xposed you can add some tweaks to your Stock ROM or firmware and get the features of a custom ROM.
Official build of Xposed framework for Lollipop Samsung Galaxy Devices has not been released yet, since Samsung made a lot of changes to ART (Android Runtime) without providing the sources. So we have the unofficial build now and we need to flash the Framework (SDK.zip) rather than just installing the Apk like in other versions of android so as Jelly Bean and Kitkat (Where the Xposed installer apk file would install the framework on your system automatically.)
Preparations
1. Make a nandroid backup using TWRP (in case if anything goes wrong) before installing Xposed Framework.
With the Nandroid backup (which is an excellent feature on custom recoveries like TWRP) you can backup all your current state of your operating system on your device and save it in your SD card or on your Computer storage and restore it at anytime you want. Many people will have perplexity that, If their Stock ROM (Firmware/OS) is rooted would it be able to do a backup of their OS and can able to restore it?. Yes you can do backup of the current state of your firmware with the custom recoveries like TWRP no matter your OS is rooted and made changes by using root.
Steps to to install the Xposed Framework for Galaxy J7
1. Install Xposed Installer App
2. Download & copy the Xposed file and the Xposed Uninstaller to your sdcard
3. Go to TWRP select Install and navigate to Xposed file "xposed-vxx-sdk22-tw-arm-custom-build-by-wanam-xxxxxxxx.zip" Make sure you select the storage as Micro SDcard in the above when you navigate to find the Xposed Framework file to flash (install through TWRP).
4. Reboot It takes a little time to boot up as it want to update our Android System.
Enjoy the Xposed framework on your Samsung Galaxy J7 !
Credits: @rovo89 @wanam
How to use Xposed Installer
1. Go to Xposed installer app on your phone and select Download.
2. Download and install the different modules you want to tweak your phone. After downloading a modules please don't open the app untill you enable it on Xposed framework by going to Module section on xposed installer app and selecting it on the check box there. Then retstart your phone to use the module you have installed.
All the Exposed modules listed on the download section won't work for Samsung Lollipop Stock based Roms. Please refer the the screen shot above to see the Modules that I use on Xposed framework.
Downloads
1. Samsung Android USB Driver for Windows
2. Odin3_v3.10.7
3. Recovery - TWRP-3.0.2-0-j7elte-j7elte.img.tar
4. UPDATE-SuperSU-v2.65-20151226141550.zip
5. Xposed Installer App
6. Xposed file
7. Xposed Uninstaller
sharvinzlife said:
Enjoy the Xposed framework on your Samsung Galaxy J7 !
Credits: @wanam
Click to expand...
Click to collapse
Thanks for the credits, but when it comes to Xposed, the first person you should thank is @rovo89 , i'm just adapting his work to Samsung devices.
Edit: and please do not mirror my files.
wanam said:
Thanks for the credits, but when it comes to Xposed, the first person you should thank is @rovo89 , i'm just adapting his work to Samsung devices.
Edit: and please do not mirror my files.
Click to expand...
Click to collapse
Post edited, Included the credits for @rovo89 ! Sorry for mirroring your files, I did that only because once you actually update the Xposed files on your OP, the links will be invalid, so I might have to always alert to update my OP with correct links again ! Thanks for suggestion, have the best day @wanam :good:
Does unlocking bootloader factory reset the phone?? Is there any way of taking this back up with samsung stock recovery??
It resets in xperia. Dnt knw abt samsung
When I am trying to enable a module ..it says Xposed Farmework Did not Installed
The_Runner said:
Does unlocking bootloader factory reset the phone?? Is there any way of taking this back up with samsung stock recovery??
It resets in xperia. Dnt knw abt samsung
Click to expand...
Click to collapse
No it doesn't factory reset the phone. As far I know you cannot take the nandroid backup using Stock Recovery !
Prasuram said:
When I am trying to enable a module ..it says Xposed Farmework Did not Installed
Click to expand...
Click to collapse
You may have not installed the framwork file correctly through TWRP (SDK file from @wanam), Did you even try installing the framework file, what did it say, when you did it ?
sharvinzlife said:
How to Root, Install TWRP (Custom recovery) & Install Xposed Framework on Samsung Galaxy J7 (SM-J700F)
Disclaimer
Your warranty is now void.
Flashing firmware void your device warranty. You alone are responsible for any consequences that might occur during the process. I am not responsible for any bricked devices.
Preparations
Enable USB Debugging on your phone:
This is very important thing to be done before you try flashing a firmware or recovery file. USB Debugging mode make Android devices receptive to download and send data over USB cable connection. If you do not know how to turn debugging mode ON, do this:
Go to Settings> About Device.
Scroll down to find Build number and tap it 7 times.
You will see a message that “Developer mode has been enabled” on your device.
Now go back to Settings panel and you will find a new item called Developer options there.
Tap it and go to USB debugging option and check the box to enable it.
Enable OEM Unlock: Go to Settings> Developer Options> and turn on OEM unlock.
Install Samsung Android USB Driver for Windows to your Laptop/PC
Steps to root your phone:
1) Download Odin, TWRP Recovery & SuperSU file to your Laptop/PC.
2) Turn off your phone.
3) Go to download mode (by pressing Volume down+home+power buttons at the same time for about 6-8 secs)
4)Press the Volume up button to continue.
5)Open the ODIN file you downloaded on your Laptop/PC. (By Double-clicking the Odin v3.10.7.exe file. This will open an Odin window.)
6) Connect your phone to your laptop/PC through USB cable.
7) When ODIN detects your phone, It will show added in the Log.
8) In ODIN click on AP and then select the recovery file (twrp-2.8.7.0-j7elte_2.tar) you downloaded.
9) Click on start. The flashing process will start.
10) If the flashing succeeds, ODIN will show 'PASS'. That means the recovery flashed successfully. It will boot into recovery.
11) Swipe to Allow Modifications. Click on Reboot then System.
12) Copy and place downloaded SuperSU file to your external SD card.
13) Turn off your phone.
14) Reboot to recovery (by pressing Volume up+home+power buttons).
15) The recovery will start. Select 'install zip'.
16) Click on Storage to change from Internal Storage to Micro SDcard.
17)Select SuperSU which you downloaded. Swipe to Confirm Flash. Flashing process will start. Once Completed. Wipe Cache/dalvik.
18) After it finishes, go back and reboot your phone.
Enjoy your rooted Samsung Galaxy J7 !!!
Install Xposed Framework on J7
Most Android users mainly root their devices only to install Xposed Framework. Xposed Framework is a powerful tool that enables you to modify your ROM as you wish using some tweaks. Xposed Framework can be installed not only on Custom ROMS but also on the Stock ROMS. So using Xposed you can add some tweaks to your Stock ROM or firmware and get the features of a custom ROM.
Official build of Xposed framework for Lollipop Samsung Galaxy Devices has not been released yet, since Samsung made a lot of changes to ART (Android Runtime) without providing the sources. So we have the unofficial build now and we need to flash the Framework (SDK.zip) rather than just installing the Apk like in other versions of android so as Jelly Bean and Kitkat (Where the Xposed installer apk file would install the framework on your system automatically.)
Preparations
1. Make a nandroid backup using TWRP (in case if anything goes wrong) before installing Xposed Framework.
With the Nandroid backup (which is an excellent feature on custom recoveries like TWRP) you can backup all your current state of your operating system on your device and save it in your SD card or on your Computer storage and restore it at anytime you want. Many people will have perplexity that, If their Stock ROM (Firmware/OS) is rooted would it be able to do a backup of their OS and can able to restore it?. Yes you can do backup of the current state of your firmware with the custom recoveries like TWRP no matter your OS is rooted and made changes by using root.
Steps to to install the Xposed Framework for Galaxy J7
1. Install Xposed Installer App
2. Download & copy the Xposed file and the Xposed Uninstaller to your sdcard
3. Go to TWRP select Install and navigate to Xposed file "xposed-vxx-sdk22-tw-arm-custom-build-by-wanam-xxxxxxxx.zip" Make sure you select the storage as Micro SDcard in the above when you navigate to find the Xposed Framework file to flash (install through TWRP).
4. Reboot It takes a little time to boot up as it want to update our Android System.
Enjoy the Xposed framework on your Samsung Galaxy J7 !
Credits: @rovo89 @wanam
How to use Xposed Installer
1. Go to Xposed installer app on your phone and select Download.
2. Download and install the different modules you want to tweak your phone. After downloading a modules please don't open the app untill you enable it on Xposed framework by going to Module section on xposed installer app and selecting it on the check box there. Then retstart your phone to use the module you have installed.
All the Exposed modules listed on the download section won't work for Samsung Lollipop Stock based Roms. Please refer the the screen shot above to see the Modules that I use on Xposed framework.
Downloads
1. Samsung Android USB Driver for Windows
2. Odin3_v3.10.7
3. Recovery - TWRP-3.0.0-0-j7elte-j7elte.img.tar
4. UPDATE-SuperSU-v2.65-20151226141550.zip
5. Xposed Installer App
6. Xposed file
7. Xposed Uninstaller
Click to expand...
Click to collapse
Is it work on Samsung Galaxy J700H
Kindly upload a full list of module that will work on j700f
durrjunaid said:
Is it work on Samsung Galaxy J700H
Click to expand...
Click to collapse
Even though the tutorial is just for J7 Sm-J700F, it should work for for all the Exynos varriants of J7, that is J700H and J700M !
Xposed Files (in list to download) not work here. Invalid link.
joaonds said:
Xposed Files (in list to download) not work here. Invalid link.
Click to expand...
Click to collapse
All the links have been updated, now it should work
ty bro
Does gravity box working?
gmanrapp said:
Does gravity box working?
Click to expand...
Click to collapse
Since it less or only partially works.. I don't use it !
My J7 2016 run 6.0.1, can root ?
kkkkkkkkkk
sharvinzlife said:
How to Root, Install TWRP (Custom recovery) & Install Xposed Framework on Samsung Galaxy J7 (SM-J700F))
Even though the tutorial is just for J7 Sm-J700F, it should work for for all the Exynos variants of J7, that is J700H and J700M !
Disclaimer
Your warranty is now void.
Flashing firmware void your device warranty. You alone are responsible for any consequences that might occur during the process. I am not responsible for any bricked devices.
Preparations
Enable USB Debugging on your phone:
very godddddddddddd .
Click to expand...
Click to collapse
Link to Xposed is invalid
Same here!
eladbuzaglo92 said:
Link to Xposed is invalid
Click to expand...
Click to collapse
same here!
Xposed file Invalid
{
"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"
}
Video about this tutorial please watching
https://www.youtube.com/watch?v=n-2XYEUNy1o
Hi guys,to make root in 5x in nougat is much easy
1 - Put your device in fastboot mode and Unlock your bootloader
https://www.youtube.com/watch?v=hwDwxy3Z7bQ (use this,or other video of you like )
2 - Download This Files
5x TWRP https://dl.twrp.me/bullhead/
ADB Tools http://files.androidpit.info/content/adb-tools_treiber.zip
SuperSU (Put in your memory this file to install in TWRP)
https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
3 - Extract "ADB Tools" and open all folders like this "adb-tools_treiber\adb-tools_treiber\adb-tools"
4 - Put TWRP "https://dl.twrp.me/bullhead/" in this folder
5 - in Windows 8 or 8.1,10 select "file,in top" and select open prompt command,and select open prompt command in administrator
6 - in "CMD" put this code :
fastboot flash recovery twrp-3.0.2-1-bullhead.img
7 - push volume down button 2x and push power button
8 - in recovery mode go to install,and select SuperSU2.76 after install select reboot system
9 -waiting your phone turn on
10 - Enjoy <3
Flashed, supersu app is there, but I still don't have root access?
It's already been mentioned in another thread that this does not work, at least not if you're encrypted.
pkadavid said:
It's already been mentioned in another thread that this does not work, at least not if you're encrypted.
Click to expand...
Click to collapse
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
jsgraphicart said:
I was told that encryption doesn't matter with the new TWRP that was released yesterday. Is that not true? I haven't tried it yet. Waiting for the Android N factory images to start clean.
Click to expand...
Click to collapse
You can give it a try. Looks like people have had mixed results. TWRP hasn't stuck for me, and I couldn't install SU. I've seen a few other posts with the same result.
Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.
pkadavid said:
Do you mind sharing your steps? I followed Heisenberg's instructions however TWRP didn't stick, and SU didn't install. Thanks!
Click to expand...
Click to collapse
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.
Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.
Ryandos said:
I decided to boot into TWRP instead of flashing it; instead of "fastboot flash recovery twrp.img", I just did "fastboot boot twrp-3.0.2-1-bullhead.img". This booted my 5x into TWRP without flashing it.
After that I flashed supersu-2.76.zip through twrp the usual way and rebooted. Obviously my twrp didn't stick but I'm not sure why or how this method succeeded in rooting.
Click to expand...
Click to collapse
I resolved the issue with these steps. Looks like something was messed up after I upgraded from 6.0.1 to 7 yesterday using the beta program. I noticed something was wrong because changes to the system UI via the stock settings (% in battery) didn't stick. A factory reset solved it.
1. factory reset (stock, encrypted)
2. install twrp -1 (it has stuck so far after two reboots) - https://dl.twrp.me/bullhead/
3. install su 2.76 (confirmed rooted) - http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:30 AM ---------- Previous post was at 12:24 AM ----------
jsgraphicart said:
Is the SuperSU linked in this thread systemless root? If not, is systemless root available for the Nexus 5X? Chainfire creates so many threads I can't keep up with what's the latest and what's systemless and not systemless.
Click to expand...
Click to collapse
It automatically installs systemless on newer versions of Android. Use the one below, and you'll be fine.
http://forum.xda-developers.com/showthread.php?t=1538053
---------- Post added at 12:32 AM ---------- Previous post was at 12:30 AM ----------
Nightshadow931 said:
Well, I did the same, did you flash supersu linked in the op?
Btw, twrp didn't stick for some reason first time I installed it(I unlocked bootloader, flashed twrp through fastboot, rebooted in twrp, and it worked. However, after I rebooted into the system, I couldn't boot back into twrp. It said 'no command'.)
Then I flashed it again with the same method, rebooted the system, and tried to boot back into twrp, and voila, now it did stick.
Weird.
Then I flashed supersu, the one linked in the op, and I've got supersu app, but as I said, no root access.
Click to expand...
Click to collapse
Try the steps in my post above. I had the same thing happen. You'll have to do a factory reset.
Actually, seems like I have root access. Root checker says I do have it, the app I tried(quickboot) couldn't acquire root access at all. I guess it's because of the systemless root?
Only systemless root is available on 5X?
If you want Android Pay to work, then you need to do the following.
Flash Magisk.
Flash phh's SuperUser 17 (Magisk Version).
Install phh's SuperUser from the Play Store.
Then when you want to use Android Pay, temporarly disable root with Magisk Manager.
It would do you some good to read those thread's to see how things work. You can discuss Android Pay/magisk here.
Should go without saying you need to unlock and install twrp before you do any of this.
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I can confirm that, I did completely the same.
Including flashing TWRP two times through fastboot, and it works now.
Ryandos said:
I managed to root 7.0 earlier by booting into TWRP 3.0.2-1 (fastboot boot twrp-3.0.2-1-bullhead.img) and proceeding to flash the SuperSU zip from there. I have full root access and my device is encrypted.
Click to expand...
Click to collapse
The1nonly1 said:
I used this method as soon as I updated to Nougat. I flashed TWRP from fastboot, rebooted bootloader and then went to recovery to check it worked (and make nandroid backup) I then restarted system to make sure device was working, it was (NOT ROOTED YET). I then tried to boot into recovery from bootloader menu and I didn't have TWRP. I then flashed this again in fastboot, flashed SuperSU 2.76 from TWRP, restarted phone to check to see if root works and it did. I have since turned phone off and on twice and TWRP is still there.
My device is still and always has been encrypted.
Click to expand...
Click to collapse
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root
ikyeye said:
I confirm this.
I'm using exactly same configuration (TWRP 3.0.2-1), flashed thru fastboot (fastboot flash recovery twrp-3.0.2-1-bullhead.img) and using SuperSU 2.76 systemless root
Click to expand...
Click to collapse
So what's new? This is usual procedure to root every android version on a Nexus: flash latest TWRP recovery, latest supersu, done.
This worked perfectly on the first try! Thank you
Sent from my Nexus 5X using Tapatalk
A short summary of upgrading my YotaPhone 2 to run Magisk v9 on the latest RU lollipop build (1.1.34) because I've seen no threads about Magisk here yet and writing my experience down might help others (or myself in the future).
Background: Got the phone last week from bestgear, and I'm surprised at how great it is. The EPD is much more responsive than I expected. And the phone looks just great! So much has changed/improved in the modding community in the last years (and I got out of touch with it), that I decided to go cutting edge with systemless Xposed through Magisk with root hiding, having no experience with either.
Lollipop
The phone had exactly the same about screen as in the lollipop upgrade thread so I sort-of followed that and subsequently went for the latest Russian version (RU1.1.134).
However, my setup prevented flashing directly to any of the 5.0 versions. The YotaPhoneFlasher showed that flashing /system failed (which can be seen by scrolling up on the prompt about flashing the user data). Probably due to the file size being too large. However, this procedure seemed to do the trick (see above thread for details):
Flash 5.0.0-RU1.1.124. Booting hangs at the 'Powered by Android' screen.
Flash 4.4.3-S01-003-RU1.0.3.61a. Booting succeeds.
Somehow, it now knows that it can perform an OTA update and proceeds through several versions to get to RU1.1.134
Not sure whether the RU version is worth it though, because it adds some bloatware like a Russian NFC payment app, a Russian air plane app and a dictionary app that primarily supports to/from Russian.
TWRP
Subsequently the recovery was flashed to TWRP 2.8.5.0. This seems a rather old version of TWRP though, perhaps too old to flash Magisk v9, see below. (This is my first TWRP experience as well, absolutely fabulous compared to older recoveries!)
Magisk
Magisk v9 refused to install directly. Flashing Magisk-v9.zip always ended up with either "E: footer is wrong" or "E:Error executing updater binary in zip". I tried to 'Install' from TWRP and to 'adb sideload' from both TWRP and modified stock recovery. Googling these errors lead me to believe that it might be related to the TWRP version. (The download was fine, because the zip file was exactly the same as the one that the Magisk Manager installed.)
In the end it was rather simple:
Flash Magisk-v8.zip
Install the magisk version of phh's superuser (and the corresponding Superuser app).
Install Magisk Manager
Upgrade Magisk to v9 from within the manager.
The "Emoji One" module proved that Magisk works (by replacing all the smilies). However, couldn't get Pokemon Go to login, so the root hiding might not work, but I didn't try PoGo before installing Magisk, so could be another issue.
Xposed
My actual goal was experimenting with Xposed, but the Xposed Installer keeps saying that the "Xposed Framework is installed, but not active." I'll keep you posted if I manage to get it working.
Some more notes:
A windows 10 laptop was used for all of the flashing (because the YotaPhoneFlasher software is windows only it seems).
Several reboots and cache/data wipings were omitted from the above. These did make the process take ages though, updating all the apps etc. all the time.
Thank you for all the information on this forum that let me get this far. I'm very happy with having a Lollipop YotaPhone with root.
Thank you for your detailed experience. I read the magisk thread here on XDA buy I didn't understand why is it for? And another question, why are you installing xposed? Are there benefits or special added features added to our Yotaphone?
I'm both new to Magisk and Xposed myself, and indeed it is not directly clear 'what these are for' from their xda posts. So I decided to just try them out and see for myself.
Xposed allows hundreds of modules to be installed to alter the OS in one way or the other. I'm most interested in Xprivacy, which should allow the user to limit what data / functionality apps can access and provides apps with mock data and such. Like a fine grained permission system I think.
Magisk also allows modules to alter the OS, but there seem to be only a handful, including Xposed. The selling point of Magisk is, if I understand correctly, that it does not alter the system partition. This makes it easy to apply future OTA updates etc. Supposedly it can also hide itself and root from certain apps.
It's not that important to me, so not sure whether I'll continue my exploration soon. (The Magisk threads are many, many pages, so it could take quite some research to get it to work properly.)
Did you get any further with Magisk & Xposed? My YD201 just arrived and I'm trying to decide how to proceed with hacking the crap out of it.
hippy dave said:
Did you get any further with Magisk & Xposed?
Click to expand...
Click to collapse
Not yet hippy dave. The Marshmallow beta came out soon after my initial experiments and I decided to wait for the official Marshmallow release before experimenting further. My concern was that I didn't want to redo the entire process every other week, and I messed something up so I can't boot to recovery...
The final Android 6.0 rom seems to take a while, so maybe it is worthwhile to continue with the latest beta. My plan is to first fix my recovery partition somehow, then upgrade to the latest Marshmallow beta, and then try Magisk again. I don't want to use the 'normal' system-partition-modifying Xposed because I like the cleanliness that Magisk promises. I haven't followed the Magisk development since, so maybe things have changed.
Your experiences would be welcome.
BlackShift said:
Your experiences would be welcome.
Click to expand...
Click to collapse
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc, so I tried Magisk out on the latest Russian LP. First I tried the latest release of Magisk 11.x, and then the latest unofficial source build 12.x, and tho it installed (with TWRP 3 latest version) and worked fine in terms of root, I couldn't get Magisk Hide to work and pass SafetyNet. Tried all the tips I could find like turning off USB debugging, turning things off & on in Magisk in a particular order with reboots in between etc. So I gave up for now and didn't get as far as trying Xposed for Magisk or any other modules.
For the time being I decided to go with the tried and tested stuff, standard root and regular Xposed, and will reevaluate when Marshmallow gets an official release or if I hear of improvements to Magisk Hide.
hippy dave said:
Makes sense, I decided to skip the MM beta for now and wait for release, but I couldn't wait that long to get root etc
Click to expand...
Click to collapse
The official MM came out a couple of days ago, but so far, no more success than you got.
Updated to MM. Forgot how, it refused to update over the air, so think I adb sideloaded the full 1.34 OTA with TWRP. Safetynet check from Magisk manager successful (of course).
Installed TWRP 3.0 and the official Magisk 12. However, the Magisk root seemed to have failed, also after a reboot. Safetynet check failed.
Installed SuperSU systemless by typing echo SYSTEMLESS=true>>/data/.supersu in the TWRP command prompt because SuperSU failed to install systemless automatically. Magisk Hide claims it doesn't operate that well with SuperSU, and safetynet check failed.
So Magisk and root access works, but not root hiding. Which kinda defeats the point of using Magisk. I didn't try many of the clever tricks you refer to though and I gave up for now. It is supposedly cleaner than other methods of rooting, so I'll keep it anyway. Next up is
(Not really relevant to this thread.) Getting 800Mhz band to work
Getting XPosed installed systemless.
Perhaps send a boot image to the Magisk team so they can improve the support for our yotaphones? Not sure how this process works.
Hi, has there been any more progress with Magisk and Yotaphone? My bank finally started using Android Pay, so I'm keen to have another crack at hiding root. I don't think there have been any changes to Yotaphone firmware since you last posted, but I don't know what progression there's been with Magisk. Maybe when I have the chance I'll try to send the Magisk people whatever they need to try and get it working.
I haven't made any attempts since last time and probably won't soon. Let us know if you are successful.
Ok I did a fresh install of the latest Russian MM (kept my data tho), installed the current Magisk release version (14.0), and it just worked straight off, Android Pay is running happily and root is working in the few root apps I've tried so far. Only downside so far is no Xposed, there's an unofficial Xposed for Magisk but it doesn't pass Safety Net so would presumably break Android Pay. I'm gonna see what Magisk modules are available and if they can fill the void, and decide from there I guess.
{
"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"
}
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.
hippy dave said:
Woop, finally got SafetyNet passing while Xposed is running (as slightly evidenced by the circle battery).
This wasn't straightforward, and didn't end up using Magisk. This is using SuperSU, suhide v0.55, and a patched system library (I had to patch the yotaphone one myself, let me know if anyone wants it).
The only quirk now is that the Xposed Installer doesn't see the xposed framework as installed/active, even tho the framework and modules are working fine. Gonna investigate that too, but can work around it for now. edit: Compiled my own version of Xposed Installer with tweaked paths and now it works fully.
Click to expand...
Click to collapse
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk
stanley321 said:
Would you please send me the patched library ?
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
Sure thing, I'll attach it to this post. You might know that you have to fix the file contexts when you replace the original library with the patched one - I'd boot into TWRP and use adb push to put the file into place, then adb shell and use the following command in the right directory:
chcon --reference=libandroid.so libandroid_runtime.so
{
"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"
}
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
It should work when you flash it, but using it is still a try at your own risk procedure.
Our device comes with forced encryption and, more important,
verity which checks at every boot if /system partition has been changed or not.
If /system has been changed, verity won't allow booting your device which means
you can't flash anything unless you disable verity.
So, you must be sure to keep /system in ReadOnly mode in TWRP and don't try to alter it unless you're using a custom Kernel/boot to disable verity.
Of course, custom ROMs come with custom boot, so no worries about verity security with Lineage or AOKP for example.
Click to expand...
Click to collapse
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is up on moto.shreps.fr.
Changelog:
twrp-3.0.3-n2-athene_shreps.img
- Kernel and boot update - should be compatible with more variant
- Some TWRP fixes
twrp-3.0.3-n1-athene_shreps.img
- Qseecom and crypto stuff updated to N
> I'm able to decrypt my /data partition (F2FS) - Tested on XT1650-03_NPL25.86-17-3
- Fully rebased on AOSP Recovery 7.1
- TWRP bump to 3.0.3, with a lot of fixes
- Dark Material Theme
- Removed cursor pointer
XDA:DevDB Information
[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z, Tool/Utility for the Moto Z
Contributors
Shreps
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2017-01-30
Last Updated 2017-03-07
[ROOT] How to root with latest N firmware NPL25.86-17-3
Simple procedure:
Unlock your BL
Flash this TWRP Recovery
Download the superuser zip (thanks to phh)
Flash it through TWRP
Reboot
Install phh's SuperUser app from play store
Enjoy
Shreps said:
Here is TWRP 3 for the Moto Z
I decided to open this thread and make unofficial builds because the official TWRP (3.0.2) is still based on MM and will not work properly with N Firmwares and ROMs.
Click to expand...
Click to collapse
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
erfanoabdi said:
Thanks for this, could you please patch this :
https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
To make supersu systemless root possible
Thanks again
Click to expand...
Click to collapse
Use superuser systemless root, has mentionned in post #2. It's safer.
Shreps said:
Use superuser systemless root, has mentionned in post #2. It's safer.
Click to expand...
Click to collapse
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
erfanoabdi said:
I added pull request for this
And I also built it : https://mega.nz/#!ScxHASjB!teSpEOZnO2cYej7W41sgTELAv3Z8-6qa6GH1z1mRwdI
I don't know why, but I hate phhsuperuser
Click to expand...
Click to collapse
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
[email protected] said:
I hate phhsuperuser too, but what is this recovery.img that you linked ?
in your images you show up SuperUser 2.78 R2, it works ? What happend with the release 2.59. I tried before and my phone don;t boot any more when I install SuperUser
Click to expand...
Click to collapse
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
erfanoabdi said:
My Link is TWRP recovery image
Here I installed SuperSU as systemless mode, which is always fails installation on official TWRP
In pictures I really only installed es explorer as root needed app and I didn't mess with SuperSU anymore not sure about other's
BTW I recommend to stay on phh's superuser
Click to expand...
Click to collapse
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Shreps said:
Again, it's safer to flash supersuser by phh, everything works out of the box
See post #2
Click to expand...
Click to collapse
Currently I'm using phh without any issue but FlashFire doesn't work with this, it requires SuperSU
silvercat said:
So using this recovery and forcing to flash in systemless mode boots into ROM? Because last time I tried system mode ended up in bootloop and systemless mode dint gain any root access
Click to expand...
Click to collapse
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
erfanoabdi said:
First at all I really don't recommend this root method, cause I didn't test it too much
But your answers:
There's no force just flash released superSU from chainfire this will flash in systemless
Before this recovery, old official one could not install SuperSU as systemless and it was stops on decompressing ramdisk, I just fixed installation part which is only related to TWRP bug
And force system (xbin) root still makes bootloop , as I know it's not about TWRP
Click to expand...
Click to collapse
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
kethsawant said:
Then according to you which method of Rooting is the Best or safe instead...or which TWRP & supersu file should be flash , if i am on Nougat updated through OTA
Click to expand...
Click to collapse
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
I tried that in Stock rom but ended up in bootloop..
erfanoabdi said:
I recommend to follow OP guide, it's safe
But if you like SuperSU use my TWRP and flash latest SuperSU
Click to expand...
Click to collapse
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
kethsawant said:
Pls provide the link of TWRP & Super SU you recommend (i am stock Nougat)
Click to expand...
Click to collapse
OK use my TWRP and flash this super su
This is not modded version just old version of stock superSU
Please test it and tell how is it.
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
paulnorinn said:
Is this only for N bootloader?
I am still on MM bootloader and got freezing screen on TWRP home. Could not touch/select the menu, had to flash back to official TWRP 3.0.2.
Click to expand...
Click to collapse
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Shreps said:
Hum yes, but should work too with MM bootloader. You can try to press power to shutdown the screen and then power or volume again to wake up and the touch should be initialized.
Click to expand...
Click to collapse
Ok, thats fix it. I can now touch the screen. Guess I have to do it on every boot?
Thanks for the tip.
OK I formatted my partitions in twrp and it was formatted as ext4. I read somewhere that the moto Z uses f2fs by default. Is this true and I just reduced performance of my phone because of a bug in twrp? I couldn't find an option to format as f2fs.
Hi,
I would like to do the last update for the Mi A1, but without losing the root. I'm rooted with CF-Auto-Root and SuperSu is installed without TWRP. How can I do? Possible with FlashFire?
Thanks.
AFAIK it isn't possible. There is a feature in MagiskManager that lets you root the OTA update in the second slot but its not working for our device yet. The same goes for FlashFire.
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
So, I too rooted my phone using the CF-Auto-Root. I tried to unroot through SuperSU, but it didn't work. I also tried to flash the boot.img, and that didn't work either. I'm new to all of this, and I don't really know what I'm doing.
How can I actually unroot this sucker?
What do you mean by it "didn't work"? What steps have you tried? You're not supposed to flash the CFAR boot.img, instead you should use `fastboot boot boot.img` to boot into it (don't do anything after it's run, it'll automatically boot), use FlashFire to flash the zip version of SuperSU (found here http://supersu.com/download), and then reboot normally on the phone.
justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
After the full unroot, all the apps that had access for root (eg. Viper4Android, BusyBox, SELinux, etc) will working again after the update?!
http://techintouch.it
The apps will work once the system is rerooted, but you'll need to authorize the apps in SuperSU again.
Can I use the SuperSu OTA survival mode? Maybe it works?
Ok, so here's what I did.
I followed kraatus90's guide to using CF-Auto-Root. I ran the .bat executable, and I rooted my phone. Everything works. I downloaded SuperSU from the Play Store to manage the apps.
I then tried to lock the bootloader, and got the "The system was destroyed" error. So, I had to unlock it again for the phone to function.
I went into the SuperSU app and tried to do the full permanent unroot, but all I got was "Uninstallation Failed"
So, then I went to find a stock boot.img, and got one.
Now, I don't know how to reverse what I did.
I tried booting into the stock boot.img from fastboot mode, and it looked like it worked because my rooted apps spotted working, but I wasn't able to download the latest security patch.
Those are the steps I did, and I don't know how to proceed further.
EDIT 1: So, after toying around with it some more, and trying to recover the stock.img in both FlashFire, and SuperSU, and trying to flash an external stock.img through fastboot, I think I know what the problem is.
{
"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"
}
I think that the A/B partitions are what are getting me in trouble. Do I need to change the active partition through fastboot? do I need to flash something to one of the partitions through FlashFire? What can I do?
EDIT 2: So turns out, you need to use fastboot flash boot_b boot.img, and then it'll work.
Can I flash the OTA file with FlashFire without losing root? I don't have TWRP installed and I'm rooted with SuperSu.
justin97530 said:
Just updated today, here's what I did
- Uninstall FlashFire (prevented update from installing)
- Performed full unroot in SuperSU
- Installed update and restarted
- Used Fastboot to boot into CFAR (N2G47H.7.10.14_t1)
- Reinstalled FlashFire
- Used FlashFire to flash SuperSU zip on current slot, also used EverRoot to inject SuperSU, again on current slot.
It should flash SuperSU and reboot back into the normal system, which should be rooted.
Click to expand...
Click to collapse
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
kkn14 said:
Does this still work for January update?
Im getting Mi A1 tomorrow for my father
Want easy way to root, enable cameraapi2 , use OTA without loss of data
Click to expand...
Click to collapse
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
DeV91 said:
the easiest way to keep ota and still be able to update via ota is by simply having only magisk installed. in magisk you can activate modules for camera2 api, eis etc.
when updating just read up on the magisk tips -> OTA installation (on github, google) for A/B partiton (pixel devices):
1. uninstall magisk via manager (this restores boot image, deactivates modules) so you are able to take OTA.
2. install OTA the usual way, when step 2 is shown in OTA process, simply head to magisk manager again and press install and select "Install to second slot"
the only time this does not work is when updating to a major android update (O -> P), but then you just dont have to patch the boot image after u took the OTA and wait for either a patched image or create one yourself with magisk manager and flash with twrp
Click to expand...
Click to collapse
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
kkn14 said:
This helps wonders !! Thanks alot, I saw alot of conflicting info before this
So I can use this- https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 for latest January patch? The same boot.img I mean?
Click to expand...
Click to collapse
i didnt read the whole thread, but i didnt find a january oreo boot image there.
only flash a patched boot.img that is from the current build you are on.
anyway, you could try to simply boot the patched boot.img with fastboot:
fastboot boot patched_boot.img
while this may boot the system without problems, things like not being able to activate wlan could happen. because this boot image was for a different build.
however, as long as it boots the patched image, you could then simply go to magisk manager and press install direct (recommended method) - this way it will patch your stock boot image, modfying your partition directly. remember: you only "booted" the patched boot image before with the "fastboot boot" method, this will only "load" the boot.img in to memory, and will not modify your actual partition.
another way would be to just boot into twrp revovery and flash the newest magisk on your own. i'd recommend this method as you will not risk in flashing a wrong boot.img from a different build version
fastboot boot recovery.img
as long as you just boot stuff, this will only be loaded into RAM, which is a volatile memory and will be lost on a reboot - hence not modifing partitons and maintaining the possibility of taking OTAs.