Related
i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?
dalbig said:
i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?
Click to expand...
Click to collapse
Do you have TWRP installed? The automatic root feature in it worked fine for me.
mandrsn1 said:
Do you have TWRP installed? The automatic root feature in it worked fine for me.
Click to expand...
Click to collapse
I have the exact same problem with not being able to root every method I try
mowz9999 said:
I have the exact same problem with not being able to root every method I try
Click to expand...
Click to collapse
use toolkit for nexus 7 2013 and chose root and twrp recovery
work very well with me
murad052 said:
use toolkit for nexus 7 2013 and chose root and twrp recovery
work very well with me
Click to expand...
Click to collapse
I tried root kit too and it completes with no problems but superuser is never there and I don't have root access
mowz9999 said:
I tried root kit too and it completes with no problems but superuser is never there and I don't have root access
Click to expand...
Click to collapse
wired.. try this. first enable usb debuging mode from developer option
rebot to fast boot. and open tools kite i have version 1.0.2
chose ur device.
first install recovery TWRP.. number 6 i think in toolkit
then go back again and root the device number 4.. then chose number 2..
remember you have to unlock ir device first.
i hope this could work for you
dalbig said:
i have tried numerous ways to gain root on 4.4 but failed miserably. ive sideloaded and used nrt without success. supersu icon doesnt appear in the app drawer. any suggestions?
Click to expand...
Click to collapse
Install this in TWRP
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
Some later versions have non-functioning install scripts.
would using ART be a conflict maybe?
dalbig said:
would using ART be a conflict maybe?
Click to expand...
Click to collapse
no effect at all... i disable it just cuz of whatsapp
i still cant gain root.. im going to try using dalvik and see if there is a change.
All I did was I flashed TWRP then installed SuperSU 1.65 through TWRP. It says I have root access.
murad052 said:
wired.. try this. first enable usb debuging mode from developer option
rebot to fast boot. and open tools kite i have version 1.0.2
chose ur device.
first install recovery TWRP.. number 6 i think in toolkit
then go back again and root the device number 4.. then chose number 2..
remember you have to unlock ir device first.
i hope this could work for you
Click to expand...
Click to collapse
I still could not get superusersu installed Its able to flash over recovery fine but when rooting it says everything is fine but superuser never shows up and I dont have root access Thanks for trying I appreciate it
I had problems originally but I did like others. I downloaded the newest SuperSU 1.65.zip, moved it onto the N7. Booted into TWRP, selected Install and selected the zip. After that I rebooted from TWRP and I had root.
Sent from my Nexus 7 (2013) running 4.4
ive tried 1.55, 1.65 and 1.69... not one of them worked
dalbig said:
ive tried 1.55, 1.65 and 1.69... not one of them worked
Click to expand...
Click to collapse
Exact same thing here!:crying:
dalbig said:
ive tried 1.55, 1.65 and 1.69... not one of them worked
Click to expand...
Click to collapse
How are you installing them? Where are you downloading from? Have you tried just allowing TWRP to install root using the one it comes with?
sfhub said:
How are you installing them? Where are you downloading from? Have you tried just allowing TWRP to install root using the one it comes with?
Click to expand...
Click to collapse
Sideload, flashing the zips through twrp, using nrt... Got the zips of this forum.
Sent from my MB886 using XDA Premium 4 mobile app
dalbig said:
Sideload, flashing the zips through twrp, using nrt... Got the zips of this forum.
Sent from my MB886 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am just trying to understand where things are going wrong.
I went back and did a fresh factory image of KRT16O wiping user data.
I then copied
http://download.chainfire.eu/346/SuperSU/UPDATE-SuperSU-v1.55.zip
to the virtual sdcard.
I rebooted to bootloader and started twrp using
fastboot boot twrp.img
Then I chose to install SuperSU 1.55 using the above file.
Then rebooted to Android.
The SuperSU app was in the app drawer and I could perform su from adb shell and it would ask for permissions.
After I installed the factory images, I rooted my device. I don't use toolkits, because I think they make thing more complicated that it actually is. It is best to learn ADB whenever you can. That makes rooting so much easier.
Before I entered the bootloader, I downloaded SuperSU v1.69 through Chrome.
I made sure that all drivers were installed and began rooting.
Since my bootloader already was unlocked, I just flashed TWRP 2.6.3.1 with fastboot using this command:"fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img" without quotes.
That went smoothly, afterwards I rebooted to TWRP and flashed the zip... There I was rooted.
SuperSU: http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
TWRP: http://techerrata.com/file/twrp2/flo/openrecovery-twrp-2.6.3.1-flo.img
Hope this helped.
I just got root access! I found superuser in settings under apps but it would not show up in app drawer and would not give permissions to anything.I then disabled the updates back to superusers 1.55 and it showed up in app drawer and busy box asked for permission right away and root checker confirmed root access. Then updated through play store and everything is good now. Hope that helps
I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Edit: fixed it, just needed to uninstall and reinstall SuperSU! Thanks y'all
whmgreen said:
I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Click to expand...
Click to collapse
I am using stock L 5.0.2, and used Chainfire Auto Root to flash it on 5.0/.1/.2 without issue. I am running SuperSU 2.40 currently, and it does not appear to have an update pending on the Play store.
Did you try using 2.45 on a clean install that had not previously used 5.0? Wondering if something is getting gummed up from that, and sticking around on the older version.
Maybe try a fresh clean install on stock or whatever ROM you want and try 2.40/2.45 first before 5.0.
So question is, when we ill we be able to successfully root Android M?
Have tired with TWRP. get stuck on HTC One boot screen.
Had to flash stock ROM via stock recovery...
***
TWRP 2.8.7.0
SupersU 2.46 (also tried beta version 2.52 zip
You need to use latest SuperSU 2.65. Download
When TWRP want to install SuperSU check "Do not install" and reboot.
Hmm, I've done the above and it seemed to install correctly, but the SuperSU app which I installed from the zip is saying "no SU binary installed".
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Click to expand...
Click to collapse
Thanks, I've also tried the app store app, it says "no SU binary installed".
For me, I can't install SuperSU as system app. (not currently available in system-less root mode). And Twrp says I'm not rooted, asks to install
Try 2.64.zip no problems for me
Running 2.65
2.64 didn't work either, still get the same problem. Think I'll just try to install it the system way.
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
It worked well for me too:
http://forum.xda-developers.com/showpost.php?p=64493553&postcount=296:bien:
Gandalforce said:
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
Click to expand...
Click to collapse
MegaGalan said:
It worked well for me too[/url]
Click to expand...
Click to collapse
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
BenPope said:
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
Click to expand...
Click to collapse
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
sssssbarn said:
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
Click to expand...
Click to collapse
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
BenPope said:
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
sssssbarn said:
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
Click to expand...
Click to collapse
thanks for the files... fyi you transposed the numbers in the version of twrp. it is 2.8.7.1.
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Gandalforce said:
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Click to expand...
Click to collapse
I had problems with 2.66 as well. I reported it with a logcat and sticking with 2.65 for now
Same
Gandalforce said:
Same
Click to expand...
Click to collapse
Yeah same here.
Had to install TWRP twrp-2.8.7.1_CPTB-B1-hima and BETA-SuperSU-v2.65-20151226141550. then finally booted in to the OS.
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
Install Twrp or other custom recovery, dissable update cm recovery first in dev option, then install supersu.
Hello thanks a lot for your reply but twrp custom recovery requires root access
Diaa toulba said:
Hello thanks a lot for your reply but twrp custom recovery requires root access
Click to expand...
Click to collapse
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
NeoLogY said:
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
Click to expand...
Click to collapse
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Diaa toulba said:
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Click to expand...
Click to collapse
check it under Grand Android Development thread, there are twrp and cwm in zip file, can be flash through recovery. Same thread with cm12.1 that you flashed.
Flash superuser zip.
Your Rom is Pre-Rooted But you need to flash latest Superuser.zip to gain Root accesses .
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Diaa toulba said:
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Click to expand...
Click to collapse
Try type this in dialer *#1234#* or *#*#1234#*#*. If any of 5hose doesn't work, visit supersu thread.
OK I tried these lines but nothing happened can you give me link to supersu thread?
cm12 has root disabled by default. Activate it from developer options.
Or you can flash supersu
Diaa toulba said:
OK I tried these lines but nothing happened can you give me link to supersu thread?
Click to expand...
Click to collapse
After you flash supersu, did any app need root worked? Which version supersu did you flashed?
Used the non systemless one( 2.56 and below).
http://forum.xda-developers.com/showthread.php?t=2868133
Also might wanna try twrp recovery.
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Diaa toulba said:
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Click to expand...
Click to collapse
Good to know. New thing I've learned from your issue. Thanks for that.
I got the same problem as above I just flash su2.76 but it didn't worked out the cm update rec. Is disable ... It give installation completed but doesn't get rooted..
Hi,
Not too long ago a weird bug forced me to do a wipe of the device before i can start using it again (was all stock). Now i'm debating on a custom rom since the biggest obstacle for me (wiping the device and reinstalling everything again after) has been taken away.
I did however remember reading about devices with root and custom rom not being able to use the play store anymore since Google marked them as unregistered and such.
Is this still a problem? or is there a work around / fix for this to be found?
Thanks in advance.
DDakara said:
Hi,
Not too long ago a weird bug forced me to do a wipe of the device before i can start using it again (was all stock). Now i'm debating on a custom rom since the biggest obstacle for me (wiping the device and reinstalling everything again after) has been taken away.
I did however remember reading about devices with root and custom rom not being able to use the play store anymore since Google marked them as unregistered and such.
Is this still a problem? or is there a work around / fix for this to be found?
Thanks in advance.
Click to expand...
Click to collapse
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
abhishekjain.ims said:
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
Click to expand...
Click to collapse
Great thank you for your reply. Was losing hope i would not get an answer anymore.
Does this mean it's possible to use Google Pay with a custom rom? Or just the play store?
Edit: I think I have found my answer reading other threads, that it does work.
abhishekjain.ims said:
Its not a problem if you flash custom rom + gapps + magisk altogether. Once all those files are flashed successfully then only reboot to system & your Google play store will say your device is certified.
Click to expand...
Click to collapse
Alright so i have managed to install lineage and gapps, but somehow i cant get magisk to work.
1) can i just leave it like this without magisk and not have problems with google uncertified stuff?
2) if the above can't be done or if i can still somehow install magisk, please explain how. (i rooted one other time long ago with superSU, i dont have experience with magisk). I followed: https://www.xda-developers.com/how-to-install-magisk/ but i get an error 1 when trying to install in TWRP.
Please help and thanks in advance
DDakara said:
Alright so i have managed to install lineage and gapps, but somehow i cant get magisk to work.
1) can i just leave it like this without magisk and not have problems with google uncertified stuff?
2) if the above can't be done or if i can still somehow install magisk, please explain how. (i rooted one other time long ago with superSU, i dont have experience with magisk). I followed: https://www.xda-developers.com/how-to-install-magisk/ but i get an error 1 when trying to install in TWRP.
Please help and thanks in advance
Click to expand...
Click to collapse
To make magisk working properly just make sure you have /data partition EXT4 formatted also install this version of TWRP for Lenovo p2 https://androidfilehost.com/?fid=5862345805528044694 after that install latest version of magisk through recovery & you will be able to install magisk successfully.
anewman said:
Does this mean it's possible to use Google Pay with a custom rom? Or just the play store?
Edit: I think I have found my answer reading other threads, that it does work.
Click to expand...
Click to collapse
Correct. Even with Magisk root Google Pay and other secure banking apps work fine. You may just need to activate Magisk hide for certain apps.
abhishekjain.ims said:
To make magisk working properly just make sure you have /data partition EXT4 formatted also install this version of TWRP for Lenovo p2 https://androidfilehost.com/?fid=5862345805528044694 after that install latest version of magisk through recovery & you will be able to install magisk successfully.
Click to expand...
Click to collapse
Thank you for your reply.
Yes i did format the data partition to ext4. I used the TWRP version of their original website, searched for the lenovo p2a42 and found kuntao_row. (twrp-3.2.3-0-kuntao_row.img to be exact). Is there a difference in the version you linked there and this one ?
I currently have lineageos with gapps installed and working. If i am going to try and make magisk work. Are the following steps correct?:
1) install magisk manager
2) shut down and enter fastboost
3) flash different TWRP version
4) Boot into TWRP recovery
5) install magisk from ext sd
6) Then done? Or do i need to reinstall LineageOS and gapps again after those steps? And maybe wipe and reformat again at some points? if so, where?
Again thanks in advance and i really appreciate the help.
DDakara said:
Thank you for your reply.
Yes i did format the data partition to ext4. I used the TWRP version of their original website, searched for the lenovo p2a42 and found kuntao_row. (twrp-3.2.3-0-kuntao_row.img to be exact). Is there a difference in the version you linked there and this one ?
I currently have lineageos with gapps installed and working. If i am going to try and make magisk work. Are the following steps correct?:
1) install magisk manager
2) shut down and enter fastboost
3) flash different TWRP version
4) Boot into TWRP recovery
5) install magisk from ext sd
6) Then done? Or do i need to reinstall LineageOS and gapps again after those steps? And maybe wipe and reformat again at some points? if so, where?
Again thanks in advance and i really appreciate the help.
Click to expand...
Click to collapse
Just download latest version of the magisk, keep it somewhere in the storage then reboot to recovery, update your current recovery by the recovery I have given you above, reboot again to recovery then flash magisk & reboot to system. After successful flashing of magisk zip install magisk manager apk from play store or Google.
abhishekjain.ims said:
Just download latest version of the magisk, keep it somewhere in the storage then reboot to recovery, update your current recovery by the recovery I have given you above, reboot again to recovery then flash magisk & reboot to system. After successful flashing of magisk zip install magisk manager apk from play store or Google.
Click to expand...
Click to collapse
Perfect. Worked like a charm! Hero
So the TWRP version i used was the wrong one? Although it came from their website?
DDakara said:
Perfect. Worked like a charm! Hero
So the TWRP version i used was the wrong one? Although it came from their website?
Click to expand...
Click to collapse
Yes, the TWRP which I gave you is special. Cheers :good:
abhishekjain.ims said:
Yes, the TWRP which I gave you is special. Cheers :good:
Click to expand...
Click to collapse
Hi,
Back again haha. It still works properly and almost have everything set up as i wanted to. One more question arose:
The system is telling me there is a new version update for lineageos.
I am assuming i just click download on the latest version, then reboot into recovery (backup as optional), click install, search the zip and let it install then reboot again is the way to install it. But do i have to reinstall gapps? and does this process delete any data or is it just like a normal update and everything stays the way it was before installing the update?
Thanks again in advance.