Related
I wanted to share two things with you guys here in Tablet z forum:
1- First of all, @zxz0O0 has developed a code based on the CVE-2015-1805 vulnerability that gives temporary root access to a select range of devices (including Tablet Z4). Let me try to explain in my words what that means. A full blown root gives permanent read/write access to /system and /data partitions. On an unrooted Tablet Z4 you only have read access to /system and no access to /data. With this root, you will be able to have a temporary terminal or adb session that gives you read access to /system and read/write access to /data. Why not write access to /system? Because Sony runs a service called RIC on Xperia devices that makes it impossible to mount /system as writable. In the past this would be patched by modifying the system partition. But in the recent Kernels sony has implemented a mechanism (dm-verity) which checks /system and if it is modified the device does not boot. So even if this (or any other) root method gave you the ability to write in /system you could not use it because your device would not restart the next time you turn it off. The solution would be to patch the kernel which requires an unlocked bootloader. IF you unlock your bootloader you lose your TA partition permanently which includes some of the Xperia features and licenses that have to do with image processing and some DRM. So a lot of us do not want to unlock the bootloader.
Then what good is this new root method? Since it gives you read access to the system partitions you can use this method to back up your TA partition. The idea is that if you ever unlock your bootloader you may be able to use this TA back up to return the system to its original state if you ever decide to relock it. Another benefit is that tools like Titanium back up which require access to the /data partition can now function (in a limited sense) although someone has to work out the details of that.
To download the pack that allows backup and restore of the TA partition go to http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
After you create the backup, you can unlock the bootloader, and use your TA backup and the procedure outlined here: http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605 to create a csutom kernel that uses all the good stuff in the TA backup and emulates an environment where your tablet behaves like one with an unlocked bootloader. The camera denoising algorithm and all other Sony proprietary software which would be disabled after unlocking the bootloader should work.
If you want to return the tablet to its unlocked condition you will need this TA backup. Some explanation about retrieving the TA partition from this backup, if you unlock the bootloader and decide to relock it, is given here http://forum.xda-developers.com/showpost.php?p=66142823&postcount=16 and methods to do so are outlined at: http://forum.xda-developers.com/showpost.php?p=66158970&postcount=68
Note that to use this root you need to downgrade to lollipop (preferably version 28.0.A.8.260)
I have explained procedures to use the above tools here http://forum.xda-developers.com/z4-tablet/general/guide-safe-bootloader-unlock-restore-t3362391 at length.
2- Now, here is the use I have found for this temporary root: I was always bothered by the fact that not only I could not (easily) get the 17 hour advertised on-screen use out of my tablet, the standby power consumption was always too much. Whereas I could optimize my other (rooted) devices to only drain 1-2% a day in standby, tablet Z4 seems to settle for nothing less that 5-10% a day in standby. This is what you can do to get excellent standby power from your tablet:
A) Say goodbye to your google apps (with the exception of Chrome and Maps) and other marginally advantageous apps. They wake your device up all the time when it is supposed be sleeping and endlessly chat with google servers even if you turn all the communications off in the google settings. So disable all of the apps listed in the attached pictures , plus lifelog,via settings. Don't complain about not being able to use the gmail or youtube apps. Other great replacements exist. Leave "Google App" active if you use the voice search or voice typing feature. Also uninstall the pre-loaded apps that you aren't using like facebook (which is cancer for any phone), Lifelog, Privilege, spotify, etc.
B) In settings under wifi open the advance menu turn off both "network notification" and "scanning always available", and change "keep wifi on" to "only when plugged in"
C) Under "power management" in settings, activate stamina mode and extended standby (no need to activate extended usage).
D) Finally (and here is where the temp root becomes useful) extract the file "iovyroot" from the file in the above link and put it in your adb directory. Open a command terminal and type:
Code:
adb push root\iovyroot /data/local/tmp/iovyroot
adb shell chmod 777 /data/local/tmp/iovyroot
adb shell
This gives you an android terminal shell. Continue with the following:
Code:
/data/local/tmp/iovyroot
pm disable com.sonyericsson.idd.agent
pm disable com.sonymobile.entrance
pm disable com.sonyericsson.updatecenter
pm disable com.sonymobile.anondata
pm disable com.dsi.ant.server
pm disable com.sonymobile.gmailreaderservice
pm disable com.sonymobile.googleanalyticsproxy
pm disable com.sonymobile.mx.android
pm disable com.sonymobile.enterprise.service
pm disable com.sonymobile.synchub
pm disable com.sonymobile.phoneusage
That is it. You just disabled the update service and a bunch of other things and extended your standby battery life. These settings will survive a reboot.
Let me know how it works out for you. If you find other creative uses for this temp root share here.
This is the BEST and probably the most right to the real point post ive ever readed in this particular forum since I joined....
Forgive me if I say I have had lost the faith on sony's z4t development here... It's a real pleasure to know there's still ppl working on what I think should be the right development direction on gettin' control of our loved devices, instead of breaking them and throw a lot of expensive features to the flush.
Thanks again mate to share it.
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Stevethegreat said:
Interesting, if I downgrade do I also lose my Marshmallow data and settings (i.e. is it the same as factory reset?)
BTW Finally this tablet becomes viable, almost a year after its release...
Click to expand...
Click to collapse
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Hmm, but if you can also temp root then you can backup everything using TitaniumBackup anyway before unlocking.
So if I understand this right, if you can back up TA we can infact unlock the bootloader now with no loss of DRM ?
So can now actually get full root based on that ?
najoor said:
If you want to have a stable system you will need to overwrite the user data which means you will lose your apps and settings and possibly (depending on how you flash) your internal storage so make a back up.
In general application data of Android firmware are not downward compatible with older versions.
Click to expand...
Click to collapse
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Stevethegreat said:
I will only downgrade to get a TA Backup, so stability is not an issue to me (after the TA Backup, I'll go back to MM and probably unlock it).
My only issue would be if downgrading would actually harm my data and/or my capacity to get the TA backup properly (if I'm not wipe first I mean).
Click to expand...
Click to collapse
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
najoor said:
I don't think it will affect the TA back up process by it may harm you application data (not your sdcard data). The reason is that on every reboot android cleans up the) /data partition as much as it can (for example if it sees that an app has been uninstall but it has left some data behind). I'm doing so lollipop may corrupt some of your marshmallow data,
Why don't you take a backup of your data before a downgrade and the restore them later? The tablet itself has a utility to do it and I hear Helium is a tool that backs up your app data without the need for root.
Click to expand...
Click to collapse
Mostly to save time as I have too much data. I though to do it like this
Downgrade to Lollipop -> Use the Exploit -> TA Backup -> Upgrade back to Marshmallow.
In principle everything should have had worked as by the end of it I would be back to Marshmallow (I would not linger into Lollipop). But now that you're telling me that lollipop may corrupt my data permanently I have second thoughts.
I thought, that my data would not work well on Lollipop, but that wouldn't matter to me; but now you're telling me that they won't work when I'll back in Marshmallow too, which is a totally different beast. Am I understanding you correctly?
Does everyone need to downgrade tho?
Once we have the TA partition available to restore, once its made available online surely everyone else can just restore the same one?
Or is the key unique?
Kinda assuming here that all the stuff that needs the TA partition will work with an unlocked bootloader, or does it have to be locked to be usable again?
Edit: Can we restore TA partition after unlocking bootloader?
Yes but this will also relock the bootloader.
Bugger
Ultimately never rooted my device for fear of losing something (that I will never use anyway!)
DRM Keys are unique, in fact that's the whole point of TA backups.
Also there's a talk (on the other thread) of a tool that would merge your particular keys with a particular custom kernel.
That way you'd keep all Sony Exclusive features, but also be able to make use of root apps. It would be great if such a tool becomes usable with AndroPlus Kernel...
Nice, had all but given up hope of being able to unlock my Z4 so that sounds promising!
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
D0MINO said:
I am looking for a high-end tablet and it seemed the Z4 Tablet was the best one for me over the Pixel C and even the iPad Air 2..though I did consider the budget Nvidia Shield K1 also.
The next thing I did was see if the bootloader could be unlocked and custom ROMs installed as I really hate the Sony UI that I have experienced with my sisters M2, and I never stick to the stock ROM in any of my phones. I just love knowing and doing customising!!
..Unfortunately, it seems like I will be stuck with it so I may have to look for another brand now
Click to expand...
Click to collapse
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
I unlocked the bootloader and rooted the device SGP771.
Bevor that, i backed up the TA.
Then i flashed the androplus kernel.
Everything works great.
But you cannot modify androplus kernel with that tool. That means DRM restore is only possible on stock rom.
When you restore TA to stock rom, your bootloader will be in a lockes status again and there is no more root. Too bad
odicamillo said:
Can anyone confirm how to re-lock the bootloader once unlocked?
I would say:
1. Flash a stock firmware (the lollipop version that you used to backup the TA partition).
2. Use the iovyroot temp root batch tarestore to restore your TA partition.
3. Reboot and that's it: you are back to unlocked bootloader unrooted original drm included stock firmware.
Anyone already tried?
Thank you.
Click to expand...
Click to collapse
Can ta be restored on any fw like marshmallow or can it only be restored on the fw that you backed it up from?
This looks very promising, thanks OP.
Has anyone else managed to get it to work as described?
Thanks in advance
najoor said:
I don't know how you got that impression, since the whole point of the OP and the links I posted with it is that you will not be stuck with the stock firmware.
So to summarize the points mentioned in the OP:
As of today, the following is possible with a tablet Z4:
1- The TA partition can be backed up.
2- The booloader can be unlocked.
3- The unlocking is reversible with the help of the backed up TA pertition
4- When the bootloader is unlocked a custom kernel can be flashed (currently one is posted in the Z4 forum courtesy of @AndroPlus).
5- When the bootloader is unlocked the stick Kernel can be patched to retrieve the Xperia proprietary facilities that are lost to the unlocking process (courtesy of @tobias.waldvogel).
6- When the bootloader is unlocked /system can be fully modified. That means flashing completely custom ROMs.
So you can either make your own modification to the system, or wait for someone to make a ROM. In light of the above possibilities it is only a matter of time before customs ROMs start to pop up.
By the way, to the extent that the stock firmware is customizable without unlocking the bootloader, it is actually a good ROM and you can change a lot of things from the general appearance to the default launcher.
PS: Tablet Z4 is my second Sony tablet and the third Sony mobile device and I have about 10 of this kind of devices at any given time. The other android devices are miles behind in terms of elegance and manufacturing quality. There is just something about a Sony device that is unique and unmatched.
Click to expand...
Click to collapse
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
retikulatus said:
Dear najoor,
are you telling us that, now, we can unlock a z4 tablet which has the "rooting status: Bootloader unlock allowed: NO" , in the service info/configuration area ?!?
if it is the case, i would be delighted to know how to proceed step by step, as i would love to install a lineage rooted custom rom on it (it is the SGP771 one,with phone capability)!!!
thank you
kind regards from France
Click to expand...
Click to collapse
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
najoor said:
Unfortunately if that is the case you cannot unlock the bootloader.
I am just curious, why does yours look like that? Do you have myXperia or some other find-my-phone service activated on your phone?
Click to expand...
Click to collapse
Thanks for the fast reply even if you ruined my hopes
no, i don't think i have myXperia , i checked on my apps and find nothing.
Since i had display issues with my tab s (sm-t800), i tried the z4 tablet for its LCD screen instead of the super amoled of samsung...
My bootloader was already locked when i purchased it, i updated it thinking it will change that but unfortunatly that did nothing.
It wasn't a new one though, perhaps the previews owner messed up with it and got its bootloader locked :/
Because it is some kind of lotery to have a bootloader unlockable with sony, i will wait patiently until samsumg release its 16:9/10 tab s4: imho, the tab s3 actual 4:3 format is a nonsense....
Thank you again
Kind regards from France
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
What version are you running? B20/B27/B29
If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.
S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.
No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.
Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA
totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with
I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system
rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.
rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis
It seems like everywhere there's circular logic in the steps to get from stock to root and at some point a tool which gets flagged as a trojan by 20 or so antivirus products is a part of the process.
step 1 - download and use tenfar's axon7backup.exe to make a backup
step 2 - download and use tenfar's axon7root.exe trojan. I guess you have to turn off any antivirus on your computer for it to work which makes no sense because I've never had to root an Android device with a utility flagged as Windows malware - which is even more suspect considering half of VirusTotal's scan engines detect malware. False positive? Really?
step 3 - flash tenfar's boot.img (I don't know which to use since only B27 is provided), maybe DrakenFX's StockSystem and BootStack but his notes say it requires TWRP recovery
step 4 - flash tenfar's unofficial TWRP recovery
step 5 - wipe everything 5 times.
step 6 - install SuperSu or PHH superuser
and then there are several other suggestions sprinkled in to install other files to unlock w/o an unlocked bootloader or something yet say you need TWRP... which requires an unlocked bootloader. It sounds like every suggestion ends up depending on this axon7root.exe file
I don't get it.
There's no way I'm using literally closed-source malware to root my phone. I also don't feel the response that tenfar's method is not malicious when he's not the one making that claim... it's just random users. It makes no sense.
The way to do it is just follow the guide but I'll do my best to answer what I can.
The trojan is because the tool is pretty much a rootkit for your phone. It is hacking the system and if you're not doing it yourself, well that's not good. I personally just went to defender and restored the file and told it to ignore it.
Back when you could officially unlock the phone, you had options. Since that isn't possible at the moment (I think?), you'll have to go through this sequence to get root or unlock. I recommend rooting without unlocking if you don't really care (no real reason to unlock at the moment other than Magisk or something).
You're not flashing the bootimg with twrp you flash it with the tool on your pc. Once you do have twrp it makes everything easier imo.
When you go through the steps in tenfar's root program you should end up with backups, twrp and root, however this is NOT POSSIBLE on B29, so you'll have to do it on B20 or B27.
Hope I helped, but you should really go and look over those threads again, they'll be a lot better than I am.
I understand why you're confused. When a phone is new, threads and guides are made as progress is made. Some are updated, some aren't, some methods become obsolete with updates, some don't. Right now, this is the most painless process for rooting your phone and it includes unlocking the bootloader (otherwise, you're going to be stuck with an encrypted data partition in TWRP and it will be inaccessible in recovery).
1.) Copy everything off your internal storage that you don't want to lose.
2.) Get all of the files you need from the steps below and put them on your microSD card.
3.) Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
4.) Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
5.) Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
Now, you say: "There's no way I'm using literally closed-source malware to root my phone. I also don't feel the response that tenfar's method is not malicious when he's not the one making that claim... it's just random users. It makes no sense."
If that's the case, this phone isn't for you. In fact, many phones with dev support on XDA aren't for you. In many cases, it requires a "malicious" tool to "break into" a phone that's locked down. I'm surprised you made it this far without realizing it.
thank you both
@rczrider perhaps I am suspicious because I have gotten this far without using methods which employ this behavior. If it was detected with an Android/Arm/Qualcomm signature that is a little more understanding but the heuristics point to a Win32 trojan.
I guess I've just rooted Nexus, LG, and Samsung devices and this is my first least unfriendly method I've come across :/
https://virustotal.com/en/file/070b...8ba19b57c66a9cc27b286d50/analysis/1478566368/
https://virustotal.com/en/file/4c47...70ee78db8fd3ebda2f54de31/analysis/1478567966/
Regardless, I'll go ahead and mark as answered even though it's not really answered. Plus, I don't know what is being exploited and if it is making a permanent lower-level vulnerability open for attack by doing it. That's the part that concerns me. I mean, I use Virtualbox to do this stuff just to keep my machine safe. But if it's a lower-level permanent backdoor that is what concerns me because it isn't explained in his thread.
I am so confused
Sent from my ZTE A2017U using Tapatalk
I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
yourSAS said:
I wish to root my phone(XT1686) but intend to keep the stock ROM(no bootloader unlock).
Is there any advantage in doing so? And will OTA updates be affected?
Click to expand...
Click to collapse
It is not possible to root without unlocking the bootloader on this device...
If you don't have a specific reason to root, don't do it.
And once rooted, you cannot accept any OTA... most likely case if you do it will just fail, worst possible case it bricks (which can happen but is extremely rare).
To answer the question in your title, about the advantages of rooting...
Rooting gives you near full access to your device, and thus the ability to customize it beyond the options provided to you via the default interface. Also, some apps provide additional features on rooted phones. For example, some security programs recommend rooting your device so that it can more forcefully integrate itself with the device to protect against malware, hacking, etc. I tend to install a security package that works better on a rooted device, as well as make use of features that tend to only work on a rooted device, such as folder mounting from the internal SD card to the external one. Also, allows me to access system files that are unavailable otherwise, allowing me to customize certain sounds (or copy them at least).
If you decide you want to root your device, make sure you understand the steps to take BEFORE trying it. That means when you come across a guide on how to do it, make sure you get all the files that will be required and reading through the instructions step by step. If any of the steps sound like it will leave you lost on what to do, then DO NOT do any of it. Also, make sure you read the comments for the guide as well, looking for any mention of issues encountered and consider if you might encounter those issues as well. For example, if it causes issues for devices that use a particular carrier and you use that same carrier, you might want to leave well enough alone. Compare your phone version numbers with what others report having issues with (kernel, baseband, build, etc). Anything that someone has an issue with where their phone somehow matches up with yours in some way, take that as a sign to investigate deeper, so as to avoid having any issues yourself.
For the most part, unless you have a need or desire for a feature/function that requires rooting your device, don't mess with it. I'm not kidding, as one mistake can leave you without a working phone and without any options for returning/replacing it.
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
yourSAS said:
Thanks for the replies & warnings.
I'm not a noob so I know the risks of rooting. So maybe I should have rephrased it-
What are the advantages of rooting Moto G5 plus specifically?
Say like in terms of mods and other stuff? Also, is it possible to unroot once rooted- I mean to ask if it's possible to revert the state to factory mode with bootloader locked and stock ROM so that device will be eligible for OTA updates again?
Click to expand...
Click to collapse
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Unrooting is easy, the issue arises undoing what you did with root, undoing them all depends what you changed.
I don't know of any reasons specific to this device to root.
acejavelin said:
Bootloader lock is not relevant to OTA's. You might be able to relock, but the fact it was once unlocked cannot be hidden, it will always be very clear that it was unlocked.
Click to expand...
Click to collapse
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
yourSAS said:
If the OEM knows I've unlocked bootloader, why will it push OTAs to my phone even though I've locked bootloader on my end? So isn't bootloader lock status relevant for OTA?
Click to expand...
Click to collapse
No, the status of your bootloader is not relevant... Moto will notify you of an available update and happily attempt to apply it regardless if your bootloader is locked or not.
What matters is if the boot or system partitions is changed, if there is ANY change to those, among other things like if the radio version or recovery versions don't match or the partition table is changed, the update will fail. If you flash any custom recovery it will fail as well.
On this subject I mention a slight con which is that some banking or financial apps might complain to you if they detect root. I have maybe 10 different bank and credit apps installed and all work flawlessly except 1. The Huntington Bank app wont allow me to use fingerprint login but otherwise the app is fully functional like mobile deposits. Just wanted to mention to be aware.
EDIT 3: It appears this device has a locked bootloader, which means that twrp wont work, and that device tree was a waste of time... I guess I'll just wait until someone or Samsung releases the firmware for Magisk.
EDIT 2: I have successfully built a device tree for this device using TWRPBuilder's script on github. Although it might not be fully complete, it is still a start. Note: I built using an android 8 release. Does the boardconfig.mk file still work for android 9????
I plan on comparing it with a different device tree to make sure nothing is blatantly wrong with it, but I'm not a developer so I don't know if that will help.
(Anyone willing to help me? If I could efficiently navigate the linux CLI I would probably be much faster...)
My current plan is to build TWRP for this device to back up the ROM so that I can use Magisk.
https://github.com/TwrpBuilder/twrpbuilder_tree_generator/blob/master/README.md
Link to device tree builder for those interested. Dont even ask how long it took me to realize I had to add the commands to the end of the java executive instead of typing TWRPBuilder -r recovery.img. command.
-------
EDIT: To those that read, Samsung has restrictions against downgrading apparently. Currently, the only way for root is by waiting for someone to share the official stock ROM. The first half of this method about getting the firmware Does Not Work I don't know about the rest...
-----
Hello everyone,
I would first like to say that I think this is a working method, but I want to double check with someone who has rooted before.
I have the above mentioned phone, and after a ton of research, have determined a path to rooting it through Magisk. I'm currently running Android Pie 9, on the latest stock firmware from att.
This phone does not have A/B partitioning, but has system-as-root and it will require a copy (and Magisk patched) ROM to root.
One of the main problems I have is not having the latest firmware for my device. (Don't tell me to look it up. Its non-existent on the web) I have found that Samsung's Smart Switch will allow you to obtain the official ROM.
However, to download the ROM, I have to have an outdated phone. The most recent update for my phone was to upgrade from Android 8.0 to 9.0.
I assume such an upgrade requires the whole ROM to be downloaded.
Is it possible to use an outdated ROM for my phone (Yes, I have one for android 8) and downgrade my OS so that I can then update from Smart Switch and get a copy of the current firmware to use with Magisk?
Edit: apparently Samsung has protections against downgrading. I tried samfirm but to no avail.
Anyone know of any compatible custom ROMs?
Will keep trying to root though...
I know many people will immediately say yes, but this phone is different.
There is no OEM unlock in Developer options (read more about this further!), and there is no fastboot. There is no TWRP for this phone either (some older threads on Magisk mentioned TWRP, so I am confused if I need it for rooting via Magisk)
I have discovered, that if you were to hold HOME + POWER + UP, on powerup, you can get to a warning about installing custom OSes and an option to continue.
I pressed continue.
Someone on the web said pressing up will wipe the phone, since it unlocks the bootloader.
My phone did not get wiped.
Is my phone's bootloader/OEM unlocked?
I want to know because I Think Magisk requires an unlocked bootloader.
If Magisk doesn't, I'm all good, and I am glad I can install custom OSes (not my goal, but will do if desperate)
If it does require it, I believe my hone already has an unlocked bootloader/OEM
One last note, does downgrading trip anything? I have no warranty, but I know there are other protections (like KNOX) that could affect the outcome.
(I've heard downgrading won't change anything)
Is there anything I need to turn off?
To Recap:
Downgrade OS
Update via Smart Switch to get stock ROM
Use Magisk to root my phone.
I'm simply asking if everything will turn out OK.
(Sorry for the exceedingly long post)
Thanks.
I don't have this phone but I wanted to have one, but after I realized there is no method to unlock it, you are out of luck I also have a phone laying around (Zte Avid Plus with android lolipop), I built a ROM and recovery for it but I realized there is no method to unlock the bootloader. The only method is to get your hands on the bootloader from this device and try and modify it and pray that it works. That is just how a lot budget devices are built nowadays. And that's sad. The thing is that there was a successor to the Zte Avid with the same specs but it ran Android Oreo. Meanwhile the Avid ran Lolipop. A method from manufacturers to always force us to buy new phones.