I couldn't find any simple instructions for rooting so hopefully this helps someone.
I'm assuming you've already unlocked your bootloader. If not, download the deep testing app (there are various apks on xda e.g. from here). Then submit the application (it took me a few minutes to get approved) then use the app to reboot into the bootloader, then run command fastboot flashing unlock. I don't believe the deep testing app works on android 12 yet so you may have to downgrade to android 11 to unlock your bootloader.
If your bootloader is unlocked you can update to android 12 (though it isn't necessary to root). If your gt isn't offering you the latest version you can download a recent version on this thread and then use "local install" in the update menu.
Next, download twrp from:
https://github.com/qiurigao/RMX2202
The latest version is twrp-3.6.0-V2.img
And download magisk from:
https://github.com/topjohnwu/Magisk/releases
The latest version is Magisk-v24.3.apk
Put your gt into fastboot mode by powering off, then hold the power and volume down buttons together until you're in the fastboot screen.
Then run command:
fastboot boot "twrp-3.6.0-V2.img"
Do NOT try installing twrp as I've read it can cause issues.
This should boot twrp (it will be in chinese but it doesn't matter).
Rename the magisk apk to a zip e.g. Magisk-v24.3.zip
Now run:
adb push Magisk-v24.3.zip /data/Magisk-v24.3.zip
Then:
adb shell "twrp install /data/Magisk-v24.3.zip"
Now you can adb reboot and you should be rooted!
Good luck.
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Having the same issue. Unfortunately no banking apps working for me.
F0Xie said:
Having the same issue. Unfortunately no banking apps working for me.
Fjsdfjasdasd said:
Thank you so much this guide. i've successfully rooted my device. but how can i run the banking apps ? because magisk hide not working. thanks in advance.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Look in Magisk settings, enable Zygisk (beta), enable enforce denylist, add apps to the denylist then install universal safetynet fix module from github and reboot device.
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Unlocking bootloader and rooting the device will format data?
Unlocking bootloader - yes
Thanks, this worked!
Also, really DO NOT install Magisk by clicking on "Install" in the TWRP interface, it can brick the device. Just don't touch the phone while installing Magisk, only use the fastboot and adb commands.
F0Xie said:
Update: now we can use deep testing app to unlock bootloader while using Realme UI 3
Click to expand...
Click to collapse
still working on last update?
robertaalves said:
still working on last update?
Click to expand...
Click to collapse
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Thanks man, it worked like a charm.
F0Xie said:
Yes, absolutely. It will work in Android 12 no matter how many updates you'll get. But will not work in Android 13.
Click to expand...
Click to collapse
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Hiiii, I'm thinking of buying this phone so I got 2 questions; 1) are there any custom roms available? From my little to none research, I've only found gsi, andd after my failed attempts, hearing the word gsi brings a bad taste, lol. Aanndd 2) is there any development/general discussion group about this device on telegram?
Gordin said:
This method works with the Android 13 update.
Use the same twrp image (twrp-3.6.0-V2.img) but use the latest Magisk (25.2)
I did this with 2 devices and had no Problems with root. Had to reinstall the Magisk App afterwards though.
(FWIW I did not remove root before updating to Android 13, that doesn't seem to be a problem)
Click to expand...
Click to collapse
can you open the bootloader in a13? or you need to open it before update?
Hm, to unlock bootloader, you need the right deep testing apk for your system version. I haven't looked into if there exists one for Android 13, but I would just downgrade the phone to a patch that works. I think I unlocked mine by downgrading to stock, and then installing the latest system update that is still Android 11. Sounds like there is a working Android 12 too, but I haven't tested it. Having to downgrade doesn't really matter to me, because unlocking will wipe all user data anyway. (Of course if you find a deep testing apk that is meant for 13, you can also try that, I just don't know if one exists)
alex61194 said:
can you open the bootloader in a13? or you need to open it before update?
Click to expand...
Click to collapse
Related
General info:
There will be a lot of discussion, do not follow untested tuts in this thread. It could cause you to brick your phone into a Cool paperweight.
AS OF 9/1/2015
XT1528-Surnia_Verizon
Board- MSM8916
Bootloader-NOT UNLOCKABLE!- EVEN IF YOU GO THROUGH MOTO'S WEBSITE (Verizon Locked it, not moto. & verizon cant unlock it) Viewable by booting into recovery & reading the screen.
Android 5.0.2-armv7l-240 DPI
Updated to 5.1
200MHz-1.21GHz quad core-Qualcomm Snapdragon 400/410
Root- No Write/full access-Cant seem to uninstall system apps on Android 5.0?/5.1
Screenshot: Attached at bottom of KINGROOT APK(4.5) via One click root method working on my updated 5.1 lolipop xt1528.
KingRoot does not root your device, just allows for removal of pre installed software via kinguser.After uninstalling, it crashed my Google launcher app & was fixed via rebooting which caused my system to have to re-optimize all apps which took 5 minuets. Root access is denied. Autostart manager works
Unrootable, Locked bootloader, but excellent capability. I love 5.1 better. I wouldnt recommend this device for anonymous browsing (I like to use Tor as a VPN), torrenting, or sharing. But I love the battery (lasts all day without heavy gaming use), phone calls & txts, Browsing the web is good too. I love being able to take out my phone and say "Ok Google" to vocally search or open things (like cortana) and my phone talk back. As well as the easy-to Use feeling comes if you've expierienced 5.0 before, a little confusing if you've been stuck on <4.0.I feel comfortable with it & it fits in my pocket pretty well. I don't know how much radiation it throws off... I say 7/10 overall. No xposed, if your lucky to rebuild the APK & patch it you can do it.. 4g is awesome! & I'm happy I didn't go with a free phone. Although, i'll be getting one soon to play with.
Thank you, Thanks for reading, & Have a wonderful day! (ALL Useful info & credits to who said it will be added via a reserved spot below.)
LATEST Answers :SU-ME didnt work for me on 5.0, and even though KingRoot said i had root access, It wouldnt give it to anything or allow write access.... Also, I attempted to root 5.1 off the v4.1 apk. It said root strategy available-Gave me (nothing past words)root access-But caused a bunch of apps to continuously crash. (I'll try it again once i go through my dev settings, i also factory wiped it earlier). It said i could remove system apps, It couldnt though. I used the auto-start manager too (we'll see if that stuck). (pics below) Also, Anyone who provides any testing will get thanked & a name below.
_______________________________________
| RESERVED |
| Thank you, kmani.k78 |
| Whoareyou |
| DBlake1 |
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
The hardest part is unlocking the bootloader. Without that, it's impossible to root.
I wish I had seen this thread before I picked up this phone today. :/
As I did pick one up as something to play with and not necessarily just for custom roms, I'm not immediately returning it, but it's a strong possibility.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
When I try installing twrp via fastboot I receive a preflash error. I have yet been able to boot into recovery., I just get a red triangle and "no command" . What am I doing incorrect?
I don't understand the recovery mode for this phone, I'm used to 4.0.4 lol. I'm not sure either. I thought I broke my system when I tried to adb flash twrp & found out you can't shut your phone off when its in recovery mode. (Also, you can't flash without unlocking the bootloader) DUH right?
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
You can't flash without an unlocked bootloader. The XT1528 isn't supported by Motorola for unlocking because its a Verizon phone. Verizon doesn't like giving out codes, and wouldn't even if you asked. I think unless someone can Dev the crap outta it, We're screwed XT1528 wise. But, I don't know much about anything lol. I'm still learning.
Manish_Sky said:
Yep it is possible to root.
First download supersu.zip here-
https://download.chainfire.eu/696/SuperSU
Now install custom recovery on your device using adb and fastboot. (TWRP is preferred coz many reported cwn not working)
Once twrp is installed boot in recovery.
Then tap install and select the supersu.zip where u downloaded it.
Just flash it and tada!!
Reboot in system and your moto e with lollipop is rooted.
I rooted by same method.
#peace and hope it helped you.
Click to expand...
Click to collapse
this is not possible on verizon version xt1528. bootloader is unlockable. will need an android 5 vulnerability to gain root which is the best the verizon version will ever get.
Most likely way to root this phone would be to use an app that has a Lollipop exploit, but they're getting harder according to this article:
http://www.androidpolice.com/2014/1...ew-modified-kernels-may-become-a-requirement/
Okay so now I have gone and picked up the AT&T XT 1527 version. I now have a XT 1528 I can test with. Question, should I go ahead and root the XT 1527? I am thinking about wiping everything off Verizon phone and installing Fedora on it, but if there are other suggesting, I now have a test sled that can be used. I am open to suggestions with the verizon phone, let me know what you all think.
XT1528 can be rooted by "Kingroot" method - a closed source app!
kmani.k78 said:
XT1528 can be rooted by "Kingroot" method - a closed source app!
Click to expand...
Click to collapse
Have you tried it yourself?
Sent from my XT1528
Ace42 said:
Have you tried it yourself?
Sent from my XT1528
Click to expand...
Click to collapse
Yes I have already rooted my xt1528.
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
kmani.k78 said:
Yes I have already rooted my xt1528.
Click to expand...
Click to collapse
Can somebody please confirm?
Thanks!
Just run on XT 1528 android 5.1..... not rooted according to root check
Harish_Kumar said:
Have you used any GSM sim in India with Verizon Moto E?
Are you getting 3G?
And if you are using with CDMA, atleast 3G working with that?
I will be receiving mine tomorrow, dunno if it works or not
Click to expand...
Click to collapse
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
How did you root your XT1528? Link?
Whyzor said:
How did you root your XT1528? Link?
Click to expand...
Click to collapse
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
kmani.k78 said:
I followed this video - https://www.youtube.com/watch?v=QicDqTKb_sU
Click to expand...
Click to collapse
kmani.k78 said:
I am using it on Reliance CDMA netowrk. When it was on 5.0.2, I could able to connect to 3G.
But After update to 5.1, I could not use 3G. Only call & sms working.
I have rooted xt1528 in android 5.1 to make modification in the system partition. Rooting works perfectly. but changes made to system partition revert backs to stock after reboot.
Could anyone help me to make permanent changes to /system/build.prop file?
Click to expand...
Click to collapse
Thanks for reporting root worked on your moto e, this is fairly new, Im waiting to see if others can repeat it, and whether it really does work. Have you tried some other apps that require root to see if they actually work with root?
For your specific /system/build.prop issue, some roms write that file from another location, /etc/build.prop or some other similar paths, so maybe need to find that file. Also you have to remount /system as read-write, assuming this worked otherwise there would be an error right away.
Usually I edit /system/build.prop files manually with terminal emulator app, then type these commands:
su (proper root needed)
mount -o rw,remount /system/build.prop
vi /system/build.prop ( may need to install busybox app)
Stock Pixel/PixelXL Kernel + SafetyNet Patch
Current version: android-msm-marlin-3.18-nougat-mr1
Suitable for build: NMF26U
Security patch level: January 5, 2017
I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says marlin, but this also works on sailfish. Google just created one kernel that works on both sailfish (Pixel) and marlin (Pixel XL) devices.
I posted this over in the Pixel thread (as I have the regular Pixel), but thought I'd share it over here as well.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.
Installation:
- Download attached .zip and unzip into a folder
- Reboot device into bootloader (power down device, then Power + Volume down)
- Connect device to computer
- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)
- Enter command: fastboot flash kernel <kernel_image>
- Once flashing is complete, enter command: fastboot reboot
- Disconnect device and wait for reboot sequence to complete.
- You now have a stock Pixel with an unlocked bootloader that can use Android Pay
**WARNING**
If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!
And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest
Downloads:
NMF26U
All versions
Not sure why no ones replied here yet! - it's no use to me but thank you very much
Just downloaded and tried to install using fastboot but my device is stuck in a bootloop My bootloader is unlocked and I had previously rooted using twrp but I was using the stock recovery. I was on version NMF26O. I'm going to try re-rooting again and see if that fixes it.
I don't know how this will interact with rooted devices. I'm personally not rooted and I don't have any issues with this kernel. Try being fully stock first before flashing this.
Sakete said:
I don't know how this will interact with rooted devices. I'm personally not rooted and I don't have any issues with this kernel. Try being fully stock first before flashing this.
Click to expand...
Click to collapse
I might try out a few things later and try different versions of root and post if anything works Thanks mate
THANK YOU! I've been looking for a completely stock kernel that would let me use Android Pay with an unlocked bootloader! Any plans to do this for other Nexus phones, like the 5X?
iissmart said:
THANK YOU! I've been looking for a completely stock kernel that would let me use Android Pay with an unlocked bootloader! Any plans to do this for other Nexus phones, like the 5X?
Click to expand...
Click to collapse
I'll only do it for the Pixel as that's the only phone I have. It's not super difficult to do this yourself though, if you're somewhat technical it's pretty straightforward to do.
I have TWRP updated, newest build F260 and followed the steps but still unable to use Android Pay. Says it cant verify the device or software.
EDIT:Im dumb didn't read that it wasn't compatible with root.. just unlocked bootloader.
ghostENVY said:
I have TWRP updated, newest build F260 and followed the steps but still unable to use Android Pay. Says it cant verify the device or software.
EDIT:Im dumb didn't read that it wasn't compatible with root.. just unlocked bootloader.
Click to expand...
Click to collapse
Yeah, if you're rooted, Android Pay will not work. There is a workaround however. You can add cards to Android Pay before you're rooted. If you root after that, Android Pay should work with the cards you've added. You just won't be able to add new cards.
Thanks for the kernel, just want to ask one question:
I have unlocked bootloader + systemless root, when I power up my phone, there is a yellow warning on the boot screen, if I use this patched kernel, will the yellow waning be gone as well ?
churchmice said:
Thanks for the kernel, just want to ask one question:
I have unlocked bootloader + systemless root, when I power up my phone, there is a yellow warning on the boot screen, if I use this patched kernel, will the yellow waning be gone as well ?
Click to expand...
Click to collapse
You mean the orange warning? That's because unlocked bootloader. Only with locked bootloader the warning disappears.
Tylog said:
You mean the orange warning? That's because unlocked bootloader. Only with locked bootloader the warning disappears.
Click to expand...
Click to collapse
I see, thanks for your explanation. AP is actually not available in my country ( China ), what a pity.
Sakete said:
Yeah, if you're rooted, Android Pay will not work. There is a workaround however. You can add cards to Android Pay before you're rooted. If you root after that, Android Pay should work with the cards you've added. You just won't be able to add new cards.
Click to expand...
Click to collapse
Holy **** thanks for the advice I went ahead and unistalled SuperSU and I added my cards! Thanks!
EDIT: I went to my local McDonalds and tried to pay it said "it couldn't authenticate the device" after adding my cards. This is with root just fyi maybe systemless root will have success.
anybody managed to get AP working with root?
nbhadusia said:
anybody managed to get AP working with root?
Click to expand...
Click to collapse
Not going to happen! Maybe when/if Xposed comes out but until then I don't imagine so
Sent from my Google Pixel XL using XDA Labs
DaveHTC200 said:
Not going to happen! Maybe when/if Xposed comes out but until then I don't imagine so
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I believe a clue of posts up in this thread, someone posted that if you add the cards before you root, Android pay will work for those cards.
Sent from my Pixel using XDA-Developers mobile app
Protibus said:
I believe a clue of posts up in this thread, someone posted that if you add the cards before you root, Android pay will work for those cards.
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Correct, try adding cards before rooting. Once cards are added, root your phone and Android Pay should still work for making payments, you just can't add new cards to it (you'll have to unroot first for that).
ghostENVY said:
EDIT: I went to my local McDonalds and tried to pay it said "it couldn't authenticate the device" after adding my cards. This is with root just fyi maybe systemless root will have success.
Click to expand...
Click to collapse
Oh weird, maybe it doesn't work then? Or it could be another issue. I got this idea from someone else who said it works for him. I myself am not rooted so can't verify otherwise.
Hello, will this still get OTA's and install them / or be able to sideload them???
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Whoa! the unlock tool is out!
Is there any chance someone can make a root guide? I really want to buy Zenfone 3 Ultra but I wouldn't do it without root method out there. Any help is appreciated.
Were waiting on a dev to compile TWRP for us then we can get root
Trying to root ZU680KL
Hi!
I have unlocked my ZU680KL with the Asus unlock tool. Bootloader shows 'unlocked'.
Then I unpacked the stock boot.img (from WW_13.6.15.21_20161215, this what I have installed) and using Vim I set:*ro.secure=0, ro.adb.secure=0, and*ro.debuggable=1 in default.prop.
Repacked the new boot.img and flashed it with 'fastboot flash boot new-boot.img'.
'adb shell getprop' indicates that the new setting was applied.
Yet in the stock recovery mode I cannot install SuperSU-v2.79.zip and no adb devices are seen in recovery mode.
What else is needed? Do I have to edit something in the stock recovery or must wait for custom TWRP?
I was following the basic instructions found here:
https://machiry.wordpress.com/2012/10/26/getting-root-access-on-android-the-actual-way/
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
hillg001 said:
iirc, there's already a thread going where both root & TWRP have been successfully loaded
.
Click to expand...
Click to collapse
Any news?
https://forum.xda-developers.com/ze...t-zenfone-3-ultra-7-0-ww14-1010-1703-t3612108
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
when the ultra 3 first came out, many suggested waiting for a boot loader unlocker, & not updating any Android versions, because an unlock program might not work on subsequent Android versions. Is that the case? ... or does the unlocker work on the newest Android version too.
Thanks
.
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
I have just downloaded the zip, made the APK and installed it on my Zenfone 3 Ultra.
When I run the app, after clicking all the "are you sure..." acknowledgements, the app does not succeed in unlocking the bootloader. The error message indicates an unknown or perhaps network error, and suggests I "try again later..."
Running WW_14.1010.1804.75_20180612
Anybody else seeing this?
Ideas??
Reading on the ASUS blogs, they indicate it isn't supported anymore (no surprise), but shouldn't it still work??
heroxbd said:
The official download link is
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZU680KL/ZU680KL_SIGNED_Android_M_UnlockTool_2017_0222.zip
Available from page:
https://www.asus.com/us/supportonly/Zenfone3 Ultra(ZU680KL)/HelpDesk_Download/
Click to expand...
Click to collapse
Note the links above no longer work. Yes, you can get to the page, but the unlocker isn't there any more.
ndi said:
There is tool from Asus this month to unlock the bootloader. You should know that you lose the guarantee and may no longer receive official updates. After you install the apk and restart the phone, all data on the internal memory will be deleted.
Click to expand...
Click to collapse
Does anybody know which version(s) of the stock ROM this works with? I've tried a couple, and all of them just yield the "unknown error" when running the unlocker.
If you know of a stock ROM version this works with, please post a URL for where I can find it (as it's proven really hard to find specific versions...)
Thanks in advance.
agree it no longer works. getting the unknown error...wait message that everyone else is getting. there are other XDA threads that indicate the same.
Keeping bootloader locked. Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even the SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
-
jrchester said:
Used ADB to install full root with Magisk and Recovery with TWRP. Phone is working fine and even and SafetyNet checks pass as well. Debloated with ADB App Control program (paid for full version).
Click to expand...
Click to collapse
How did you do that? Can I get more details?
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hi Madlzz:
Checkout my XDA post here for more details on how I did this:
unlocking bootloader zenfone ultra
Hi all ive had my zenfone 3 ultra (zu680kl) for some years, until a couple of days ago, my friend wanted to see if my phone could be charged with a dash charger, where others wouldnt my battery was already low and overnight it ran out and when i...
forum.xda-developers.com
- John
Madlzz said:
How did you do that? Can I get more details?
Click to expand...
Click to collapse
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
lucy1983 said:
Hello. I can confirm that on this phone TWRP can be flashed WITHOUT unlocking the bootloader, since that seems not to be an option anymore (since the official unlock tool doesn't work anymore and neither are the usual commands for unlock).
Indeed it is weird that we can install a custom recovery and root with the locked bootloader but i've done it yesterday and there is no problem. My bootloader is locked, I have TWRP installed and root by Magisk latest.
You just need to boot into fastboot mode (press volume up and power at the same time), connect your phone to PC, go into where you have stored your adb and fastboot folder and in that folder open a CMD prompt and enter the command "fastboot flash recovery" and copy the name of the TWRP for our device after "recovery". And press enter. Then you disconnect from PC and navigate in the fastboot menu to the section "recovery" and press power button to boot into TWRP.
After that you can flash latest Magisk zip from the "install" section in TWRP and there you go, you have root.
And the bootloader will still remain locked, hence the safetynet will pass without any problems (play store certified).
Click to expand...
Click to collapse
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
jrchester said:
It's what I've been saying and what I posted originally. I posted to help others out. I don't have to argue with users here that say it can't be done. I did it and mine is still working 100% correctly. I stand by what I said originally and what you just posted. And the comment that I was lucky is ludicrous. Luck has nothing to do with it.
Click to expand...
Click to collapse
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
lucy1983 said:
Yup. It's not a matter of luck. It just can be done without unlocking bootloader on this phone. I can't explain why, because on the majority of phones you can't do anything without unlocking the bootloader. Although an explanation could be the lack of server maintenance from Asus side (since the problem with the unlock tool seems to be from their servers) for this phone. But yeah, you can have TWRP and root on this phone with the bootloader locked. That is a fact.
PS: I'm running the latest official firmware (.75) from Asus.
Click to expand...
Click to collapse
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
jrchester said:
Ditto. Running 1804.75_20180612 official. Also running and keeping Magisk at 23.0 to retain safety check functions. Magisk 24 removes that, but you can reinstall back to 23.0 without any issues and just ignore the updates.
Click to expand...
Click to collapse
You can install Magisk 24 without any problems. For me it doesn't break safetynet and play store says "certified". Even without enabling zigisk.
Dear All , this method maybe already here somewhere ,
i have tried to root this specific device and i ran into many issues !
but successfully i have done it .
i'll upload the patched file here and i'll mention what method i have done ! ..
unlock boot loader is a must . ( Please read about it in google , All Samsung devices is the same method )
u might repeat the process to times until it successfully unlocked and greyed-out !
Next download this firmware only to be able to run the patched AP .
un-tick Auto-reboot before flashing .
once flash done , power + Volume down to restart , then volume up with power until u boot into the recovery
wipe data . restart . done
to make sure u have done every thing correctly u'll see RED massage once u boot you're device
Firmware ( This is UAE Firmware " T725XXS1ATC5_T725OJM1ASJ3_XSG " ) All Languages included . Link
Patched AP File Link
Please Note that i'm not responsible if u break your Tablet ! .
Proof ( IMG )
GD day :angel:
after rooting is it possible to update firmware to a new one?
moresat said:
after rooting is it possible to update firmware to a new one?
Click to expand...
Click to collapse
No ! ..
Hi
Do I just need to use odin to flash the Firmware you mentioned then use ODIN again to flash the patched ap
I can just add that with this specific fw version and patched ap everything worked on LTE version but I might add my little deviations ...
1st original firmware flash (BL,AP,CP,CSC-non-home one) instantly followed by wipe data in recovery mode.
2nd After the initial setup + wifi connection I installed and updated magisk.
3rd "adb restart bootloader" (here i am not sure if it mattered but anyway) and flush again with the provided Patched AP File (BL,the_patched_AP,CSC - the home one this time ... using CP failed with modem err with me so I just skipped it here)
4th get trough the init setup again with wifi on and open magisk which will install more stuff.
The prerequisites still apply oem unlocked bootloader before you start and keep your battery at least 60-70% since the process drained mine a lot.
You know you are on the right track when you have warning with tablet bootloader is unlocked (at startup yellow) and tablet not running Samsung's official software (red after the first one)
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
chadandchew said:
Ive just bought this SM-T725 model android 11. There is no sign of OEM Unlock Bootloader under development. Does anyone know how I can unlock this.
Click to expand...
Click to collapse
The option only shows up when you are connected to the internet.
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
chadandchew said:
Thanks for reply mate, I got it figured. I also manage to get root and twrp recovery but not both at the same time. After flashing and using twrp recovery I then lose root after reboot and have to flash a patched magisk bundle over odin again. Bit inconvenient but I only intend using twrp now and then for backup/recovery.
Can you recommend a stable rom for this device - far too much google bloat on it for my liking. I tried latest lineage but found it unstable.
Click to expand...
Click to collapse
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Thanks for reply. Will try the LOS ROM later. Wish Google crap would disappear totally. I hate it enormously.
By the way which folder am I looking for on that LOS ROM download page
Ah gts4lv I presume
chadandchew said:
Wish Google crap would disappear totally. I hate it enormously.
Click to expand...
Click to collapse
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
topaza said:
then go for LOS+MG: https://download.lineage.microg.org/gts4lv/
Click to expand...
Click to collapse
Recently switched to using MicroG Lineage. Timely enough, MicroG passes the SafetyNet now as per the instructions mentioned below and indicated in the attached screenshot. For the fingerprint, I had selected the T720 from the list.
https://www.reddit.com/r/MicroG/comments/shmpng
Along with Aurora store installed as a service, I think you don't need Google anymore.
topaza said:
Just install LineageOS. Clean, no Bloat, everything smooth and you can have TWRP and Root/Magisk at the same time.
Depending on how much Google you want to have on your device, you might rather choose LOS+MG ( https://lineage.microg.org/) I can highly recommend it. You get rid of Google which debloats it even more and is a plus for your privacy but almost everything works (at leat for me. But migh depend on your needs)
If you like Google, just use normal LineageOS (https://lineageos.org) + GAPPS
Click to expand...
Click to collapse
I'm having some problem here:
I can install LineageOS, I can root/Magisk, I can have TWRP, but not all together at once.
Can you help me on how to do this?
Working on a SM-T725 of course, actually rooted, lineage and TWRP installed, but my Magisk can't install modules, it seems it doens't have root privileges.
Thanks in advance for your answer
anybody have an updated one, the file has been archived on the said link... thanks in advance
My Realme 6 is kept showing me:
The serial is not match
fastboot_unlock_verify fail
every time I tried to get into fastboot mode Using command adb reboot bootloader,
the bootloader is already unlocked, so I can't enter fastboot mode via the (In-depth Test) App.
It would be my pleasure if anyone got a fix for this problem,
regards
Do u have a solution for this? I was able to unlock but I want to relock and in I'm getting a similar window in fastboot, mine shows this :
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 12, after accidentally updating from rooted android 11 to android 12 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 12.
Any ideas??
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
soler37 said:
I only recieved the error when I tried to load into fastboot, the problem is with the newer update of Realme, you cannot unlock the bootloader from ADB, you must revert back to older versions, I used this guide:
[GUIDE] UNBRICK/DOWNGRADE YOUR REALME 6/6I(INDIA)/6S USING SPFLASH TOOL FOR FREE!
Hello everyone! So after the new mediatek DAA and SLA protection bypasses you can find github repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX2001, RMX2002 and RMX2003 ONLY...
forum.xda-developers.com
once my phone was back to B.53 - Mega - Google Drive - Mirror3, I was able to go into fastboot and relock my bootloader.
Click to expand...
Click to collapse
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
leopseft said:
@Alabfa @soler37 You guys found out what triggered those messages?
Me and another user of realme 7 are receiving the same errors. I recieve the first error, with unlocked kernel, non rooted android 11, after accidentally updating from rooted android 10 to android 11 without removing root before the update.
And the other user @Y-YoUsSef-F recieves the second error with unlocked kernel and rooted android 11.
Any ideas??
Click to expand...
Click to collapse
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Y-YoUsSef-F said:
Bro I am android 12 (F.07)
not android 11?
Or you meant something else?
Click to expand...
Click to collapse
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
leopseft said:
Yeah, android 11 and 12 not 10 and 11. I'll fix it.
Click to expand...
Click to collapse
Ok bro
leopseft said:
Yeah we receive the errors when try to enter in fastboot mode too.So they have locked access to fastboot in newer version probably.
Thanks for letting us know!!
Click to expand...
Click to collapse
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Hi, but bro I am in android 12 (F.07) with magisk Root and google wallet (NFC) works great, I think for now not sure if I gonna upgrade to F.09 and losing root access
As my friend @leopseft described our situation, can't enter fastboot mode
soler37 said:
sure thing!
I had this in my mind for a long time as once bootloader is unlocked, you cannot use google pay / Wallet, finally, I took to the guide and sat a whole night just incase I have any issues, I did run across one but its all in the guides.
Click to expand...
Click to collapse
Actually you can pass the safetynet tests with Magisk modules and magisk hide. But this is another topic. I can help you if you decide to re unlock and root!!
But I have an idea which I wanna try first about the access to fastboot mode.
In the guide you posted there is a step in which you bypass mtk authentication.
(4. Turn off your phone and again connect to PC while holding Vol+- buttons then run the brom.bat under Bypass folder. If it says "Protection Disabled" in the end you're ready to go on. (If it's like the screenshot below go on.))
Did you try to access into fastboot after this step or you continue to the flash process??
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
leopseft said:
Guys I found the solution.
I managed to get into fastboot mode using the following commands:
adb devices
adb shell reboot fastboot
Click to expand...
Click to collapse
Thank you bro for this solution and I'm so glad you replied to this thread,
but for me, I was able to get into fastboot without this problem after I installed A13 custom Rom (EvolutionX v7.2 UNOFFICIAL)
I used these commands:
adb devices
adb reboot bootloader
As a reminder, my problem was:
The serial is not match
fastboot_unlock_verify fail
Click to expand...
Click to collapse
Thanks again <3