Recovering data from factory reset Axon 7 - ZTE Axon 7 Questions & Answers

Hey guys,
So about 3 weeks ago my Axon 7 reset itself in my pocket. This was days after I had updated to Android N. I have not used the phone since then as I have combing the internet for any possible way to recover the data from it. It would be nice if you can provide a solution that does not require rooting.
However, most solutions I have looked into need root access in some form or fashion, so I am not entirely averse to rooting. Since I am currently running Android N, I have been unable to find a way to root it without unlocking the bootloader (or root it at all). If the bootloader MUST be unlocked for me to be able to recover my data then could you please tell me a way to relock it afterwords. Also, I would prefer to return the phone to an unrooted condition after attempting data recovery since certain apps (such as Pokemon Go) will not run on a rooted phone.
The best solution I have found so far is that I root the phone (preferably without unlocking bootloader) and then dump an image of all the partitions for a recovery software such as Recuva, Testdisk, or Photorec to scan through. I am not sure if this requires flashing TWRP (I am an extreme newbie to this). I could potentially also just root the phone then try to run an android recovery software such as Asoftech. The last solution I have found is getting the phone to be recognized as a mapped drive for Photorec to scan successfully.
Presumably all of these methods NEED the phone to be rooted. If you have any ideas where these solutions can be implemented without rooting please post.
Before you ask, I did not have Google Photos sync on and had not backed up the data from it. Please only give pertinent solutions and not snarky remarks about how I should have been smarter and made backups and am now screwed. I realize that, but am hoping that maybe someone on here can help.

https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en
There's at least 3 guides on how to root the phone.

bornlivedie said:
https://play.google.com/store/apps/details?id=com.defianttech.diskdigger&hl=en
There's at least 3 guides on how to root the phone.
Click to expand...
Click to collapse
Sorry for my seeming ignorance. I'm quite the newbie to this. Can you please tell me if the process would be the same for Nougat B15? Because the following link gives instructions for rooting without unlocking bootloader, but does not appear to have the .zip file for the B15 software version.
Link: https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
If yes, can you please link me to these guides?
Thanks for the disk digger suggestion. I will be sure to try that.

tupurl said:
Sorry for my seeming ignorance. I'm quite the newbie to this. Can you please tell me if the process would be the same for Nougat B15? Because the following link gives instructions for rooting without unlocking bootloader, but does not appear to have the .zip file for the B15 software version.
Link: https://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
If yes, can you please link me to these guides?
Thanks for the disk digger suggestion. I will be sure to try that.
Click to expand...
Click to collapse
It's the same, yes.
I used tennear's (not to be confused with tenfar) tool to flash signed TWRP:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
and then unlock the bootloader with this:
https://www.androidfilehost.com/?fid=24723757092307343
Here are the required drivers for your computer:
http://www.filedropper.com/qualcommqusbbulkdrivers
The recovery must be named recovery.bin and not .img or any other name/extension
And the command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery

bornlivedie said:
It's the same, yes.
I used tennear's (not to be confused with tenfar) tool to flash signed TWRP:
https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254
and then unlock the bootloader with this:
https://www.androidfilehost.com/?fid=24723757092307343
Here are the required drivers for your computer:
http://www.filedropper.com/qualcommqusbbulkdrivers
The recovery must be named recovery.bin and not .img or any other name/extension
And the command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Click to expand...
Click to collapse
Thank you so much for this detailed explanation! One last question, is it possible to relock the bootloader after this? If not, does this work without unlocking the bootloader? And how difficult is it to unroot the phone? Again, I'm really sorry for pestering you with this.

tupurl said:
Thank you so much for this detailed explanation! One last question, is it possible to relock the bootloader after this? If not, does this work without unlocking the bootloader? And how difficult is it to unroot the phone? Again, I'm really sorry for pestering you with this.
Click to expand...
Click to collapse
Sorry, In fact, you can actually root without unlocking your bootloader, so don't flash that zip.
Just flash SuperSU 2.79
And yes, you can relock, but you must be completely stock before doing so.

