Database Users

[ROOT][RECOVERY][ALL IN ONE] Cf-Autoroot-twrp-T700/705/800/805/Tab S- UPDATE 23/4/15

Updated CF-autoroot with latest Supersu binaries and combined TWRP recovery for SM-T800/SM-T805/T700/T705 Exynos only, Lollipop and Kitkat
I've noticed that quite a number of people seeking to root their device also flash TWRP afterwards, seeing as it's unnecessary to do both steps I have made an all in one package to root and install TWRP recovery.
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version (ADB root shell and Download mode fixes).
UPDATE - I have updated all versions with new builds. TWRP is now v2.8.6.2 and now includes the fixes recently pushed to their repo for encrypted backups. I have also addressed the slow wipe issue, cache, system, etc., which some have experienced and should now be much quicker.
Each device now has it's own build, this is to ensure that TWRP recovery build properties reflect the device it's installed on. ROMs such as CM12 should now install without issue.
Feedback is welcome.
Simply flash with ODIN. Odin 10.6
cf-autoroot-twrp-t700
cf-autoroot-twrp-t705
cf-autoroot-twrp-t800
cf-autoroot-twrp-t805
Check root status with ROOT VALIDATOR
Guide how to flash, credit to Usama m.
http://techbeasts.com/2015/05/01/root-twrp-recovery-galaxy-tab-s-84-running-lollipop-502/
UPDATED TWRP:
http://forum.xda-developers.com/showthread.php?t=3074633
NOTE: It is important to boot to recovery after flashing or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Credits to chainfire for his great work.
FEEDBACK PLEASE
AND DONT FORGET THAT THANKS BUTTON :good: HIT AND RUN IS NOT NICE
.

Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks

d3xtr0 said:
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
Click to expand...
Click to collapse
Good stuff. :good:

Just picked up a T800 as a birthday present to my mom.. Its going to be hard to give this thing to her..lol
Anyways.. just used this to root and it worked perfect.. Had already took ota to LP..
Thanks !!

delete post !

tids2k said:
delete post !
Click to expand...
Click to collapse
What?

ashyx said:
What?
Click to expand...
Click to collapse
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.

snapper.fishes said:
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
Click to expand...
Click to collapse
Why the forum doesn't allow users to delete their own posts is beyond me?

In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx

lloydb9382 said:
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
Click to expand...
Click to collapse
Correct.

thanx so much it worked great ,

T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app

almony8 said:
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately AT&T lock the bootloader, so atm you're stuck with a device that cannot be modified in any way.
Sent from my SM-T805 using XDA Free mobile app

After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.

cyaclone said:
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
Click to expand...
Click to collapse
Use Root Validator and post the output. Root checker doesn't give enough information.

ashyx said:
Use Root Validator and post the output. Root checker doesn't give enough information.
Click to expand...
Click to collapse
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive

cyaclone said:
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
Click to expand...
Click to collapse
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.

ashyx said:
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
Click to expand...
Click to collapse
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Thanks

Not sure if it matters but what version of twrp is being installed?

AKfortyseven said:
Not sure if it matters but what version of twrp is being installed?
Click to expand...
Click to collapse
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version.
Click to expand...
Click to collapse
= 2.8.6.1

M8 Eye Recovery and Root

Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks

This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.

Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.

redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..

Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.

redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.

Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.

redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.

necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired

moto x pure 6.0 mm ( root )

Tried everything flashing every supersu via twrp and just gets stuck at the moto logo. Tried systemless root and did the same thing. So thinking it was my kernel and flashed elementalx moto kernel ( frankenclark ) then tried to flash supersu once again with the same fail and noticed with that kernel I lost my wifi connection but ran it anyways but failed. After much forum browsing and that supersu just isn't for the MXPE I even went as far as kingroot to achieve root then slap supersu to keep root like I did with my kindle fire. I'm pretty lost for words here. I'm previously running resurection remix and works flawless but I do really like the original setup. Ps tried the stock rooted roms and they was a lil off and kept trying to ota update but failed because my bootloader is unlocked so I had to uninstall it. Just looking to root the original rom so I can keep all the moto apps. Looking forward to hearing the ideas. Thanks in advance.

