Database Users

Help withAndroid N Preview 5

Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker

You have to flash another version of TWRP... But, dude, i'm on the exact same case, same preview, and i can't get it to work. TWRP doesn't seem to work :/ I always got the god damn "no command" even if i follow some of the tutorials here...
EDIT : Try flashing the 3.0.0 or 3.0.1, and when all will be working (if you achieve, tell me how xD) update it.
EDIT 2 : I may find something, i'll let you know !

TWRP doesnt work with the developer previews without modifying the boot image.
If you want to root, you can use CF-Auto root.
You will still have the stock recovery.

Taker18 said:
Hi Guys, i have 1 little problem.
im on the last Android N Preview 5 and i wannt to root it.
i have downloaded SuperSU 2.76 and TWRP 3.0.2.0
I rebooted to bootloader flashed thw twrp via Terminal, now i wanna boot into recovery because of the SuperSU zip, but i am stucking on TWRP Logo.
Phone is working normal, but i cant enter into recovery, anyone else has the same problem?
Thanks and best Regards,
Taker
Click to expand...
Click to collapse
This is a known issue, Search the forum for the resolution. Basically TWRP won't work on the Android N on Encrypted device.

The solution is pretty simple. You need to decrypt your device's storage. TWRP currently doesn't work with encrypted N preview.
This could be easily done by flashing the modified boot image, that will disable forced-encryption. After that, you will need to format the current userdata partition to decrypt the storage.
Code:
fastboot format userdata
fastboot format cache
Once that is done, you can flash TWRP and then use SuperSU to root.
Another way to direct root is by using Cf-Auto-Root. But I am not sure about that specifically. While some users have succeeded, there are a few who have failed to root using Cf-Auto-Root.