bornlivedie said:
Sorry, In fact, you can actually root without unlocking your bootloader, so don't flash that zip.
Just flash SuperSU 2.79
And yes, you can relock, but you must be completely stock before doing so.
Click to expand...
Click to collapse
So in summary:
Download tennear's axon7tool and use it to flash SuperSU 2.79.
Then do the following and I should be able to perform an image dump?
Name file recovery.bin and not .img or any other name/extension
And use this command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Question: So in a comment in his guide, tennear mentions that the tool writes out the raw partition when taking the backups. So, theoretically, can I just use the tool to write out an image of the system partition for a program like TestDisk to scan?
(TestDisk and PhotoRec are programs that can scan through mapped drives or partition images in order to recover data from them)
If this is not possible, is flashing SuperSU enough to give me the permissions to perform an image dump without unlocking bootloader? And to go back to unrooted condition do I just unflash SuperSU?
(Sorry for all these questions. I really appreciate your help. You're a real lifesaver since I've been wrestling with trying to recover data from the phone for almost a month.)

tupurl said:
So in summary:
Download tennear's axon7tool and use it to flash SuperSU 2.79.
Then do the following and I should be able to perform an image dump?
Name file recovery.bin and not .img or any other name/extension
And use this command to write it:
axon7tool-1.5-win64 -w recovery
I recommend you back up everything before writing the recovery
axon7tool-1.5-win64 -r gpt boot recovery
Question: So in a comment in his guide, tennear mentions that the tool writes out the raw partition when taking the backups. So, theoretically, can I just use the tool to write out an image of the system partition for a program like TestDisk to scan?
(TestDisk and PhotoRec are programs that can scan through mapped drives or partition images in order to recover data from them)
If this is not possible, is flashing SuperSU enough to give me the permissions to perform an image dump without unlocking bootloader? And to go back to unrooted condition do I just unflash SuperSU?
(Sorry for all these questions. I really appreciate your help. You're a real lifesaver since I've been wrestling with trying to recover data from the phone for almost a month.)
Click to expand...
Click to collapse
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.

