Related
Hi there,
I found there is a thread describing how to root the US/Chinese model without unlocking the bootloader -
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
However it mentions that this'll brick the European model because of the included TWRP version and unfortunately I'm on a ZTE A2017GV1.0.0B08 (Android 6.0.1, Kernel 3.18.20).
Is there any news if this can be done now with the international variant -
I'm not interested in a custom ROM or updating Android, I'm happy at the moment with the 6.0.1 version I have, but really would like root for xposed framework, Titanium, Tasker ...
Is there a different TWRP version that can be used or is it not working due to the ZTE's signature key used?
Alternatively is there a way for the A2017G to re-lock the bootloader that's 100% working/safe, if you don't apply a custom ROM?
Thanks a lot for your help!
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
marcus.linkenbach said:
The answer you will find here
https://forum.xda-developers.com/showthread.php?t=3441204
This is the way I did it with my first A7
sent from zte axon 7 with tapatalk
Click to expand...
Click to collapse
Hallo Marcus
Danke fuer die Antwort -
Maybe I didn't fully comprehend the thread - I was under the impression that it bricked some A2017G, while not others and didn't want to take the risk.
Reading through the instructions - which of these steps did you take (and in what order)?
I read it that you do not need to flash TWRP? So can I just root the phone without bricking it and all is good as long as I stay with my 6.0.1 B08 version?
I understand the instructions as
- boot into edl
- install Qualcomm driver
- run axon7root to already root the device (backup seems to be done in the next step?! according to instructions).
However there is no axon7root version for the A2017G (B08) as it was removed due to TWRP?!
All I can find is the axon7backup tool (would you actually do this before you run the axon7root the first time?)
If you run the axon7root, did you do 'axon7root.exe -p 4 -b'
so that it only flashes the boot.img (not TWRP recovery) and therefore this is safe?
Sorry for the long essay, help is really appreciated!
Hey, sorry for the delay.
I am quite busy. I really don't know the procedere anymore. It is a long time ago. But if you would give me some time, I will have a look on it and will let you know. But why won't you unlock your bootloader? Without unlocking not everything runs as it should with unlocked BL.
OK. I will let you know.
Marcus
Sn8K said:
Hi.
It didn't really answer the question : Is unlocking necessary to root, or can we root without unlocking ?
Every tutorials founds all follows the same paths : Unlock first, then root. But why ? is there a reason for that, or is it just a "since i'm rooting, let's unlock it while i'm at it" thing ?
(edit : Sorry 4 my english ... i hope i've been clear enough)
Click to expand...
Click to collapse
Theoretically, yes, you can root w/o unlocking the bootloader. This is how things are done typically with certain manufacturers (LG, Samsung) that rarely offer BL unlocking. To be able to flash TWRP on a locked BL is even more difficult, as it would require a BL-level exploit. The reason that's not an option here is the ability to unlock, which precludes such development.
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Whoooo? said:
Hi Marcus,
Thanks a lot, that would be really great.
Regarding Bootloader unlock - I didn't buy the phone in the EU, hence my warranty would be void if I unlock it. And my warranty even comes with screen replacement (not that I ever cracked a screen, but there's always a first).
I have to admit that I'm tempted by Lineage OS, but for now (as I just bought the phone) - if there's a reasonably safe way to root without unlock, I'd prefer to just root and then maybe in a year's time or so switch to Lineage OS...
For now I managed to have my phone recognized as QUSB_BULK and I can boot into edl.
I was trying to use the axon7toolkit (1.1.1), but for whatever reason I cannot use it in commandline mode (maybe as there seem to be different versions, or maybe cause I am on Win7 32bit, no idea).
Any help would be really great!
Hi jeboo, Hi Sn8k,
Hope above explained my motivation, regarding root without unlocking - there's a thread about this
https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
HOWEVER there are two problems:
1) The bootloader can stay locked as it's using a signed version of TWRP, which can brick your device (A2017G)
2) The linked axon7root.exe is not for my device (A2017G B08).
Having said that, some users have been successful with rooting this version, so there seems to be a way, if you get the steps right.
Click to expand...
Click to collapse
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
catadoxy said:
Did you figured out a method to root the A2017G without unlocking?
I just got mine and need root for transferring all the apps from my old Nubia Z7....
Thx.
Click to expand...
Click to collapse
You can't. Don't even try it if you don't want to face DFU...
Just use the same app that the phone comes with, I think it's WeShare or something like that. It should let you transfer all of your crap via a LAN wifi transmission (If you use a 5GHz hotspot it'll be fast as heck).
Or just unlock the phone. But don't relock it if you do, because you can make a huge mess
Hi all,
I don't have this phone yet, but was wondering if the bootloader can be unlocked. If it can then it will be possible to root.
Here is a simple guide, if there is anyone here that would like to try. No software required.
http://techbeasts.com/how-to-enable-oem-unlock-on-android-nougat/
If OEM Unlock shows up in the developers options menu.. good news!! If OEM Unlock doesn't show up, then there is no way to unlock the bootloader.
Please let me know if your phone is the Amazon Prime version. The Prime version may be locked down.
Thanks for any replies!
Prime version is indeed locked down. Also, at any point that you change anything on the phone to do anything with the software, Amazon will not provide you updates again.
I was able to unlock developer options in my Amazon version but now what? I'm assuming that the bootloader is now unlocked and theoretically, I should be able to flash a new rom? Problem is, does one exist? Cheers.
Just an FYI that my Prime Version did allow me to activate Developer Options/OEM Unlocking. Next step is trying to find a rom or even flash it to regular factory default. That I have not found yet.
Quick question SDACymru - I'm getting this phone in a few days... how did you perform the OEM unlock in dev options?
The normal way. Just tapping on the option for 5 or 6 times.
SDACymru said:
The normal way. Just tapping on the option for 5 or 6 times.
Click to expand...
Click to collapse
Thanks. Is there a reason we shouldn't be able to restore from a backup of a non-ads phone stock image and at least get that running on ad-based versions? From my understanding they are exactly the same hardware-wise, so should be possible...
Being able to expose "Developer option" and access to "OEM unlock" still don't make this is developer-friendly device, but I quite surprised that the Amazon Prime version even show the "OEM unlock" in the "Developer option". Anyway, it is close, if you can also perform the last 2 steps, then this device can be considered as developer-friendly.
The next 2 steps are:
- Reboot into fastboot
- fastboot oem unlock (from adb console)
Some devices with full fastboot implementation can check the device lock state by
- fastboot getvar all
If all these commands work, then the device will have good developer support. In addition, if all these commands work on the Amazon Prime version, then it is a piece of cake to remove the Amazon ads.
did anyone every try any of this? ADB Shell temp root has been achieved on this model, I have the temp root xploit but it's useless unless people know what they are doing with it. You can easily brick your phone. I don't physically have this phone but what I do have is a little knowledge, access to the stock rom and a way to flash it. I also know that the recovery can be swapped with TWRP during that flash process. Hit me up on Telegram: https://t.me/PizzaG
So being that I have actually gained temp root access (all credit to PizzaG, he knows his stuff)
Should I go ahead and give the fastboot steps a go? Would the persdata\nvdata remove the temp root access with a reboot or am I way off course?
Any input appreciated
Sent from my Alcatel 6060C using XDA Labs
DelRi0 said:
So being that I have actually gained temp root access (all credit to PizzaG, he knows his stuff)
Should I go ahead and give the fastboot steps a go? Would the persdata\nvdata remove the temp root access with a reboot or am I way off course?
Any input appreciated
Sent from my Alcatel 6060C using XDA Labs
Click to expand...
Click to collapse
Just rebooting you will lose temp root access. all you have to do is run the commands again any time you want adb shell temp root.
Please check out my new thread in the idol 5 forum. I have some things and ideas brewing
Magisk working
Thanks to the Mtk Easy Su app I have magisk working without flashing anything. How do ya get to fastboot on this thing? Recovery sucks, factory mode is pointless, so where's the good boot mode 99?
My guide to unlock bootloader and install twrp recovery.
https://androidforums.com/threads/6060c-bootloader-unlock.1327876/
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.
I've used the search function and found nothing for this phone. I've used Google and found nothing about rooting this exact model.
I'm looking for the technique to root this phone and I'm finding nothing. Has anybody rooted and flashed a Custom ROM/custom recovery on this device and how did you do it?
I just got this phone as well, and I have been looking and also have found nothing for this exact variant. I have tried the usual one-click methods to no avail. Is there any development in the works? If you need a test dummy, let me know. I have several other phones to use as spares, so I am not afraid of a soft brick.
Rooting ZTE Blade a7 Prime
I too can be a test dummy to root this phone. Since Visible is such a hands off company you really need your phone to be rooted to do things for yourself. Currently for some reason my ZTE BLADE A7 Prime can’t send or receive calls and their techs are telling me 3 to 5 business days... counting yesterday and today that’s a week! Ridiculous! The APN settings look off compared to my wife’s phone but you can’t edit the settings.
ZTE Blade prime A7 Visible
I've been having the exact same problem with making and receiving calls also with losing service(for the service prob. Found great n easy solution- till find permanent one-**go to airplane mode in settings turn it on for 30secs to a minute then turn airplane mode back off TAKES SIGNAL FROM 0-4 BARS EVERYTIME AND I CAN GET/MAKE CALLS INSTANTLY ETC AGAIN ?)
Data saver seems to work for resetting connection as well. I too would be interested in rooting. I kinda like the phone, but it does have its issues.
First glance at unlocking bootloader
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Has anybody tried this?
https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I don't own this phone (yet), so I can't give it a shot myself.
I'm not very familiar with mediatek processors in general, but that looks rather promising with some restrictions... If I have time over the weekend, I'll give that a whirl and report back whether it works or bricks my device
seems lke ts gonna be a long process before were able to fiddle with roms but im atleast glad this is close to stock android.
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
Ditto here too. Couldn't get it working at first. Turned out I miss read the instructions and put all files in the init.d folder instead od the two files in the bin folder. Then your tip on using the 32bit binary got it working. Thanks.
Anybody figured out a way to change build.prop to make it stick after reboot? I am trying to enable APN editing by modifying /system/build.prop, but whenever I reboot I lose the changes.
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
wunderdrug said:
/system and the root filesystem are mounted as a kind of RAM Disk. You would have to modify the actual image files (varies depending on partition scheme) and reflash to make things stick. Now, to my knowledge, doing so would require an unlocked bootloader, which currently is not possible with this phone.
Click to expand...
Click to collapse
Looks like we can not add an APN even with root then? It's a bummer.
sasuke33 said:
I just received the phone today. I was excited to see that I could get into developer mode and move the OEM Unlocking icon to allow bootloader unlock... Unfortunately, that's where the excitement ended. The typical fastboot oem unlock and fastboot flashing unlock yielded no results. I then did some research and it would seem MediaTek only implements two oem commands, and unlock is not one of them...
"The bootloader may implement additional, manufacturer-specific commands. These do not follow the usual protocol command format, and they cannot have a payload. Some manufacturers implement a lot of OEM commands, as can be seen here. MediaTek just implements two: fastboot oem p2u on and fastboot oem p2u off, these enable or disable the redirection of Linux kernel messages to the UART."
Will tinker with it some more later since I'm limited with time. Hope someone figures out how to unlock the bootloader and go from there.
Click to expand...
Click to collapse
They removed the fastboot command to unlock the bootloader. I found it out by comparing the similar ZTE Blade 10 and Blade 10 Prime. The Blade 10 non-prime has the unlock command and it works whereas the prime version has the command removed but funnily enough the lock command is still there but is useless. I then looked at the bootloader for the a7 prime and same thing the unlock command is removed from the bootloader. So there isn't much hope for it unless a bypass can be found.
virx14 said:
I can confirm that mtk-su R20 downloaded from https://forum.xda-developers.com/hd...xperimental-software-root-hd-8-hd-10-t3904595 gets you root prompt. Use 32-bit binary (arm).
Edit: I can also confirm that the process in https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434 works and root survives the reboots.
Click to expand...
Click to collapse
+1 to another confirmation that the above works. Root is available, but there are limitations. I cannot install many of the modules from magisk, but this is still a great start. Thanks for the links :good:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
ultrasoul said:
I was able to add new APN easily to make it work on AT&T 4G LTE data network. Are you saying any reboot of phone will make the newly added APN disappear?
Click to expand...
Click to collapse
I was also able to add and APN by just clicking on the "+" icon on the top-right corner of the APN configuration screen. When I inserted by MINT SIM Card (T-Mobile MVNO) there were not default populated APNs, but was able to get everything to work after adding an APN -- even after rebooting.
Big Tip: After entering the APN data and before leaving the data entry screen, make sure that you save the APN or it will not be persisted. Click on the "three dots" menu on the top-right corner and hit the Save menu item.
---------- Post added at 05:49 AM ---------- Previous post was at 05:39 AM ----------
AmazerG said:
I installed the magisk, however, it seems no root permission when I installed Titanium to remove stock apps, it never get root permission.
Click to expand...
Click to collapse
After studying the process a bit, I've come to conclude that this isn't really permanent root. All this does is the equivalent of running a script to gain temporary root after after reboot. This is done very late in the boot process, if you can even call it a part of the boot process since it's really just a user-space application auto-starting.
The modules are probably trying to be instantiated well before the root is made available through the pseudo "init.d" scripts.
It's still nice to have root access using this technique, but its usability is pretty limited. For example, I can't even get AFWall+ to start up, even if I configure it with a startup delay (hoping that it kicks in after temporary root).
So what are the odds we can make this a permanent root using a firehose file and QPST/QFIL? Similar to the Visible R2 phone?
I have turned on USB debugging in dev. options.
I believe it is possible to root android TV with Magisk and with or without a custom recovery, depending on the method. Please see the tutorials linked below for reference:
On my PC connected to the android TV using ADB appcontrol, I can type: adb reboot recovery or adb reboot bootloader (although I am not sure which one to use, as I am unsure on what is the best method to root my android TV simply and easily. I do not want to lose my data and I believe that is what happens when you unlock bootloader, but not if you do via custom recovery method). No.1 is the tutorial I am trying to follow, as well as secondary tutorials if the first one does not work (and if I am struggling with doing custom recovery);
2b (to be done before commencing onto no.2):
(if I am really struggling and all else fails, but I honestly think this tutorial isn't that great, as there some things like finding the firmware for the android TV I am REALLY struggling to find!! I know it's version though - it is 9.0):