Topic.
I have latest Kitkat version for the device and when I tell it to install SU it refuses to, with any exploit. I also tried other options and refuses to do them too.
Isn't it supposed to be one of the supported devices?
Related
hello
im from mexico i have a s4 m19v
my issue is..
the phone was root with the version 4.2 but i decided update via ota... to 4.3 and the same day to 4.4.2, well.... the issue is that i need root my phone cause i need 4g, and other language... i read the motochoppear method but doesnt work the "super user" appear in my phone and when i open show a message dialog with
" there is no SU binary installed, and superuser cannot install it. this is a problem.
if you just upgraded to android 4.3, you need to manually re root consult the relevant forums for your device" so.. i hope someone would help me.
theres not a solution???
davcastroruiz said:
hello
im from mexico i have a s4 m19v
my issue is..
the phone was root with the version 4.2 but i decided update via ota... to 4.3 and the same day to 4.4.2, well.... the issue is that i need root my phone cause i need 4g, and other language... i read the motochoppear method but doesnt work the "super user" appear in my phone and when i open show a message dialog with
" there is no SU binary installed, and superuser cannot install it. this is a problem.
if you just upgraded to android 4.3, you need to manually re root consult the relevant forums for your device" so.. i hope someone would help me.
Click to expand...
Click to collapse
doesnt exist a solution?
I installed TWRP on my Sprint Galaxy S4, but yet the phone is not showing as being rooted. The installation seemed to be a success. When I try to run SuperSU, I get the message that the SU binary needs to be updated, but the installation fails. I tried upgrading to a newer version in the Google Playstore, but that did not work either. I have since reverted back to the original version.
I downloaded Root Checker and it says my device does not have root access. But yet, when I go into the phone recovery mode, I do get into the TWRP mode and I see the version number installed on my phone. If the TWRP was a success, why is my phone not showing as rooted?
Does the SuperSU program have to work first?
Also, I need clarification on the TWRP versions.
I have tried 2 different versions and don't have success with either one. They both installed successfully, but my phone will not show as rooted when I use Root Checker.
My Sprint Galaxy S4 is a SPH-L720.
The 2 version of TWRP are: jfltespr and jfltexx
The texx seems to be for I9505 phone (which I'm sure mine is).
The spr seems to be for Sprint, but on some other websites, it shows to be for L710 version.
Both have installed successfully on my phone. Not sure which I should be using.
The TWRP site does not really specify spr only being for L710 (that is something I saw on another site).
What am I missing to get my phone to be recognized as rooted?
My build number is: KOT49H.L720VPUFNG2
I solved the problem. Found out TWRP is not the actual rooting process. I found the file I needed and rooted successfully.
Hertz305 said:
I installed TWRP on my Sprint Galaxy S4, but yet the phone is not showing as being rooted. The installation seemed to be a success. When I try to run SuperSU, I get the message that the SU binary needs to be updated, but the installation fails. I tried upgrading to a newer version in the Google Playstore, but that did not work either. I have since reverted back to the original version.
I downloaded Root Checker and it says my device does not have root access. But yet, when I go into the phone recovery mode, I do get into the TWRP mode and I see the version number installed on my phone. If the TWRP was a success, why is my phone not showing as rooted?
Does the SuperSU program have to work first?
Also, I need clarification on the TWRP versions.
I have tried 2 different versions and don't have success with either one. They both installed successfully, but my phone will not show as rooted when I use Root Checker.
My Sprint Galaxy S4 is a SPH-L720.
The 2 version of TWRP are: jfltespr and jfltexx
The texx seems to be for I9505 phone (which I'm sure mine is).
The spr seems to be for Sprint, but on some other websites, it shows to be for L710 version.
Both have installed successfully on my phone. Not sure which I should be using.
The TWRP site does not really specify spr only being for L710 (that is something I saw on another site).
What am I missing to get my phone to be recognized as rooted?
My build number is: KOT49H.L720VPUFNG2
Click to expand...
Click to collapse
Tough case resolved​
I hate to start a new thread but there is so little information out there about this variant of the G Pad. This is my second one (I had one with AT&T) and I absolutely love it. I just switched to Verizon and got the new one for free, but have had a devil of a time getting it rooted. When I first set it up, there was an update available which I applied. Probably my first mistake. I tried every root method out there. Here is how I got it done.
1. I secured the Verizon 06/12/2015 release rom from here http://devtester.ro/projects/lg-firmwares/#imei . This site has all of the LG roms. You can look it up by country and provider, or simply type in your imei. I installed the Rom using the LG flashtool, available here http://forum.xda-developers.com/showthread.php?t=2797190. I had hoped it was not patched; it was, so I am not sure if it was necessary.
2. I used Kingroot, available here http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461. As best I can tell, it is safe. If anyone knows of any issues, please advise. It has it's own software to control root permissions, but it says you can install SuperSU, I did, but it does not update the binary using the normal mode. I have not tried as yet to update via recovery.
3. I had some issues with the Kingroot su, particularly with Foldermount. I followed the Wolfdroid guide here http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html to remove the Kingroot su and install Chainfire's. Script will show some "failures." Be patient and let it run. It will open SU when complete, and SU will unistall the Kingroot software.
Good Luck!
I tried looking up my verizon lg g pad 7.0 and it didn't find anything
I have been trying to root Lenovo-phab-pb1-750m and referred here http://forum.xda-developers.com/general/xda-assist/root-root-help-lenovo-phab-pb1-750m-plus-t3427518. Well so many deivices in the market are stable to root, why rooting would cause so many problems with this device. Is it dependent on the exploit or the method to gain root access so that device should remain stable to root, without any malfunction. Mine I have experienced hardware keys volume down and power button not responding trying after kingroot. Kingroot which modifies the stock recovery, we will not be able to accept OTA Updates after trying this. I got the issue fixed from an ASC as when I tried reflash using qfil I got sahara error and ended in bootloop.
My main concern is to gain root and it should with full support of su binaries with busy box. Many times it is required to unlock bootloader and install custom recoveries for this I didn't mind doing it. But there is no support officially nor in XDA. But I found one thread here http://www.unlock-bootloaders.racing/2016/10/lenovo-phab-8142.html not sure they are referring to this model but they are referring to XDA site but I can't find it in this site. Are they referring to this model lenovo-phab-pb1-750m in the above thread and can I try it on my device model.
However, I noticed that there is one latest method called systemless root here http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/, Hence I want to upgrade to Android 6 and unlock its bootloader to try this. please advice how I can go about. In the mentioned link http://www.unlock-bootloaders.racing/2016/10/lenovo-phab-8142.html there is a method given to unlock the bootloader not sure this is for this model and am running lollipop version 5.1.1. Please check and provide me some info.
Hiee Guys ! I have used lots of android phones since 10 years and also familiar with them . I always try to root every phone but a problem is that every android phone cannot be rooted . So, please anyone tell me that how i can make root for any device and how i can make twrp for any device .
Thank You in Advance......
As far as compiling TWRP, you can start with this thread. Any device such as pixels upgraded to A10 don't have TWRP so because recovery has changed drastically and development of TWRP had not yet caught up.
Root is available for any device that is rootable. Magisk does a pretty good job of covering the bases and is under active development so properly reported issues are generally addressed.
Finding an exploit to be able to root a device is a different matter. Some, like pixels, are straightforward to root since if bought from Google (not a carrier directly) they have unlockable bootloaders allowing the installation of non-stock images. On a device that does not allow the bootloader to be unlocked, an exploit to achieve root must be found. That is often the issue combined with many of these devices do not attract developers to purchase them and thus no attempts are made.
Animesh._.Mamgain said:
Hiee Guys ! I have used lots of android phones since 10 years and also familiar with them . I always try to root every phone but a problem is that every android phone cannot be rooted . So, please anyone tell me that how i can make root for any device and how i can make twrp for any device .
Thank You in Advance......
Click to expand...
Click to collapse
If the device is a device that has a locked bootloader that can not be unlocked, you will not be able to use TWRP. These devices can only be rooted if there is a rooting app or rooting program available for PC or android that has an exploit that works on the device.
If the bootloader is locked, you won't be able to install TWRP or use TWRP to root the device and you will not be able to flash a Magisk patched boot.img to achieve root.
If there are no exploits available that are proven to work on the device, you won't be able to root the device.
Sent from my SM-S767VL using Tapatalk