Database Info

[Q] How to root this device without deleting any data?

Is it possible to root one plus one, without deleting any data and apps from it? I just want root access but don't want any custom rom.

yes, of course..
root doesn't delete any of your data

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
Thanks for that. How can I do that?
#newtorooting

senaferdy79 said:
yes, of course..
root doesn't delete any of your data
Click to expand...
Click to collapse
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
sourabhkejriwal said:
Thanks for that. How can I do that?
#newtorooting
Click to expand...
Click to collapse
Sorry you got your hopes up, but the other poster isn't right. As per my reply to him you need to unlock your bootloader first, which is going to wipe your device. I'd suggest backing up any files that you have that are important to you. As for your apps and settings, you'll have to set them up again afterwards. Go to my guide thread here:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
You need to follow (in order) sections 1, 2, 3, and 4. This will give you root access on your stock ROM. You should also follow section 10, it's very important that you make a backup of your EFS partition.

timmaaa said:
That isn't technically true. In order to get root you must have a custom recovery installed. In order to install a custom recovery you must unlock the bootloader. Unlocking the bootloader wipes the device.[
Click to expand...
Click to collapse
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
Step-7: If you want to root the phone without installing TWRP recovery, type the following command
fastboot boot twrp.img
Click to expand...
Click to collapse
I guess the real question being, why would you need a custom recovery?

pdhx said:
So are you saying all the many how to's that tell you that you can skip installing recover are wrong? Apparently, I don't have enough posts yet to create a link but I've seen posts here on XDA that say other wise and the one I have in front of me at the moment is from ibtimes . com titled "how-root-oneplus-one-install-twrp-recovery-1450708"
Their "Step-7" reads
I guess the real question being, why would you need a custom recovery?
Click to expand...
Click to collapse
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Transmitted via Bacon

The default recovery will only flash cm signed zip, which is another reason for needing a custom recovery. That method you mention at ibtimes meant that it would allow you to, for one boot cycle, do a "live boot" of twrp
Sent From Lollipopified Bacon Goodness!

But how is anything going to be written to the system partition if it is locked ?

timmaaa said:
You're looking at outdated information. They used to be correct, but now they are wrong. This is because you can no longer use the fastboot boot recovery.img command with a locked bootloader. In fact, that functionality was removed quite some time ago.
You need a custom recovery because that's how you flash SuperSU to get root. There's no way around it.
Click to expand...
Click to collapse
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?

pdhx said:
Ugh, was afraid of that, you might want to add a comment to that effect to your guide....
Would have been nice to just add a setting to the default recovery to allow you to toggle whether you need a signed zip or not. Sucks that I could root my SGS III (which is far less hacker friendly than the One) without wiping it but I can't do that for the One, all i want is root for the moment. However, after playing around some more I'm getting stick before I even get that far; I can get ADB to find the device but when I adb reboot bootloader I cannot get fastboot to find the device. I've tried multiple drivers, different USB ports. When my One goes into fastboot the screen seems awfully dim, almost like it hasn't completely initialized, is that normal? And if so, any suggestions on why I can get adb to work but not fastboot?
Click to expand...
Click to collapse
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
what do get when you type fastboot devices ?

bombadier said:
The one's bootloader is not like a nexus one where you can at least reboot recovery etc, once it boots thats it
Click to expand...
Click to collapse
Which seems to be somewhat limiting for such an otherwise developer friendly device?
bombadier said:
what do get when you type fastboot devices ?
Click to expand...
Click to collapse
Nada, nothing, nil. however, "adb devices" works fine... WTF?

pdhx said:
Which seems to be somewhat limiting for such an otherwise developer friendly device?
Nada, nothing, nil. however, "adb devices" works fine... WTF?
Click to expand...
Click to collapse
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help

bombadier said:
Point one was just to say there is not anything really you can do in the bootloader, being able to reboot to recovery etc is actually a handy feature
Try a different fastboot.exe ? if you say that adb works perfectly then there has to be something wrong with your fastboot binary
I have attached my one,download and change the name back to .exe and see what happens
Going to need more info in order to help
Click to expand...
Click to collapse
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?