Wow... So I assume you flashed back to pure stock?
Rooting is not difficult, there is only 2 ways to do it, either flash SuperSU 2.62-3 beta or the latest stable version with the "echo" command for systemless installations. Look at this thread (note the pictures in the OP are of my XT1575, I fudged a little) but the method is identical. If it doesn't work, no offense, but your not doing something right.

I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.

fastjohnson said:
I have both pure stock in a restore and resurection remix in a restore which is pretty much my daily because the active display drives me nuts. And supersu 2.6.2 I haven't tried yet but the SR supersu I've flashed via twrp with the stock kernel and ( frankenclark ) kernel and it responded the same stuck at moto. I've flashed it via windroid toolkit also it shows it's installing without any failure but on boot up she says no way. And I've updated the toolkit to it's newest version and still ends up stuck at moto. I'm sure I'll figure it out and get it. And no offense on doing something wrong it's been known to happen. Some lg double tap to wake the screen would be nice over the active display.
Click to expand...
Click to collapse
It sounds like the install script for SuperSU is not doing a systemless install...
So you are flashing stock, booting at least once (this is required), the open TWRP and allow changes to system (In mounts make sure Mount System Read-Only is NOT checked), go to Advanced - Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and press enter, then go to Install and select the SuperSU zip file and install it. It should clearly say it is doing a system-less install, patching boot image, etc. as shown in the first post of the link I shared a couple posts previous.

OK I tried this info word for word and tried multiple times and its still gets stuck on the moto logo, I don't get it.

I don't know... it's a puzzler.

2.62-3 and stop using toolkits.

lafester said:
2.62-3 and stop using toolkits.
Click to expand...
Click to collapse
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.

fastjohnson said:
I'm using twrp to obtain the root like specified. But I'll try adb commands and see if the version you mentioned will do it. I appreciate the help.
Click to expand...
Click to collapse
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.

fastjohnson said:
Well that worked perfectly the first try I used those terminal commands with that version SuperSU it rooted and booted right up like normal and started asking the SuperSU adb shell permission banners. Perfect guys maybe this thread will help some other poor soul to get root. Awesome advice that works. Thank you.
Click to expand...
Click to collapse
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.

acejavelin said:
Yeah, glad it's working... Did you read through the link I posted earlier? The 2.62-3 method was clearly described in the second post under Alternative Methods.
Click to expand...
Click to collapse
No actually I didn't see it, lol probably would have helped made me not look dumb. Buy who am I kidding you guys love flexing you rooting muscles..

Deleted.

My ZE551KL only boots to TWRP (and various other fun)

Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy

Well dang. I tried installing LINEAGE OS rom again and hoped for some strange reason it would boot into it. TWRP just keeps loading. I try the Reboot command in TWRP then choose SYSTEM and it still just goes to TWRP.

Well sometimes it just helps to air your frustration. As is true with many things in life. Say it out loud. Etc...
I was sure I had THE latest version of TWRP installed when this was happening. I rechecked to make sure. I didn't. I was 1 version away. Fastboot flashed that and it's booting normally . For now. Now, to see if I can get those apps to show up in the play store.
Things like Snapchat, Facebook messenger, etc... would just not show up.
Nope. That's still a problem . I wonder why this is happening?

Try clearing dalvik cache and sync you data for your mail account. I think those app wil show up. As for snapchat, you can't install it via playstore you can't pass safetynet.

