Had a quick query on the relocking of the bootloader. So, I am planning to flash back the full stock ROM and relock the bootloader. Will this ensure that I get any future updates (OTAs) as on a new phone?
Yes, as long as you flash the correct firmware for your software channel.
That depends....
If you have flashed any Oreo ROMs, it is highly likely you will boot stock ROM to no signal. This forces you to unlock again in order to get signal.
I been trying to lock and back to stock for a while. I'm hoping official Oreo will solve the efs problems.
Related
Please forgive my stupidity - I'm a longtime Samsung Android user and this Fastboot/adb process is all new to me. Last time I used that was with Original TMOBILE Mototola G1!!
So, this is what I have: I had my device ( ZE551KL ) on LP, Bootloader unlocked with TWRP and rooted. 'Cause I first unlocked the Bootloader with the official ASUS app.
Then I installed the OTA ASUS MM version, but according to everyone, once one install the OTA upgrade, it relocks the Bootloader, correct? How can I test this??
This afternoon I put device in Fastboot mode and did a "fastboot boot twrp-3.0.4.img" and it worked!!!
It boot into TWRP and am busy making a backup now.
My Question: if my bootloader is still locked, how could I boot TWRP?
Can I try and 'Fastboot flash recovery twrp....' and will this work or am I going to brick the device?
Ideas? ( well, rather experienced advice, please)- as I would hate to brick my device.
The TWRP backup I am currently making - is that any good/helpful to anyone that can help us getting this device properly unlocked and rooted?
Thanks
I did try the official ASUS unlock tool on MM....
I forgot to mention that.
I did try the official unlock tool on MM, but the app just failed.
I opened an issue with ASUS regarding this, as their website specify version 1.16 'and later'
Does this mean I am good to flash TWRP??
Am I good to flash TWRP if I get this message??
You are good. I had unlocked the bootloader long time ago, and I have installed MM, they don't relock it back. It would be strange to do that, since once unlocked you lost the warranty... it would be like they will gave you back the warranty!
Dude, your bootloader is unlocked. You're good to go. Fastboot flash that recovery and go to town.
From your description it is clear that you have successfully unlocked your device. Once it is unlocked, you wont be able to lock it back. So there is no way to revert the process and it affects warranty. Now anytime you can flash TWRP with fastboot and install custom ROM. If you want to install Stock rom install stock recovery and use ADB sideload to install Stock ROM. if you have any other doubts visit my youtube channel [TheMobileShots] where i have provided the tutorial to do these things. Have a great day!
Is it possible to restore to stock and re lock the boot loader after installing Soak Test Nougat? I tried everything with fastboot. I was successful in reverting back to stock but I can`t seem the re-lock the boot loader. Any help appriciated!
No
You need to wait for stock nougat rom, for flash
Because to relock your bootloader you need to flash all the files from the rom, and if you updated to soak nougat, you wont be able to flash marshmallow gpt.bin and motoboot.bin (there are 2 files that you cant flash, i am not 100% sure if these are them) so you need to wait for the nougat rom to flash and then you will be able to relock the bootloader
Saludos
ivan290 said:
No
You need to wait for stock nougat rom, for flash
Because to relock your bootloader you need to flash all the files from the rom, and if you updated to soak nougat, you wont be able to flash marshmallow gpt.bin and motoboot.bin (there are 2 files that you cant flash, i am not 100% sure if these are them) so you need to wait for the nougat rom to flash and then you will be able to relock the bootloader
Saludos
Click to expand...
Click to collapse
That's why I don't update to N soak test(or n modem) . I'm waiting for this stock N rom too, then it's more safe in case of hardware problems like my zuk has encountered....
OK just to be clear, there is absolute no way to re lock the boot loader now? I needed to restore to stock now because I am replacing my G4 Plus at Amazon and I don`t want to send the phone with unlocked boot loader. But I don`t think they will notice.
Hi!
I have got two G4, one with Marshmallow and one with Nougat.
The one on N (offical N, updated by OTA and did a full wipe) has lots of problems with BT, and I want to downgrade it to MM.
I have read lots of posts, here and everywhere else, and saw some vids about the procedure. But I still have some doubts about the proccess:
* Most of the procedures I have read relate to downgrade from N leak to MM in order to upgrade to official N. I have seen someone ask if the same procedure could be used to downgrade from offical N, but no answer. Can I use the same procedure to downgrade from official N?
* Some say you have to unlock the bootloader, others make no mention of it. Some say you should not write gpt.bin and bootloader from the MM ROM as N udated them and it is not possible to downgrade them. Do I have to unlock the bootloader before using fastboot to write the MM ROM? Should I avoid writing gpt.bin and bootloader?
I don't mind voiding the phone warranty, and I don't mind not being able to OTA update future versions.
Thank you very much.
Regards.
If you have bootloader locked, you can't overwritte nothing including system, boot, bootloader and gpt. I tried with my Moto G4 and i can't go back from official N to official MM through fastboot
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
CalvinH said:
Thank you.
So I understand I have to unlock the bootloader.
Now I just need to make sure if I should overwrite gpt and bootloader with MM versions (coming from stock N) or not.
Regards.
Click to expand...
Click to collapse
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
lerg96 said:
A couple of weeks ago, I read something about it. I think you should not overwrite the bootloader and recovery but I do not remember very well.
But if you have your bootloader unlocked just flash (or boot into) a custom recovery and make a backup of everything and after play along a while
Click to expand...
Click to collapse
Thank you.
Based on the overwhelming popularity of this thread (thanks lerg96!) I have decided to come back and tell how it went.
I had a Moto G4 with official Nougat. I wanted to downgrade it to MM.
The first problem is that I didn't find the .63 ROM (last MM one) for my device (XT1622). I found the 23.5 version (previous one), and the .63 version for the XT1624. Since 22 and 24 differ on LTE bands and so, I decided to use the older but right ROM.
First attempt: downgrade without unlocking bootloader... NO WAY.
Second attempt: unlock bootloader + downgrade without overwriting bootloader and gpt.bin. :good::good:
I got the boot warning message, but everything went ok and my BT problems are gone. I got the .63 OTA notification, but didn't installed it as I read scary histories about doing it.
Regards!
now that your bootloader is unlocked, install TWRP and make a backup of your system. I used TWRP to restore my OS. I went from Nougat back to MM, I am sure you can go the other way around too.
also, the fastboot method for reload the os seems to work well on phones with unlocked bootloaders.
Hello all.
Im a little bit confused about the bootloaders and their marriage with their standard ROMS.
I am in MM B13 in a 2017 unlocked using bkores toolkit and would like to check Nougat ROMS.
What happens if, from this MM unlocked state I flash an official Nougat for 2017? Is safe? Could I eventually flash a TWR to return to my "original and safe" state? Could I flash back an "official" MM B13 for example?
I am guessing that maintaining the phone in the unclocked area is safer than recover the lock. Is this true?
There is a "Universal bootloader" for Nougat ROMS. How "Universal" is this bootloader? Does this bootloader runs in MM?.
If I apply a SD "complete" update (being MM B13 or Nougat), do I relock the phone's bootloader?
If I upgrade fro MM to N, do I lost the possibility of flashing a custom recovery? (TWRP). This is a non go for me, as you cannot go back...
Hope you can answer these questions
Regards
jrotaetxe said:
Hello all.
Im a little bit confused about the bootloaders and their marriage with their standard ROMS.
I am in MM B13 in a 2017 unlocked using bkores toolkit and would like to check Nougat ROMS.
What happens if, from this MM unlocked state I flash an official Nougat for 2017? Is safe? Could I eventually flash a TWR to return to my "original and safe" state? Could I flash back an "official" MM B13 for example?
I am guessing that maintaining the phone in the unclocked area is safer than recover the lock. Is this true?
There is a "Universal bootloader" for Nougat ROMS. How "Universal" is this bootloader? Does this bootloader runs in MM?.
If I apply a SD "complete" update (being MM B13 or Nougat), do I relock the phone's bootloader?
If I upgrade fro MM to N, do I lost the possibility of flashing a custom recovery? (TWRP). This is a non go for me, as you cannot go back...
Hope you can answer these questions
Regards
Click to expand...
Click to collapse
Forget about the bootloader thing for now - it should be universal for MM and N. Not gonna relock itself.
-If you want to go back from a custom ROM (you'd have the A2017X_Universal_Bootloader, the ROM and the modem that goes with your device, plus a version of TWRP installed) what you would do, at least in A2017Gs and Us, is to flash a stock recovery zip to get the stock recovery. After that you reboot to the recovery, and you'll get to MiFavor's recovery. from there you would flash an official zip and every partition would be overwritten with what's on the zip. I suspect that ZTE packs every update with everything in it so that you can roll back, say, from Nougat to Marshmallow officialy, without messing everything up.
OR you can use MiFlash to reflash everything with a computer. Just download the full EDL file from 4PDA and flash, you'll get full stock (but still unlocked BL anyways)
So yeah, you CAN get back to full stock anytime.
-Don't just try to relock the bootloader. AFAIK if you relock it and you have root or TWRP or somesuch you can brick your device. I'd advise against trying to do that, but if you must, look at a guide or two at least.
-Yeah, pretty universal. I wonder why you'd want a custom MM ROM though. if you want to go back to stock MM it will get replaced by another one anyways.
-Already addressed, no
-I don't know the exact case with A2017 phones, but you said you cannot go back? You can. If you're on official N and want to roll back all you have to do is put an official MM zip on your SD or internal storage and go to Updates.
That being said, you still can use axon7tool on Nougat if it supports A2017 phones, which it should. You use EDL mode to flash the recovery. it is what I always do on my A2017G.
Choose an username... said:
Forget about the bootloader thing for now - it should be universal for MM and N. Not gonna relock itself.
....
Click to expand...
Click to collapse
So...
i) Bootloader unlocked is safer than locked and problems can arise if i try to relock.
ii) I can flash from SD every official thing published by ZTE if I flash previously ZTE recovery. (bootloader still unlocked). From that startpoint, I could reflash TWRP using fastboot or EDL. Once in TWRP, every ROM is flashable if partition compatible...
iii) I can stay with my unlocked bootloader with every MM or N. Important things are the modem and other stuff. N is not much different from MM and I like Xposed....
Big, big THANK YOU!!!!
jrotaetxe said:
So...
i) Bootloader unlocked is safer than locked and problems can arise if i try to relock.
ii) I can flash from SD every official thing published by ZTE if I flash previously ZTE recovery. (bootloader still unlocked). From that startpoint, I could reflash TWRP using fastboot or EDL. Once in TWRP, every ROM is flashable if partition compatible...
iii) I can stay with my unlocked bootloader with every MM or N. Important things are the modem and other stuff. N is not much different from MM and I like Xposed....
Big, big THANK YOU!!!!
Click to expand...
Click to collapse
i)Yeah
ii)Every LOS-based ROM is flashable if you flash the Universal Bootloader and the corresponding modem for your device, except stock roms and maybe stock-based roms (not sure)
iii)Yeah
Thank you again, my annonimous friend.
Hello everyone, I stumbled upon this problem but I can't find much useful information to solve this: I rooted my Moto G4 Plus and after some time I decided to unroot and I flashed stock rom in it with unlocked bootloader. After that I'm stuck at Marshmallow and can't receive Nougat update. Everything was fine before I rooted and flashed stock rom in it with unlocked bootloader but now it doesn't seem to update. My model number is XT1642. How can I solve this problem and receive OTA updates? I also want to relock my bootloader. So to sum it all up: I want my device to be just as after I bought so to speak.
Depending on what Marshmallow ROM you flashed, it might have not been the correct version for your software channel, and thus your device won't have received an OTA (since the server is expecting a different build to the one you have).
If you wish to update to Nougat and re-lock your bootloader, you may wish to flash the June 2017 fastboot ROM, which should also re-lock your bootloader if you use the commands mentioned. Be aware that re-locking your device may wipe your data, back up and keep your data off your device until you're done.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the June fastboot ROM. If at a later date you choose to unlock your bootloader again, do not downgrade your device to an older stock ROM from the June update.