Unable to unlock bootlader a2017g - ZTE Axon 7 Questions & Answers

I tried it with this tutorial https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 and I've tried it about 15 times and couldn't fix my issue. I always get error messages and I KNOW that he said to not do it on the a2017g model but on a german forum (a2017g) he copied it and it worked. Then I saw NOT to do it on nougat but I still tried it nevertheless and finally I tried it with the most idiot proof and safest and newest method avaiable: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108 This SHOULD work on nougat and a2017g but sadly the bootloader is still locked after succesfully flashing with MiFlash
Can someone help?

C2015_Fan said:
I tried it with this tutorial https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 and I've tried it about 15 times and couldn't fix my issue. I always get error messages and I KNOW that he said to not do it on the a2017g model but on a german forum (a2017g) he copied it and it worked. Then I saw NOT to do it on nougat but I still tried it nevertheless and finally I tried it with the most idiot proof and safest and newest method avaiable: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108 This SHOULD work on nougat and a2017g but sadly the bootloader is still locked after succesfully flashing with MiFlash
Can someone help?
Click to expand...
Click to collapse
He said not to do it with the A2017G? That guide is made specifically for the A2017G...
You know, error messages don't exist just to scare you or whatever. When you go to the doctor you don't just make him guess what your problem is...
Plus, MiFlash doesn't unlock your bootloader. axon7toolkit needs to flash fastboot via miflash then access it and run "fastboot oem unlock". So axon7toolkit is also failing somewhere along the road.
Just do Controllerboy's process again and this time actually tell us what the errors are...
---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------
C2015_Fan said:
I tried it with this tutorial https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 and I've tried it about 15 times and couldn't fix my issue. I always get error messages and I KNOW that he said to not do it on the a2017g model but on a german forum (a2017g) he copied it and it worked. Then I saw NOT to do it on nougat but I still tried it nevertheless and finally I tried it with the most idiot proof and safest and newest method avaiable: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108 This SHOULD work on nougat and a2017g but sadly the bootloader is still locked after succesfully flashing with MiFlash
Can someone help?
Click to expand...
Click to collapse
Okay, I'm gonna help you read a little
Controllerboy said:
The following guide describes how to go from a stock, not rooted, locked bootloader A2017G on Marshmallow Firmwares (B03 to B10) to an unlocked bootloader TWRP recovery LineageOS 14.1 A2017G. A2017U users, this guide should work for you too, but I hear there's an alternative, easier process exclusively for A2017U users. A2017 users do not proceed, this guide won't work for you. Users on stock Nougat, do not proceed, this guide won't work for you. You need to downgrade to Marshmallow first. Even A2017G or A2017U Marshmallow users must proceed with caution.
Click to expand...
Click to collapse

Choose an username... said:
He said not to do it with the A2017G? That guide is made specifically for the A2017G...
You know, error messages don't exist just to scare you or whatever. When you go to the doctor you don't just make him guess what your problem is...
Plus, MiFlash doesn't unlock your bootloader. axon7toolkit needs to flash fastboot via miflash then access it and run "fastboot oem unlock". So axon7toolkit is also failing somewhere along the road.
Just do Controllerboy's process again and this time actually tell us what the errors are...
---------- Post added at 04:17 PM ---------- Previous post was at 04:13 PM ----------
Okay, I'm gonna help you read a little
Click to expand...
Click to collapse
Yes, I managed it and it works but thy didnt the second method with axon7toolkit work?

C2015_Fan said:
I tried it with this tutorial https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379 and I've tried it about 15 times and couldn't fix my issue. I always get error messages and I KNOW that he said to not do it on the a2017g model but on a german forum (a2017g) he copied it and it worked. Then I saw NOT to do it on nougat but I still tried it nevertheless and finally I tried it with the most idiot proof and safest and newest method avaiable: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108 This SHOULD work on nougat and a2017g but sadly the bootloader is still locked after succesfully flashing with MiFlash
Can someone help?
Click to expand...
Click to collapse
hello, I have just do it today using ZTE Axon Toolkit only following instructions within this tool.

C2015_Fan said:
Yes, I managed it and it works but thy didnt the second method with axon7toolkit work?
Click to expand...
Click to collapse
Good lord. I was asking you for error messages. How would I or anyone else know if we don't have the cause if the error?

