Database Develop

Help Rookie - Which Nexus 6 Root Method is Best?

Hello,
So I am still newer to the Android / Modding world (Had my Nexus 6 for about 3 weeks now, first Android phone). The extent of my experience is manual flashing 6.0 to my Nexus 6 and Nexus Player and flashing custom recoveries and boot images. I am a bit confused right now. I seen a post in the XDA News that you can now root 6.0 without modifying /system. I thought that was already the case when rooting the Nexus 6? All you had to do is flash TWRP, flash the modified boot image, and install SuperSU through TWRP. There appears to be two different root methods now. Could someone please clarify what the difference is and which I should go with? Here is the link to the XDA Post from Chainfire on the rooting methods.
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
Thank you in advance.

1. unlock your bootloader with fastboot oem unlock
2. fastboot flash twrp recovery
3. flash any marshmallow custom kernel(if on marshmallow) and the latest supersu in your new twrp recovery
4. reboot with root

simms22 said:
1. unlock your bootloader with fastboot oem unlock
2. fastboot flash twrp recovery
3. flash any marshmallow custom kernel(if on marshmallow) and the latest supersu in your new twrp recovery
4. reboot with root
Click to expand...
Click to collapse
Thank you for the info but I do know this. I have done this already. I am trying to understand how doing this modifies the system. How does this method differ from the newer method that has been posted? I am trying to learn all I can about Android, Root, etc. I have learned so much already in a very short time. I would like someone to explain the differences in / in the outcome of these two methods. I don't want to be a noob forever here. lol. Thank You.

Rektifying said:
Thank you for the info but I do know this. I have done this already. I am trying to understand how doing this modifies the system. How does this method differ from the newer method that has been posted? I am trying to learn all I can about Android, Root, etc. I have learned so much already in a very short time. I would like someone to explain the differences in / in the outcome of these two methods. I don't want to be a noob forever here. lol. Thank You.
Click to expand...
Click to collapse
There is no difference in the outcome. Root merely lets one modify files (root files) that you could not before. It does not put anything else on your device.

Rektifying said:
Thank you for the info but I do know this. I have done this already. I am trying to understand how doing this modifies the system. How does this method differ from the newer method that has been posted? I am trying to learn all I can about Android, Root, etc. I have learned so much already in a very short time. I would like someone to explain the differences in / in the outcome of these two methods. I don't want to be a noob forever here. lol. Thank You.
Click to expand...
Click to collapse
there is no other way to root a nexus.
whichever method you choose to root a nexus with, even a root toolkit, they all do it the exact same way.

/system is always modified by root. You need the su binary and scripts to call it in /system. You have to add these files to get root access and adding files counts as a modification. You cannot root any phone without this.
Sent from my Nexus 6 using Tapatalk

blu advance 5.0 hd compatible?

Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.

xda123455 said:
Hey so do you think the blu advance 5.0 hd will be compatible with the work being done on the R1 hd? I would really like to jump on this hype train with my similar but slightly less powerful phone.
I am hoping that I will be able to install a custom rom like R1 users. I also want to root my phone to disable google services in the meantime.
Click to expand...
Click to collapse
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com

kal250 said:
That phone is based on the 6580 SoC, the R1 uses a 6735. There is a site that lists some roms for blu products that may help, I don't know how reliable they are, I have never used them, but if you want to check it out...
http://www.blu-dev.com
Click to expand...
Click to collapse
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/

xda123455 said:
Thanks I checked out the site and it seems like there is no blue advance 5.0 roms and no forum activity =/
Click to expand...
Click to collapse
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??

kal250 said:
If your wanting to root it, I'm hearing Kingroot is working, never used it though, so I can't say if it works or if it's safe??
Click to expand...
Click to collapse
I've tried Kingroot, Kingo Root and Frama root. All with no luck.

devanttrio said:
I've tried Kingroot, Kingo Root and Frama root. All with no luck.
Click to expand...
Click to collapse
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.

Autolounge said:
Did you use the desktop versions? Those have higher success rates. I tried rooting an HTC that way and it worked flawlessly even when the apk didn't.
Click to expand...
Click to collapse
I did.
I also tried the apps, of the ones that have apps.

devanttrio said:
I did.
I also tried the apps, of the ones that have apps.
Click to expand...
Click to collapse
You're going to have to do it manually.

no go on kingo
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
consider yourself blessed my friend, i'd like to root mine just to get marshmallow.... i have lollipop and checked for updates and says i'm up to date, i can only install 1 app at a time because there is no room on the internal storage, i have to move every app to sd card and then clean cache for each and every app i want.. never recommending blu to anyone

