Related
So I upgraded to Nougat on my P9 Lite, unlocked boot loader, used twrp, flashed roms and everything went smooth. Saw a more up-to-date version with no bugs, so I had to downgrade to MM first.
I followed a guide, but I messed up somewhere and ended up having my bootloader locked, and I can't access the OS to enable developer options and oem unlock from settings. The reason why I can't access the OS is that I am stuck in the setup. I am stuck at the part where I have to sign in to my google account. It doesn't show a keyboard, only a microphone, and I can't use that for my password (it won't let me).
Any ideas?
TL;DR messed up during downgrading from Nougat to MM, now TWLR is gone, bootloader is locked and my main issue is that when I get to the google account sign in part during OS setup, there is no keyboard (I can only use dictation) so I can't sign in... So I'm stuck
Also, can I unlock bootloader without access to OS, without being able to navigate to settings, enable developer options and then oem unlock?
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Jagiel88 said:
1. Stuck in OS setup? Signing in to Google? Hey, it's not obligatory, can't you just skip it?
2. Flashing ROMS locked your bootloader, it's normal, but I'm sure it didn't change the "oem unlock" setting you had surely enabled before. Go to fastboot mode and check Bootloader and FRP status on the bottom of the screen. If FRP is unlocked, you will be able to unlock bootloader again.
3. If you have your TWRP gone (flashed by stock ROM), flash the recovery partition manually - fastboot flash recovery TWRP.img (download from Meticulus Project site).
Click to expand...
Click to collapse
It is obligatory, I couldn't skip it. I tried to use other methods of signing in, but then it asked me to reset password at the end.
Both Phone and FRP are locked
I think I have missed this, but I can't do it via fastboot because I keep getting "Command not allowed" whenever I try to unlock bootloader or do anything via fast boot.
Also, thank you so much for your time and input. It is much appreciated.
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Jagiel88 said:
That's weird, I flashed my phone several times with different ROMS (not Nougat) and this setting (oem unlock / FRP unlocked) stayed enabled. Don't know where it sits then and how to change it without getting inside OS. But - what about TWRP? Oh right, you won't be able to flash it without unlocked bootloader... Oh, crap. I would try SRK Tool for Huawei to play with bootloader, it uses fastboot so shouldn't help, but maybe, just maybe? Maybe try flashing whole ROMs through dload folder on SD? Stock 120, 161, Nougat, I would try these. I hope there is some way to unlock FRP, probably it's possible in DC-unlocker (it's a paid software).
Click to expand...
Click to collapse
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
No problem, unfortunately I haven't tried Nougat yet, so search for help on down/upgrade Nougat beta <-> Marshmallow threads .
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
Click to expand...
Click to collapse
There is 1 thing to unlock in settings . U have OEM lock
youssefSamir said:
Yes, it's very weird. I haven't done the process a lot. But I've flashed a couple of phones I had before, went smooth. Nothing major like this happened before.
I will consider the SRK Tool and I did not know about the DC-Unlocker tool, thank you for telling me about it.
Flashing whole roms through dload folder only works with Nougat for some reason, and I keep getting stuck in the signing in problem because of no keyboard, someone told me that's incomplete software, I'm hoping that's the case, any ideas where can I get it from?
Again thank you Jagiel88 for your time and advice xD
Click to expand...
Click to collapse
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
ScaleneVirus288 said:
There is 1 thing to unlock in settings . U have OEM lock
Click to expand...
Click to collapse
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
islandman75 said:
Hi, have you found how to solve this? I can't access recovery because I messed up, cant flash recovery because bootloader locked. Cant unlock bootloader because says command not allowed... I did 3 times so the code is working... Any clue?
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
Can't access to any OS. I definetly know i had OEM unlocked, then after unlocking via fastboot, I wasn't able anymore to access the system.
Click to expand...
Click to collapse
Unlock bootloader, after that you able to flash rom.
You use this command?
fastboot oem unlock YOUR_OEM_CODE
If you tip:
fastboot devices
What's you see?
My wife got a P9 Lite L31. I wanted to upgrade to Nougat. I finally succeeded, but after that I messed things up. I tried to do a clean intall with a update that wasn't ment for this.
In the beginning I could still enter the Nougat recovery, but I wasn't able to reinstall the update.zip. The device wouldn't boot, etc.
I tried to do many different things, but at this moment I cant enter TWRP anymore, I can enter fastboot and is says:
PHONE Unlocked
FRP Unlocked
But flashing an other TWRP recovery doesn's work because I get an error:
(Remote: Command not allowed).
Also relocking the bootloader doesn't work because is gives the same error as the one above.
I can't flash a OEM file through fastboot because it gives the same error as the one above.
I can't use HiSuite because it says it does not support the phone.
I don't know what else I can do right now.
I tried the 3 button method, but I can't get in the official recovery. The phone reboots to some kind of recovery where it wants to update the recovery through wifi, but it ends up with an error that it can't fails to get the package info. But there is no option to do a factory reset (I've put the MM update.app file in sdcard/dload folder).
Any ideas what else I can do to recover the phone?
Unlock the bootloader again.
Johnny TDN said:
Unlock the bootloader again.
Click to expand...
Click to collapse
Ok, did not expect to do that again, but I did it.
What's the next step? flash a nougat recovery? flash a oem recovery?
Fastboot now says:
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Looks like fastboot isn't recognized by the computer anymore after the re-unlocking of the bootloader.
Windows device management also doesn't see the device. Not even as an unknown device.... Looks like the bootloader unlock completely bricked the device.
Well.
You must change your motherboard.
Johnny TDN said:
Well.
You must change your motherboard.
Click to expand...
Click to collapse
As per usual, your comment was of no help at all.
Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?
igreja94 said:
As per usual, your comment was of no help at all.
Click to expand...
Click to collapse
-_-
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
Try to discharge your battery by leaving it on Fastboot mode.
Charget the batery and let it boot itself.
If it boots in the software, it will be very easy to fix. If no, then changing the motherboard is required
Potato997 said:
Take a look to this thread, it seems similar to your problem https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872
What are you able to do with the phone?
Click to expand...
Click to collapse
To be honest, nothing.
It can do two things, you can let it boot and then it says it's booting, and that's it (after the warning that the bootloader is unlocked), or I can boot into fastboot but the phone is not detected by the computer. Device manager doesn't see the device at all not even as an unknown device. Nothing. So no way to flash anything using fastboot. KI also can't get into the fastboot&repair.
So yeah, I decided to send it in for repair.
Hi all,
I've wanted to go back to Stock OS but when i type "fastboot oem lock" it says "FAILED <remote: Flashing Lock is not allowed."
Everything boots normally to OS 4.5.2. In DEV options the Unlock Bootloader is greyed out and says bootloader is already unlocked.
What can i do?
Cheers
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
reayard said:
These instructions did work for me with the OnePlus 3/3T. They should also work for the OnePlus5, just make sure that you download the OnePlus5 version of the software and recovery.
https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Use this link for the stock recovery: https://forum.xda-developers.com/showpost.php?p=72748921&postcount=5
Click to expand...
Click to collapse
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
r1card0amr said:
Hi i tried but does the same when i get to fastboot oem lock (it says Flashing Lock is not allowed).
Click to expand...
Click to collapse
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
mohan_kr said:
Thanks I asked the same question earlier glad u tried it..I want to make sure we can relock it before I get the phone. Did u enable oem unlocking in the developer options before doing a fastboot oem lock? Also, make sure you are on stock everything including recovery..
Click to expand...
Click to collapse
Hello. I first thing I do always is to install drivers. I start by connecting the phone to the laptop in charge mode, then in transfer files mode, MTP or camera. In this way he will recognise all the drivers your laptop needs.
Also I enter in fastboot mode and recovery so the laptop can recognise the drivers and always reboot laptop and phone just to double check.
What I did was: go to Developer Options and enabled Unlock Bootloader and USB Debugging.
Then I accepted the laptop request on my phone and all drives were OK.
I run CMD and typed fastboot devices to see if it recognises my phone and it displayed a serial number. So I proceed next to type fastboot oem unlock and the process went OK and on my phone it asked Yes or No to unlock and I choose yes.
Then I flash a twrp image by typing on CMD: fastboot flash recovery recovery.img (my twrp I'm had other name so I rename it. You need to enable "Show file extensions" in Windows so you can see what the extension is).
I then type fastboot boot recovery.img and the phone entered in Recovery Mode in this case TWRP.
My phone was always connected to the laptop and he open the internal storage window so I drag the supersu inside.
Then on TWRP I wiped dalvik and cache and I went to Install and installed the SupeSU on my internal memory root.
The phone then rebooted and ready to go.
But then I went to developer options and the Unlock bootloader was greyed out. I unroot my phone and flashed a stock recovery for OP5 and the stock image 4.5.2 and when I type fastboot oem lock it always says it can't be flashed.
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Just installed supersu to try an app. I never install 3rd party roms.
r1card0amr said:
I need to stock it since I'm giving to a family member and they don't understand much about phones and If there's a problem the warranty doesn't cover.
Click to expand...
Click to collapse
the warranty is not voided with unlocked bootloader..
https://oneplus.net/hk/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
r1card0amr said:
I found now that if i take pictures or screenshots the Album Folder is empty. I think my phone is bricked. Hence i can't lock the bootloader.
Click to expand...
Click to collapse
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Hogyoku said:
if your phones boots its not bricked... My guess is that you data is corrupted, i would wipe everything including userdata en reflashing the stock with recovery.
Click to expand...
Click to collapse
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
I rooted my device with Magisk, and now I want to restore it to factory state.
I flashed stock recovery and OOS several times, wiped everything but fastboot oem lock failed all times (FAILED (remote: Flashing Lock is not allowed)).
Can you help me?
What should I do to relock bootloader?
here is your solution
r1card0amr said:
Hi right before your comment i managed lol.
I re-flash the stock recovery and in recovery i reset and wipe everything. then i install the OS4.5.3 by ADB Sideload and it's working now.
Just wanted to get rid of the inital warning that my bootloader is unlocked. I want to lock again.
Click to expand...
Click to collapse
here in this video u can see in detail how to lock bootloader. hope this help you
https://www.youtube.com/watch?v=CQYCSdDUdAU
HOW TO RELOCK..
Install TWRP and Magisk if you don't have them yet.
Magisk should allow you to slide "OEM unlocking" to "enabled"
Reboot to fastboot
Flash stock recovery via fastboot.
Run locking via fastboot flashing lock
Allow it to reboot and upon start up it will say device corrupted (THIS IS NORMAL)
Boot to recovery via the warning start screen.
Once in recovery, sideload latest FW.
Profit.
I usually do it this way (successfully):
Wipe everything but OTG in TWRP
Format data
Reboot to TWRP
Flash the full stock OOS zip
Reboot to fastboot
Flash stock recovery
Lock bootloader with the fastboot lock command
Has anyone made any progress with this? I too am having the issue as described and have tried the solution by Ricyksydhu, along with solutions from various other places around the net.
Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.
Hi Rakesh,
Is you issue get resolved?
I have also got warnings of internal storage full in my MI-A1 and after that my phone got switched off. I also tried to switched on and it got stuck at android one logo.
Please help me out if your issue get resolved?
Try booting in TWRP and using the file manager to delete some user data to make space.
barrack1 said:
Try booting in TWRP and using the file manager to delete some user data to make space.
Click to expand...
Click to collapse
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
saurabhsh23 said:
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
Click to expand...
Click to collapse
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
manpildo said:
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
Click to expand...
Click to collapse
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
saurabhsh23 said:
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
Click to expand...
Click to collapse
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
manpildo said:
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
Click to expand...
Click to collapse
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
Click to expand...
Click to collapse
Yes, unlocking bootloader wipes data.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
Click to expand...
Click to collapse
No, if you wipe your phone through recovery you won't need to flash anything. It just deletes all your stuff without touching the system.
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Any update here please?
vaibhav08 said:
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Click to expand...
Click to collapse
Guys pls help me i got stuck on boot logo i want to flash stock rom pls help me
I'm in the same boat. Unable to access developer options as phone won't boot and its stuck at the android one logo.
Fastboot oem unlock gives error Flashing Unlock is not allowed.
Is there anyway around this?
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Face_11 said:
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Click to expand...
Click to collapse
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
jack_21 said:
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
Click to expand...
Click to collapse
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Face_11 said:
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Click to expand...
Click to collapse
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
jack_21 said:
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
Click to expand...
Click to collapse
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Face_11 said:
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Click to expand...
Click to collapse
If you see a triangle, you are in recovery mode
You need to press a button combination to see options, Search on Google for that
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html