Related
Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.
Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM
It worked for me
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer
Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot
Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d
BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.
+1 for flashing boot.img worked perfect after I did that.
I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.
This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img
Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.
gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.
Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
AnthonyAldrete said:
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
Click to expand...
Click to collapse
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
funny i just did this exact same thing like you instructed and was about to reply to this post saying i resolved it hahah. Thanks anyways though =), i dont understand why i was getting that though because i had every file in the same place
No worries glad you got it working
qnc said:
No worries glad you got it working
Click to expand...
Click to collapse
Also found out that you Dont do the ./fastboot erase userdate command because it puts 0s in and leaves the phone unbootable which was my root cause for my phone being stuck. Instead, after flashing the boot.IMG you do the ./fastboot partition userdata instead and it will do a factory reset and when booting it will not encrypt the phone.
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
And I was having the same issues executing the flash all command too until I opened the command in a text editor and for every command put the "./" in front and was able to execute it but this is the first time I've gotten an error. My nexus5 worked with this command no problem
worked for me but still could not decrypt
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
so all of this worked for me and its back up and running, but my phone still says that its encrypted
Hello, my watch R has 5.1.1 (LDZ22D) stock ROM and it has some problems. I tried factory reset, still not ok. I would like to try flashing again the stock ROM. I have found this thread: http://forum.xda-developers.com/g-watch-r/development/stock-boot-recovery-g-watch-r-t2956964 , i downloaded boot.img, recovery.img and system.img, checked SHA1 but i don't know which version should i try? 5.1.1 (LDZ22D), 5.1.1 (LCA44B), 5.0.2: ??? Are there limitations for downgrade / upgrade ?
And as a guide to flashing...
1. i start watch, swype 11 to 5, so now in fastboot mode i connect to PC, the PC detect the watch as what ?
2. adb devices and if watch is detected i continue.
3. fastboot flash boot boot.img
4. fastboot flash recovery recovery.img
5. fastboot flash system system.img
6. restart
is that ok ?
How long does it take to flash each of those imgs ?
thank you
intersectRaven said:
Notes/FAQ:
1.) I re-mkbootimg-ed them since I'll be uploading 2 x 20+MB files if I didn't. Still has the same SHA1 checksums as the ones being checked by stock ROM so it's safe to flash.
2.) If you're confused on how to download click on the box marked in this pic.
3.) The commands for flashing are as follows:
Boot: fastboot flash boot boot.img
Recovery: fastboot flash recovery recovery.img
System: fastboot flash system system.img
*replace boot.img, recovery.img and system.img with their respective filenames
**how to obtain the fastboot executables and drivers are explained in a separate thread
4.) The system.img provided above are stock and NOT ROOTED. If you want to go completely stock, just flash ALL the 5.0.1 images above.
*only for 5.0.1 since I didn't make a system image for 4.4W.2 or below
Click to expand...
Click to collapse
took that from the link you posted, just conect the watch to the dock while in fastboot mode, search for 15 second adb/fastboot installer, after installing that and the computer detects your watch just follow those steps using cmd and navigating to the directory where the files are at first, remember to install fastboot and adb system wide on the 15 second adb installer
when in fastboot mode the watch is not detected:
C:\Users\user>adb devices
List of devices attached
when i chose "recovery" in fastboot mode (android robot on back with door open and red exclamation mark) i get:
C:\Users\user>adb devices
List of devices attached
410KCHserialnr888 sideload
but the watch says he waits "adb sideload <filename>"
what i am doing wrong ? something else had to be done ?
thank you
you can use adb to boot watch on bootloader, but it is not needed since you can boot into fastboot already, problem is the watch is not detected on fastboot mode, try finding some drivers or something, what i usually do is download cydia impactor and select usb then let it do the driver stuff for me, quote me next time so i can get notified when you respond
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
IMPORTANT NOTE ABOUT ROOTING:
After flashing TWRP 3.0.2, use the SuperSU 2.46 flashable zip, do NOT use latest version or will result in a bootloop. Good Luck and have fun with rooting.
REQUIREMENTS
1- Unlocked Bootloader (search on google if you dont know how to unlock)
2- Drivers and Adb/Fastboot commands knowledge
--------------------------------------------------------------------------------------------------------------------------------
New TWRP bugfix update! Now you can flash stock rom on TWRP without bricking! Download Page updated!
Bugs:
1- adb shell command needs to be sent before system partition is mounted or it will give an error, after doing adb shell you can mount system and do all the modifications you need.
2- You cant flash any img on twrp it gives an error, im trying to fix.
3- Backups do work, but everytime twrp restarts, the serial number folder seems to change (which means that on /TWRP/BACKUPS/serialnumber/backupsinside/ changes every reboot so you have to go get the backup inside the old serialnumber folder and put on the new serialnumber folder).
Im leaving an unsecured boot image because system does not boot android if anything seems changed. So please if system does not boot after flashing twrp/rooting, flash the unsecured boot img on fastboot
Steps to Install TWRP and root
1. Download and extrct the files: https : // drive. google . com/file/d/0BxzG5iupOOSKNTdlRC1Wd0VmTlk/view
2. Power off the tablet.
3. Enter fastboot mode by pressing the power button while holding down Vol -
4. Open up command prompt and navigate to the directory where fastboot.exe is located.
5. Pass the following commands:
fastboot flash boot unsecuredboot.img
fastboot flash recovery TWRP.img
6. Reboot into recovery (TWRP) and install SuperSU v2.46.zip ---
Continuation 6. Step by Step of Step 6 since people seem to have been running into issues with it:
After rebooting to TWRP and having SuperSU.zip in the tablet storage. Go on Install tab and press the supersu file and install/flash it then reboot the device.