Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Longlast said:
Dears
my G900T was rooted normally with CF auto root after a while it became unroot with 4.4.2 ng3
i tried to install CF auto root many times stuck in the seandroid enforcing
with root checker i get this errors
stage 3 root user account :error
error:stderr :null, stdout:null,exit_value: 1
additional google safetynet status false
additional selinux enforcing
any help would be highly appreciated
Click to expand...
Click to collapse
You should just install TWRP with Odin and use TWRP to flash supersu zip, that's more or less what cf auto-root is doing anyway. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.
thisisapoorusernamechoice said:
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again.[/QUOTE
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
Longlast said:
Dear thisis.
thanks for your kind respond
i did as you said, odin pass, then immediately boot into twrp recovery and successfully installed then restart from twrp, but still get the same result.
i highly appreciate help
Click to expand...
Click to collapse
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
thisisapoorusernamechoice said:
You said you installed the supersu zip in TWRP, are you able to run the supersu app in normal android? Because if so, you're rooted
Click to expand...
Click to collapse
when i run supersu a message appear that there is no su binary installed, and supersu connot install it. if you just upgrade to android 4.3 you need to manually re-root.
the current version is 4.4.2 bn3
Related
I rooted the device
Then ı installed dualrecovery recovery with----- 1 Installation on Rom Rooted with Superuser
Then An app called NDR Utils Installed .
When I Open the app and select Teamwin Recovery I press Reboot to primary Recovery
But phone Reboot Normally and Opens no recovery comes.
What should I do?
I also tried hardware enter to recovery green light comes And phone vibrates but normally reboots again ..
Thanks
univercode said:
I rooted the device
Then ı installed dualrecovery recovery with----- 1 Installation on Rom Rooted with Superuser
Then An app called NDR Utils Installed .
When I Open the app and select Teamwin Recovery I press Reboot to primary Recovery
But phone Reboot Normally and Opens no recovery comes.
What should I do?
I also tried hardware enter to recovery green light comes And phone vibrates but normally reboots again ..
Thanks
Click to expand...
Click to collapse
What firmware are you on and did you try NUT dual recovery installer (program)?
IreshS said:
What firmware are you on and did you try NUT dual recovery installer (program)?
Click to expand...
Click to collapse
ıM Using .314 android 4.4.2
I tried NUT Installer after Rooted the device .
Then When I try to reboot to primary recovery doesnt open phone starts normally
thanks,
Did you install busybox from play store? Installing that causes the recovery to fail. If you did install busybox you will need to uninstall it & then run the dual recovery installer again. Dual recovery installs a specific working version of busybox that works with the recoveries, installing any other busybox means you can't boot into recovery.
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
chugger93 said:
So either I suck or I literally have the process wrong, but I was trying to install 6.0.1 last night for 2 hours. Originally I had 6.0 installed rooted, twrp, etc. OTA didnt work because I'm guessing twrp was installed as it errored out. So I decided to take WUG downloaded the binaries/newest stuff and decided to just manually flash 6.0.1. However at the same time I wanted to use the decrypter tool here.
My process was/is:
Flash Stock/Unroot button in WUG (with newest 6.0.1 already downloaded
Root button and flash customer recovery button/checkbox
Flash the perm recovery zip, supersu, and busybox
Flash the decrypter zip
Wipe data/cache/system/davik/etc and then freshly reboot
The problem is, it just hangs on the animation screen and never loads. I've tried it twice now, and its driving me insane. Where could I have went wrong? What is flawed about my process or maybe I'm using the wrong stuff. Thank you in advance guys!
Click to expand...
Click to collapse
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
corkiejp said:
I don't think the NRT is updated to properly root on 6.0.1 (Could be wrong).
Get the Latest SuperSU-v2.62-3 and flash that, It will modified the boot.img for you and include no forced encryption.
As long as you remove the encryption of the data partion in twrp from this guide
You shouldn't need the decrypter zip, also if you flash TWRP and boot into it before booting the system, you also won't need perm recovery.
Going by what I have read, still encrypted on my Device.
Click to expand...
Click to collapse
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
chugger93 said:
ok so everytime I flash the supersu, it does its thing, then I format data, the reboot and twrp says supersu is not installed, do you wanna install it now? You can swipe to install or do not install.
Which I dont get becuase clearly I flashed the supersu zip a sec ago. if I continue to just flash it like it says, when I boot up, all I see in my drawer is the "SuperSU Installer" I have no idea what I'm doing wrong. If I dont have twrp install it when it asks, I got nothing in my app drawer
Click to expand...
Click to collapse
From the linked SuperSU thread
From the linked SuperSU thread said:
If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!
Click to expand...
Click to collapse
This is do with the new systemless root and TWRP needs to be updated to reflect this change.
chugger93 said:
think I may have gotten it, had to download supersu from play store, then reflash, then let twrp flash it when it says it needed too, not I can launch supersu from the app drawer and it works.
Next problem is encryption. Under security it still says "Encrypted" do I need to actually hit the "Format Data' button in twrp? I just did a factory wipe slide.
Click to expand...
Click to collapse
From the linked guide above said:
11.Once in TWRP, hit “cancel” when asked for the password and then erase/wipe data and make sure MTP is enabled (dig around the menus in TWRP, it’s all in there somewhere). This erases the encrypted partition and allows you to use adb to push files to your sdcard.
Click to expand...
Click to collapse
Answers in quoted messages.
Never had to get SuperSU app from the store, maybe because I already had it installed, the app is also in the SuperSU zip.
I just got a T-mobile S5 g900T and i want to root it. it's running 4.4.2 and i'm thinking about upgrading to lollipop but im worried i wont be able to root afterwards. What are my root options here?
Motorolaseries said:
I just got a T-mobile S5 g900T and i want to root it. it's running 4.4.2 and i'm thinking about upgrading to lollipop but im worried i wont be able to root afterwards. What are my root options here?
Click to expand...
Click to collapse
You can root on any version of android for this phone:
Just install TWRP with Odin and use TWRP to flash supersu zip. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again
What is I flash supersu then it keeps saying set warranty bit kernel
I keep flashing supersu but it keeps saying set warranty bit kernel
To succesfully install the newest Versions of SuperSU you have to install it in systemless mode. If you flash the ZIP it will install it in /system mode, so you have to force the systemless install.
Before you flash the newest Beta SuperSU.zip go to the TWRP terminal and write:
echo SYSTEMLESS=true>>/data/.supersu
Then flash the ZIP.
SuperSU will be installed in systemless mode and your Phone will boot up fine.
I'm getting stucked in boot logo +1... after installing some apps, with root permissions, like Viper4android, DPI changer, SElinux permissive... don't know what happend. what should i do?
I try this, but still stuck at boot logo...
This method doesn't resolve a boot loop when it is caused by something else. I would recommend you to do a clean install and then install your desired apps one by one with a testing reboot in between to see which app is causing your boot loop.
Scherzengel said:
This method doesn't resolve a boot loop when it is caused by something else. I would recommend you to do a clean install and then install your desired apps one by one with a testing reboot in between to see which app is causing your boot loop.
Click to expand...
Click to collapse
i flash the rom again, and everything works fine now... gonna keep trying if something else happened. thanks.
Is there a way to do this from stock recovery on an encrypted phone?
Scherzengel said:
To succesfully install the newest Versions of SuperSU you have to install it in systemless mode. If you flash the ZIP it will install it in /system mode, so you have to force the systemless install.
Before you flash the newest Beta SuperSU.zip go to the TWRP terminal and write:
echo SYSTEMLESS=true>>/data/.supersu
Then flash the ZIP.
SuperSU will be installed in systemless mode and your Phone will boot up fine.
Click to expand...
Click to collapse
Thanks
First it didn't work for new Update SuperSu V2.46.zip
But it worked for Beta SuperSu V2.74-2xxxxx.zip
This guide provides all the steps and patches required to root the Stock system and having Xposed installed while maintaining SafetyNet (Android Pay, Pokemon Go, etc) compatibility. There are some problems of this method that Magisk is supposed to fix, however the latest Magisk v10 is not supporting our stock ROM yet.
The prerequisites of this guide is to have the bootloader unlocked and TWRP recovery.
DOWNLOADS
The recipe require the following ingredients to be downloaded to your internal or external storage:
1. TWRP 3.0.3 (This is the last release at this moment). more info in the Official Thread. Thanks to @jcadduono . TWRP 3.0.2 can't succesfully flash SuperSU 2.79
2. Default Stock ROM for your phone (Required only if you have modified your system or boot partition). You can download them from this thread. Thanks to @DrakenFX . You can alsouse any other custom ROM based on stock such as ZADMix or HelsAx7 SubMix (both tested).
3. SuperSU v2.79. more info in its official thread.
4. SUhide 0.55. More info in its official thread. Thanks to Chainfire.
5. SafetyNet-KCAL Kernel patch, thanks to @jcadduono also for this one!
6. Xposed v86.2 So far only this version is compatible with SUhide.
7. Material Design Xposed Manager app by DVDandroid. More info about this release in its official thread.
8. Root Switch 1.3.3.2 app. Thanks to shakalaca. More info in its official thread.
INSTALLATION
1. Do a backup of your system, I recommend Boot+System+Data partitions. The next steps will modify at least your boot and data partitions, and some Xposed modules will modify also your system partition.
2. If you already have TWRP 3.0.3 then just boot to recovery and proceed to step 3. If you are still using TWRP 3.0.2 please upgrade to the latest TWRP 3.0.3 and reboot to recovery again.
3. I recommend to flash the default Boot and System Partitions and reboot directly to recovery. You can also use any other custom ROM based on the stock ROM such as ZADMix or HelsAx7.
4. All this step must be done without leaving TWRP. Flash SuperSU 2.79 adding also the zips for SUhide 0.55, Xposed v86.2 and the SafetyNet Kernel patch in that order. They must be flashed together. Without leaving TWRP, navigate from the main menu to Advanced > Terminal, introduce the command reboot disemmcwp and the system will reboot by itself once or twice while configuring the settings for SuperSU. Do not be alarmed.
5. Install Xposed Manager and Root Switch apps.
6. Now you have your system fully rooted and you can now install Xposed modules. However you will see the test app SafetyNet Helper reporting a validation failure. Do not worry about it anymore! When you want to initiate a SafetyNet sensitive application (Android Pay or Pokemon Go among others), just open Root Switch and disable root, no need to reboot. SafetyNet will pass and all your apps will work. You can see that Xposed continue working even after disabling root since it was started before. Do not forget to enable root again otherwise new apps requiring root won't load.
Magisk v10+ promises auto root hide per app, but sadly our stock ROM is not yet supported and the method psoposed here requires the user to disable root before loading any SafetyNet protected app.
Enjoy
Reserved for future Magisk guide.
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
H0lmEd said:
Has anyone managed to get this working on A2017G/B09? I've had a few attempts, forcing systemless SuperSU, but it hangs at the "AXON" boot screen
Click to expand...
Click to collapse
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Oki said:
At what point of the guide is it hanging at the Axon boot screen? after step 4? Have you ensured that the SafetyNet patch is the last thing you flashed before boot?
Click to expand...
Click to collapse
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
tron1 said:
I'm on the same configuration (A2017G B09). I did a step by step installation/reboot/installation/reboot. The Problem is with suhide. After installing suhide the boot process will stick in the Axon screen.
Click to expand...
Click to collapse
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Oki said:
You do not have to reboot after SUhide. The files at step 4 have to be flashed together without leaving TWRP otherwise it won't work.
Click to expand...
Click to collapse
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
tron1 said:
In theory you're right. But how do like a bugfix to be done if you don't know at which point you're failing?!?
Click to expand...
Click to collapse
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Tikerz said:
That looks way complicated. What's wrong with the easy way of flashing Magisk V10 + Phh Superuser r266? This has worked on all my devices since the November security patch broke suhide. Magisk now takes care of the flag to hide bootloader unlock status so no need for a kernel patch too. Then flash systemless Xposed by topjohnwu if you want that and you can turn it on and off in Magisk Manager if you want to use Android Pay, play Pokemon Go, etc.
Click to expand...
Click to collapse
For some reason Magisk is not compatible with the Axon 7 kernel. Not yet. This is why it is so complicated and requires a guide. Last time I tested this was yesterday using Magisk v10.2 and phh Superuser r2, and they still failed to root the system.
le_cactus said:
Hi,
I have a A2017G running B08, already unlocked and witch SuperSU 2.79. Just the older version of TWRP.
Can I just upgrade the TWRP and proceed with step 4 and so on? Hate to go back to stock...
Tia,
Cheers,
/Cacti
Click to expand...
Click to collapse
Yes you can try to begin with step 4 with SUhide on. It should work. However I recommend you to upgrade to TWRP 3.0.3 and do the whole step 4.
Gr8. Thanks.
Cheers,
/Cacti
Oki said:
The last patch fixes some problems created by SuperSU, SUhide and Xposed. This is why all the patches in step 4 have to be flashed together without leaving TWRP and in the specified order, otherwise it wont work on stock ROMs.
Click to expand...
Click to collapse
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
H0lmEd said:
Not quite sure I understand you.
I've tried doing this on A2017g, b09;
0) wipe data/system/boot
1) flash stock Boot stack + System stack zips in twrp 3.0.3 unlocked bl
2) rebooted straight to recovery
3) flashing SuperSU wrote to system so I had to start again but forcing systemless (in terminal; echo "SYSTEMLESS">/data/.SuperSU
4) flash supersu, suhide
5) flash xposed
6) flash the safety net/kcal patch
7) reboot
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Oki said:
SuperSU 2.79 installs in systemless mode, no need to set systemless.
Regarding your problem, please try this. Instead of rebooting using the button, open the terminal in TWRP and type "reboot disemmcwp". I hope this was your problem.
Click to expand...
Click to collapse
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
corpdecker said:
I just did this on my B29 A2017U phone and it worked perfectly, can switch root on and off with the root switcher and Safetynet passes fully with root set to off.
My previous attempts were all thwarted by the bootloader being unlocked, so that patch to the kernel works great. I'll be backing this up with twrp and getting a little more adventurous (really want to try the BeastMode kernel) soon.
Much thanks for making it nice and simple, Oki !
Click to expand...
Click to collapse
Don't install beast mode yet, from my experience all the steps from op worked fine until I flashed beast mode and it broke safetynet.
lexman098 said:
This doesn't work for me. Steps:
1. complete wipe
2. install b29 boot stack
2. install b29 system
3. install super su 2.79
4. install su hide 0.55
su hide comes back with an error that says it can't find super su and I should make sure I've installed 2.79 or greater.
edit:
I missed the part in step 3 where you say "reboot directly to recovery". I tried that, but it rebooted to system instead and now I lost TWRP entirely.
edit2:
fastboot flashed twrp again and once in recovery I was able to get through step 4
edit3:
Now it's just stuck on the axon logo. Tried force reboot and the same thing.
Are you sure you tested this from scratch? I have the US version of the axon 7.
Click to expand...
Click to collapse
Are you using TWRP 3.0.3? SuperSU 2.79 installs fine and in systemless mode when flashed with the latest TWRP. TWRP 3.0.2 can't flash it properly.
Yes this method has been tested, not only with stock Roms, but also with ZADmix.
If you are doing a complete cleanup before flashing the ROM, boot into system at least once after installing the ROM so the data tree structure is setup. You actually don't need a full cleanup.
Kingo64 said:
I have tried it and am stuck on the same stage also even after using "reboot disemmcwp".
I followed all of your steps and am using an A2017G B08.
Click to expand...
Click to collapse
H0lmEd said:
And I still get stuck on "AXON" boot screen
Click to expand...
Click to collapse
Please ensure you have flashed the right stock ROM for your unit. I have modified Ingredient 2 in the OP since it was highly misleading. Ensure you have unlocked bootloader, TWRP 3.0.3 and flash the right ROM for your system: ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip and ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip. And boot to the system at least once before continue to the rest of the procedure.