trc117 said:
I'm in the same boat. I've got 20 of these BLU Advance 5.0 HD devices and I need to root them to gain access to the VirtualSensor app to emulate a gyroscope. I've tried Kingo and Mobogenie (barf-boo-hisssss). I'm wondering if kingo isn't working on these since they have Marshmallow. I read somewhere they originally shipped with Lollipop.
Did you get anywhere Devanttrio??
Click to expand...
Click to collapse
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - https://bluroms.info . Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!

ray2jerry said:
I've been trying to root a Blu Advance 5.0 HD for a while now and stumbled on this post. I visited your site but am not sure what a 'Scatter File' is, or in what order I need to do things in order to get root.
If you could provide a little more detailed info that would be very much appreciated.
Thanks!
rAy
EDIT: Sorry, to clarify I tried all of the other PC and APK rooting solutions but was able to unlock the bootloader using ADB. I guess I'm just looking for the proper way to root and add TWRP. Thanks!
Click to expand...
Click to collapse
I found a option in developer settings that is "Enable OEM unlocking" and it makes it so you can unlock the bootloader from fastboot, if you do adb reboot-bootloader and then fastboot unlock it should undo the bootloader for you

zjr8 said:
I was able to root mine successfully the long way.... had to obtain a dump of the boot.img / recovery.img using software that I'm not sure of the policy of discussion on here at XDA - compile TWRP - unlock bootloader - fastboot boot the compiled recovery - flash SuperSU to get patched boot.img (kitchen was being dumb and systemless root didn't want to work) - Flash SuperSU in system mode - Convert SuperSU.apk to system app so it doesn't get removed every reboot. I can post my compiled TWRP when I'm back at my office or grab it from my repository that I'm trying to establish - Sorry for the design mess / lack of much there at moment haven't had much free time lately in process of cleaning up the device kernel sources to build from source... its sort of ... messy in there...... can post on github if anyone wants in
Click to expand...
Click to collapse
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.

CreativiTimothy said:
Like the others said, I would really appreciate if you could give an explanation or tutorial on how to use these files that you uploaded to root the phone. I'm willing to donate some money if required. I only know basic technical stuff haha.
Click to expand...
Click to collapse
I too am trying to root this device, and am unclear on a few of the steps here. I actually found your site with the recovery and boot images independently, really appreciated! I am at the point where I just need to patch the boot image, though I am not sure how to do this. If you could help me out with this step I might be able to put together some sort of list of steps to get through the whole process if you don't have the time.
Any help would be appreciated, thanks!

Magisk How To Install Page Does Not Help At All

this is mosty a copy and past cuz i didnt find this part of the forums when i had to remake my acc. if u watch the video u'll see what i did and what i should cuz the how-to for install magisk is broken to say the least
i have a sony xperia z3v and before u ask yes i did follow when was on the xda but NOTHING works as u see in this video here - https://www.youtube.com/watch?v=Jaga6MUcTdc&feature=youtu.be.
so first thing i need is a Custom Recovery. so i follow what that page here - https://www.xda-developers.com/how-to-flash-install-custom-recovery/ says...
first thing it is say i need Android SDK but never once talks about needing it ONE TIME.
2nd, both links given on that page for the custom recoverys 404! - https://imgur.com/bV9egdH
so what do i do next? i follow whats given and BOTH SITE R DEAD! also that page doesnt ONCE going into how to set up a custom recovery at all.
how is that u guys can help me out when it comes to flashing my sony xperia z3v back to stock after i F-ed up on a root and yet not have a set by set for geting Magisk to work install and work on your phone?

You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html

Didgeridoohan said:
You don't need a custom recovery to install Magisk. I'm not gonna sit and watch some video about what you have and haven't done, so I'm not sure what how-to you've been following.
But, I can tell you what instructions you should be following (the official Magisk docs):
https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
yes u do need a custom recovery as said on this page here - https://www.xda-developers.com/how-to-install-magisk/
"What You’ll Need:
A device running Android 4.2+
Custom Recovery (how to install)
We’ll be using TWRP in this guide"
i have the magisk manager already install as is my phone it rooted as u can see in this SS from the phone here - https://imgur.com/a/Kq1EChq but as u see magisk has a red X since its not installed so i go to install it but it give a .zip so i use that and it errors out EVERY ****ING TIME as see here - https://imgur.com/a/VyAslvt
if u toke a few mins of your day to watching the video instead of being a ass and commenting that knowning full well u could have watched the video to see i did everthing that the pages sad u wouldnt be most the comment u just did. u just make yours look like a ass. i want ppl the help me not say "u dont need a custom recovery" when the page on the how to install SAYS U ****ING NEED ONE.