Just use CF-Auto Root, it will do all the things.
Make sure you have unlocked your Bootloader and downloaded the good version of CF for your device.
Reboot your phone in bootloader mode, plug it to a computer, and just open the .bat (if you're on windows, or the equivalent for Mac / Linux). It will install SuperSU. When it's done, don't forget to download the TWRP Manager on the Playstore, and you'll have a working Recovery ! I did that, i know have a rooted nexus 6P on Android N preview 5
Also, lot's of Root's only apps will not work properly, because lots of changes took place on Android N. So make sure you follow some guide out there (exemple : Ex Kernel don't work if you don't tweak some things, same with Ad Away, so make sure you're googling)

I followed the premise of this thread here so all credits go to the OP http://forum.xda-developers.com/showthread.php?t=3410906 I flashed the latest Marshmallow vendor.img via fastboot, then flashed TWRP via fastboot. Booted into recovery from the bootloader then side loaded supersu using adb side load in TWRP. After that I rebooted to bootloader from TWRP and fastboot flashed the DP5 vendor.img and recovery.img. All is working well.

TWRP bootloop after flashing TWRP Solved

Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.

Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.

I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.

Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.

Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis

mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.

EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.

cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.

Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.

[RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z

{
"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.

(SOLVED) Unlocked Stock A2017U B25 - Current way to TWRP/Magisk root, and OTAs after?

Thanks all - I've figured out most of these steps, including how to install Magisk successfully - only new beta versions will install, and I've only tested the 20170520 build with Magisk 13.0 beta, but it worked entirely as intended. Below are the steps needed, and below that is my old post (hidden) for posterity in case it helps troubleshoot later if something breaks. Since this has now become a guide, I will put it into the Guide section and this thread can be deprecated.
This assumes you are starting at B25, but the instructions should work for any B version number, since MiFlash is going to force us to B19.
STEP 1: FLASHING FROM B25 TO B19 USING EDL MODE:
1. Install MiFlash using the EDL thread
2. Install the QUALCOMM drivers linked in the same thread.
3. Download "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread.
4. Extract the ZIP file.
5. Open MiFlash, selected on the named sub-folder from the ZIP
6. Connect Axon 7 via a USB cable, and hold VOL-UP/VOL-DOWN/POWER until the screen goes black and the red notification LED blinks very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirm device is shown in list.
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then do the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)," found in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time. You MUST flash the B19 FULL first to avoid this.
STEP 2: INSTALLING MAGISK 13.0 BETA WITH ROOT AND SAFETYNET PASS
1. Make sure you have a clean image with NO SU (PHH or MagiskSU or otherwise), and NO Magisk/Magisk Manager installed.
2. Enable Settings->Security->Unknown Sources in stock.
3. Download Magisk Manager 20170520 13.0 beta and Magisk 20170520 (here, and attached for convenience) (full beta thread here if needed), and copy them to your device.
4. Install Magisk Manager 20170520 13.0 beta via File Manager direct as an APK.
5. Go to TWRP, and install the Magisk 20170520 beta (here, and attached for convenience)
6. Reboot into stock, and open Magisk Manager 13.0. You should see both Magisk and Root installed (Root as "Magisksu"). If you try SafetyNet right now, it will fail.
7. Go into Settings in Magisk Manager and enable MagiskHide.
8. Now if you check SafetyNet, it should pass.
Note that the temporary beta builds appear to only be available for a short time, so either use the files attached, or go ahead and try the latest beta build. The first build I tried, 20170520, worked. My guess is all beta builds or full builds after 20170520 will work with the instructions above, but feel free to test.
STEP 3: GET OTAS: I have not tested yet to ensure Magisk doesn't break, but you should be able to download OTA packages and flash them. Will update when I care to, or others can feel free to try it and report.
Edit 5/21/2017: Added additional steps to Magisk to show process after flashing in TWRP.
Old Post (NOT CURRENT):
I unlocked my phone some time ago, but did not install TWRP or root so that I could get OTAs. I'm currently on A2017 B25 (fully up to date) and am stock otherwise. I was hoping I could get help with updated information since the guides and threads are usually old and the reply updates can be contradictory. Two questions:
1. Can someone confirm how to take my unlocked stock A2017U B25 Axon and (1) install TWRP and (2) install Magisk?
There have been a number of threads related to installing TWRP and Magisk, but all of them have question marks. The Phh Magisk guide is from 2016 so would be pre-Nougat. Then there's also a tutorial to build your own Magisk ROM, which seems like it's more complex than other people who just flash Magisk - though for them it seems like there are still problems, with it not being clear whether Magisk 10.2 or 12 is needed.
I assume I can flash TWRP using the toolkit, but it sounds like rooting via the toolkit is not going to be Magisk. I'd really like to have a root that can pass SafetyNet if needed so my device is fully functional - if there are other methods than Magisk, that'd be great too.
2. Can someone confirm what process I use to get future stock OTAs after I install TWRP and am Magisk rooted?
Do I just download the OTA file from this thread and flash it via TWRP, or do I need to go back to stock (such as with the toolkit) first?
-------------------------------------------------------------------------------------------------
UPDATE 2017/05/21:
I came very close to solving all problems. My steps are below in case anyone wants to try.
FLASHING FROM B25 TO B19 USING EDL MODE: See my explanations here: https://forum.xda-developers.com/showpost.php?p=72294934&postcount=11
INSTALLING MAGISK 12.0 WITH ROOT AND SAFETYNET PASS
I was able to get Magisk 12.0 to run on Unlocked A2017U B19, and it appears I pass every test and Pokemon Go (test app) runs. Starting from A2017U B19 clean wipe, these are the exact steps I did. They can probably be optimized.
HOWEVER, MAGISKSU ROOT DOES NOT GIVE PERMISSION TO APPS SO THE METHOD BELOW IS NOT A SUCCESS - it says "X is denied superuser rights," without prompting. I tried all options in Magisk and could not solve this problem. If you think you can solve this problem, please feel free to give it a shot below - you will pass all status tests in Magisk but I cannot get root to actually grant access. Any suggestions?
1. Install Magisk Manager app in Google Play.
2. Boot into TWRP, flashed Magisk 10.2. Reboot. (This appears to flash successfully in TWRP, then booting back into Android it does not appear Magisk is installed in Magisk Manager).
3. In Magisk Manager, download Magisk 12.0.
4. Boot into TWRP, install/flash Magisk 12.0.
5. Boot into OS, check Magisk Manager. Magisk is shown as installed, NO root is installed.
6. Download PHH Superuser ZIP from the main post here: https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394 (NOTE that I cannot tell which version this is. It appears to be r170 based on the changelog, but no version appears in the "superuser.zip" that I download.)
7. Boot into TWRP, install "superuser.zip".
8. Boot into OS, check Magisk Manager. Magisk shown installed, and Superuser is shown installed. SafetyNet FAILS.
9. Enable MagiskHide in Magisk Manager settings.
10. SafetyNet should PASS in Magisk Manager.
Note that I think step 2 is unnecessary, but I kept it in anyway since that's what I did exactly. Images below show the current state of things:
{
"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"
}

Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.

I also am curious about this... having just scratched my head for like 2 hours as to why i cant boot into fastboot mode trying to install TWRP. so at this time as far as i can tell there is no way to flash twrp if you are on b25? the update packages in the EDL sub forum are all for b19

I would actually like to know which toolkit I should use to get root and keep my data on stock for A2017U
Sent from my ZTE A2017U using XDA-Developers Legacy app

B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.

StickMonster said:
B25 took away fastboot. Assuming you are unlocked, you can flash twrp in EDL mode using axon7tool, or I think, miflash. I'm sure the toolkit uses one or both of those.
Click to expand...
Click to collapse
Ok but how do i do that? which package do i download do i just put the TWRP zip file into miflash? whenever I use axon tool it tries to do it through the bootloader which of course doesnt exist anymore. also what is the deal with like 25 different miflash tools? I cant seem to find one that works for anything

That's interesting. I accidentally upgraded to B25 OTA a couple of days ago (well, not accidentally, but now I suppose that was a stupid idea). Is there a way to root the phone and unlock the bootloader now?
Cheers,
Mike

StickMonster said:
Magisk 12 works with custom roms but doesn't work with stock. 10.2 is what I use with stock, and I haven't heard anyone be successful with a later version. Let me know if you can't find a download.
To flash an OTA you don't have to downgrade. Just dirty flash the stock system and recovery of the version you are on and you can OTA without losing data. If you can be patient it's better to wait a few days for the twrp flashables from drakenFX. I don't think the thread you linked to is for your variant (U).
Good luck. Let us know if you get stuck.
Click to expand...
Click to collapse
Thanks! I haven't had time to get around to trying it, but thinking about doing so tomorrow.
Assuming that I don't have an issue getting TWRP via the Axon Toolkit I linked to above, do I just flash Magisk 10.2 via TWRP? It seems like the process goes wrong for 50% of the people who post here, so I'm expecting some crazy process. But maybe I'm worried about nothing.

Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.

ScaryBugThing said:
Well, ran into trouble before I could do anything.
On B25, I cannot access Fastboot, so Axon7Toolkit and other methods fail. In the bootloader, I can choose to restart, go to recovery (no TWRP, so it's stock recovery), and there's still the option for Fastboot. However, selecting it just reboots into the bootloader.
I researched and read that it was removed in B25. So I looked for ways to get it back. I saw MiFlash, tried installing that to apply the EDL rollback to B19 (as outlined here), but MiFlash in Windows doesn't appear to recognize the EDL file, so I can't try to apply it.
When the device is booted into stock, ADB sees the device. Can I ADB sideload TWRP onto it despite not having fastboot? I wanted to check before I brick my device trying something dumb. Or see if anyone has other suggestions to get TWRP onto my stock A2017U B25 unlocked system.
Click to expand...
Click to collapse
Have you tried the TWRP app from the Play Store? Pretty straight forward.

amphi66 said:
Have you tried the TWRP app from the Play Store? Pretty straight forward.
Click to expand...
Click to collapse
Thanks for the suggestion. It turns out the Miflash method DID work. I had to extract the EDL folder, and then in the app select the subfolder for the EDL type. In detail:
1. I first installed the MiFlash at the EDL thread
2. Installed the QUALCOMM drivers linked in the same thread
3. Downloaded "B19-NOUGAT_FULL (Nougat 7.1.1)" from the same thread
4. Extracted the ZIP file
5. Opened MiFlash, selected on the named sub-folder from the ZIP
6. Connected my Axon 7, and held VOL-UP/VOL-DOWN/POWER until the screen went black and the red notification LED blinked very intermittently (~1 time per 4 seconds) to get it in EDL mode.
7. Hit Refresh in MiFlash and confirmed my device was shown
8. Hit Flash in MiFlash to flash it. (This rolled back my B25 device to B19 stock)
9. Then did the same process again with "B19-NOUGAT_TWRP (Nougat 7.1.1)" in the same EDL thread (to get TWRP).
Note that first I just downloaded the TWRP version, and TWRP successfully installed and I could boot into TWRP, but it would totally freeze before loading the OS ROM every time (since it was on B25 but had the B19 TWRP partial update, which caused problems).
My problem now is that I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick? I have the option in Magisk Manager to download 12.0, but I hear that that does not work (and I don't want to have to restart this process) so I haven't tried it.
Edit: Also, Magisk Manager shows SafetyNet fails with a "CTS Profile Mismatch" error (though no SU is installed) - though Pokemon Go seems to run so I don't know what that means.
Edit 2: This is resolved, see first post.

I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.

BoboBrazil said:
I just bought an Axon 7 and it is on b25. Is there a way to downgrade or root? I bought this thinking it was still possible.
Click to expand...
Click to collapse
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).

ScaryBugThing said:
Use MiFlash to apply B19 FULL, then apply the TWRP MiFlash file. It's in the Dev Thread (and the post right above you ).
Click to expand...
Click to collapse
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app

troy5890 said:
Will that erase internal storage?
Sent from my ZTE A2017U using XDA-Developers Legacy app
Click to expand...
Click to collapse
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.

ScaryBugThing said:
I can't say definitively, but when I did it all settings and data remained. All my installed apps, etc, everything were retained from B25.
Click to expand...
Click to collapse
I see, thanks for telling me. I'll give this a go pretty soon
Sent from my ZTE A2017U using XDA-Developers Legacy app

Sorry, in case it got lost in my old post: I downloaded Magisk 10.2, and flash it in TWRP, but when I open Magisk Manager after booting, it shows no Magisk or SU is installed. Does anyone have an idea how to get Magisk 10.2 to stick?
If anyone can answer this, I'd really appreciate it.

With help from here: https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
I am running B25 whilst keeping TWRP and a bootloader.
How? Simple really, I just took the latest B25 zip from the above link of the system and installed it without the new B25 bootstack. I guess I was running B19 before so my bootstack will be the same from there.
So that means TWRP+Unlocked bootloader, it also means I can use SuperSU to root.
Downsides:
Magisk doesn't work, tried v12,11.6,11.1,10.2 and none work, no root access.
Now I am on B25 I can't use any prior stock rom , B19 stock or bad boyz rom (based on B15?) causes me to have major problems with my gsm signal turning on and off repeatably, I tried to fix it by installing different modems but failed.
BTW this is all A2017U, no idea if it will also work with other variants.

In case anyone is wondering, I updated the first post to show that I did succeed in getting a full pass on SafetyNet with Magisk and MagiskSU/PHH SU "root" installed, and I gave the full method there.
However, all apps are denied Superuser rights with no prompt, even if the Superuser app is set to prompt or allow all. Turning off MagiskHide also fails to give Superuser, so it appears MagiskSU/PHH Superuser is simply not installing correctly.
Just for kicks I also tried flashing SuperSU 2.79. It does work as root, and gives root to apps, but of course fails SafetyNet, and Pokemon Go (test app) fails.

Hi all - I think this is solved - i.e., Magisk is fully functional. See first post which has been updated with the details.

Perform the update without losing the root

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.