FuzzyFone said:
Hi. I was enjoying Lineage OS's latest ROM (14.1) and wasn't able to enjoy the "nightly" updates because when I went to do the update, I found out I needed a compatible recovery to do so. I had TWRP sitting on my computer and would FASTBOOT Boot twrp.img to flash roms. When I saw you needed to install twrp to make the Nightly update feature work, I flashed it with fastboot. I also went ahead and decided to start from scratch with a fresh install and used the latest Nightly LIneage OS file . After it installed, it booted up great. But when I went to add many apps back to my phone, so many of them were not showing up in the play store. And when some did, it would say "Incompatible Device" So I went to my settings and decided to try out the Nightly update hoping maybe that was the problem. When it booted to TWRP, nothing happened. So I hit REBOOT. and no matter what I choose, it just boots back into TWRP. Even when I hold the power button down and let it boot back up. Without touching any volume buttons, it just boots into TWRP. I can't get back to my OS. I'm going to try to install Lineage OS again and just hope I can get to my phone to make sure I'm getting messages from friends, doctors, etc...
Any help on how to fix this would be appreciated. I used this site " http://www.androidinfotech.com/2016...2-laser-ze551kl-marshmallow-install-twrp.html "
to root my phone so I could use Titanium Backup. I'm hoping something in there didn't mess me up.
Thank you in advance.
-Fuzzy
Click to expand...
Click to collapse
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.

darkeyes22 said:
What version of TWRP have you used? If it's 3.0.2.4 and below, update it.
Click to expand...
Click to collapse
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:

FuzzyFone said:
(As shown in Post #3)
Already updated it. I got that part of the problem fixed. Thanks tho! :good:
Click to expand...
Click to collapse
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.

darkeyes22 said:
What do you mean by saying "part of the problem"? Maybe I can help you with the rest of it.
Click to expand...
Click to collapse
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy

FuzzyFone said:
Hello. I'm running the latest version of LineageOS 14.1 (just installed the nightly update) and several of the apps close the second I launch them. Clock was the first one I noticed . Loading pictures to share in other apps from Quckpic. and other apps I can't remember right now.
So I wanted to backup everything and try a different Rom thinking I might not have those problems. I installed SU and TWRP and then Titanium Backup Pro. After installing SU I had root. This morning I went to run a current backup and it said I no longer had root.
Dang. I have to go to the Pain Clinic. Time always catches up with me so fast when trying to problem solve.
Thank yo for reaching out! I really appreciate it. Especially with a phone that's not so popular out there in the wild that it's limited on folks available for help. it's 9:16am where I'm at. I'll probably be back in a few hours from now.
Thanks again, DarkEyes.
-Fuzzy
Click to expand...
Click to collapse
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.

darkeyes22 said:
Re-check your root with Root Checker. If you still have it, flash su removal through TWRP and flash systemless SuperSU. If you don't have it, just install systemless SuperSU. After you do that, boot back to the system (your boot might loop once - it's normal, do not interrupt boot), give TB pro root access, and see if it helped.
Click to expand...
Click to collapse
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.

FuzzyFone said:
Hello. Sorry it took me long to reply. After appointment, I was in too much pain to get online.
I installed thru Fastboot "addonsu-remove-14.1-arm64-signed.zip" rebooted, then installed addonsu-14.1-arm64-signed.zip thru Fastboot too and rebooted. Still no root. I checked it with RootChecker and there was no root.
Running latest nightly of LineageOS.
Click to expand...
Click to collapse
Through Fastboot? Try through TWRP, flash removal, then flash Systemless SuperSU (not the one you have now).
Here is the link to systemless SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.

RonakRonak said:
Hi
1st Step is Install official TWRP 3.1.1 which is availble for our device ze551kl aka Zool or ZooLD.
Boot in to TWRP
wipe cache+Dalvik cache+system+ASDF+internal storage.
now install Lineage rom latest version.
then gapps.
wipe dalvik cache.
hit Reboot system option
.it wlll not go in bootloop if u followed these steps which are guided by Devs here.
if u still facing bootloops u must have done extra ordinary thing with ur Device.
Click to expand...
Click to collapse
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs

darkeyes22 said:
It is Z00T that is ZE551KL, not Z00L. Do not even think about flashing something that was developed for Z00L on Z00T. It will not work.
Sent from my ASUS_Z00UD using XDA Labs
Click to expand...
Click to collapse
Yes.i already mentioned model name.

Strange root / Recovery issue. Please help

Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you

The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse

Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?

Should be, but it's not safe since you do not know the current root method.

Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse

Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha

tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??

Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse

tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??

Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.

Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin

Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you

Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse

Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..

tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal