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!
Related
Hello Zenfone2 community,
I'm still a little bit noob in the android world, so there are a few things that are a bit abstract to me, so, let me start to explain why i'm here.
Earlier this month i rooted my device, unlock BL (unofficially) and installed Cm13, but i found a dead pixel, so i want to send i'm to warranty.
So, today i started the proccess backwards, first i reverted to stock, then i flashed blacksplashscreen, then i "uninstalled" twrp, and finally i flashed raw (with asus flash tool) then flashed recovery, droidboot and boot and adb sideload .97.
My question is, did i really relock bootloader ?? How do i test if my bootloader is unlocked ?
I already updated, (placed the zip into internal storage) and it showed that i had a new update ? Does this mean i have ota working ?
Cumps
Bootloader once unlocked remains unlocked unless u decide to update to MM Beta
Unofficial bootloader unlock = will get ota updates
Official bootloader unlock = ota not allowed(u can update manually)
To check if ur bootloader is locked or not, just flash a custom recovery & boot into it, if it boots ur bootloader is unlocked if not its locked simple
Plz move ur thread to Q&A Section or ask a Mod to do it for u
so i heard that when you flash raw file , your bootloader will locked. you can try that then take your phone to asus service center to claim warranty.
Send ior to repair, they will not notice that you unlocked
yakub234go said:
Bootloader once unlocked remains unlocked unless u decide to update to MM Beta
Unofficial bootloader unlock = will get ota updates
Official bootloader unlock = ota not allowed(u can update manually)
To check if ur bootloader is locked or not, just flash a custom recovery & boot into it, if it boots ur bootloader is unlocked if not its locked simple
Plz move ur thread to Q&A Section or ask a Mod to do it for u
Click to expand...
Click to collapse
If I used the official unlocker and update to MM beta will I get OTA updates?
Nope they will have ur serial no & u will be barred from getting ota
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.
Dear Seniors.
I am facing great hardship because my phone is stuck at boot logo.
No booting in recovery mode to flash another rom.
I did unlock bootloader of it by using tuliptool with success. After that i flashed custom rom in it. after reboot it is happening that.
Please suggest to recover it.
Did you flash twrp after unlocking? Did you make backup of stock ROM? Perhaps find a version of the factory firmware and flash that.
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
modorate said:
Dear I have no backup and i flashed TWRP recovery.......
It is to aware you that i did relock bootloader now my phone is working properly. but i am unable to enter recovery mode. !!!
Now my phone is running android 6.0.1 B02
But i am failed to root this rom uptill now due above mentioned problem.
Click to expand...
Click to collapse
I found software update notification but when i update an error accruing while update. (This update not compatible with this device"
In easy words......... my recovery.img has been corrupted. I have no idea to get rid of this situation.
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
bao_gg said:
I planned to unlock my Mini's bootloader this weekend. After reading this post, I decided to act later until the root cause has been figured out.
Click to expand...
Click to collapse
Several people myself included have been able to use tuliptool to successfully unlock and root the device.
mine is hard bricked too. but I think it is worse than the case listed on the op.
if you want to hard bricked these are the steps:
follow the procedure to install the Spanish ROM 6.1, than another android m b12, than finally the android seven......use tulip tool and install twpr fine, root ect. amazing ROM.......buuuuut......I lost my IMEI somewhere in this process, and the original FTM which had a small menu changes to another static one, without the menu.
I needed this menu to open the com port to fix the IMEI. than I had the brilliant idea to re-flash android M via twrp (without modifying the zip file to remove the recovery, something I knew so well from the older axon mini).
results:
-lost twpr because the stock ROM wrote over it,
-cannot boot the OS because I flashed android m but the phone had the aboot 7.
-i now have a brick
I need a genious to sujest something to bring it back to life........sh....t...sh...t.....sh...t
any chances I could inject aboot7 via ADB through my dead recovery which somehow the phone recognises? ADB shell still seems to be working
thanks
Hey all, so I had the DotOS vanilla rom installed for a while now but I think something broke when I flashed it so it was very glitchy. Yesterday I decided I just wanted to go back to stock but kinda screwed the phone over and bricked it while using MSMDownloadTool. I'm so confused as to which one I should use to reset my phone. People are saying contradicting things like you need to use the correct version of MSMDownloadTool and also it does matter if you have a T-Mobile branded phone.... yatta yatta yatta...
I'm just extremely confused about how the hell I'm supposed to standardize the process of flashing roms and such onto this phone without running into walls in the dark and hoping it randomly will work. Is this just expected? Also if someone could please give the steps needed to get my phone back to stock and working that would be very appreciated.
Groovy vibes ~ u41c
You might not have to use msm tool if your bootloader is still unlocked. Msm tool should be last resort and is only needed if you can't enter your rom and bootloader is locked. So let me know if it's unlocked yet. You should still be able to get into your bootloader holding volume up while booting.
Brettroth said:
You might not have to use msm tool if your bootloader is still unlocked. Msm tool should be last resort and is only needed if you can't enter your rom and bootloader is locked. So let me know if it's unlocked yet. You should still be able to get into your bootloader holding volume up while booting.
Click to expand...
Click to collapse
Well I fixed it by using a different computer entirely to run MSMDownloadTool. I was able to get into fastboot mode but every time I tried manually flashing the partition images it did nothing.
So now I'm on OxygenOS 11.0.1.2 and am curious to know what I would need to do to debrand my phone and root it... the right way.
Debrand for what? The way I would root is install twrp then flash magisk from twrp. You can fastboot boot this twrp then make it permanent in the advanced menu.