Database Users

Return to Stock? (B20_Boot)

Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
Yes you can via Rczrider 's TWRP backup

tele_jas said:
Not that I want to, but if I wanted to.. Is there a way to return the unlocked bootloader version back to stock to where I can receive OTA's?
Like I said, I don't necessarily want to, but if I needed to for some reason.
Click to expand...
Click to collapse
XblackdemonX said:
Yes you can via Rczrider 's TWRP backup
Click to expand...
Click to collapse
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204

rczrider said:
Yeah, it looks like @tenfar updated their tool to use the stock files from my untouched B20: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Click to expand...
Click to collapse
if someone can make a guide on HOW-TO (Steps + FIles + Images needed) i can give it a shot...
just send me a PM if you know the HOW-TO :good:

Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?

DrakenFX said:
Mmmmm, noone yet?.... I guess I'll start gathering info.
One thing I wanna make sure flashing @tenfar boot. Img = need Data wipe right?
Click to expand...
Click to collapse
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!

tele_jas said:
I've been flashing custom ROM's for several years, but I've bricked one too many phones over the years "not knowing" the correct way to do certain things... So I started this thread to see what those steps were because I'm too scared to attempt it myself. :silly:
So, I know I'd appreciate your efforts in this!
Click to expand...
Click to collapse
I'm curious too and I wanna give it shot,
P. S. Any way to use terminal or adb to pull the partition list with their Extension?
Like for sample. " ext4 system /dev/block/sde13 " or something similar with extension?

Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread

tele_jas said:
Has anyone got a step-by-step for this yet? I searched, but don't see a "Back to Stock" thread
Click to expand...
Click to collapse
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader

It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet

peramikic said:
It is still not clear where the unlock bootloader state is recorder. I have checked a couple of partitions but they are identical to locked B20 (aboot, devinfo were my prime suspects)
So assuming that this is not a permanent thing for the bootloader state and can be reversed, steps would be something like this
1. lock bootloader
2a. flash Stock B20 image and signed(tenfars) TWRP via axon7root
3. Reboot in TWRP (read only mode), full factory wipe (wipe plus /data format), flash original system image via twrp, wipe data again
4. turn off phone, don't reboot (no system start)
5. flash stock recovery via axon7root
6. Reboot to Stock Recovery direct (do not boot)
7. Factory reset from stock recovery
8. Reboot
But there are a few unknowns yet, even with stock system, boot and recovery we still have stuck loops unless using modded boot. My guess is that TWRP mods /system on exit, that's why i put read only mode but not sure if you can restore it if it's not rw. Since it's image to device it should work, RW is for mounting partition
And big one is if unlock state is permanent or not, not sure anyone tried yet
Click to expand...
Click to collapse
those steps were the same i was planning to do plus flashing something else, but seems like i may be not doing the other flashing file now......well still gathering more info and will see.
P.S. Thanks for the info. @peramikic

DrakenFX said:
i created a Thread for users who have run into the No Boot issues and those problems , so i can gather more info of the causes of their problems but nobody had reply yet,
just waiting so i can test things and get back to Stock B20 with Root + TWRP and lock bootloader
Click to expand...
Click to collapse
Gottcha.... I was just curious, because I'm starting to have a few random issues (reboots, apps opening without tapping them, google voice commands not working like they did just a few days ago) I'd like to get back to stock and maybe start over. Of course, I didn't make a backup up until after I flashed SuperSU and my apps downloaded so I have no "stock" TWRP backup. **But, this all could be "theme" related too, since I'm running a dark theme that isn't quite compatible with the A7 yet.
I may try removing the theme and let it run a day or two and see how it does?

Recovering data from factory reset Axon 7

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.

Huawei Nova Dload Bootlop

Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.

Noctyk said:
Hi, I recently tried to downgrade back to stock firmware from Lineage OS using the Dload method.
However now its on a bootloop, the versions of CAN-01 and CAN-11 all give me a bootloop, after waiting on it a while it will boot into recovery mode.
Usually this is a simple problem to fix however it reset my bootloader to locked as well as my twrp recovery, I'm not sure how I can recover from this other than sending to repairs.
Any suggested solutions!
It could just be I have the wrong update.zip but I want some more views on this.
Click to expand...
Click to collapse
Hello!
Check this post.

#Henkate said:
Hello!
Check this post.
Click to expand...
Click to collapse
Hi! Thank you for the fast reply, I remember that I've tried method 1 already and since it reset my bootloader, it's no longer unlocked. The first thing I did when I realised it was a bootloop I tried to reflash my TWRP as I have a backup but it fails everytime I try to flash anything through fastboot as my bootloader is locked.
I was slightly naive and didn't think it would wipe my TWRP and bootloader back to locked.
What do you recommend I try?

Well, Unlock your Bootloader again.. ^^

Bad2hold said:
Well, Unlock your Bootloader again.. ^^
Click to expand...
Click to collapse
I've fixed the issue now thanks, I forgot to wipe the cache and extra bits after the Dload update thats why it was stuck on the bootloop :silly:
My problem before was I couldnt get the IDs needed for my bootloader unlock code since I couldn't actually check the IDs through settings.

Possible brick

Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks

mike_1983 said:
Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.

mike_1983 said:
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.
Click to expand...
Click to collapse
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH

beachfl said:
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH
Click to expand...
Click to collapse
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!

mike_1983 said:
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!
Click to expand...
Click to collapse
Well done ? so glad it got sorted x
Sent from my Asus P027 using XDA Labs

Messed up and my phone now cannot boot!

I tried to remove root.
First, I used supersu and used the full unroot setting. However, after rebooting back to android, it is still showing root.
Therefore, I used magisk uninstall. After that my phone is in boot loop with dm-verity error.
Tried to go into TWRP (still works) to install no-verity 6.0 zip but it says boot cannot be found.
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Can anyone help shed some light? How can I restore back the phone without losing data?
If all else fail, what are my last resort to get the phone back to working?
Appreciate any input. Thanks!

Ok, I tried a few things and all failed. Now the phone keep looping into fastboot when I plug in the usb.
I would like to just flash to latest firmware will do. Data recovery is secondary now.
I tried AFT 1.0.0.45 but it only allow zip files. I cannot select the raw file. I tried renaming the raw to zip but it still refuse to flash. I get error saying unable to unzip. However, before that I can see the app is trying to connect to somewhere for verification. I think something about FRP. Don't know what is that.
Appreciate any input on this. Thanks.

abubin said:
So, I am now trying to install recovery.img and boot.img. However, I am unable to find recovery file for WW_15.0410.1807.75 (Android O).
Click to expand...
Click to collapse
if you flash stock ROM, recovery is restored automatically.
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip

aIecxs said:
if you flash stock ROM, recovery is restored automatically.
View attachment 5825195
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE552KL/UL-ASUS_Z012D-WW-15.0410.1807.75-user.zip
View attachment 5825209
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE520KL/UL-ASUS_Z017D_1-WW-15.0410.1807.75-user.zip
Click to expand...
Click to collapse
Thanks! I manage to flash the stock ROM and it is able to boot into the OS again.
However, I am still seeing this "DM-verity in EID" screen whenever I boot up. Is this okay? Cause I remember this screen wasn't shown previously. It supposed to show a screen saying bootloader is unlocked and some security thing. Now it's showing this EID screen. Anyway to fix it?

if there is something like vbmeta partition, flash vbmeta.img otherwise I don't know. the screen ask for locking bootloader, but I do not recommend this. usually locking bootloader only works if every partition is stock, I doubt the locking process will fix anything.