No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU

Didgeridoohan said:
No need to swear or scream at me... I am actually trying to help.
I did not need to watch that video (and didn't feel like spending 12 minutes doing it, would have been better to just link that how-to from the start), since from your post I knew you had not been following the official Magisk docs (that I linked you). If you took a moment to read those you would have seen that you don't need a custom recovery to install Magisk (it can be useful, but you don't need one).
The guide you've been following is outdated (but unfortunately doesn't have a date, so that's hard to know). Take a look at the link I posted above and see if you can figure things out from there.
If you need further help it's just too ask (but without the swearing and screaming, please). It's also possible that you can find some information in my Magisk guide:
https://didgeridoohan.com/magisk/HomePage
You might run into some troubles since you're already rooted with some other root solution, but there's a section about that as well in my guide (if you're using a systemless root that is):
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Click to expand...
Click to collapse
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?

let me make it as simple to understand what im looking for. i want to use my Sony Xperia Z3v to game assets dumps for Uta-Macross so i can have pull the 3D models and cards (very nice photos) from the game. to do this i need to have my sony phone rooted and i need to have Magisk so i can hide the root from Uta-Macross so i launch into the game to download the assests to do a dumb. everthing up to this point i have YET to understand what do at all. that link u give - https://topjohnwu.github.io/Magisk/install.html says to this then go here then go here and do this over and over again never saying just do this, this, and this, and your done.

tankball said:
i saw that page and it makes no since to me. it still says i need a custom recovery also. i dont understand a single think. why cant they make it set-by-set?
Click to expand...
Click to collapse
The instructions by @topjohnwu are pretty complete... They do assume that you are somewhat familiar with things like fastboot, but that is information that can easily be found by searching the big ol' interwebz.
Using a custom recovery is one of the ways of installing Magisk. If this is the route you really want to go I suggest you take a look in your device's forum here on XDA:
https://forum.xda-developers.com/z3
That's usually a good first step since you'll likely find others discussing the same device specific topics.
But if you take a look again in the linked docs, you'll find that you can also use something called boot image patching (which doesn't require a custom recovery at all):
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Rooting and tinkering with your device does require a certain level of knowledge about what you're doing. If you can't follow/understand the instructions available there's a good chance you might mess up your device. If you have your data backed up somewhere off the phone (which you should always have when playing with this stuff) you should be good since a complete and catastrophic failure is very unlikely. It's really annoying to have to set everything up from scratch though...

But if you take a look again in the linked docs said:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching[/url]
Click to expand...
Click to collapse
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?

tankball said:
i did see this. witch is want im thinking of doing. by "boot/recovery image" does it mean the stock rom for the phone? if so does this work sice my Xperia Z3v is on 5.1.1? - https://xperiastockrom.com/sony-xperia-z3v-d6708
also right now i went and removed everything from the phone when it comes to rooting, but kingroot (what a stupid name. i also unrooted the phone) and Magisk manager. i cuz i need to reroot my phone and get magisk manager back on my phone?
Click to expand...
Click to collapse
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.

Didgeridoohan said:
You'll need the boot image that corresponds to your currently installed firmware/ROM. If that is the firmware you have, then that should work.
You'll need to install the Manager again so that it can patch the image.
A small warning as you progress further: I've seen reports of old Sony devices having issues installing Magisk. Therefore it might be a good idea to visit the Z3 forums (linked in my previous post) and see if there's any information available on this before you continue. Doing proper research before committing always helps in the long run.
Click to expand...
Click to collapse
i should also root the phone again also?

tankball said:
i should also root the phone again also?
Click to expand...
Click to collapse
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...

Didgeridoohan said:
No. If you want to install Magisk you should not install any other root solution.
Install the Manager.
Patch the boot image.
Flash the patched boot image to your device.
Those are the basics...
Click to expand...
Click to collapse
ok now im lost again. to do date dumps for Uta-Macross i need a rooted phone so i can pull the files without windows again tard and saying "unknow error" when i go to copy the files from my phone. but to play this game i need to hide the root from Uta-Macross so i need to use Magisk. is Masgisk a root itself? im really lost again

Magisk provides a way to do systemless modifications to your device, it is a root solution in itself, and it has the ability to hide itself and it's components from most apps and services that look for a rooted or modded device.
This is kind of the basics, so I reallly suggest you do more research before continuing. The best source for information is the Magisk GitHub page:
https://github.com/topjohnwu/Magisk
Start there, take a look at the readme and the documentation available and continue searching for whatever other information you might need.
I'm not going to be available for further assistance for the next 8 to 9 hours (I hope, but that's entierly up to my little one). G'night.

nothing i did worked. the .zip fail or the D6708_23.4.B.0.319_1288-1477_R30C.ftf file in the .zip witch in the rom from the phone, it will ALWAYS say failed, unsupported/unknow image format.

Morning. Like I posted previously, old (and new) Sony devices have been known to have issues installing Magisk. Search your device's forum for Magisk related posts and you'll likely find the info you need.
Good luck.

Help! Please create a proper rooting guide.

Hello everyone! I am new to rooting and stuff, so can anyone please create a proper rooting guide for Asus ROG phone 3. Thanks in advance.

https://www.ytechb.com/how-to-root-asus-rog-phone-3-and-unlock-bootloader/
Remember to plug the usb cable in the side port.

Bumping up an old thread as I got my ROG3 yesterday and was able to unlock the bootloader today. Would like to know whether there's an updated rooting guide with TWRP and Magisk (for an Android 11 device). Failed to find a proper rooting guide and any help is welcome as I am bit scared of botching it somewhere.

iamronin said:
Bumping up an old thread as I got my ROG3 yesterday and was able to unlock the bootloader today. Would like to know whether there's an updated rooting guide with TWRP and Magisk (for an Android 11 device). Failed to find a proper rooting guide and any help is welcome as I am bit scared of botching it somewhere.
Click to expand...
Click to collapse
Haven't seen one but rooting the ROG 3 is fairly straight forward, no unusual steps involved beyond a standard root procedure. Unlock bootloader Extract the boot.img of your rom. Patch it with Magisk. Flash it to the device boot. Install the Magisk Manager app. Done. TWRP is of course recommended but optional for rooting.

Question Recovery without losing data? On rooted Tab S8 w/bootloop from failed Magisk Update

Hi all,
I'm hoping someone here can give me advice on how (or if!) I can recover from a bootloop after a failed Magisk update attempt, without losing the data on my tablet...
My Tab S8 was boot-looping constantly after I tried a Magisk update; trying the plugged-in-volume-up+volume-down trick from this thread gives me the screen with options for Continue, Device Unlock Mode, or Cancel. Before I go any further, I really want to make sure I don't do something that will accidentally wipe all my data!
I'm a long-time Android user and generally just competent enough to follow instructions (like the incredibly helpful howto guide in this forum!) and root my various phones and tablets, but tbh I don't have a full understanding of the various modes and what does / doesn't wipe the data on the device. I have a handful of documents on it that I would really like not to lose, so I don't want to screw this up by choosing options I don't fully understand... Any suggestions will be greatly appreciated!
(Or if someone with actual clue is willing to jump on a web meeting and help me recover it without losing data, I'll gladly compensate you for your time...)
Thank you in advance,
Lisa

Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!

roirraW edor ehT said:
Have you tried the Root How-To's instructions to update your firmware without wiping, only using the same version of the firmware your were on already?
Apologies if you already tried that.
Good luck!
Click to expand...
Click to collapse
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!

lorenzin said:
Thank you! I looked at that, but haven't tried it yet - my concern is that I don't know why the Magisk update failed, so I don't know whether trying the Root How-To's update would run into the same problem. The bootloop is incredibly difficult to interrupt - I had to try the volume up + volume down multiple times before getting the timing right.
If that's the best way to proceed, though, I can certainly give it a shot!
Click to expand...
Click to collapse
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.

roirraW edor ehT said:
I do believe it's the best option since Magisk needs to be updated in the AP file. You likely need to dirty flash to stock first, if possible (not rooted, without wiping), so that you can have a working system to use the Magisk app to manually patch the AP file, copy the AP file back to the computer as the instructions say, then flash again.
Click to expand...
Click to collapse
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa

lorenzin said:
THANK YOU for your advice here! I was just able to restore it to the original firmware simply by following the Root How-To's update-without-wiping instructions. Currently debating whether I really want to update it and risk further problems, or just stick with the working firmware... But either way, I was able to recover the documents I need and it's great to have the tablet working again. I really appreciate your help!
Be well,
Lisa
Click to expand...
Click to collapse
You're welcome, glad that helped! I know I was nervous the first time I updated Magisk, but I did it at the same time I updated the firmware. That is, I would've had to update the Magisk app first, so that I could apply that updated Magisk to the new AP file.