Database Develop

[GUIDE] How to get root on the 10.1v

BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.

Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad

FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System

Awesome news! Thanks to everyone who worked on this - I can't wait!

Great, great job you guys! This thing needs root so it can grow

Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App

Thank you guys, it's working great on my 10.1v

I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??

This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition

Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..

gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox

bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..

gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?

Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!

black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.

seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot

Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .

Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge

Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.

I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App

Retail 3.1 CWM Recovery, Root & full back up!

This will only work for unlocked tablets. If you get the 0x4 error then you have a locked tablet. I am trying to get my hands on a locked tablet. I will know more once I have one to test on but it sounds like we need the secur key.
http://androidroot.mobi/tf-secure-boot-key/
Credit for CWM goes to pershoot. So thank him for the custom i/o recovery. I used smaskell stock i/o recovery dump so thank him as well.

Read the whole thing before starting!
Mirror 1
Mirror 2
Section 1: cmd prompt setup
1: Download files
2: Extract nvflash folder to c:\
3: Open c:\nvflash then right click in side c:\nvflash folder and select create shortcut
4: Type cmd then enter enter
5: Right click cmd.exe & start cmd.exe as admin
6: type cd c:\nvflash then hit enter
7: You should be at c:\nvflash in the cmd prompt now
Section 2: Putting tablet in nvflash ADX mode
1: Turn tablet off
2: Unplug the tablet from pc
3: Hold vol up(right vol button) then hold power button at the same time
4: Keep holding them for 15 secs
5: The screen will stay black the whole time
6: After 15 sec let go of the buttons and plug the tab in to your pc
7: Open device manager and look for APX Device listed with an error
8: Right click on the APX device
9: Select 'Update driver software'
10: Select 'Browse my computer...'
11: Select 'Let me pick...'
12: Select 'Have disk'
13: Browse to c:\nvflash\usbpcdriver and make sure use sub folders is checked
14: Select NVIDIA USB Boot-recovery driver for mobile devices
15: Accept any warnings, including the big red alert (you may need to disable UAC)
16: Now in Device Manager under USB Controllers you should have an NVIDIA USB Boot-recovery driver for mobile devices
17:Run this command and you should get a black screen with white text at the top left. If you do not get this screen you need to restart at Section 2 step 1.
nvflash --bl bootloader.bin --go
Section 3: Back up recovery (optional)
1: I included stock recovery in the files but if you want to backup recovery then follow this step.
nvflash --resume --read 8 part8.img
Section 4: Installing recovery-cwm_4.0.0.4-sam-tab-10.1 custom recovery
nvflash --resume --download 8 recovery-cwm_4.0.0.4-sam-tab-10.1.img
Section 5: CWM Android Backup then Install Root
You should have custom recovery now
MAKE SURE TO DO A BACKUP IN CWM BEFORE DOING ANYTHING ELSE!!!!
Now install root for i/o tablet (I use pershoot's root & tools)
[Tools] – SU/BusyBox/Misc – Galaxy Tab 10.1 by pershoot (Update: 6/18/11)
or
[GUIDE] Rooting the 10.1 Tab

nvflash commands
http://developer.nvidia.com/tegra/forum/nvflash-man-page-or-command-line-switches
partition table
2 BCT 
3 PT 
4 EBT 
5 EB2 
6 GP1 
7 EFS 
8 SOS<----Recovery!!!!
9 LNX 
10 APP 
11 CAC 
12 MSC 
13 MDM 
14 UDA 
15 OTA 
16 HID 
17 GPT

thanks.thanks.thanks for the efforts.
Sent from my SHW-M110S using XDA App

This is great news, I was getting worried that the retail version wasn't getting much attention here.
is this a permanent root? or I can unroot it if I want.

Akarim47 said:
This is great news, I was getting worried that the retail version wasn't getting much attention here.
is this a permanent root? or I can unroot it if I want.
Click to expand...
Click to collapse
You can unroot.

quick question. what about those with locked bootloaders? only some tabs came with unlocked bootloaders

This is so exciting
Thank you for your work... can't wait to root!

to enter APX (nvflash) mode on IO:
press power + vol up.

Is there any way I/we get a link to the necessary files? I'm willing to give everything a shot on a 16Gb Retail 10.1 with a locked bootloader.

xavierdylan said:
quick question. what about those with locked bootloaders? only some tabs came with unlocked bootloaders
Click to expand...
Click to collapse
I don't think it matters. This is a nvidia development recovery tool. From the research I did it sounds like it bypasses it. I may be wrong but I cant test since my tab had the unlock button. It wont hurt anything if it does not work.

nagmier said:
Is there any way I/we get a link to the necessary files? I'm willing to give everything a shot on a 16Gb Retail 10.1 with a locked bootloader.
Click to expand...
Click to collapse
Files are up on 2nd post

here is bootloader from IO tab:
http://droidbasement.com/galaxy/sys-backup/bootloader.zip

Omg. U guys absolutely rock. Huge acomplishment. As soon as I get home this is getting tested.

OMG I LOVE YOU... i was working with pershot on a similar method you beat me to it. excellent thankyou. trying now. if it works STICKY!!

Good Day,,, after attempting to flash the the stock i/o how long is it supposed to sit on the NvFlash started?
all I did was run the sync and then tried to flash the i/0 recovery.... I haven't tried to reset the the nvflash on the device as yet.
Nevermind I think I am good now.

msm903 said:
Good Day,,, after attempting to flash the the stock i/o how long is it supposed to sit on the NvFlash started?
all I did was run the sync and then tried to flash the i/0 recovery.... I haven't tried to reset the the nvflash on the device as yet.
Click to expand...
Click to collapse
it will sit there at that screen. it is waiting for your commands.

i've let it sit for 5 min, and nothing yet. i did try and reset and restart. so going through it again. shouldn't take long should it? since it's only a 5MB file.

pershoot said:
it will sit there at that screen. it is waiting for your commands.
Click to expand...
Click to collapse
what would be the command? i can't type in anything after it says nvflash started.
if i reset apx mode i get "uid read failed"
tried again after that.

madsquabbles said:
what would be the command? i can't type in anything after it says nvflash started.
Click to expand...
Click to collapse
re-read the tutorial.
it shows all on what to do/type for this particular procedure.

[Streak10][Recovery]Team Win Recovery 2.2.2.1

Setting up NVflash:
Download:
NVflash.zip
usbNvidiaBootdriver.zip
S10 568-2 bootloader.bin
Extract NVflash.zip, and place bootloader.bin into a directory
Place Device into APX mode:
Connect device to pc
Press the pinhole button until screen goes off
Hold down pinhole button AND power button until windows gives connection cue
Extract usbNvidiaBootdriver.zip and install driver
Finished
Click to expand...
Click to collapse
Requirements:
Ability to enter APX mode
Basic understanding of the command line
Windows XP or newer
Click to expand...
Click to collapse
Install Instructions:
Download: Team Win Recovery recovery.img
Place device into APX mode
Open command prompt and navigate to directory where NVflash is extracted
In the prompt type: "nvflash --bl <name of bootloader.bin> --go" to prepare device
OPTIONAL: Back up the current recovery: "nvflash -r --read 6 recoverybackup.img"
Install the new recovery: "nvflash -r --download 6 <name of recovery>.img"
Unplug USB cable to reboot
Finished
Click to expand...
Click to collapse
What works:
Nandroids
Update zip flashing
Fac resetting
What doesnt work:
USB mounting (not fixable)
Click to expand...
Click to collapse
Notice:
USB mounting does not work, it cannot be fixed without kernel mods
Click to expand...
Click to collapse
Changelog:
Sep 08 2012: Updated to 2.2.2.1
Aug 07 2012: Updated to 2.2.1.4 - updated formatting code
Jul 21 2012: Initial release
Click to expand...
Click to collapse
2char

Not a streak10er... but wondering if you have a typo in your first line of op?
Sent from my Galaxy Nexus using xda premium

I am not quite sure if S10 is different but I flash my twrp from fastboot
Sent from my Nexus 7 using Tapatalk 2

The S10 doesnt have a working fastboot (you can only enter fastboot by doing adb reboot-bootloader, there is no valid button combination for it, it also does not respond to fastboot devices while in fastboot mode)

So you can't do volume down and power?
Sent from my Nexus 7 using Tapatalk 2

The only mappings I'm aware of are:
Hard reboot + Power + VolUp = rec
Hard reboot + Power + reset pin = apx
The only way I can enter fastboot is by "adb reboot-bootloader"
and it wants to enter nvfastboot mode, unlike every other device.
It might be possible to force it to accept fastboot commands, but there's no point if you can only enter it from a working rom

Updated to 2.2.1.4, includes updated formatting code from CWM/S7 6.0.1.1

Updated to 2.2.2.1

Root Zenfone 4 . ANDROID LOLLIPOP

Download:
1. Intel USB Driver ( HERE )
2. CWM ( HERE )
3. SuperSU ( HERE )
Instruction
1. Download file and install intel USB Driver ( If you don't have it )
2. Extract CWM
3. Copy SuperSU to SDCard
4. Turn off Zenfone 4
5. Go to Droidboot ( Power + Volume Up + Volume Down )
6. Connect Zenfone 4 to PC
7. In CWM folder open CMD.CMD ( Shift+right Click --> Open Command )
8. Type fastboot flash update update.zip
9. Choose update from SDCard
10. Choose SuperSU and YES .... Wait until finish
11. Reboot and ROOTED

JustinSang said:
Download:
1. Intel USB Driver ( HERE )
2. CWM ( HERE )
3. SuperSU ( HERE )
Instruction
1. Download file and install intel USB Driver ( If you don't have it )
2. Extract CWM
3. Copy SuperSU to SDCard
4. Turn off Zenfone 4
5. Go to Droidboot ( Power + Volume Up + Volume Down )
6. Connect Zenfone 4 to PC
7. In CWM folder open CMD.CMD ( Shift+right Click --> Open Command )
8. Type fastboot flash update update.zip
9. Choose update from SDCard
10. Choose SuperSU and YES .... Wait until finish
11. Reboot and ROOTED
Click to expand...
Click to collapse
Does not works
But I tried Temporary CWM Session for Intel Device method and it worked fine with T2 option

arun483 said:
Does not works
But I tried Temporary CWM Session for Intel Device method and it worked fine with T2 option
Click to expand...
Click to collapse
Can you explain your method?

Subhajitdas298 said:
Can you explain your method?
Click to expand...
Click to collapse
It's 3 years old post, I don't even own the device anymore ??

arun483 said:
It's 3 years old post, I don't even own the device anymore
Click to expand...
Click to collapse
Need the method. Can you find it? It would be great help.

Subhajitdas298 said:
Need the method. Can you find it? It would be great help.
Click to expand...
Click to collapse
Ok so the method was to unlock bootloader, flash twrp and flash magisk zip.
The other way was using temporary cwm for intel devices using T2 option. What this does is that it gives you a temporary CWM session which can be used to flash magisk zip.
Edit: You can find most of the resources here https://forum.xda-developers.com/ze...12-1-cyanogenmod-12-1-asus-zenfone-4-t3249637

arun483 said:
Ok so the method was to unlock bootloader, flash twrp and flash magisk zip.
The other way was using temporary cwm for intel devices using T2 option. What this does is that it gives you a temporary CWM session which can be used to flash magisk zip.
Edit: You can find most of the resources here https://forum.xda-developers.com/ze...12-1-cyanogenmod-12-1-asus-zenfone-4-t3249637
Click to expand...
Click to collapse
Can you give exact files?
I need the proper recovery file.
Thanks in advance.

Subhajitdas298 said:
Can you give exact files?
I need the proper recovery file.
Thanks in advance.
Click to expand...
Click to collapse
The link I mentioned has the proper resources including bootloader unlocker and TWRP recovery img
Edit: Full Method
1. Download bootloader unlocker from http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/Unlock_Tool_A400CG.zip
2. Extract Unlock Bootloader Tool > Install apk> Unlock
3. Install Intel Driver from http://d-h.st/ZN2 and turn on USB Debugging mode.
4. Copy fix-twrp_zf4_recovery.img to adb folder.
ADB can be downloaded from http://d-h.st/ZN2
TWRP can be downloaded from https://drive.google.com/file/d/0B_qQULhmnkV1Y092TGRsekJyVkE/view?usp=drive_web
5. Turn off your Zenfone 4 and boot into Droidboot (Power + Volume Up).
7. Open adb terminal and enter following command
- fastboot flash recovery fix-twrp_zf4_recovery.img
8. Boot into recovery and flash Magisk or SuperSU whichever you prefer.
** I take no responsibility if your device gets bricked. I used this device over 3 years ago and have only fragments of memory of how I rooted it.
** Perform steps given above at your own risk

arun483 said:
The link I mentioned has the proper resources including bootloader unlocker and TWRP recovery img
Edit: Full Method
1. Download bootloader unlocker from http://dlcdnet.asus.com/pub/ASUS/ZenFone/A400CG/Unlock_Tool_A400CG.zip
2. Extract Unlock Bootloader Tool > Install apk> Unlock
3. Install Intel Driver from http://d-h.st/ZN2 and turn on USB Debugging mode.
4. Copy fix-twrp_zf4_recovery.img to adb folder.
ADB can be downloaded from http://d-h.st/ZN2
TWRP can be downloaded from https://drive.google.com/file/d/0B_qQULhmnkV1Y092TGRsekJyVkE/view?usp=drive_web
5. Turn off your Zenfone 4 and boot into Droidboot (Power + Volume Up).
7. Open adb terminal and enter following command
- fastboot flash recovery fix-twrp_zf4_recovery.img
8. Boot into recovery and flash Magisk or SuperSU whichever you prefer.
** I take no responsibility if your device gets bricked. I used this device over 3 years ago and have only fragments of memory of how I rooted it.
** Perform steps given above at your own risk
Click to expand...
Click to collapse
How to boot into recovery?
Also recovery link does not work.

Subhajitdas298 said:
How to boot into recovery?
Also recovery link does not work.
Click to expand...
Click to collapse
Well I'm sorry then I can not help you. Try following this method https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 with T2 option

arun483 said:
Well I'm sorry then I can not help you. Try following this method https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 with T2 option
Click to expand...
Click to collapse
Shortcut for reboot into recovery?
adb reboot recovery is not working.
What is T2 option?

Subhajitdas298 said:
Shortcut for reboot into recovery?
adb reboot recovery is not working.
What is T2 option?
Click to expand...
Click to collapse
Shutdown >> Press Power and Volume Up button together
I think that was the shortcut not sure if it's for bootloader or recovery

arun483 said:
Shutdown >> Press Power and Volume Up button together
I think that was the shortcut not sure if it's for bootloader or recovery
Click to expand...
Click to collapse
No it does not work.
Droidboot is only thing. Shortcut : Vol UP + Power.
Thanks for the temporary recovery method though. Thanks a lot.

axon7tool: Flash and backup boot/recovery using EDL mode

Note: This is an inherently dangerous tool. I have made every effort to make it as safe as possible. But there is always a risk of bricking your device. You assume all responsibility for the consequences. Proceed with caution.
Warning: To avoid bricking your device, NEVER write both boot and recovery in one session. ALWAYS write one partition, test, then write the other. This is why the tool will only write one partition at a time.
Warning: There are versions of TWRP for the Axon 7 that are known to erase your IMEI when doing a restore. Do NOT do a TWRP restore unless your are SURE that you have a good version of TWRP!
This tool will allow you to:
Backup your boot and recovery partitions.
Flash a boot or recovery image (including the signed TWRP image).
See following posts for operating system specific setup instructions.
Once your setup is complete, enter EDL mode:
1. Power off phone.
2. Hold both volume buttons.
3. Plug phone into computer.
4. For G models, you must "adb reboot edl" (see other threads).
Usage:
axon7tool <mode> <partition(s)>
Note: The tool name will vary depending on your operating system.
<mode> is -r for read, -w for write.
For read mode, <partition> is one or more of gpt, boot, recovery. Files will be created as <partition>-backup.bin
For write mode, <partition> is boot or recovery. File will be read from <partition>.bin
Examples:
To backup everything on Linux:
./axon7tool-1.5-linux -r gpt boot recovery
To write recovery on Win64:
Place file as recovery.bin
axon7tool-1.5-win64 -w recovery
Links to axon7tool:
axon7tool-1.5-linux (main)
axon7tool-1.5-linux (alternate)
axon7tool-1.5-win64.exe (main)
axon7tool-1.5-win64.exe (alternate)
Link to signed TWRP removed.
FAQ:
Q: Can you provide a signed boot image with root?
A: No. I do not have the ZTE signing key, and tenfar's images are not current.
Q: Can I have the source code for the tool?
A: No.
Q: Can you provide the programmer?
A: No.
Q: Do you accept donations?
A: No, all work is provided freely for community use.

Setup instructions for Linux:
1. Ensure your login user is in the "plugdev" group.
$ id
You should see plugdev in the list. If not, add yourself to the group and logout/login to take effect.
2. Ensure your udev rules are setup.
Create a file eg. /etc/udev/rules.d/qcom.rules that contains:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="05c6", GROUP="plugdev"
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", GROUP="plugdev"
3. All done!

Setup instructions for Win64:
1. Download zadig from http://zadig.akeo.ie/
2. Put device in EDL mode.
3. Run zadig. Select the WinUSB driver. If you have installed the Qualcomm EDL driver, you may need to tick "Edit" and find the device in the list.
4. All done!

Reserved for Mac instructions.

Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1- No this doesn't work like backing up with TWRP, This tool is more powerful than Custom Recovery (TWRP), and you should be very careful on how to use it.
Like @tennear mention about try first by using -r (read) then just flash the sign TWRP.
I personally recommend just flash TWRP and DON'T mess with Boot image.
2- the Sign TWRP is not provided by ZTE, ZTE will NEVER release a Custom Recovery for us users.

kgptzac said:
Questions:
1) Does the backup of boot and recovery partitions work like backing up through TWRP (if the recovery is already flashed to TWRP)
2) The signed TWRP image is by... ZTE?
Click to expand...
Click to collapse
1. The tool writes the raw partitions to your PC. Whatever you have in the partition is written out, whether it is stock recovery or TWRP or whatever.
2. The signed TWRP image is copied from the zip that tenfar provided in his post. I did not create it, and I cannot create signed images.

Forgive me my noobiness, but here’s a step-by-step-instruction list. Am I thinking right? I want to minimise the risk when I try your tool tomorrow.
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan

@Controllerboy close, but not quite. I'll attempt to provide detailed feedback on your step by step list tomorrow. Time for sleep now.

Controllerboy said:
Step 1: Enable Developer options in phone by tapping the build number
Step 2: Enable OEM Unlock in phone (is this needed?)
Step 3: Enable debugging (for adb)
Click to expand...
Click to collapse
None of these steps should be necessary.
Controllerboy said:
Step 4: Connect phone to PC
Step 5: Download Zadig
Step 6: Install Zadig
Click to expand...
Click to collapse
I believe you just run zadig, I don't remember an installer.
Controllerboy said:
Step 7: Open command in the folder in which you downloaded adb.exe (and the rest of the files that come with it) (Richt click while holding shift to get the option to open CMD in a folder)
Step 8: Enter the command “Adb Devices” to reassure your device is detected
Step 9: Enter the command “Adb reboot edl” to reboot the phone to EDL mode
Step 10: After phone has rebooted to EDL mode, run Zadig, select WInUSB driver and install it for your device
Step 11: Rename “axon7tool-1.5-win64.exe” to “axon7tool.exe”
Click to expand...
Click to collapse
Renaming the tool is optional.
Controllerboy said:
Step 12: Download “axon7-2017u-twrp-signed.img” to the folder where axon7tool.exe is located
Step 13: Open command in the folder in which you have downloaded axon7tool-1.5-win64.exe (renamed to axon7tool.exe)
Step 14: Enter command “axon7tool -r gpt”.
Step 15: Enter command “axon7tool -r boot”
Step 16: Enter command “axon7tool -r recovery”
Click to expand...
Click to collapse
The tool is "one shot". You can read any combination of gpt, boot, and recovery in one session, then the tool will restart the phone.
Controllerboy said:
Step 17: Verify if the tool has created “gpt-backup.bin”, “boot-backup.bin”, “recovery-backup.bin”.
Step 18 (unsure): rename “axon7-2017u-twrp-signed.img” to “recovery.bin” ?
Click to expand...
Click to collapse
Yes, this is correct.
Controllerboy said:
Step 19: enter “axon7tool -w recovery recovery.bin
Step 20: Wait for the command to finish
Click to expand...
Click to collapse
Yes, this is correct. Writing boot or recovery takes about 30 seconds. Then the tool will reboot your phone. Be sure to hold the Vol+Up button to reboot into recovery.
Controllerboy said:
Step 21: Place the .zip file for Z.A.D. Mix7 or CM13 on your SD card via your PC or Axon 7. Also download Gapps.zip of your choice and place on SD card.
Step 22: Boot your Axon 7 to TWRP Recovery by holding the power button simultaneously with volume down (or is it volume up?)
Step 23: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 24: Flash the .zip of your custom ROM of choice in TWRP
Step 25: Flash the .zip of your Google Apps of choice in TWRP
Step 26: Perform a full wipe of Dalvik, Cache and Data in TWRP
Step 27: Reboot your phone, enjoy the custom ROM of your choice.
Click to expand...
Click to collapse
Everything past step 20 is up to you.
Controllerboy said:
Is this the correct procedure?
I’m a bit unsure of step 18. Am I doing it right? Or do you need to unzip that .img somehow to find a recovery.bin file? Or do you need to get that file from somewhere else? Or do you need to rename “axon7-2017u-twrp-signed.zip” to “recovery.img”?
For Z.A.D. MIX7, I suppose you still need to flash a SuperSU version seperately? I heard in CM it's baked-in.
Thanks for the help.
Jan
Click to expand...
Click to collapse
You cannot unzip an img file.
The TWRP image provided is just as tenfar provided for 2017u users. You only need to rename it to recovery.img for using the tool.
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.

Folks who are able to use this new tool/method successfully, please report back with your variant. I can't test this myself, so I'm relying on some verification before I update the newbie guide to point here instead of tenfar's thread (which is outdated and no longer updated as tenfar is now inactive).

tennear said:
<-- SNIP -->
If someone has the 2017g TWRP file, I can upload and link it. The links in the tenfar post have been removed.
Click to expand...
Click to collapse
I found this on the 65th page of Tenfar's thread (http://forum.xda-developers.com/showpost.php?p=69215285&postcount=642)
khaino said:
Step 1: Download the zip file and extract to your local disk. a2017 for Chinese model,and a2017u for US model,a2017g for HK & EU model
a2017u :B20_blunlockedhttp://d-h.st/KaaQ
a2017u B20 http://d-h.st/LqR5 (modified from @rczrider�s backup real stock b20 boot.img)
a2017u B27 http://d-h.st/kRgq
a2017 B06:http://d-h.st/ztXw
a2017 B07:http://d-h.st/VVlf
a2017 B08: http://d-h.st/bT6r
a2017 B09:http://d-h.st/sBjo
a2017 B10:http://d-h.st/cBOE(wifi not working) http://d-h.st/aceq (from official update.zip)
a2017g B02 :http://d-h.st/aPiC
a2017g B03:http://d-h.st/r3Z4
TWRP recovery 3.0.2-2 : http://d-h.st/dgWW
latest tools:http://d-h.st/Ienb with dump function
Click to expand...
Click to collapse
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...

Controllerboy said:
So I just use the file from http://d-h.st/r3Z4 (axon7root-a2017g-b03.zip), unzip and rename the .img file to recovery.img?
The issue here is that the hosting used is so crappy I can't even download the file...
Click to expand...
Click to collapse
That is correct.
d-h.st seems to be down for the past few days. I guess it will come back at some point, and you can download the zip file to extract the recovery image. Or maybe someone else has a copy of it...

@tennear
As far as u know TWRP is the same for every A7, sign or not.

DrakenFX said:
@tennear
As far as u know TWRP is the same for every A7, sign or not.
Click to expand...
Click to collapse
Unpacking the TWRP image for A2017U, it says:
ro.product.model=A2017U
So this recovery seems to be specific to A2017U.
But unpacking the TWRP image for A2017 (China), it says:
ro.product.model=ZTE A2017U
Hmm, different but still A2017U.
I don't have the TWRP image for A2017G (yet), so I can't tell what it says. But given the above, and that the G and U models are almost identical, I am thinking the A2017U image will run on all devices.

tennear said:
Reserved for Mac instructions.
Click to expand...
Click to collapse
So can the Linux tool be used on Mac?

nuserame said:
So can the Linux tool be used on Mac?
Click to expand...
Click to collapse
No. I have not built the tool on Mac yet. I will try to do that soon.

I wouldnt say I was a newbie but how do you get the file to run. Even with Antivrus off, the computer just wont run it.
Thank you for the time and support.

The .exe file isn't meant to be ran on it's own. Double-clicking it won't do a thing. You need to use cmd (command) to execute commands to the file. If you look at my post on the first page of this thread, you'll get an idea of how the process works. But please don't follow my post as of now, since it's not detailed nor 100% correct yet.
It's my intention to try my luck tomorrow and I'll post a detailed and 100% correct step-by-step-process.

Excuse me for my ignorance, but how does this tool differ from tenfars tool? Beside not being able to write two partitions at the same time that is.
TIA,
Cheerz,
/Cacti