bornlivedie said:
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.
Click to expand...
Click to collapse
This leaves the bootloader untouched which is awesome. I really appreciate the help.
So, flashing SuperSU 279 gives me the super user privileges I need to perform an image dump of the data partition correct (will be using adb shell for this)? Or qualifies the phone as having root access for software like DiskDiggerPro to be able to scan and recover files from?
Out of curiosity, what exactly is it that the axon7tool does? I got the impression that it can write out raw images of the boot, recovery, and gpt partitions separately and then can be used to flash the signed TWRP. Is this not true? Does it only read those and flash the signed TWRP? And if it can write raw images can it write an image of the data partition? I'd guess not, but wanted to know your thoughts.
I know I said last question like many questions ago, but final question, what is the process to unroot the phone (in case it turns out I can't use certain apps in a rooted condition)? Do I just remove the signed TWRP and SuperSU279?
I really truly appreciate all the help you have provided. You are truly a lifesaver. (There aren't enough thanks that I can give.)

Pretty sure you have to unlock to root but good luck.

bornlivedie said:
No, that tool only flashes recovery, gpt and boot partitions. You can't flash a zip or any other thing, you'll brick your device.
Just use it to flash SIGNED TWRP (I posted you the link) and use TWRP to flash SuperSU 279. If you don't have experience with TWRP I suggest you watch a video on YouTube. It's dead simple.
Flash Signed TWRP
Flash SuperSU using TWRP
Reboot to system, enjoy.
Click to expand...
Click to collapse
So I have managed to successfully flash the SIGNED TWRP but every time I try to flash SuperSU from the zip file you linked TWRP crashes. I read on another post that I should try the SuperSU v2.79 SR3 version but TWRP crashes while trying to install it too. (By crash I mean it freezes while installing and then turns the device off. Upon reboot, the SuperSU app is not present on the phone.)
Is there any way I can successfully flash SuperSU without having to format data or unlock bootloader?
EDIT: I just tried to use adb sideload through TWRP to flash SuperSUv2.79 and in the command window it successfully got to ~75% before it stopped, the phone turned off, and it gave an error of " * failed to read command:" When the I tried the same with SuperSUv2.79-SR3, it got to ~77% before stopping, turning off and giving the same error.
Any ideas why this might be failing and how to fix it?

tupurl said:
So I have managed to successfully flash the SIGNED TWRP but every time I try to flash SuperSU from the zip file you linked TWRP crashes. I read on another post that I should try the SuperSU v2.79 SR3 version but TWRP crashes while trying to install it too. (By crash I mean it freezes while installing and then turns the device off. Upon reboot, the SuperSU app is not present on the phone.)
Is there any way I can successfully flash SuperSU without having to format data or unlock bootloader?
EDIT: I just tried to use adb sideload through TWRP to flash SuperSUv2.79 and in the command window it successfully got to ~75% before it stopped, the phone turned off, and it gave an error of " * failed to read command:" When the I tried the same with SuperSUv2.79-SR3, it got to ~77% before stopping, turning off and giving the same error.
Any ideas why this might be failing and how to fix it?
Click to expand...
Click to collapse
You need to flash tenfars b27 and follow his guide.

lafester said:
You need to flash tenfars b27 and follow his guide.
Click to expand...
Click to collapse
So downgrade to B27 then follow his guide?

tupurl said:
So downgrade to B27 then follow his guide?
Click to expand...
Click to collapse
If you want root without unlock.

Related

How to root 4.4.2 nakasig

Hello! Can somebody help me with the question how can I root this device?
Please?
Try this man, i always use this guide for root and unlock with cwm.
https://m.youtube.com/watch?v=9C_QEYHzoEk
As far as I know there isn't a Exploit for 4.4.2, so you have to unlock the Bootloader at any rate.
If you just want to root, the easyiest way is just to boot the CF-Auto-Root boot image for your device: http://autoroot.chainfire.eu/
If you just want to flash custom roms, theres no need to root your actual ROM. Just flash the TWRP recovery Image via fastboot.
antila said:
Hello! Can somebody help me with the question how can I root this device?
Please?
Click to expand...
Click to collapse
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.
Root does't work
GedBlake said:
Hi, antila...
Straightforward enough, if you know how to use fastboot...
------------------------------------------------
* Unlock the bootloader with fastboot oem unlock
-- BEWARE... THIS WILL FACTORY RESET THE NEXUS 7... and you will loose everything on it. All user installed apps and any files (music, video, pics etc.) will also be lost.
* Fastboot flash a Custom Recovery, such as CWM or TWRP, with fastboot flash recovery recovery.img
-- (where recovery.img is the name of the recovery image file to be fastboot flashed).
* Using that Custom Recovery, flash Chainfire's SuperSU root updater .zip.
* Reboot and you're rooted.
------------------------------------------------
I've written about this procedure in slightly more detail here.
The only thing that's changed since, is Chainfire's SuperSU root package has been updated to v1.86, and which you will find here...
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
If you prefer CWM to TWRP, then the latest CWM recovery can be found here...
http://www.clockworkmod.com/rommanager
(It's important you get the correct recovery for the particular type of Nexus 7 you have.)
For a fuller understanding of fastboot, checkout the 'stickies', particularly this one, which pertains directly to your question. It's a little out of date now... but the basic principles still hold.
This thread is also worth a look.
Good luck rooting your N7... (it's really not that difficult).
Rgrds,
Ged.
Click to expand...
Click to collapse
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.
Once you've got TWRP installed, just download the latest SuperSU (http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip), and flash it through TWRP.
antila said:
Hello! Thank you for your help. I did everything as you wrote. Unlocked bootloader, installed TWRP but for some reason root still don't work. Can you give me a link on SuperSu where I can flash it trough TWRP? Please?
Thank you very much for your help.
Click to expand...
Click to collapse
Hi, antila...
If you've unlocked the bootloader, and flashed TWRP... then you've pretty much done the 'hard' part..
As @jfmcbrayer says, download SuperSU v1.86 directly to your Nexus 7, and flash it in TWRP.
However, sometimes the SuperSU app icon doesn't always appear in the app drawer after the TWRP flash... although it's very likely you are actually (probably) rooted.
To fix this, see my post here.
If this **still** doesn't work... try flashing an older version of the SuperSU root .zip, available here...
http://download.chainfire.eu/368/SuperSU/UPDATE-SuperSU-v1.75.zip
This will flash SuperSU v1.75... and then go to Google Playstore to update it to SuperSU v1.86. You will probably be prompted to do this anway, as soon as it is detected you're running a slightly out of date version...
Good luck.
Rgrds,
Ged.
Why didn't you just boot the CF-Autoboot bootimage as I suggested? It's the easyest way and you could have kept your stock recovery (less trouble with OTA Updates)
Just fastboot boot boot.img and a few seconds later your device is rooted...

[Q] stock rooted Lollipop OTA fails?

All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
moriarty00 said:
All,
Thanks in advance for any help you can provide. I have a Nexus 4 that I rooted and installed CWM recovery on, but I never installed any new kernels, ROMs, or radios. I'm currently on 4.4.4 and I want to upgrade to Lollipop. The OTA upgrade failed. So I tried returning to stock recovery and doing both the OTA and adb sideloading the OTA zip. Both fail.
The error message is "Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.4/KRT160/907817:user/release-keys." (But I definitely have 4.4.4 on my phone, not 4.4.0.)
The extra difficulty is that I really, really do not want to wipe my phone. I have a lot of apps with a lot of configuration and other user data. So is there anything I can do? I guess I should try unrooting somehow? Or is there some other zip I can download that, through some type of recovery, will install the OTA without doing this check and also without wiping me?
Thanks again!
Click to expand...
Click to collapse
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
moriarty00 said:
Actually, I figured out what works! This was on a stock rooted device with stock recovery, but I bet it would work with custom recovery too. Instructions modified from https://pay.reddit.com/r/nexus4/comments/1qny3f/howto_update_your_stock_w_lte_nexus_4_without/ .
1. Download the image you want from https://developers.google.com/android/nexus/images . Extract it, extract the .zip file inside it too, and collect all of the .img files into one folder.
2. adb reboot bootloader (and wait until the bootloader comes up)
3. fastboot flash bootloader bootloader-mako-makoz30f.img (or whatever file has a similar name, if you got a different image than I did)
4. fastboot reboot-bootloader (and wait until the bootloader comes back up)
5. fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.04.img (or whatever file has a similar name, if you got a different image than I did)
6. fastboot reboot-bootloader (and wait until the bootloader comes back up)
7. fastboot flash boot boot.img
8. fastboot flash recovery recovery.img
9. fastboot flash system system.img
10. fastboot format cache
11. fastboot reboot
12. Don't panic unless you've seen the startup animation for at least 15 minutes without anything else happening.
I lost root, but I imagine re-custom-recoverying and re-rooting won't be any harder than the first time around.
Click to expand...
Click to collapse
Wow, a 12-step program
I simply rolled back my changes, and applying the OTA was as simple as pressing the "restart and install" button Here are some steps:
I used the app Flashify from Play Store to flash stock 4.4.4 recovery. I downloaded the stock factory image from google's own site (this one), used 7zip to extract the archives (tgz and tar), found "recovery.img" and transfered that to my phone. Then chose that file in Flashify.
Uninstalled all apps that made system changes, like Xposed framework and mods, BetterBatteryStats etc.
Removed Root with SuperSU cleanup function
Rebooted for good measure and apply OTA from notification - wait an hour or two for it to complete
Profit (do we still say that on the internet? Getting old here...)
I don't know if certain ways to get root will break the OTA. I used towel-root, and apparently SuperSU was able to undo that completely.
DrDruge said:
Hi moriarty00,
I'm going to try the same procedure, thank you for posting this.
Can you confirm that your data and app are safe after the upgrade?
Click to expand...
Click to collapse
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
venu123 said:
OTA wants complete stock and obviously it doesn't think so about your phone. One option could be to back up to the cloud or some place outside the phone with TiBu (or whatever backup app you trust), then flash lollipop and try restore from TiBu. Another option would be to unroot (Supersu has an option to completely unroot), then retry.
Click to expand...
Click to collapse
If I unroot with Supersu how do I get root back?
moriarty00 said:
Yup, perfectly safe! Just make sure not to flash other images, like userdata.img.
Click to expand...
Click to collapse
Thank you!
Unfortunately the steps did not work for me, maybe I had some irreversible modifications or I had followed a different rooting procedure.
Or maybe I made a mistake in the upgrading steps.
Anyway, I had to flash the whole ROM and now everything is working fine.
Hey!
Basically I have similar problem with upgrading from 4.4.4 to 5.0 using OTA. Log from TWRP says:
Package expects build fingerprint of google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys or google/occam/mako:5.0/LRX21T/1576899:user/release-keys; this device has google/occam/mako:4.3/JWR66V/737497:user/release-keys.
Click to expand...
Click to collapse
Phone has been rooted using Nexus Root Toolkit. And as long as there wouldn't be a problem with flashing using adb and wiping all data, there is one setback... My nexus is somehow broken. Communication via USB does not work, at all. Neither phone nor PC sees other device. Certified LG service centre nearby said that it is problem with main board, so generally repair is unprofitable.
So question is: How do I update to 5.0 and then root, without USB connection to my PC?

Root / Unlock Bootloader without removing encryption!

I am not very good at making good step by step instructions but Lots of others are.
Here are the steps that I used.
Unlock bootloader via normal means
Flash chainfire boot img from here
Flash Twrp
Boot into Twrp and click mount and mount /system/
ADB Push supersu Zip file to /system/
Twrp install SuperSu.zip
Reboot
Profit
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Hi
Evo_Shift said:
Are you sure you're encrypted? What's it say under security in your settings under encryption? I assumed that kernel you flashed disabled the automatic encryption. Or did that just allow you to disable it later?
Click to expand...
Click to collapse
Wish I tried that first, turned off encryption now, although could re-encrypt.
Yes this should work. TWRP doesn't support decryption, which means any files copied to the phones user storage that we might want to install by TWRP (such as SuperSU), can't be seen by TWRP, as it can't decrypt the user data, so it can't be installed from recovery.
However, the system partition isn't encrypted, so pushing a file to the system, will allow TWRP to read it and install SuperSU. Of course you can't do things like full back ups as there probably isn't enough space on the system file system, so you need the user storage area for that, so you would need that decrypted for larger files so that TWRP can gain access.
Regards
Phil
Don't forget adb sideload for installing zips without using internal storage
Use Oem Unlock?
fastboot oem unlock
Yes
How does this affect using Android Pay?
Rado_vr6 said:
How does this affect using Android Pay?
Click to expand...
Click to collapse
Same as other rooted/unlocked devices it doesn't work.
So you can root while keeping encryption enabled? I need encryption for work, but root is a MUST have. Would like to verify before I order. Thanks.
I was under the impression that flashing the chainfire boot img disables encryption?
Did you fastboot into TWRP (no flashing/installing needed) Code = fastboot boot twrp-2.8.7.0-bullhead.img and then adb push supersu?
I've done what the op had and I have root with encryption.
Sent from my Nexus 5X using XDA Free mobile app
I also want to agree. I just tried to unlock tethering without full root, but ran into issues. So to fix my issues, I just decided to follow the ops steps and root the phone. After adding the image, I was unable to push supersu due to adb not working in twrp. However, I rebooted the phone and saw the encryption password on boot. Once the os was loaded, I went into settings -> security and noticed the phone was set to encrypted. Looking through the program list, supersu installer was in the list and worked perfectly. Thanks op.
Sent from my Nexus 5X using XDA Free mobile app
How long does the device take to boot up? I've been sitting at the boot animation for a while now.
You can have root access through SuperSU with encryption enabled. I have it running just fine with encryption enabled. What you do have to have turned off is dm-verity. With dm-verity enabled, modification to the system partition are "not allowed".
And Chainfire's modified boot image has 3 main modifications:
1. A modified sepolicy with SELinux provisioning for SuperSU
2. dm-verity turned off
3. forceencrypt for data partition disabled. Basically disabled forced default encryption, but you can still encrypt.
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Camp As A Champ said:
Is there a way to root MDA build numbers at all? Whether it be encrypted or decrypted?
Click to expand...
Click to collapse
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
dbrohrer said:
I'm not sure why you would want to. I ran the mda89f build for an hour or so before the ota to mdb08i. Phone seemed to run much smoother after the update. Possibly this was just related to timing.
Also, if you root on either of the mda builds, you won't be able to flash the ota to mdb08i. You'll be stuck. If you're waiting on the ota, just download the image and flash the system and boot, then follow OP / Chainfire's instructions.
Click to expand...
Click to collapse
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Camp As A Champ said:
Oh I'm special, I didn't know it was on OTA. When I go to check for system updates though, it shows that I'm up to date already. I've unlocked the bootloader and installed TWRP if that affects anything.
Should I just manually flash it to my device?
Click to expand...
Click to collapse
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
This worked for me too - I tried to:
>adb push supersu.zip /system/
... Then in TWRP install -> select /system/supersu.zip
But this failed for some reason... However, this worked:
>adb sideload supersu.zip
Then reboot, and restore Thanks a lot! Didn't want to give up encryption either...
dbrohrer said:
Since you already have trwp, you will have to update manually (unless you flash the stock recovery and wait for the ota, but who knows how long that will take). I would download the 80i image and just flash system.img and boot.img. That should be the equivalent of you getting the ota. Reboot and confirm that it will boot and you are on the new build. Then follow OPs instruction to root and/or decrypt.
Download, Extract everything.
Fastboot flash system system.img
fastboot flash boot boot.img
Reboot, check OP for further instruction.
Click to expand...
Click to collapse
Will I be able to do this through TWRP or should I just use ADB to flash the image files? Sorry for all the questions, this is my first nexus phone and I'm getting used to all the new methods
Nevermind, got everything to work, thanks for the help though

Soft Brick/possible full brick in need of help

I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks
Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
neo4uo said:
I was trying to root and unlock boot loader. I was on the latest update B29 and tried following the guide but used the B27 files. I flashed the files got into TWRP but for some reason my system got wiped. I can get into fastboot, recovery, and EDL but when i try to boot my phone regular it boots ZTE boot screen real quick and then goes into a BLACK screen and stays there? Any Suggestions on what I can do? If I try to unlock the bootloader it says failed cannot do remotely probably because my phone system get erased and so the option isnt clicked in phone to allow oem unlock.
I was going to try flashing;
- ZTE_A2017U.B29_MergeBootStack_by_DrakenFX.zip
- ZTE_A2017U.B29_StockSystem_by_DrakenFX.zip
There is some kind of problems with android file host does anyone have a copy of these two files hosted somewhere else?
Thanks
Click to expand...
Click to collapse
lafester said:
Did you make the backups shown in both the twrp flashing guide and the unlock bootloader guide?
Could you provide a little more detail on what you did so far?
Click to expand...
Click to collapse
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now
neo4uo said:
I ended up going to ZTE site and getting there B20 image and flashed back my backed up recovery and boot and flashed the update zip with there recovery and I am back in business now. I was trying to unlock and root but somewhere or how my system got deleted so it would not boot. What is the easiest way to unlock the BL and then root? Is DrakenFX the most up to date way? Anyways thanks for the reply, I was going to download DrakenFX files for stock recovery, but Android File Host is having some problems and you can not download anything from them right now
Click to expand...
Click to collapse
Yes, flash twrp and flash drakenfx unlockbootloader file. Look for the newbie guide to unlocking and follow. Read the thread first as always.

[Guide] How to install June Security Update via Image and retain Data (plus Root)

Since the May Security Update, there have been changes.
I won't get into that here, as there are already a number of threads where the new AVB process and what it means for updates and root is discussed at length on this forum.
For example - https://forum.xda-developers.com/an...-boot-images-android-verified-t3600606/page16
I'm just going to outline my process for installing the new security updates via full image (Not OTA) and then rooting the phone via TWRP.
A few things to bear in mind first.
You will need to have the following:
0. Know how to use ADB/Fastboot and have them installed. If not, you should please do some research first.
1. Full Image for Pixel (https://developers.google.com/android/ota)
2. TWRP boot image and zip files (https://dl.twrp.me/sailfish/)
3. Latest SuperSU by Chainfire (https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip)
4. VerifiedBootSigner by Chainfire (https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606)
Also...I don't make use of the vendor provided flashing scripts, I simply use the script commands and eliminate the '-w' flag manually.
*The SuperSu, TWRP and VerifiedBootSigner zips need to be saved to your phone*
From the bootloader ->
fastboot flash bootloader bootloader-sailfish-8996-012001-1704121145.img
fastboot reboot-bootloader
fastboot flash radio radio-sailfish-8996-012901-1702171013.img
fastboot reboot-bootloader
fastboot update image-sailfish-njh47b.zip
***The phone will automatically reboot at this phase and you will need to reboot back into the bootloader to continue either by manual means or by using "adb reboot-bootoader"
fastboot boot twrp-3.0.2-0-RC1-fastboot-sailfish.img
from TWRP (using files saved on phone) ->
TWRP install twrp-pixel-installer-sailfish-3.1.0-0RC2.zip
reboot TWRP
TWRP install SR3-SuperSU-v2.79-SR3-20170114223742.zip
TWRP install VerifiedBootSigner-v8.zip
reboot system
Edit - You should also update your SuperSU binary to 2.82 from within the app once you're booted into Android.
You're Done!
DISCLAIMER
I didn't create any of these files or take credit for them in anyway. This is simply an instructional that I hope will help many of you.
It requires some proficiency in using fastboot and TWRP.
If you don't know what you're doing and mess up your device, I take no responsibility for your actions or the results.
gonna give it a try, thanks dude.
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
churchmice said:
The only issue is that after updating the system image the phone will auto reboots so you have no chance to input the fastboot command.
Click to expand...
Click to collapse
phonepersonality said:
You're right.
I should update the instructions about that.
The reboot isn't really an issue, but it does add an additional step and some inconvenience.
Click to expand...
Click to collapse
fastboot has an option to skip reboot:
--skip-reboot
so the command would be something like: fastboot --skip-reboot update image-sailfish-njh47b.zip
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
TENN3R said:
Can't we just use ota? Like:
- sideload ota
- let reboot
- reboot bootloader
- boot twrp rc1
- flash twrp rc1
- flash bootloader signer
- reboot recovery
- flash root
- optional kernel
- flash bootloader signer
- reboot
I ask because I always did this and never got problems, so if anyone tried/wanna try just let me know
Click to expand...
Click to collapse
If you'd like.
I don't like to use the OTA files, personally.
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Tulsadiver said:
That is weird. Never had a problem with my phone being wiped except when flashing other than manually. I always flash mine one at a time, and never have a problem. I like to be in control but I am old lol! I've been wiped before.
Click to expand...
Click to collapse
I did manual fastboot commands earlier, not the autoscript, automatically wiped my data.
---------- Post added at 05:43 PM ---------- Previous post was at 05:31 PM ----------
Not sure what happened. Just pretty much treated like a dirty flash and fastboot flash the image. It must have detected the prior and wiped it. Had the thing rooted which is the only thing I can think of, it was not untouched stock.
mikeprius said:
Will the OTA even work with root ? I thought OTA is like taking the update over the air and if the system files are altered it fails ? I recently re-flashed the stock image but I may try this next time. The Pixel has become more difficult to update and in the past when I have even tried to reflash the stock boot it starts wiping my phone.
Click to expand...
Click to collapse
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Did anyone else have to install the TWRP 3.1 zip via USB-OTG? After flashing the full factory image for June 2017, rebooting to system, rebooting to bootloader then running fastboot boot twrp3.0.2-RC1.img, I wasn't prompted to enter my password so my user data remained encrypted and I couldn't install the TWRP 3.1 zip from the internal SD card, had to load it on a usb dongle and mount USB-OTG storage.
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp. After booted up you can re-mod, keeping your data.
Have you deleted the "-w" near the fastboot command in the factory image "flash-all" file? This causes wipe, if you remove it'll skip wipe.
Click to expand...
Click to collapse
I've tried to take out the -w erase flag. I've also tried to reflash the stock boot in the past when reloading a new kernel. Not sure if it is triggering some kind of system default but it just auto wipes. It's not the end of the world, I have everything backed up, I just have to restore everything. Just have not had any luck
Guys I can confirm also sideload ota method works flawlessly, 7.1.2 june rooted
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Coronado is dead said:
Does anyone know if once rooted and bootloader signed via this method Netflix becomes available again?
Click to expand...
Click to collapse
A phone setup according to this thread is not expected to pass the Safetynet check. I've been updating with SuperSU using FlashFire, and my phone just shows Netflix VR in the Play Store. The Magisk discussions are primarily the threads that have been active recently for having root and passing Safetynet.
Pixel discussion:
https://forum.xda-developers.com/pixel/how-to/magisk-pixel-t3573845
Pixel XL discussion:
https://forum.xda-developers.com/pixel-xl/how-to/guide-stock-7-1-2-root-safetynet-ok-t3617347
TENN3R said:
You can update via ota, but you need to download the zip on your pc and sideload it in twrp.
Click to expand...
Click to collapse
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Flitskikker said:
Could you please elaborate on how to sideload in TWRP? I used to use adb sideload, but maybe your method is easier.
My current steps are:
1) adb reboot recovery
2) adb sideload ota-update.zip
3 Reboot and check if everything is okay (root and TWRP are lost, data are not)
4) adb reboot bootloader
5) fastboot boot TWRP.img
6) Flash TWRP and SuperSU
7) Flash boot signer
8) Reboot
Click to expand...
Click to collapse
I use the same method I don't think there are any others
TENN3R said:
I use the same method I don't think there are any others
Click to expand...
Click to collapse
Thanks for confirming.
Does this VerifiedBootSigner-v8.zip apply to the August security patch as well?

Categories

Resources