pdhx said:
Fair point about bootloader, what I don't get is why they forced you to have to do the unlock to root? All I started out wanting to do was install Titanium and run a Nandroid or two. Guess if I'm going to have to wipe I guess I may end up installing a Lollipop ROM. However, I still can't get there. The fast boot you supplied gives the same problem. I was running the latest fastboot from the Android SDK and your's appears to be the same (though I haven't done a binary compare). As far as I can tell that leaves the device drivers, the laptop, or the phone itself. I'm running Win 7 SP 1 64 bit and I've tried various drivers including the Samsung the Google generic and they make no difference. Not sure how they would since adb works but I've seen some suggestions that drivers can be finicky in this regard.
What else can I tell you that might help?
Seems since I can get into the recovery that comes with the phone I could maybe get a works around somehow?
Click to expand...
Click to collapse
They're "forcing" you to unlock the bootloader in order to root the device because that's the universally accepted standard (unlock bootloader, install custom recovery, flash root). Some devices have super secure bootloaders and that's why you end up needing to use hacks to get those devices rooted, but that isn't the normal way to go about it. Anyway, there's no advantage to leaving the bootloader at all. There's also no disadvantage to unlocking the bootloader at all. You might say that the fact that the device is wiped during the unlocking process is a disadvantage, but that fact is very well documented both here, on the OnePlus forums, and pretty much any other reputable tech site that mentions unlocking the bootloader on this phone. The point to that last sentence? It pays to research a device thoroughly before buying it, or before using it, the wiping of the device is no issue at all if you do it when you receive the phone (prior to using it), like many people have. But in your situation you're just going to have to backup any important media from the phone prior to unlocking.
Anyway, on to your fastboot issue. Exactly which drivers do you have installed on your PC? Do you have any other phone drivers or software installed on the PC? And do you have access to another PC in case the one you're using is the source of the issue?

Got it, 27th try (give or take) is the charm.... Had to use USBdeview and uninstall the Google and the Qualcomm drivers. Reinstalled the Google drivers (after a reboot) and got it to work. Guess I could have figured that out from dev manager by watching what drivers got activated while fastboot was active but nothing ever jumped out at me as an obvious culprit.
Interesting to note that TWRP now automatically prompts you to install SuperSU if you reboot after installing it. Maybe it found the zip but either way, nice touch!
Now to go and decide what ROM to install....
Thanks for your help!

I would suggest temasek unofficial cm12 ROM. Been using it pretty much as a daily driver since version 1.something of the ROM and no problems. At this point it's been almost a month of not having to boot into my cm11s ROM lol. I use it with AK kernel, seems like a good match cuz both devs are working together looks like. Flash AK ukm special edition after flashing his kernel and install synapse from play store if you want to play around with settings of the kernel
Sent From Lollipopified Bacon Goodness!

zenix23456 said:
I have been using AnyRooter for months and it is quite good to root OnePlus phones.
Click to expand...
Click to collapse
Except the Oneplus One.

How To Root...?? oppo f1

plz... help how to root oppo f1

samir1718 said:
plz... help how to root oppo f1
Click to expand...
Click to collapse
as of now there's no root available for this device. :good:

Hoppning some one find out how too root soon

Hey, give this link a try: I'm not sure if this works or not as I haven't and won't try but I just wanted to suggest it http://www.osroots.com/how-to-root-oppo-f1-oppo-rooting-tips/
Also, if that doesn't work, give this a try: http://reviewroots.com/root-Oppo-F1-with-or-without-pc
Plus, could you give me your thoughts on the battery life? I am on the edge of buying this phone or the moto 3rd gen and the battery life is the only thing holding me back.

I can try reviewroots one later this day.. I post back how it work or if phone brick

ellirhc said:
I can try reviewroots one later this day.. I post back how it work or if phone brick
Click to expand...
Click to collapse
Any further information ? Please share it with us ......

allen0a said:
Any further information ? Please share it with us ......
Click to expand...
Click to collapse
Im still on the work. 3-4h i post how it workde on my Oppo F1

I did try root whid out pc. And it did not work for me kingroot did just tell me phone not support

ellirhc said:
I did try root whid out pc. And it did not work for me kingroot did just tell me phone not support
Click to expand...
Click to collapse
I had tried "Kingroot" and "Framaroot" two days ago. Both of them don't work for F1.
Anyway，thanks for your sharing.:highfive:

There is no working root for Oppo F1 at the moment. Safe rooting methods are not available. The bootloader is locked and fastboot has been disabled.
I'd be very careful about trying to use one click app solutions for attempting to root the device, if you can get them to work. They are responsible for suspicious behavior, such as downloading stuff and installing their own root manager. Beware.

No hope
I tired everything, kingroot, Framaroot, oppo tool, Kingoroot no hope ?
Someone please find a way to root this phone

You still haven't figured out how to root this?
http://imgur.com/TEAypKE
Keep trying guys, remember: no public root exploits work

uberlaggydarwin said:
You still haven't figured out how to root this?
http://imgur.com/TEAypKE
Keep trying guys, remember: no public root exploits work
Click to expand...
Click to collapse
nice :good:
perhaps you can give us more clues :
1. does we need unlock bootloader / not ?
2. it need flashing from recovery (or even flash custom recovery) or only just an apk ?
this is interesting :highfive:

Has anyone tried TowelRoot?

Please help us root this device!
Thank you guys so much!

would using adb and remounting everything manually work? or downloading a firmware update and modding that

It will be much like my Find 7. Need to unlock bootloader to install TWRP recovery so you can flash SuperSU.
The trick is having an unlocked bootloader in the first place. The Find 7 wasn't a problem. Oppo didn't try to lock the user out.
I have an F1 here for my wife. Will root it once a developer has the exploits developed, tested and released to public. Just have to be patient and don't rush in doing risky experiments.
Try changing the launcher so it has a better UI for the daily stuff. ColorOS launcher is a PITA.

the nerdling said:
would using adb and remounting everything manually work? or downloading a firmware update and modding that
Click to expand...
Click to collapse
lol. uh no.
1: you can't remount system as /rw on a user build (only engineering/userdebug).
2: I think you mean a OTA update for system. Both the firmware and system are signed. You can't just do that.
You can use CVE-2015-1805. I got root via a kernel vuln, then exploited the bootloader to unlock it

uberlaggydarwin said:
lol. uh no.
1: you can't remount system as /rw on a user build (only engineering/userdebug).
2: I think you mean a OTA update for system. Both the firmware and system are signed. You can't just do that.
You can use CVE-2015-1805. I got root via a kernel vuln, then exploited the bootloader to unlock it
Click to expand...
Click to collapse
ok, just wondering, im newish to this sort of stuff

uberlaggydarwin said:
lol. uh no.
1: you can't remount system as /rw on a user build (only engineering/userdebug).
2: I think you mean a OTA update for system. Both the firmware and system are signed. You can't just do that.
You can use CVE-2015-1805. I got root via a kernel vuln, then exploited the bootloader to unlock it
Click to expand...
Click to collapse
If it's at all possible, could you (or anyone) please provide a very basic step by step/rough guide as to how you did this, for us newbies? So that I have some intructions to follow.
It would be appreciated sooo much...
Thank you for your help.

Does This CF-Auto Root Trully Works ON G930T

guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.

bump

I don't think this will work unless we get our Bootloader unlocked (which hasn't been done yet as far as i know)

UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !

this is kind of lame.... why chainfire release a auto root if the thevice have bootloader locked down? and onlockable?

Confused myself
I want to say root is possible, there are tons of sites with instructions: https://www.google.com/search?q=SM-...i57j0j69i60.9343j0j4&sourceid=chrome&ie=UTF-8
Of course, XDA doesn't seem to have a specific G930T thread for rooting with instructions, then see threads like this today. I was all set to give it a try, but unsure if should proceed...
Did find this: http://forum.xda-developers.com/tmobile-galaxy-s7/help/sm-g930t-root-doesnt-void-warranty-t3415936
EDIT: so the one linked in original comment was the bleeding edge root process and seems like had a really high failure rate. Most current I've seen is: http://lifeatsamsung.com/root-t-mobile-galaxy-s7-sm-g930t-2/
Seems a little more clean cut and easy. I'll edit again if I find a newer solution or at least commentary on success/fail
In comments OP posts:
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
Click to expand...
Click to collapse
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse

So the solution and all the fixes, etc is right here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
Worked for me, no problem. Even installed the debloated, deox'd ROM. Unfortunately after root you will need to follow rest of guide, otherwise you will see some lag issues.
On the other side of it, phone is great, fast, if not faster than before, and got root. Let me know if you would like some screenshots proving a TMO phone is rootable or if can answer any questions
blackwing182 said:
guys i want to root my phone on the fast and very simple way possible.
found this root method on https://autoroot.chainfire.eu
this is the link for the root method https://download.chainfire.eu/982/C...Auto-Root-heroqltetmo-heroqltetmo-smg930t.zip
i did not tryed it my self yet. but if theres a user that rooted their phone that way, let me know.
Click to expand...
Click to collapse

