Related
hey, im new to Android, after moving on from my Iphone 4 to my the new M9, i start wondering.
i got my phone unlock booter threw the devHTC,
got it S-ff with the great app (that i forgot the name) which i payed for it.
installed SuperSu update to give roots privilages, and also BusyBox Free.
thoese are my problems:
1. installed SB game hacker, and its says after i gave it root privilages that i dont gave it, or i dont have root acces.
the thing is that with GameKiller i do get root access...
2. trying to apply patch with the Lucky Patcher sometimes i get root unstable window error that asked me to update my
SuperSu even thew its update to last vesrion.
3. again with Lucky patcher (which does get root privilages for sometimes) - i try to install threw the toolBox -> patch to android -> Signature Verificcation Status Always True , and after it reboot i go back to it and it says its not patched. like the patch failed.
i tryed to clear the core.jar and the service.jar but it doesn't help, it doesn't patch it.
4. i got the new System Update 1.36.709.3 and when i press Install now, it enter the teemmod (the developer mode which i can wipe, install and everything) and does nothing. after reboot to system it ask me again if i want to install, and again go to this dev mode (which is needed for installing supersu to the system).
5. same as befor, apps like clean master doesn't get superuser privilages and cannot disable auto start apps even thew superSu do allow it. also, CPU manager in Battery Life app always get off after a while, or after a reboot.
i hope i could get help cuz im really lost in finding a way to fix all of this.
Please help?
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
OK, by flash u mean to go to recovery mode and install the su u told me right?
waltobc6 said:
OK, by flash u mean to go to recovery mode and install the su u told me right?
Click to expand...
Click to collapse
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
TwinAdk said:
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Okay I got 3 options - reinstall which is not what I need
And 2 more which are cleanup for switching userroot app
And a full cleanup for preparing uproot.
Which one should I pick.
Also I used last time Supersu 2.49, and now from the site is gave me I downloaded 2.46
I understand 2.49 is beta - so which one to pick?
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
TwinAdk said:
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
Click to expand...
Click to collapse
Not having SD - and install it from the internal storage of the phone can **** it up?
I press. Uninstall and it get stuck on it. I let it run for more then 40 min
And it didn't finish
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
TwinAdk said:
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
Click to expand...
Click to collapse
I mean got stuck on the please wait- I was able to switch app.
Also after trying few time to uninstall it - it worked.
I flashed the super 2.49 opened google store and unlocked the app.
The CPU manager in doctor battery still turn off after a while.
Also auto start app disable in clean master still says it don't have room access even
I have it again.
And I tried to install in lucky patcher the signal true - and after long "please wait"
And a auto robot it says it not patched.
What to do ?
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
TwinAdk said:
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
Click to expand...
Click to collapse
I do get the approve window, also it shows the permission granted
In the super all allowed listed.
I didn't change any stock rom. I'm on the default of HTC m9 system.
And I'm still-off, and unlocked
That is really wired... Either we are missing something obvious, or your system is really messed up..
TwinAdk said:
That is really wired... Either we are missing something obvious, or your system is really messed up..
Click to expand...
Click to collapse
How can I do a full reset, cuz factor reset still leave the Supersu broke
Look in the forum for it
TwinAdk said:
Look in the forum for it
Click to expand...
Click to collapse
Please oh: I'm into it for like week without any good sucsses
Guide , help please?
Find your device/carrier RUU and start over, if you went through all the steps to get s off, you should have made a back up that you could start over with in recovery. If not search for for the RUU or original system file in the m9 forum For your SPECIFIC device.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
waltobc6 said:
How can I do a full reset, cuz factor reset still leave the Supersu broke
Click to expand...
Click to collapse
Try entering ##786# on your dialer key paid
I bought my phone in Bolivia, and at the box it had Chinese so I think it's a new movie9 from Asia. How can I check my SPECIFIC so I can download what's needed
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try
Hi guys, I did the safe upgrade on my DevEd from 5.1.1 to 6.0.1. TWRP 3.0.2-0 starts up correctly. Then I try to choose any zip file to flash and TWRP immediately restarts itself instead of flashing it. Did I do something wrong with this upgrade, and why can't I flash anything using TWRP?
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
FMXP said:
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
Click to expand...
Click to collapse
wow 2 days messing around with this. man oh man thank you for the find.
works great!
I am rooted and unlocked still on 5.1.1 I updated to MM bootloader was unlocked after I updated but couldn't get root with the NewKingRoot app. It didn't give me the option to root. I also tried KingOroot and it failed also. When I was on MM when I rebooted my device I didn't see the custom lock icon on the splash screen but when I booted to download mode it said Mode developer. I work so much I can only spend a few hrs a day working on this. I would however rather go back to 4.4.4 I really miss kitkat.
Sent from my SM-N920F using Tapatalk
Having the same problem. I finished Bootloader Unlock and Upgrade to Marshmallow and now sitting on unrooted with recovery 3.0.2-0. I was rooted but one of the things I tried is a factory reset, Just throwing anything at it to see if it sticks.
ANYWAY If I try to flash supersu it starts listing activity. Gets to "creating space" phone immediately crashes when that displays with a vibration and can't turn phone back on without a battery pull. I have reflashed twrp via odin. I've tried flashing supersu from both internal and external card. No joy. I also tried checking mount system. It will crash with setting default off. Anyone have any ideas on what could be the problem?
My guess is it's something I'm not thinking and if I get a fix before anyone post I post it.
edit:
Well I could never get it to flash supersu but I did restore the Jasmine 7.0 backup. So that worked.
Is there a way to root the (2015) Nvidia Shield Android TV 500gb Pro running Nougat? I know there is a way to do the 16gb version.
Thanks
SuperRedX said:
Is there a way to root the (2015) Nvidia Shield Android TV 500gb Pro running Nougat? I know there is a way to do the 16gb version.
Thanks
Click to expand...
Click to collapse
I just updated mine this evening.
Installed SuperSU from TWRP, and everything is good, so no problems.
hallydamaster said:
I just updated mine this evening.
Installed SuperSU from TWRP, and everything is good, so no problems.
Click to expand...
Click to collapse
Okay thanks. I will try it out later.
hallydamaster said:
I just updated mine this evening.
Installed SuperSU from TWRP, and everything is good, so no problems.
Click to expand...
Click to collapse
THX 4 reply and info but when you update with ota it should reflashed your recovery and locked your bootloader again, right?
I try to find a simple way to flash the new nougat-update on my foster device (pro, 2015 version) without need to unlock the bootloader and reflash the twrp-recovery again after it. Did you use this recovery?
Greetings by Idijt
I_did_it_just_tmrrow said:
THX 4 reply and info but when you update with ota it should reflashed your recovery and locked your bootloader again, right?
I try to find a simple way to flash the new nougat-update on my foster device (pro, 2015 version) without need to unlock the bootloader and reflash the twrp-recovery again after it. Did you use this recovery?
Greetings by Idijt
Click to expand...
Click to collapse
I flashed the official TWRP when it came out. Since then, I haven't done anything.
Yesterday I just applied the full OTA as asked by the SATV. I didn't replace recovery or remove root.
TWRP flashed the OTA just fine, but halted on the restart, so did that manually.
After that, I let it boot. Restarted to recovery, which was still my TWRP, and flashed newest SuperSU.zip.
Job done!
I was running rooted MM and accepted nougat update, the update used TWRP and all went well just lost root, so I sideloaded the supersu and all working well.
Hello to all. My shield was with root before upgrading to Android 7, after I reinstalled TWRP and I loaded supersu. At first start everything worked as it should and then lose root permissions on the following day. Now when I try to install supersu seems to work, TWRP does not return errors but when I restart the shield pro, the permissions are not active. If anyone can help me solve. I'm sorry for my English, I use google translate
I_did_it_just_tmrrow said:
THX 4 reply and info but when you update with ota it should reflashed your recovery and locked your bootloader again, right?
I try to find a simple way to flash the new nougat-update on my foster device (pro, 2015 version) without need to unlock the bootloader and reflash the twrp-recovery again after it. Did you use this recovery?
Greetings by Idijt
Click to expand...
Click to collapse
Yes it reflashed the recovery partition, but why would it relock the bootloader? In any case I was able to reflash TWRP (as my Recovery), and than SuperSU, (as One does) on my '15 Pro (500Gb), without any major heartburn.
Pizzo78 said:
Hello to all. My shield was with root before upgrading to Android 7, after I reinstalled TWRP and I loaded supersu. At first start everything worked as it should and then lose root permissions on the following day. Now when I try to install supersu seems to work, TWRP does not return errors but when I restart the shield pro, the permissions are not active. If anyone can help me solve. I'm sorry for my English, I use google translate
Click to expand...
Click to collapse
Thankfully I haven't quite ran into that problem. But being slightly more careful to not slide (or swipe) the Permissions Bar (at TWRPs first boot. I can only presume that having done this, before ' cause I was an idiot, was what caused me to softbrick after the Update)... So as to avoid future softbricks.
Again everything seemed to go well I was in fact rooted, but because I opted not to reset the Permissions at that first boot. It turned out that the /system Partition was still set as Read Only! Which was a bit of a be-yitch, meaning the only way I could get AdAway working this was was to eventually open /system and set a symlink to /data/data/hosts, than make /system Read Only again.
There isn't really many other Apps sans ES File Explorer Pro that also require such special Permissions, that I'd have an immediate use for. And, IIRC ES File Explorer never gave me as much trouble as AdAway has.
So chances are that this is where you should be looking. e.g. Your Filesystem Permissions. Of course you change these ultimately at your own risk.
I think I know well the TWRP operation, I use it for a long time on all my phones. I cleaned it up and repeat the procedure from the beginning but was not successful. Not even install supersu, if I set it manually, on startup it tells me that the device is not rooted
How-To Root and Remove Bloatware on the new QE1 Update:
1 ) Via ODIN/OTA/Smart Switch, install the new QE1 update (Firmware links available on SamMobile)
2) ODIN install the TWRP recovery 3.1.1 (TWRP link: https://dl.twrp.me/zenltetmo/)
3) Download the SuperSU zip onto your phone(SU link in this post: https://forum.xda-developers.com/showpost.php?p=72187304&postcount=5)
4) Enter recovery mode and install the SuperSU zip.
You will only get one boot with this zip. If you reboot while still rooted, you will get stuck in boot.
When your phone boots for the first time, you can install Titanium Backup and remove all the bloatware. DO NOT uninstall the Samsung Music app. the stock ROM cannot load without it!!!
When finished removing your apps, open the SuperSU app, go to settings and select Full Unroot. Your phone will reboot and should load normally.
If you ever need root again, repeat step 4 and use your initial boot for your root modifications.
alexknop said:
How-To Root and Remove Bloatware on the new QE1 Update:
1 ) Via ODIN/OTA/Smart Switch, install the new QE1 update (Firmware links available on SamMobile)
2) ODIN install the TWRP recovery 3.1.1 (TWRP link: https://dl.twrp.me/zenltetmo/)
3) Download the SuperSU zip onto your phone(SU link in this post: https://forum.xda-developers.com/showpost.php?p=72187304&postcount=5)
4) Enter recovery mode and install the SuperSU zip.
You will only get one boot with this zip. If you reboot while still rooted, you will get stuck in boot.
When your phone boots for the first time, you can install Titanium Backup and remove all the bloatware. DO NOT uninstall the Samsung Music app. the stock ROM cannot load without it!!!
When finished removing your apps, open the SuperSU app, go to settings and select Full Unroot. Your phone will reboot and should load normally.
If you ever need root again, repeat step 4 and use your initial boot for your root modifications.
Click to expand...
Click to collapse
I can't seem to Odin TWRP correctly. After the reboot, my phone just sits at the T-Mobile screen .... any suggestions?? I keep having to flash QA1 stock rom to get my phone back.
I did this yesterday and after I did the full unroot I got stuck in boot loop at the Galaxy s6 edge + screen. So I just used Odin to get back to normal.
Kidlat917 said:
I can't seem to Odin TWRP correctly. After the reboot, my phone just sits at the T-Mobile screen .... any suggestions?? I keep having to flash QA1 stock rom to get my phone back.
Click to expand...
Click to collapse
I suggest using a different odin version. Try 3.07.
And it might sit on the TMobile screen longer than usual so I would give it at least 5 minutes.
darthmalus said:
I did this yesterday and after I did the full unroot I got stuck in boot loop at the Galaxy s6 edge + screen. So I just used Odin to get back to normal.
Click to expand...
Click to collapse
Why would you unroot ?
Sent from my SM-N900T using XDA-Developers Legacy app
tupirujp said:
Why would you unroot ?
Sent from my SM-N900T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'd also like to know why this would be necessary. Removing the bloat would make it not possible to receive ota updates anyway, would it not?
Is this phone still rootable?
Markyzz said:
Is this phone still rootable?
Click to expand...
Click to collapse
Why would it not be? All the tools and resources necessary are here, so unless you physically changed hardware in your device, you can still root it. Granted, you may not be rooted with the latest Android OS. But the point is, once the puzzle of root on a given device is solved, root is always available.
bobpantsspongesquare said:
Why would it not be? All the tools and resources necessary are here, so unless you physically changed hardware in your device, you can still root it. Granted, you may not be rooted with the latest Android OS. But the point is, once the puzzle of root on a given device is solved, root is always available.
Click to expand...
Click to collapse
I asked because sometimes a new update will make a device unrootable