Related
Hi all,
Bit of a noob query, apologies.
I had never rooted a device until last night when I took the plunge with WugFresh's (thankyou so much) program. Great program had an issue with the adb drivers (turned out I needed more power for the USB port) hence I plugged the USB into the rear port and it magically appeared and installed, thus if you have problems installing the driver make sure you are plugged into the rear.
But I am now on the 4.04 google factory flash.
Now my query is, now I am on this 4.04, I presume I am no longer rooted. Can I use WugFresh's program to root the phone again or do I have to wait for another update to the program?
I was rather twitchy during rooting, expecting power cuts across the UK, earth tremor to knock the lead out at the wrong time, aliens to come down and screw it up etc that I dare not try it (don't really understand what I did even though it has worked)...
There is a program on now called superuser, but does not seem to have root access, so I presume I am not rooted now??
Any help would be appreciated.
Thanks
Darren
I did refer to a guide but can't post the link to it.
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
pittnuma said:
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
Click to expand...
Click to collapse
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
does the toolkit update itself to include the 4.0.4 root? no, so download the new toolkit..also u dont need to try 3 toolkits, u need the latest and select gsm 4.0.4
if u use the su.zip, u need the latest working with the 4.0.4
again what make u say "still no root"? with no details we can't help u
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
hEaTLoE said:
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
Click to expand...
Click to collapse
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
pittnuma said:
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
Click to expand...
Click to collapse
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Hi guys, just curious but is there anyway to gain root temporarily in 4.0.4 without unlocking bootloader? Similar to the escalation of privileges hack that worked on 4.0.1/4.0.2.
I want to remove the /system/bin/su and /system/app/Superuser.apk files on the device to get rid of the "Unsupported Device" warning in Google Wallet.
Thanks in advance.
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
Ahh right, I have the Superuser, however when I tried the app suggested earlierit stated device not rooted...
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
This is not entirely true. You can have the Superuser app in your app drawer and still not have root. The permissions on su need to be set properly.
Diger36 said:
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
Click to expand...
Click to collapse
pittnuma said:
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
Click to expand...
Click to collapse
A look at the first page.... Ah well, glad you sorted it out...
Sent from my Galaxy Nexus using xda premium
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
soupmagnet said:
Flash MoDaCo rom. It's a pre rooted stock with gapps and GFS included.
Click to expand...
Click to collapse
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Thibor69 said:
DO you think this is the best way to go ?........ or should I go ahead with the only 6.3 root guide I have seen here on this site. (pooky900 guide or something sorry forgot his name) Or do you think it best to wait for a easier newer 6.3 rooter to show up ?? Just your thoughts .... I am not holding you to anything here :O)
Thanks
Click to expand...
Click to collapse
I've tried to explain much of this a couple of times now, so here's my final attempt...
The generally accepted procedure for rooting or installing a ROM:
1) Get to fastboot mode by utilizing either...
a) a factory cable
b) fbmode
2) Install recovery and custom bootloader
3) Either root by installing su and Superuser.apk or flash a custom ROM
To get back to 6.2, you will still have to do #1 & #2 and flash the 6.2 zip package like you would any other ROM. Amazon's software will not allow you to downgrade the software through stock so you can use the BurritoRoot exploit.
It's not likely for someone to come up with a newer/easier method for rooting 6.3 because...
a) It's pretty straightforward as it is
b) No one spends the time to do it when the old way works perfectly well
I've laid out the procedure in excruciating detail here...
http://forum.xda-developers.com/showthread.php?t=1638452
I invite you to keep exploring easier ways to do this, so I can make the how-to above simpler and shorter, but I doubt you will find one. Good luck.
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
soupmagnet said:
MoDaCo comes with 6.3 pre rooted along with gapps and Google Framework Services preinstalled. It is by far the easiest route to get a rooted stock because the work has already been done for you. All you have to do is flash it in recovery. (Assuming you have recovery installed of course)
Last time I heard, you still have to rename otacerts.zip to prevent any OTA updates screwing up everything but I'm not 100% on that. You should definitely look into it, though. People here are pretty good at staying on top of the latest updates and making flashable versions that won't undo everything you have so far (i.e. break root, uninstall recovery, etc.)
Pokey9000's rooting method is very effective and good if you want to learn but unnecessary IMO if you just want a rooted stock that works well. But I think you should definitely have fbmode on your device if you are using Windows. It could come in very handy when your drivers are being stupid.
It should be noted that I don't use stock and never have so I couldn't tell you much about the differences between MoDaCo and straight rooted, as in whether or not you can watch Prime Video with it, but there are plenty of stock users here that can help you sort it out.
Click to expand...
Click to collapse
Just so everybody is on the same page and because I've done more rooting experiments the last few days than I care to admit.
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell. I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. For 6.2.x, the rooting method was to use the BurritoRoot exploit to gain root and then get to fastboot mode by using idme. Amazon closed that hole so BurritoRoot can no longer be used for 6.3.x. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... so, the process has been reversed... su -> fastboot for 6.2.x and now fastboot -> su for 6.3.x. So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Laquox said:
Kindle Fire Utility .95 works easily on 6.3 and while it's not BurritoRoot it is still a simple one click root utility with a lot of features to make the rooting process easy. Any particular reason you want Burrito?
Click to expand...
Click to collapse
KFU is broken for whatever reason. It does get you su, but doesn't install the Superuser.apk... I don't know why and I'm not interested in debugging it. I'm not sure if sideloading Superuser.apk is the only thing that needs to be done after its "rooting" process, but it also installs the old versions of FFF and TWRP. That causes headaches all around for people that don't know their way around the bootloader and recovery. Otherwise, it's great!
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
kinfauns said:
...
Click to expand...
Click to collapse
Yeah, sorry about that. I was replying to his post and you beat me to the punch.
So, yeah...what kinfauns said
Thibor69 said:
I bought a new KF and it has 6.3 on it. I would like to root via BuritooRoot3 but I need 6.2 to run his app. Is there any way to take a stock 6.3 KF and get it back to a stock 6.2 ???
Thanks !
Click to expand...
Click to collapse
You can use the Kindle Fire Utility 0.9.5
That's what I used to root my Kindle on 6.3
You just have to sideload the superuser.apk file though
kinfauns said:
Thibor69 said in another one of his threads that he wants to go to the Hellfire ROM. He's not interested in rooted stock, as far as I can tell.
Click to expand...
Click to collapse
.....Yes that is what I want to do. I don't care about stock at all.
kinfauns said:
I agree though... I don't know why someone would take the time to root when MoDaCo seems to have done all the heavy lifting already. MoDaCo users also say that they can use some app (the name escapes me at the moment) that switches root on and off so they can watch videos.
Click to expand...
Click to collapse
.....I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
kinfauns said:
pokey9000 doesn't have a rooting method. He has a fastboot exploit that is being used to root 6.3.x in a guide originally written by jcase. Because jcase wasn't interested in building another root exploit, he published that guide as an alternative. The rooting method for 6.3.x is to use pokey9000's fbmode to get to fastboot and then install su privileges through TWRP... So, you still have to use pokey9000's fbmode to get to fastboot and install a recovery (and bootloader) if you want to install any ROM.
Click to expand...
Click to collapse
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
kinfauns said:
KFU uses the same fbmode exploit that I've outlined in my guide, so the process is essentially identical. If you follow along with what I have there, you'll get all the current software and a working Superuser. If you use KFU, you can go back and reinstall all the stuff I mentioned above.
Click to expand...
Click to collapse
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
I am ready to start this process now .... but I want to be 100% sure I have a recovery image in case I soft-brick somehow.
You guys are great ... and thank you for helping me !!!
Cheers
Thibor69 said:
I hear what you are saying. Since I don't care about amazon video's, I see no reason to keep any aspects of stock at all .... so I guess I should skip MoDaCo's method also ... right ?
Click to expand...
Click to collapse
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
.....Ok I understand. My question tho would be after I get to fastboot, you said to install a recovery and bootloader. Isn't TWRP the recovery method ? and which bootloader do I install ? And I do this all from within fastboot ? Also, what about FFF ? were does that come into play.
Click to expand...
Click to collapse
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
But you mentioned that KFU is broken ... so I guess I should just follow your method.
ONE LAST NOTE: Were are the drivers for Kindle Fire. I plug into PC (win7) and it doesn't find driver for kindle, but I still have access to the internal somehow ..
Click to expand...
Click to collapse
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Ok so to sum it up:
1) install kindle drivers, be sure PC see's Kindle and be sure adb is working
2) install TWRP
3) install latest bootloader (via link below)
4) then flash ROM ?
Cheers
soupmagnet said:
Right, sort of. Any custom rom you flash will be rooted, but you need recovery to flash it.
TWRP is the preferred recovery. You can install the latest bootloader from within recovery... http://forum.xda-developers.com/showthread.php?p=25598837 ...and use fastboot to change to recovery bootmode
The drivers for the KF can be found in the KFU folder along with an installation batch file.
Click to expand...
Click to collapse
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
soupmagnet said:
Sounds about right. There's a possibility you may need to fix your drivers again at some point in the process. If for some reason you can't get fastboot to connect:
http://forum.xda-developers.com/showthread.php?t=1625356
&
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
Many thanks !
Apologies for the very simple question, but I've yet to find a definitive yes/no answer on this.
I'm interested in:
- unlocking the bootloader
- rooting my nexus
With a view to install root-enabled apps like Titanium etc.
I DO NOT want to install any custom ROM (at least for the time being!) as I am happy with stock ICS 4.0.4
If I do the above (unlock & root) - will I still be notified about and be able to install OTA updates from Google?
(I'm on yakju)
Cheers
brypie said:
Apologies for the very simple question, but I've yet to find a definitive yes/no answer on this.
I'm interested in:
- unlocking the bootloader
- rooting my nexus
With a view to install root-enabled apps like Titanium etc.
I DO NOT want to install any custom ROM (at least for the time being!) as I am happy with stock ICS 4.0.4
If I do the above (unlock & root) - will I still be notified about and be able to install OTA updates from Google?
(I'm on yakju)
Cheers
Click to expand...
Click to collapse
you will be notified and assuming you still have the stock recovery and not CWM and do not modify any system files, you can install it.
is method given by Jubakuba the only way to root Galaxy Nexus??
http://forum.xda-developers.com/showthread.php?t=1529058
<lie>
Yes.
</lie>
Really though...it's the best way.
If you want to use other methods *cough* toolkits *cough* they'll probably work.
But if you end up soft bricking your phone at some point (Trust me. You will.) You'll want the tools in place (and know that they're working and how to use them) to get you unstuck.
gagan007 said:
is method given by Jubakuba the only way to root Galaxy Nexus??
http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Not the only but the safest and the proper way and the learning way
Galaxy Nexus AOKP m5 Franco kernel m3
Zepius said:
you will be notified and assuming you still have the stock recovery and not CWM and do not modify any system files, you can install it.
Click to expand...
Click to collapse
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
brypie said:
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
Click to expand...
Click to collapse
unlock: no
root: no
the problem is, most root methods flash clockwork recovery. this does break OTA.
Jubakuba said:
<lie>
Yes.
</lie>
Really though...it's the best way.
If you want to use other methods *cough* toolkits *cough* they'll probably work.
But if you end up soft bricking your phone at some point (Trust me. You will.) You'll want the tools in place (and know that they're working and how to use them) to get you unstuck.
Click to expand...
Click to collapse
Hi.
I'll read through your guide - looks good.
However, you seem to imply that to get root, I have to install a custom recovery??
Is there a separate step to simply install root using the default recovery?
Easiest method...
https://developers.google.com/android/nexus/images#yakju
You can (and should) download the factory images.
From there...unzip the .tar and the .zip inside of it.
The .zip contains a recovery.img
Flash that using my guide...post 3, I believe...detailing alternative (in this case, stock) recoveries after rooting.
brypie said:
Thanks.
So, I assume form your answer that unlocking and rooting does not modify the system files enough to break ota?
Click to expand...
Click to collapse
To expand on what Zepius said:
1) unlocking does not modify any system files at all.
2) "rooting" just means place two files on your system partition. Nothing more. As long as you don't modify or delete files already there, you can add whatever files you want.
brypie said:
Hi.
I'll read through your guide - looks good.
However, you seem to imply that to get root, I have to install a custom recovery??
Is there a separate step to simply install root using the default recovery?
Click to expand...
Click to collapse
You do not need to install a custom recovery to root. Booting a custom recovery allows you to do the same thing. In Jubakuba's guide, replace
fastboot flash recovery <name-of-recovery.img>
with
fastboot boot <name-of-recovery.img>
and it will temporarily boot the custom recovery from your PC.
So far I've had only Samsung phones, which were rooted by flashing a zip file through the built-in recovery (containing signed SuperSU).
Now I have a 2013 Nexus 7 and I'm looking at the rooting guides and I see bootloader unlocking, flashing custom recoveries and a lot of other things which personally confuse the hell out of me as to why are they needed.
So I wanted to ask if there is a way to just flash a zip file with the SuperSU (and buzybox) app like how it's done on the Samsung phones? Or if there is a method that doesn't require replacing the stock recovery / flashing ROM components?
If anything its easier than any Samsung device but the thing is don't Root if it confuses you at least until you understand how to do it there is tons of guides online
spinninbsod said:
If anything its easier than any Samsung device but the thing is don't Root if it confuses you at least until you understand how to do it there is tons of guides online
Click to expand...
Click to collapse
That's kind'a my question, it's not that I don't know how, I just don't get if all the side-stuff in 90% of the guides is actually needed, so I asked if there is a way to just get SuperSU working without any custom-recoveries or other side-things.
To my knowledge, you need to have a custom recovery to root it. Unlocking the bootloader helps with this, as it ensures recovery and root sticks.
Or, just use the Wugfresh Nexus Root Toolkit to unlock and root.
CrisR82 said:
That's kind'a my question, it's not that I don't know how, I just don't get if all the side-stuff in 90% of the guides is actually needed, so I asked if there is a way to just get SuperSU working without any custom-recoveries or other side-things.
Click to expand...
Click to collapse
I was in the exact same position as you four days ago, up until then the only android devices I had owned were the Samsung Galaxy S2 and S4. It is quite different to the rooting process on the samsung devices but just as you did with the Samsung devices you will learn as you go along. My bootloader is unlocked, rooted with a custom rom and it was pretty easy to do
CrisR82 said:
That's kind'a my question, it's not that I don't know how, I just don't get if all the side-stuff in 90% of the guides is actually needed, so I asked if there is a way to just get SuperSU working without any custom-recoveries or other side-things.
Click to expand...
Click to collapse
A sideload would only be needed if you didn't dump SuperSU on the phone first.
Unlock bootloader
Flash TWRP
Flash SuperSU
Done
Get wugfresh's nexus root toolkit. It's made for the novice in all of us.... Works great, self updates, awesome help section.. Look into it.. It's made specifically for the nexus line of products
Thanks for the replies guys, but noone seems to say what is the minimum that neds to be done for rooting.
I'll re-ask my question in a different way:
When rooting, does the bootloader always have to be unlocked and a custom recovery always needed to be installed?
CrisR82 said:
Thanks for the replies guys, but noone seems to say what is the minimum that neds to be done for rooting.
I'll re-ask my question in a different way:
When rooting, does the bootloader always have to be unlocked and a custom recovery always needed to be installed?
Click to expand...
Click to collapse
Bootloader needs to be be unlocked, but can be relocked after rooting
AFAIK, you can use stock recovery, but custom offers better options/control over the situation. Most roms/kernels are flashed via twrp or cwm..... You can flash through rom toolbox if you choose to stay stock recovery
You can use Towel root to root your tablet in about 30 seconds. It'll also unlock your bootloader for you.
Cousin recovery is only needed of you intend to flash kernels and Roms and the like. If, like me, you only want root for installing things like xposed then you don't need to bother with one.
Sent from my Nexus 4 using XDA Free mobile app
CrisR82 said:
Thanks for the replies guys, but noone seems to say what is the minimum that neds to be done for rooting.
I'll re-ask my question in a different way:
When rooting, does the bootloader always have to be unlocked and a custom recovery always needed to be installed?
Click to expand...
Click to collapse
Yes, all the steps that are listed are required for rooting your Nexus. I understand what you are asking and I was also hesitant at first, but it was super easy to root and I didnt use the WugFresh took kit I manually rooted mine, following Zedomaxs Video tutorial, that way I could stop and Pause it at every step to make sure things were happening as they should here is the link
https://www.youtube.com/watch?v=X1cD-JXRGX8
I confirm towelroot works on the 2013 nexus 7. After rooting unlock bootloader with app from google play. This method does not wipe user data or need a computer at all. And if root is lost and the towelroot exploit is patched with the next os update you can reroot the old way.
Sent from my Le Pan TC1020 using Tapatalk
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
GroovinChip said:
I've seen posts instructing how to root via SuperSu and Magisk; I know those methods have to be done a certain way because of the partition system. But I have not seen any posts about Kingroot. Would it work the successfully? I imagine it going like this:
1) root with Kingroot
2) boot to TWRP via ADB
3) flash TWRP
4) flash SuperSU if desired
Or
4) if desired, flash a kernel, flash Magisk, flash TWRP again
5) boot to system, uninstall Kingroot
Does that sound right? Would Kingroot even work to begin with?
Click to expand...
Click to collapse
Why use kingroot? Remove the first step and you basically have hot to flash su..
pcriz said:
Why use kingroot? Remove the first step and you basically have hot to flash su..
Click to expand...
Click to collapse
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Sent from my Google Pixel XL using XDA Labs
GroovinChip said:
True, but if you happen to want to root while away from a computer it could be useful.
In any case, it was simply a curiosity about whether it would even work at all. I doubt I'd ever use Kingroot for my Pixel.
Click to expand...
Click to collapse
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
pcriz said:
Oh okay. I was just curious. I haven't tried kingroot but since rooting requires patching the boot.img and I don't know if you can do that while booted into the OS I'd say no. I am only assuming how kingroot works but again whatever the solution it needs to be able to make changes to the boot.img without already having root privs.
The closest solution I would see is having twrp already loaded.
Click to expand...
Click to collapse
This makes sense. Thanks
Sent from my Google Pixel XL using XDA Labs
Even if it did work it wouldn't work the way you are describing. King Root basically acts like malware and refuses to give root privileges to any app that interferes with its functioning. Adaway won't work with King Root because adware is part of the King Root program. You also wouldn't be able to install SU while King Root is on your phone. King Root will actively prevent you from installing any other root program. People used to be able to do what you describe but King Root was updated to prevent you from installing SU.