I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks

Mordred said:
I would like to see some screens that show it is rooted, yes. I am about to purchase tomorrow and would like everything in place before I do.
Thanks
Click to expand...
Click to collapse
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root

TH3B0SS said:
There is root but the bootloaders on USA snapdragon is still locked so it's not as smooth and simple as flashing cf root
Click to expand...
Click to collapse
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...

Mordred said:
So what does this mean in layman's terms. Can I root the device safely with full functionality or not? Are there plans to get a rooted bootloader? And what does this mean because I thought the TMO version had a qualcom processor...
Click to expand...
Click to collapse
This means that the only rooting method right now isn't as stable as it would be if it had a unlocked bootloader the root right now will cause some issues but they can easily be fix from some of the steps after rooting guides that are in the xda forums and yes it using a Qualcomm processor Witch is pretty much the snapdragon and there hasn't been any luck this past year of getting the bootloader unlocked for full and smooth rooting I'm really ****ty at explaining sorry if your still lost

The Chainfire method he released does NOT work. I'm not sure why he released it...maybe he knows of a future bootloader unlock that we don't know about.

@troby86 I see you have yours rooted. How did you accomplish this?

Mordred said:
@troby86 I see you have yours rooted. How did you accomplish this?
Click to expand...
Click to collapse
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.

Thank you. Lots to look through.

troby86 said:
I used the engineering boot image to do it. There is a post in this forum that has a link to a guide to do it.
Click to expand...
Click to collapse
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?

Mordred said:
@troby86 OK, bought my S7 today. Trying Max Lee's root method. I can't get SU to inject using adb command. I have retried numerous times to include reflashing and system reset. Any thoughts?
Click to expand...
Click to collapse
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...

KillerClaw321 said:
Run CMD in admin mode or if the CMD prompt freezes unplug and replug in your phone and then it should start...
Click to expand...
Click to collapse
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK

Mordred said:
@KillerClaw321 I am at the machine now and have tried running CMD in admin mode. Still no joy. What are the beat adb drivers to use for AMD machine? Maybe the drivers are the problem? What else can I try? I am on PK1 as the phone is new from the store yesterday and a fresh shipment to them the day before.
I also see a DM verification verify failed dialogue at the bottom when i try the factory reset. No DRK
Click to expand...
Click to collapse
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!

KillerClaw321 said:
Remove any existing drivers for your S7 and install this one
http://www.samsung.com/us/mobile/ph...7-32gb-t-mobile-gold-platinum-sm-g930tzdatmb/
Make sure you click allow on the pop-up on your phone after you plug it into the computer... Good Luck!
Click to expand...
Click to collapse
Sorry for being daft... I don't see a driver link and how do I remove the previous version?

Trying To Root Pixel 2

Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.

l7777 said:
What makes you believe that TWRP for the original Pixel will work on the Pixel 2? Likely you'll have to wait for a recovery for the Pixel 2.
Click to expand...
Click to collapse
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!

