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
Related
Hi guys, i have unlock and root my prime, installed cwm via rom manager but it won't boot into recovery, just start normally when boot up. Any ideas? also when i try to "manage backup" in rom manager, show me a "blank" page and i can't do anything.
thanks!
Post goes into automating back ups
but step 3 should help
https
://plus.google
.com/103194039699472024916/posts/cNqu4cgiJqa
forum won't let me link...
When I first rooted I had the samething, turns out I was actually rooted. Check to see if you have Superuser app first, if so you're rooted if not you never got root acess. What process did you use to achieve root acess?
I was making an assumption that you were rooted and trying to get the "Reboot to Recovery" option to work. If you are rooted with a recovery installed, and want to boot manually to the recovery partion, then during your reboot at the eeepc screen, hold VOL - until it gives you the option to press VOL + for boot to recovery. My original post was a work around to boot to recovery from within your ROM
install twrp recovery through goo manager and use root checker from the playstore to varify root.
Hi
I hope someone can help me with this.
I have updated my P8 from B200 Lollipop to B317 Marshmallow. Update completed with come errors in stock recovery but phone seems to be in perfect order and fully updated to the latest build.
Now my problem is I've lost the root access. I was expecting this to happen after the update but now I can't re-root it.
In fastboot, I can flash twrp 2.8.7.0 and twrp 2.8.7.0 no problem. It all seems ok in fastboot window, however after recovery is flashed I'm trying to access it from bootloader holding power + volume up.
Unfortunately, at first phone was in bootloop and after a few loops was starting normally, and recovery was back to stock. Now after another few ties of flashing twrp recoveries and trying to access it it goes straight to stock recovery, like custom was never installed. Does not even give me bootloop anymore.
I have tried to press and hold both volume buttons but with similar result.
Recovery is not important to me as long as I have get my phone rooted but it seems like there is no other way to push SuperSU to the system without the custom recovery.
KingRoot app worked with Lollipop byt it fails now.
Booting to recovery without installing it also dees not work from fastboot.
Does anyone have an idea how to root this B317 or have tried the roll back to B200 with success ?
same
I'm in the same situation.
What is the solution?
OK. The nu twrp is the solution
Here
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
Hi. I have unlocked my Nexus 5 bootloader. I had twrp recovery 3.0.0.3 installed. From trwp I had installed LineageOS 14.1 and the build was from July 2017. Today I tried to update to 24.10.2017 build of LineageOS 14.1. When flashing from twrp I got error "zip verification failed". I thought that the problem was my recovery so I went to update it. Update was done from Official TWRP Manager (android app). From there I downloaded the newest version 3.1.1.0 and flashed it to recovery with the app. After that I went back to LineageOS updater and selected the 24.10.2017 build and pressed update. Phone restarted but this time it didnt get me to twrp recovery. Instead I got into the screen you normally go when you press power + vol up + vol down. This screen included restart bootloader, boot to recovery, power off and start. Now my phone wont start at all anymore and I cant get into twrp recovery. Something went wrong with flashing straight from android app. Can somebody help and tell me what to do to get my phone up and running again?
MrMuscle said:
Hi. I have unlocked my Nexus 5 bootloader. I had twrp recovery 3.0.0.3 installed. From trwp I had installed LineageOS 14.1 and the build was from July 2017. Today I tried to update to 24.10.2017 build of LineageOS 14.1. When flashing from twrp I got error "zip verification failed". I thought that the problem was my recovery so I went to update it. Update was done from Official TWRP Manager (android app). From there I downloaded the newest version 3.1.1.0 and flashed it to recovery with the app. After that I went back to LineageOS updater and selected the 24.10.2017 build and pressed update. Phone restarted but this time it didnt get me to twrp recovery. Instead I got into the screen you normally go when you press power + vol up + vol down. This screen included restart bootloader, boot to recovery, power off and start. Now my phone wont start at all anymore and I cant get into twrp recovery. Something went wrong with flashing straight from android app. Can somebody help and tell me what to do to get my phone up and running again?
Click to expand...
Click to collapse
I managed to flash with windows command line the new build of twrp recovery to my phone and it started to twrp recovery. In twrp recovery the phone tried to install the latest version of lineage (24.10.2017). The installation failed again. Do I need to take of the zip verification or something to get through this update?
ok I will explain what I really did to stuck in this problem 1- install stock rom for my device Samsung j5 (j530f) using Odin and device open normally 2- install magisk apk also install zip file and enable using-debugging button and OEM button 3- install TWRP using Odin also (but I have done a mistake here I am not unticked auto reboot checkbox ) 3-after that I tried to install magisk in TWRP i am not found magisk file as video mentioned i swear I doesn't make anything there so I reboot my system and stuck in it and when I press power while bootlooping he go to TWRP I tried re-install stock rom after wibe all data and format system after Odin finish and reboot !!now go to TWRP direct what should I do
amigo2020 said:
ok I will explain what I really did to stuck in this problem 1- install stock rom for my device Samsung j5 (j530f) using Odin and device open normally 2- install magisk apk also install zip file and enable using-debugging button and OEM button 3- install TWRP using Odin also (but I have done a mistake here I am not unticked auto reboot checkbox ) 3-after that I tried to install magisk in TWRP i am not found magisk file as video mentioned i swear I doesn't make anything there so I reboot my system and stuck in it and when I press power while bootlooping he go to TWRP I tried re-install stock rom after wibe all data and format system after Odin finish and reboot !!now go to TWRP direct what should I do
Click to expand...
Click to collapse
Did you flashed stock rom correctly after bootloop?