since i have unlocked bootloader by official tool i can not root it and i cannot install any recovery
please help me so i can relock bootloader of my phone
i have tried maximum methods to relock bootloader of my phone but i am unsuccesful
can someone please help me so i can relock bootloader of my phone
uhm i unlocked my bootloader via official tool, and i already installed twrp and magisk
What is the process that you apply because I am facing issue.whenever I tried to install twrp recovery it says something about target report size does not reach and partition error
twrp not installing
now i am facing issue with this
unknown partition 'recoveryC:\Users\sankalp\Desktop\asus max pro m2\unlock\twrp-3.3.1-0-X01BD.img'
error: cannot determine image filename for
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
After relock etc
Use original recovery wipe data case
Than boot to bootloder
Boot to twrp recovery
Wipe data
Install twrp
Flash rom?
https://forum.xda-developers.com/max-pro-m2/development/recovery-twrp-3-2-3-x-t3885935/page10
Unlock 1st
Flash orio file .. stock orio not pie
Related
Hi,
is it possible to relock the bootloader to original factory mode.
fastboot oem lock (will erase userdata)
Also you should restore the fbop partition: /dev/block/bootdevice/by-name/fbop
For more reference see:
https://forum.xda-developers.com/axon-7/help/lock-unlocked-bootloader-t3444044
https://forum.xda-developers.com/showpost.php?p=68738854&postcount=100
Also please don't open a thread to a question that has already been answered several times.
After i unlocked bootloader my phone now is recognized as A2017U. When i relock it will it then recognized as original A2017G ?
I am interested in a tutorial about going back to stock for G model
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Bomberus said:
The procedure for the g model is no different than the U model except you have to revert the bootloader (fbop partition) because the european model is quite restricted.
For making a tutorial I would need to know exactly what you modified.
There are already good step by step guides in this forum. All I could offer you are my backup files for the recovery and bootloader for the 2017G with update B08.
Click to expand...
Click to collapse
At the moment i am on B09 rooted but I installed it via TWRP using DrakenFx's tutorial from here : https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3
Futhermore when I unlocked the bootloader I was on B03 and I saved the aboot.img and fbop_lock.img .
Now I would like to go back to fully stock to prepare for the android N update.
I would highly appreciate it if you could offer me some directions for this matter.
Never tried this method (so I take no responsibility) but in order to receive ota you need an unmodified system with locked bootloader.
To lock your bootloader:
First backup all your apps, data and internal sdcard !
Connect your phone to a PC and start adb:
Type: "adb reboot bootloader"
Phone will restart: (if you are on linux, run fastboot with root permission)
Type: "fastboot oem device-info" (just to check things)
"fastboot oem lock" (will lock your bootloader)
According to DrakenFX you should have the stock recovery already installed. So you can flash a sd card upgrade from ZTE "http://www.ztedevice.com/support/detail?id=98CEB24F9FFD433EA99EC424163149A6" (to bring you back to stock)
If you still have TWRP use DrakenFX files to flash your system back to stock, but this time do not flash supersu.
You should be good to go and just have to wait for ZTE to release the update and apply it via the updater UI.
BTW this is my fastboot oem device-info output:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.059s]
finished. total time: 0.059s
Click to expand...
Click to collapse
dodo34 said:
Hi,
is it possible to relock the bootloader to original factory mode.
Click to expand...
Click to collapse
You mind my asking the reason WHY you want to Relock?
If is cuz the N update , I'll rather keep it unlock base on @lokissmile thread and I'm 100% sure I'll be releasing N TWRP Flashable Zips for all variants when N is available.
i have G model and flashed the aboot of the U modell.
How to flash back now the aboot of the G modell back ?
Any help for the G modell ?
dodo34 said:
Any help for the G modell ?
Click to expand...
Click to collapse
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
LifeSupportZ said:
as far my understanding the G model have factory images right? just download the one you were using and flash it using custom recovery.
Click to expand...
Click to collapse
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
peramikic said:
@dodo34
This is correct, the full image should be the one that contains both the emmc_appsboot.mbn (this is your aboot or bootloader partition) and the fastboot.img (the fbop or fastboot command partition) as well as recovery.img. This will set everything back to stock in one swoop. Otherwise you have to reflash the signed (tenfars) TWRP to flash back the fastboot image and then falsh back stock, since regular TWRP will either not be there anymore or will not run since BL is locked now
P.S, you can leave the fastboot alone for the purposes of OTA, no update so far hes checked on it and i am not sure if there is a G package with it since it has not changed from release, so as long as the image you flash has the bootloader and recover you should be good for N
P.S.2 Actually I see a little catch 22 here. If you lock the BL first, then you will not be able to run TWRP or boot into system if it was modified. You would need to flash the "signed" version of TWRP or flash stock recovery before locking the BL. Stock would be preferable since it can flash the factory package withouht modifications. If using TWRP i think you have to change updater-script to remove a .... and i just found another catch 22. The updater-script will look for product name P996A04 and if yours shows as 2017U the it will report back P996A01 so you will have to have a signed TWRP on there no matter what. Either to flash the backed up aboot fbop and recovery and then flash the full factory package through stock recovery or mod the updater-script and remove the assert line and flash the whole thing with TWRP. What do you get in TWRP shel when you run this "getprop ro.product.model"
Click to expand...
Click to collapse
if he mod the updater_script from official zte update to make it flash friendly, this is what i'll do,
* Mod updater script and remove aboot and recovery for now
* flash new zip without file mention above
* boot to bootloader while having custom recovery
* lock back the bootloader
* boot to custom recovery and perform " format data "
* create a flashable zip with stock aboot and recovery
* flash new zip with aboot and recovery
* reboot to recovery and check if boot to stock recovery and while in there perform a factory reset
i know is a lot of steps but, seems like is the way to go to get everything back in place without zte noticing anything.
Now i am on B06.
I put update.zip B08 and select update. But it boots to TWRP recovery and update fails.
@dodo34 If you are trying to restore from the OS system update you need to reflash your stock recovery for it to work properly. Wait for someone to confirm what I just said, but that's how it worked for me.
how can i flash my original recovery. what is the command for cmd ?
Please help restoring back original recovery.
dodo34 said:
Please help restoring back original recovery.
Click to expand...
Click to collapse
rczrider said:
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
Click to expand...
Click to collapse
Try this guide from newbie unlock thread.
I get this error.
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r
Usage:
axon7tool -r <boot|recovery|gpt> ...
axon7tool -w <boot|recovery>
C:\Users\Intel\Downloads\Axon7\ADB>axon7tool -r recovery
Connecting to device...
S: failed to read command
S: Failed to receive hello
terminate called after throwing an instance of 'std::runtime_error'
what(): error: Unknown error
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
what i did.
Flashed Draken TWRP System Image B06
Flashed Draken TWRP Stcok Recovery B06
Flashed full update.zip B08
Now my phone is recognized as A2017G on the PC
But when i reboot the phone i get a message that the phone is unlocked and not trusted ?
why ?
Hi guys,
I'm just finalising restoring an A2017 (China) to stock for warranty exchange.
I have gone back to stock OS, locked bootloader but I still have the TWRP recovery.
I believe all I need to do is flash a stock recovery.img though TWRP and voila I should be finished, but I can't find a download link that definitely points me to what I should use.
Could someone point me in the right direction?
Thanks!
EDIT - Actually wait a minute can I just install full A2017 factory OTA update through MiFavor stock OS which I believe contains recovery, does that mean that everything goes back to stock (including recovery)?
https://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
EDIT2 - When I try to install the A2017 B13 update.zip through MiFavor it says update failed. Should I install it through TWRP?
EDIT3 - Refused to update the whole image (update.zip) through MiFavor within the ZTE OS. I flashed the default recovery.img through fastboot, then I used the MiFavor recovery (not in OS) to manually flash the full image.
Anyway, got it to stock!
Where did you got the recovery.img?
MagicSeeker said:
Where did you got the recovery.img?
Click to expand...
Click to collapse
In the link from my post above. Download the original stock ROM you want, unzip, one of the files is the recovery.img. FYI I had A2017 B11, installed B13 recovery.img and it worked fine.
I tried to flash recovery.img but it says: FAILED (remote: Partition flashing is not allowed)
What do I do? I'm on B13 stock with locked bootloader. I want to get rid of TWRP and back to stock recovery so I can get OTA updates again.
FuzzyDunlop9 said:
I tried to flash recovery.img but it says: FAILED (remote: Partition flashing is not allowed)
What do I do? I'm on B13 stock with locked bootloader. I want to get rid of TWRP and back to stock recovery so I can get OTA updates again.
Click to expand...
Click to collapse
The first step in flashing anything is to unlock the bootloader, flash TWRP recovery, root, custom ROM etc. The inverse is the same. You are trying to flash an image to the recovery partition with a locked bootloader, which isn't going to work. I'd suspect you need to unlock your bootloader again, flash the stock recovery from the B13 stock image, and re-lock the bootloader. I am fairly new to the Axon 7 but I would consider yourself lucky if your bootloader is in fact locked. Typically locking the bootloader with anything but stock recovery is messy...
jdgesmlls said:
The first step in flashing anything is to unlock the bootloader, flash TWRP recovery, root, custom ROM etc. The inverse is the same. You are trying to flash an image to the recovery partition with a locked bootloader, which isn't going to work. I'd suspect you need to unlock your bootloader again, flash the stock recovery from the B13 stock image, and re-lock the bootloader. I am fairly new to the Axon 7 but I would consider yourself lucky if your bootloader is in fact locked. Typically locking the bootloader with anything but stock recovery is messy...
Click to expand...
Click to collapse
You usually end up with a DFU brick, sometimes only with fastboot. Very messy
There are flashable recovery zips for the A2017G, maybe @tron1 can make you one?
Hi everybody
My Zenfone Selfie after a normal update (never modified) is in bootloop.
So I installed adb and fastboot and I flashed the twrp.
Then I tried in every way to flash a rom. I've tried both with official firmware and with various versions of cyanogenmod. Through fastboot and via adb sideload.
Even if seems to work, when I reboot I get the bootloop problem again.
As far as I can understand the problem it’s that I have the bootloader still locked. The official apk solution I guees it’s not applicable in my case. By fastboot oem unlock i get an error message (probably why i can not enable usb debug).
Do you know of other ways to unlock the bootloader or in general to flick my phone?
Thanks to everyone for the help
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
24imelqui said:
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
Click to expand...
Click to collapse
i tried evrything from flashing stock image , recovery partition , boot image . but nothing works. same i dont have unlocked bootloader. i am stuck at just rebooting phone. please help
I unintentionally skip the "format data" link and the all step, so the code unlock the bootloader but I cant flash the recovery it says "[BOOTLOADER] image not signed or damaged", the phone works but I cant flash anything, any ideas?
What device do you have, what (stock) firmware do you have on the device and what firmware are you trying to flash?
Hello is a stock Moto G5 Plus with 7.0 android and I am trying to flash the Vanche's Modified TWRP or the 3.1.2 version but I keep getting the same message "[BOOTLOADER] image not signed or damaged", is like if the BL relock itself.
I think that's a standard warning from the bootloader - TWRP is not signed software, which fastboot expects. However, as your bootloader is unlocked, it'll allow the flashing of TWRP, just with the warning message alerting you to the fact you're not flashing Motorola firmware via fastboot.
1)Do you see [OKAY] appear when you flash the TWRP?
2)After flashing TWRP, do you boot to recovery to fix TWRP? Easiest way is after flashing, on your device (if still in the device bootloader), use the volume keys to select 'Recovery' and press Power to confirm.
The instructions here suggest you need to boot to recovery after flashing to fix TWRP as the recovery, else the stock recovery may overwrite TWRP. https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659 or https://forum.xda-developers.com/g5-plus/how-to/how-to-how-to-supersu-moto-g5-plus-t3587684
ok thanks, I will try that, so skipping the "format data" thing has nothing to do with it?
I'm not sure - though you'd have to unlock your bootloader so your data would be wiped anyway as part of the unlock, and that you'll have to decrypt your data. Perhaps someone with more experience in flashing on G5 plus devices can comment.
Dear all,
My A2017G is still under warranty and I would like to send it back for battery problem.
I have unlocked my bootloader and I'm using LOS.
So I want to go back to full stock and remove bootloader message or relock bootloader.
I follow these steps:
I flash B03 Oreo full EDL.
I boot into stock recovery to format data and wipe all.
I boot the stock system and activate ADB.
Then I flash official TWRP (3.3.0.0). I tried to flash NFound's TWRP 3.2.1.8 but I never succeed to launch it.
I boot into TWRP.
I format data to remove encryption.
And then I follow the raystef66's guide to remove unlock message and activate fastboot.
However, when I want to launch bootloader "adb reboot bootloader", my phone is bricked, stuck in EDL mode and I have to wait full discharge of the battery to flash again B03 Oreo full EDL ...
What am I doing wrong?
Thank in advance for your help.
TTR6214 said:
Dear all,
My A2017G is still under warranty and I would like to send it back for battery problem.
I have unlocked my bootloader and I'm using LOS.
So I want to go back to full stock and remove bootloader message or relock bootloader.
I follow these steps:
I flash B03 Oreo full EDL.
I boot into stock recovery to format data and wipe all.
I boot the stock system and activate ADB.
Then I flash official TWRP (3.3.0.0). I tried to flash NFound's TWRP 3.2.1.8 but I never succeed to launch it.
I boot into TWRP.
I format data to remove encryption.
And then I follow the raystef66's guide to remove unlock message and activate fastboot.
However, when I want to launch bootloader "adb reboot bootloader", my phone is bricked, stuck in EDL mode and I have to wait full discharge of the battery to flash again B03 Oreo full EDL ...
What am I doing wrong?
Thank in advance for your help.
Click to expand...
Click to collapse
Why don't you boot a working system first? Formatting data won't do much, because unless you flash no-dm-verity or Magisk you'll get encryption the moment that you boot to system.
Also, you might be better off by installing stock Nougat instead, because most of the flashables were made for Marshmallow, but sometimes work on Nougat.
Finally I succeeded to relock the bootloader.
I have done this steps:
Flash B10 Nougat full EDL.
Boot into stock recovery, format data and boot normally the system.
Activate ADB and reboot into EDL mode.
Flash NFound's TWRP for Nougat (TWRP_3.2.1-7_axon7-Nougat-MM.img).
Boot into TWRP and format data.
Follow raystef66's guide to remove unlock message and activate fastboot.
At this time, I have access to TWRP and bootloader with fastboot access, but the system doesn't boot.
(Flash only stocksystem Nougat via TWRP), I don't know if it is mandatory.
Still in TWRP, remove dm-verity
At this moment, the stock system boot, I have TWRP recovery and bootloader with fastboot access and no warning screen.
To lock bootloader, boot into bootloader and run "fastboot oem lock"
Start the system, the phone says "erasing ..." but still doesn't boot the system.
Finally flash B10 Nougat full EDL, launch stock recovery and format data.
Now stock system with locked bootloader, ready for RMA