bluh5d said:
Yeah I understand that. I was just hoping that since they are so similar it would work. Especially since I am not going to install it on my recovery just boot it to root and suhide.
I wanted to make sure I wasn't missing something or something I could change in the image to make it boot on a 2 .
Thanks though for your thoughts!
Click to expand...
Click to collapse
The similarities are only on the surface my friend. When dealing with computers, similar and close is rarely good enough. You need exact.

bluh5d said:
Ok I have the bootloader unlocked.
I was hoping then I could do the following
ADB Debugging on
adb reboot bootloader
fastboot boot twrp-3.1.1-1-fastboot-sailfish.img
But its not booting it. Pixel TWRP Image
So my question is can i modify the image to make the pixel 2 boot it?
Please advise?
Can I root without using TWRP?
Thanks,
Click to expand...
Click to collapse
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.

evilwombat said:
The MSM in them is totally different. Plus panel config, clock plan, power grid etc. Your original recovery kernel will not boot on Pixel2, so this is completely expected.
Click to expand...
Click to collapse
Can I root with latest supersu without recovery ?

Someone's bound to hose up their phone. Wondering where factory images are?

Born<ICs said:
Someone's bound to hose up their phone. Wondering where factory images are?
Click to expand...
Click to collapse
Yes. I agree. Might be me right. I wasn't planning on flashing recovery though just booting it.

If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.

If your bootloader is unlocked and you want root.
Try installing Chain fire's Supersu from the play store or install the apk.
I do not have my P2 yet to try.
Sent from my Nexus 5X using Tapatalk

me_droid said:
If you are feeling adventurous (as it seems you already are!) you might try the twrp-3-1-pixel-bootable-mod.img located here: https://androidfilehost.com/?fid=745425885120753892 ? I used the instructions at https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324 to root the 2016 Pixel (not xl) and if I upgrade to Pixel 2 might try that. You might just try fastbooting the twrp img referenced there and then flashing the supersu referenced there without the other modifications GroovinChip did. Again you are taking a risk trying this on "dissimilar" hardware.
Click to expand...
Click to collapse
I think this may be a waste of time because it was modded to work on Oreo. They have already released a version that works on Oreo 3-1-1 that I already tried it wouldnt boot it. I will probably just wait even though i want to play. So i guess I can just say yep I have a pixel 2 with the bootloader unlocked and thats about it.

This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(

The_Fuzz22 said:
This can't come quickly enough - I always take my Ad Blocker for granted until it's not there anymore :'(
Click to expand...
Click to collapse
Yeah, I take having root completely for granted. I guess I've never bought a phone right at the moment of release before. If I didn't really need a new phone, I suppose I would have waited. Anyway, I figured out that you can block ads, without root, with apps that run all your traffic through a vpn (that's really only running locally on the phone). The best options after much research seem to me to be Netguard and AdGuard (though I haven't tried them yet). They both also include a firewall (Netguard is primarly a firewall), which I want.
https://github.com/M66B/NetGuard/blob/master/ADBLOCKING.md
https://adguard.com/en/adguard-android/overview.html
DNS66 also seems to be higly regarded, but it doesn't include a firewall. There are other firewall only apps, which work with the VPN method, but you can only run one VPN on Android at a time, so if you want both functions, without root, you need an app that does both.
https://forum.xda-developers.com/android/apps-games/app-dns66-source-host-ad-blocker-root-t3487497
Anyway, that's my plan until root comes along. Then I will go back to AdAway and AFWall+.

There is no kernel source released for the Pixel 2/XL yet. It is based on the 4.4 kernel, this should make development very smooth.

https://forum.xda-developers.com/pixel-2/development/psa-fastboot-booting-bad-image-confuse-t3692932

Moto One 5G Ace Rooted with TWRP using stock Firmware

First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.

Your first link doesn't work for me. The Adaway link works. FYI.

RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.

Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.

Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.

iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.

egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.

iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??

egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.

iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.

egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.

Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance

Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.