Related

Axon 7 A2017U B29 Root, BL unlock, and TWRP

Can someone walk me through how to Unlock the bootloader, root, and install TWRP? I'm so confused. I tried to do the newbie way, even though I'm not a newbie, and I lost my B29 Stock Recovery and can't find the download for it.
Sent from my ZTE A2017U using Tapatalk
I haven't done it yet but I've done a lot of reading and this seems to me the best guide.
Head over to this link which is the TWRP thread. https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
Once you're in there go to bootloader unlock section. Download all the necessary files and on the bottom of the guide there will be instructions link which will take you here https://build.nethunter.com/misc/axon7/INSTRUCTIONS.txt
Follow that and that should do it.
When i get a weekend off ill be using this method to get the Lineage OS 14.1 on my device.
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
amphi66 said:
Search, Read & Follow --CAREFULLY--.
It's been a while, but this worked great for me, starting from B29.
Goodluck
Let me tell you, this is the guide that should be pinned. It gives very easy/clear instructions on what you need to do to root/flash recovery and even going back to stock. Very well written and I wish I had seen it sooner. I was going to write a clear guide on this subject only to find.. it already existed.. --nolimit78
Click to expand...
Click to collapse
greatzt said:
@amphi66 I am on 2017U B29 and want to unlock bootloader, install TWRP and root. I also read newbies thread. I am confused about one thing. which TWRP recovery image should I use? a2017u B27 http://d-h.st/kRgq or TWRP recovery 3.0.2-2 : http://d-h.st/dgWW ? There is no file for B29 on newbie's thread and in FAQ, the OP said B27 should work for B29. Which one did you use?
After reading, I also see some people said tenfar's tool is too dangerous and it may brick your phone. Some people also claimed the back up of TWRP recovery 3.0.2 provided on that thread has some bugs may cause you to loose your IMEI number when you do recovering. Do you have any issues? Thanks!
Click to expand...
Click to collapse
This was back last Nov, but I followed the guide, using the recommended files (was on B29, but used the B27 OK, then reflashed B29 at the end).
The warning involved backing up and then restoring the EFS partiton with tenfar's tool. DON'T! If you stick with system, data, and boot partitions you should be fine.
Good luck. You may want to check with @nolimit78. He has done this much more recently.
Yes, I agree with you @amphi66 that there is a lot of different places to get information about how to root/flash recovery for A2017U B29. Here's what I've done with two different A7's and both have worked each time.
1. Boot the phone to EDL Mode (Both Vol+Power on boot it'll quick flash the red notification light and then act like it's off.. it's not)
2. Use tenfar's tool to flash the recovery. (I renamed the updated TWRP img and named it "recovery". This used tenfar's tool to flash the updated TWRP on your device.
3. Once in TWRP, run the command (reboot disemmcwp and relaunch TWRP) and flash the package to use modifiable bootloader from B20.
4. Once that flashes now you can send the command in Fastboot "fastboot oem unlock" which will unlock the bootloader that doesn't trip anything notifying ZTE
5. At this point you can flash a B29 rom and have a grand ol' time. However, I would recommend using the LineageOS Rom that's available. Trumps everything else out there IMHO.
6. To do that You'll need to flash the Nougat Bootstacks for that rom to boot prior to flashing the Rom itself. I would recommend flashing the nougat bootstacks, reboot to TWRP, flash LineageOS, reboot.
Like I said, I've done with this with two different devices (Thanks ZTE) and both worked out just fine. I did this method with a device with b27 and b29, both ended up updated and flashed with CM/LineageOS with ZERO issues. This post here should also be pinned as the one true guide (THE KING OF THE NORTH) for unlocking/rooting a stock Axon 7. I spent probably about 4-5 hours working, trying to figure out how to get my device unlocked/rooted. However.. at the very end I wrote out instructions trying to help those who would come after me.. I searched the threads to make sure there wasn't already a thread out there.. and then.. it turns out there was.
Someone have the 5 files to unlock the bootloader 2017u on drive

[REQUEST] XT1700 Original Firmware

Hi there, recently just bricked my XT1700. I installed the XT1706 original rom uploaded by dr.faramroze (very thank you) but I can't install OTA updates, and i don't feel confortable with the secondary sim useless menu.
Somebody can do a backup from his XT1700? Or just a link to download it, because I can't find anything but XT1706...
Sorry my bad english and thank you.
From this page you can download Moto XT1700 stock firmware use SP flash tools to install.
http://motorolastockrom.com/motorola-moto-e3-xt1700
---------- Post added at 08:45 PM ---------- Previous post was at 08:38 PM ----------
Also I'm need here so I want to ask you something I like you erase system and backup XT1706 from recovery. I found that site and downloaded the last software version (S503) I installed and everything goes well. But when I tried to unlock bootloader again the adb window said: This operation is not allowed and I wasn't able to unlock boot loader. Then I downloaded version S116 and I tried to unlock bootloader again and surprised It works. But I tried to install OTA updates and y get no notification of updates. It says system has the last version when is not. Some idea of what can be happening here?
sfreddy15 said:
From this page you can download Moto XT1700 stock firmware use SP flash tools to install.
http://motorolastockrom.com/motorola-moto-e3-xt1700
Click to expand...
Click to collapse
Just a warning - those firmwares (at least the 2 latest versions S503 and S302) have locked boot loaders, you will not be able to unlock the bootloader with fastboot, or install TWRP/SuperSU if you install them.
Would appreciate it if anyone knows where to get either S503 or S302 with unlocked bootloader.
Use S124. It allows bootloader unlock!
k-ninja said:
Just a warning - those firmwares (at least the 2 latest versions S503 and S302) have locked boot loaders, you will not be able to unlock the bootloader with fastboot, or install TWRP/SuperSU if you install them.
Would appreciate it if anyone knows where to get either S503 or S302 with unlocked bootloader.
Click to expand...
Click to collapse
Use S124. It allows bootloader unlock!
jmak117 said:
Use S124. It allows bootloader unlock!
Click to expand...
Click to collapse
In the end I went with the S131 firmware for the XT1706... allows unlock, but isn't any newer than the XT1700 firmware I originally started with :-/
Is this thread still alive?
If so i need help. The links arent working (they work but they dont bring me to the download page, instead to another website) , so does anybody have the stock firmware with them?
It would really help. Im getting so close to rooting my phone!
Here friend, hope you find useful
http://givemerom.com/moto-e3-xt1700

[SOLVED] Fastboot Flash failes after firmware update

Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
EDIT: The solutionwas to re-unlock the bootloader (just perform "fastboot oem unlock PERSONAL UNLOCK KEY). Thanks to AndreaEl for suggesting the solution.
i have had the same problem some days ago.
Re unlock bootloader and try again
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
opal06 said:
Hello all,
I have flashed my p9 lite (VNS-L31C432B390) to the newest B390 firmware using official update routine and therefore flashing stock recovery via fastboot before updating. Now I wanted to reflash TWRP in order to get root back (I had done this before with B380 and B388 update, never having issues), but when I try the flash command in fastboot it says "FAILED (remote: Command not allowed)"
After some research, I found that this normally indicates a locked bootloader, but both on the screen of the phone (when in bootloader) and via fastboot (fastboot oem get-bootinfo) bootloader is shown as unlocked.
I just can't figure out what may have caused flashing not to work anymore... Anyone with similar issues after latest update?
Click to expand...
Click to collapse
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
opal06 said:
Thank you very much, I'm definetly gonna try, although I really hoped to spare me this factory reset
Click to expand...
Click to collapse
Have u tried using the method on this thread?
https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
AndreaEl said:
Neo Markson said:
Hi, could u please give a step by step guide on how to get to B390? I'm currently in B381.
---------- Post added at 01:36 AM ---------- Previous post was at 01:31 AM ----------
B160 -> B370(TWRP) -> B390(Firmare finder DNS method)
i have do like this
Click to expand...
Click to collapse
Tried that, it doesn't work. And I'm at B381 by the way. See when I try to send the firmware update to the updater app and install it, nothing changes. The installation completes and after reboot, when I check from about phone I see that I'm still in B381(at least according to it )
---------- Post added at 12:39 AM ---------- Previous post was at 12:32 AM ----------
opal06 said:
Re-unlocking the bootloader did the job for me... Afterwords I was able to flash TWRP again over fastboot... So this can be considered as solved...
As for my update method, I found the easiest way is to get official OTAs (I've got the B390 as official OTA, maybe not yet available in your region) by temporarely switch back to official recovery. As this thread shows, there may be minor problems and root will be lost after update. As always, you are performing these steps at your own risk. These are the steps:
- get an official recovery image from an official Huawei firmware (search here on the forums). Unzip it and use Huawei Extractor to extract recovery.img from update.app
- Flash it in fastboot mode (fastboot flash recovery /Path/to/recovery.img)
- Download update via Huawei's software update application
- Let it perform the OTA. This step is likely gonna fail, no problem though, just reboot.
- Software Updater will state that the update failed and start to download the full firmware package, which is way bigger (~2GB). Update with this one will work though...
- Performing the update will unroot, just flash latest TWRP and SuperSu like shown in many guides on this forum to regain it
Click to expand...
Click to collapse
My boatloader is already locked and I'm not rooted.
Click to expand...
Click to collapse

EDL Tool vs TulipTool

I have a new (to me) Axon 7 Mini. i hIve had an A7U from a couple of years.
This phone came via eBay, but w/o user PW from previous owner.
Using TulipTool I was able to unlock the Bootloader, wiping all previous User Data, but the Google FRP blocks re setup (it hasn't been 48 hours tho).
Meanwhile I was going to flash a new bootlaoader and ROM, but the EDL tool does not find the phone in FTM or EDL. Surprising since the TulipTool worked fine.
And when attempting to flash TWRP 7.1r1 via TulipTool Recovery just reboots to a blank acreen. Verity restores Stock Recovery after a reboot to system. Unfortunately there is no FactoryReset or Flash ROM choice in the Mi Stock Recovery.
Any ideas? Thanks.
To use EDL tool you need to remove the old driver (he works with TulipTool only), and install stock driver(It should install automatically).
bius88 said:
To use EDL tool you need to remove the old driver (he works with TulipTool only), and install stock driver(It should install automatically).
Click to expand...
Click to collapse
I removed and reinstalled all drivers and moved the EDL tool to C: root.
It now finds the ADB interface, but still receives no phone response in EDL or FTM. No message is seen on the phone asking for USB Debugging.
It has not yet been 48 hours since I removed all user data after unlocking the bootloader, so Google still has me locked out from completing registration, so we will see what happens by tomorrow.
I was hoping to flash a ROM and setthis up for my wife.
I successfully set the phone up as a new user, then Factory Reset which also restored the complete compliment of Android Recovery options. Now to (again) begin the EDL flashing experiments.
Any latest recomendations for Bootloader, ROM and Kernel?
amphi66 said:
I successfully set the phone up as a new user, then Factory Reset which also restored the complete compliment of Android Recovery options. Now to (again) begin the EDL flashing experiments.
Any latest recomendations for Bootloader, ROM and Kernel?
Click to expand...
Click to collapse
First you need read about Bootloader
---------- Post added at 09:35 AM ---------- Previous post was at 09:23 AM ----------
About Edl Tool using
bius88 said:
First you need read about Bootloader
---------- Post added at 09:35 AM ---------- Previous post was at 09:23 AM ----------
About Edl Tool using
Click to expand...
Click to collapse
Thanks. I have been working with the A2017U since Nov 2016 so am a bit familiar. I bought the B2017G as an experiment and am quite impressed with "little brother", so far.
EdIt: For kicks I tried "Check for Updates" and surprisingly received an OTA update from.6.0.1 B14 to 6.0.1 B21. That no sooner had installed when I was notified again that the B21 to 7.1.1 B12 update was available (glad to see ZTE is consistent with their confusing id scheme across the platforms) It also downloaded and installed w/o issue (a whopping 1.8 GB). We'll see where to go next.

Downgrading from Pie(pixel exp) to Stock.

Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
reganEZ said:
Hello Everyone!
I am a total noob. I have rooted many phone but never once reversed the process. Plus with stock moto being 32bit and customs being 64 it is even more complicated for me. And plus all this post about lost IMIE numbers and lost GPT makes me scared.
If i may, can I get step by step guide to relock my bootloader and get OTAs.
I have read most of the tutorials here but couldnt get the confidence to move forward(they all sound a little different)
I have moto G5 plus XT1686 indian version 4Gb/32GB currently running PE 9.0 (GTRCraft). I dont remember which version I had when I unlocked the bootloader. I do have a backup of my persist/efs.
I did see one tutorial but it is for 8.1.0 to stock and IDK if that works for me.
Thanks in advance.
Click to expand...
Click to collapse
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
riyan65 said:
Just wipe everything from twrp and then use LMSA OR manually flash the stock ROM and then go for bootloader lock procedure. Then you are done. And you won't lose any IMEI or Persist, so you will be safe.
Click to expand...
Click to collapse
So just download a TWRP flashable 8.1.0 rom and i m good?
reganEZ said:
So just download a TWRP flashable 8.1.0 rom and i m good?
Click to expand...
Click to collapse
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.bat?dl=0
Click to expand...
Click to collapse
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
+ i tried the method and it says "slot not found" error
reganEZ said:
ATTENTION:
You will need the appropriate version of the firmware according to your device version
You need the same or later version of firmware that you have when you unlock your BL
Example: If when you unlock your bl you was on NPNS25.137-33-11 you need the same (or later) complete firmware because you can't downgrade.
This is a part of the bootloader locking tutorial here on XDA. Does this make a difference?
Click to expand...
Click to collapse
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
reganEZ said:
+ i tried the method and it says "slot not found" error
Click to expand...
Click to collapse
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Wolfcity said:
You have to use the firmware you were on before you changed to a custom ROM or a newer one.
Never use an older one, downgrading can brick your device.
The "slot not found" error is normal, it's related to A/B devices with more than one recovery slot like Pixel phones. The commands should work nevertheless. Ignore the message.
Click to expand...
Click to collapse
Hello, Thank you for your reply.
I understand I cannot use an older firmware. I remember I unlocked my BL when I was in 7.0 itself, but when I installed the Arrow 9.0, I flashed the 8.1 firmware zip to get the NFC and Fingerprint working. So now my ro.build fingerprint doesnt tell me which firmware build i am on it just says "8.1"
I am confused what to do. Should I download the latest 8.1 moto rom and flash it? I tried the TWRP flashable rom but the phone just goes upto Hello Moto bootscreen and then bootloops.
I erased everything and flashed PE 9.0 again.
reganEZ said:
Hello, Thank you for your reply.
.....Should I download the latest 8.1 moto rom and flash it?.......
Click to expand...
Click to collapse
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Wolfcity said:
No, download a fastboot flashable ROM, with a TWRP flashable you won't be able to apply OTAs:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Use OPSS28.85-17-4 if you're in the US or OPSS28.85-13-3 for the rest of the world.
Follow the available tutorials for flashing that firmware and after that for relocking the BL (almost the same commands). Make sure you have Minimal ADB & Fastboot
https://androidfilehost.com/?fid=746010030569952951
and Motorola drivers
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view
installed on your PC.
For the fastboot commands you can use this flashall.bat:
https://www.dropbox.com/s/zfh67uzfle9hsco/flashallO.batflashallO.bat?dl=0
Click to expand...
Click to collapse
Wolfcity said:
That's what I would do. If you flash the latest firmware it can't be older as the one you're originally coming from.
Follow my previous post:
Click to expand...
Click to collapse
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
MrAshuBrar said:
Hello Sir, i was on OPSS28.85-13-5 when i flashed custom rom. The link you provided lists OPSS28.85-13-3 as the latest firmware. Should i install that? I am from India if that helps. Help please.
Click to expand...
Click to collapse
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
CanadianGixxerman said:
I reloaded my G5 Plus with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip sucessfuly. However, I was not able to relock the bootloader :
C:\Moto potter>fastboot oem lock
...
(bootloader) Still require signed boot.img
It got OTA'ed to Oreo 8.1 latter on, but still bootloader unlocked.
I just went through the flashing process to POTTER_RETAIL_8.1.0_OPSS28.85-17-4, same damned thing.
Everything works fine, excpet for Netflix that can't be installed no more and my bank software who keeps complaining.
I just dunno what to do to relock, any advice ?
Click to expand...
Click to collapse
Flash all the system files while locking. (0-8). Older locking guides have only 0-4. Newer firmware has 9 system files.
Wolfcity said:
Take this one:
85-13-5
https://forum.xda-developers.com/g5-plus/how-to/official-oreo-coming-soon-t3779098/post78844908
Click to expand...
Click to collapse
Thank you so much ?

Categories

Resources