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 ?
my phone (US996) stuck in Logo LG. But before I was in the red triangle because i try to back to stock and I thought that i flash the firmware US996k keeping root would work well, but not this just lock OEM. But now the OEM has been blocked and I can no longer enter recovery. What can i do?
-The LGUP detect the phone but with unknow model. I put the dll in common and doesnt work. I dont know how to unbrick my phone
-I think the OEM is blocked, because I tried the "fastboot oem lock" command and it says it was already blocked, then try to unlock it "fastboot oem unlock" and says: FAILED (remote: unknown command). I think it's because the box was unchecked in Settings> General> Development, but the problem is that I can not boot to activate it.
Use LG Bridge. It has a button to recover from a bad flash. You more than likely will have a locked bootloader, and not be able to root again, but at least you will have a working phone.
Hi i try what u say i get bad news.
When I give error recovery.
It analyzes the phone but in the end it just tells me there are no update errors that can be recovered. And there it ends and does nothing
Have you tried using Uppercut to see if LG UP will recognize your phone?
Yes i try, and recognize but always like unknows model, i can´t continue. I extract dll from KDZ but not work.
Hi guys, I am wondering that anyway that I can fully return to stock? And if I return to stock, does it still show the warning of the unlocking bootloading when we start the phone?
Thank guy!
chakchak said:
Hi guys, I am wondering that anyway that I can fully return to stock? And if I return to stock, does it still show the warning of the unlocking bootloading when we start the phone?
Thank guy!
Click to expand...
Click to collapse
+1
Sent from my LG-H870 using Tapatalk
1. Use LG Bridge to "repair" the phone will get you back to stock Oreo and LG OTA updates. But will not relock your bootloader so you still see the code orange warning.
2. To relock your bootloader, read the FAQ contained in the unlocking guide. Essentially it's a fastboot command.
Both steps will wipe the phone so backup your data first.
How to in 5 steps Lock your bootloader ,that worked successfully on (H870)
the requirement for a successful lock: flash with LGUP and uppercut LG STOCK FIRMWARE
1. Enable Developer Mode
2. Enable OEM Unlocking
3. Boot into Fastboot Mode
3. Typefollowing command ---> fastboot oem lock
4. Wait for the Command Prompt to tell you the process has finished
5. And.... ---> fastboot reboot
Your bootloader is successful locked
Why is LG UP / uppercut a requirement? I did it using LG Bridge, worked. The requirement I think is just an LG stock firmware. Pretty obvious.
I also wrote "the requirement for a successful lock: .... " ! you can see colon ? I do not say must take LGUP ,It was a suggestion to note
Quote:The requirement I think is just an LG stock firmware.
Yes :good:
Moldeb said:
1. Use LG Bridge to "repair" the phone will get you back to stock Oreo and LG OTA updates. But will not relock your bootloader so you still see the code orange warning.
2. To relock your bootloader, read the FAQ contained in the unlocking guide. Essentially it's a fastboot command.
Both steps will wipe the phone so backup your data first.
Click to expand...
Click to collapse
Bunsenbrenner said:
How to in 5 steps Lock your bootloader ,that worked successfully on (H870)
the requirement for a successful lock: flash with LGUP and uppercut LG STOCK FIRMWARE
1. Enable Developer Mode
2. Enable OEM Unlocking
3. Boot into Fastboot Mode
3. Typefollowing command ---> fastboot oem lock
4. Wait for the Command Prompt to tell you the process has finished
5. And.... ---> fastboot reboot
Your bootloader is successful locked
Click to expand...
Click to collapse
Thank you all!!! :highfive:
Just got a swappa LG G6 with a locked bootblock, and zero unlock count, with factory ROM and factory bootloader. I need to root the device for some SD work I want to try, but I'd like to do whatever I can now to make the unroot clean in the future. I've got adb and fasboot working, and I'm fine with the rooting process. I'd prefer to avoid any sketchy mediafire links if possible for obvious reasons. Anything that could be done through fastboot or adb would be great.
What I imagine this would look like would be:
Preparations
Image system partition through fastboot (how?)
Image recovery partition through fastboot (how?)
Image bootloader partition through fastboot (how?)
Install TWRP
Unlock bootloader
Boot TWRP through fastboot
Flash TWRP
Restore Factory
Restore system partition through fastboot (how?)
Restore recovery partition through fastboot (how?)
Restore bootloader partition through fastboot (how?)
Clear bootblock unlock counter (how?)
Lock bootblock
Hopefully some of that made sense, but I'm not sure if any of it can be done.
You don't say which variant LG G6 you have. Not all can be bootloader unlocked and rooted, you know.
Ah, apparently you didn't know...
https://forum.xda-developers.com/lg-g6/how-to/req-how-to-unlock-bootloader-canadian-t3934053
Too bad. Sell your Canadian LG G6 back on Swappa and buy a V30 instead...
Thx... No worries on the rootless LG. I found a way to do what I needed root-free over the weekend.
Hello. I have a lg v20 H990N. I flashed TWRP by dirty santa method and wanted to go back to stock. As per the instructions on the link https://forum.xda-developers.com/v20...-h990-t3624296, I used method 1a for going back to stock. I ran the code as mentioned in the method while using my backed up "abootbackup.img" but I accidently ran the code twice.
Code:
dd if=abootbackup.img of=/dev/block/bootdevice/by-name/aboot
sync
sleep 30
sync
After booting to bootloader. this is what I see written on the boot loader screen.
___________________________________
Welcome to fastboot mode for bootloader unlock:
*Quick Guidnance
1) Read Device Id
fastboot oem device-id
2) Write unlock key
fastboot flash unlock unlock.bin
3) Check boiotloader is unlocked
Fastboot getvar unlocked
*How to exit fastboot mide
USe "Fastboot reboot' command if fastboot is available
________________________________________
This is the meassage that pops up in fastboot. I can use fastboot but can't use "fastboot flash recovery twrp-3.0.2-1-h990.img" as it exits with error that remote: device is locked. I can't flash kdz with lg Up as Lg up says " there is no haadset connected". TWRP recovery is also not boot neither is the nougat rom that was installed. More \over my device is shown as "Kedacom USB device " in device manager in fastboot mode. Not in Com ports.
It apperas that my bootloader has locked somehow after flashing abootbackup and I can't unlock it as h990N is not supported by LG to unlock bootloader. screenshot attached.
Please help!!!
Yeah flashing the stock bootloader relocks most v20 variants, (the dirty santa bootloader can't truely unlock them, it just ignores the lock)
I'm not sure what you expected? Your link is broken, but it sounds like you reflashed stock firmware and then the stock bootloader and expected to be in a different situation than a fresh unrooted device?
You should be able to boot normally to Android or boot I to download mode and reroot from scratch.
.